linux-kernel - Re: Fwd: same problem with 2.6.24-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20071107170640.ca861b15.randy.dunlap@oracle.com>
Date:	Wed, 7 Nov 2007 17:06:40 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	"werner" <werner@...aya.yi.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Fwd: same problem with 2.6.24-rc2

On Wed, 07 Nov 2007 21:32:43 -0300 (GFT) werner wrote:

> On 7/Nov/2007 20:10 werner wrote ..
> > With 2.6.23-rc2 is the same problem:  it crashed at the beginning:  EIP 060 c03fdea4
> > EFLAGS 00010212 EIP is at xor_sse_2+0x34/0x200
> > Again during the compilation was reclaimed that <source-dir>/arch/x86/Makefile.o
> > cannot be found and were certain dependencies on it not made, such a file isn't
> > present in the source code (present are, f.ex. Makefile_32 , Makefile_64 ), nor
> > was generated automaticaly during compilation, I think this is incorrect and the
> > reason for the problems

Hi,

Please provide the complete build log (with V=1 if possible) for the
missing Makefile.o problem.

E.g.:

make V=1 all >build.log 2>&1

Make sure that build.log contains the error message and then send
the complete build.log file to us at linux-kernel@...r.kernel.org .


> > wl
> > werner@...aya.yi.org
> > =============================================================================
> > On 7/Nov/2007 16:14 Andrew Morton wrote ..
> > > > On Wed, 07 Nov 2007 15:55:12 -0300 (GFT) "werner" <werner@...aya.yi.org> wrote:
> > > > I really don't know what's happening.  I don't understand nothing about the
> > kernel
> > > error reporting system.   Because of this, always when there is a problem, I
> > report
> > > it via e-mail to  linux-kernel@...r.kernel.org .  I don't know what people there
> > > do with my messages.     
> > > 
> > > 
> > > It went like this:
> > > 
> > > 1: you sent an email to linux-kernel
> > > 
> > > 2: I sent a reply to you and linux-kernel
> > > 
> > > 3: you sent a reply to me, but NOT linux-kernel!
> > > 
> > > In other words, you did "reply", not "reply to all", thus you removed three
> > > thousand people from the discussion.  One of those people is the person who
> > > created the bug which you're hitting, and that person no longer knows
> > > what's happening.
> > > 
> > > 
> > > So please go back and resend all those emails, and retain ALL Cc:'s.  Don't
> > > just send them only to me.  Keep all indivisuals and all mailing lists on
> > > the email Cc: list.



---
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/