linux-kernel - Re: 3.1-rc6 boot problem reason searching

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 15 Sep 2011 08:21:37 -0700
From:	Andrew Lutomirski <luto@....edu>
To:	werner <w.landgraf@...ru>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 3.1-rc6 boot problem reason searching

On Thu, Sep 15, 2011 at 7:41 AM, Andrew Lutomirski <luto@....edu> wrote:
> 2011/9/14 werner <w.landgraf@...ru>:
>> The config is below.  That's the M486 config which don't boor.  The M586
>> config which boots has the diff given in my last mail, and which for make
>> the comparison more easy I give below again.   As said, all 3.0-rcX and up
>> to 3.0.4 boot with 486 too, the problem started with 3.1-rc1 . Perhaps the
>>  messages before the computer sticked (using the M486 config below) which I
>> copied manually from the screen, posted in the treat 3.1-rc5 boot problem  ,
>> may be helpful to find out what exactly causes the sticking.
>> wl
>
> Gack.  I obviously did a terrible job grepping for this stuff when I
> wrote the original patch.  The problem is probably in static_cpu_has.
> I'll send a patch in a little bit.

-ETOOEARLYINTHEMORNING.  static_cpu_has looks correct.

werner, your kernel survives:

for i in `find -name \*.o`; do objdump -j .altinstructions -r "$i"
2>/dev/null |grep R_ |grep -v R_386_PC32\ ; done

Can you try the same command in your build directory?

In the mean time, I'll see if I can reproduce the crash in qemu by
playing with -cpu.

--Andy
--
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/