linux-kernel - linux-next boot failure on 64-bit Sony Vaio (maybe x86 related)

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

Message-ID: <20080702141556.GA25441@beyonder.ift.unesp.br>
Date:	Wed, 2 Jul 2008 11:15:56 -0300
From:	"Carlos R. Mafra" <crmafra2@...il.com>
To:	sfr@...b.auug.org.au
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu
Subject: linux-next boot failure on 64-bit Sony Vaio (maybe x86 related)

Hi everybody,

The linux-next tree for 1st of July fails to boot on my Vaio laptop, it
stops booting with the keyboard leds blinking.

I can see that there are a few backtraces printed to the screen 
before the last one, but I could only take a picture of the final
state:
http://www.ift.unesp.br/users/crmafra/failed_boot.jpg

This last warning is on arch/x86/kernel/smp.c:118 and the kernel
reports it is tainted, but I am sure it is a vanilla linux-next with
no proprietary stuff.

I could not bisect this problem yet because the first linux-next
which I tried to use was next-20080618 which had a similar boot
failure, that time at kernel/smp.c:215
http://www.ift.unesp.br/users/crmafra/failed_boot0.jpg

(I did not report it back then because I am writing my thesis and
the deadline is close...)

I used the same .config as the working 2.6.26-rc8 and I did
nothing fancy with the new config options of -next
http://www.ift.unesp.br/users/crmafra/config-failed.txt

The dmesg of 2.6.26-rc8 is here:
http://www.ift.unesp.br/users/crmafra/dmesg-good.txt

I tried to boot with 'nosmp' but it also failed.

Regards,
Carlos
--
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/