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: <20080902163532.436f8fbd@doriath.conectiva>
Date:	Tue, 2 Sep 2008 16:35:32 -0300
From:	"Luiz Fernando N. Capitulino" <lcapitulino@...driva.com.br>
To:	tglx@...utronix.de
Cc:	herton@...driva.com.br, linux-kernel@...r.kernel.org
Subject: 2.6.27-rc5 doesn't boot on a Pavilion laptop


 Hi Thomas,

 I have a HP Pavilion dv6000 laptop here which doesn't boot with
latest Linus tree (2.6.27-rc5).

 The last lines I see on the screen are:

"""
hpet0: at MMIO 0xfed00000, IRQs 2, 8, 31
hpet0: 3 32-bit timers, 25 000000 Hz
"""

 Sometimes it also writes one more line:

"""
ACPI: rtc can wake from S4
"""

 By investigating this I have found that it:

 o boots with 2.6.26.3
 o doesn't boot with 2.6.27-rc1
 o 2.6.27-rc1 and current kernel boots if I pass hpet=disable at the
   command-line

 Then I bisected and git says that the culprit is:

"""
commit aa276e1cafb3ce9d01d1e837bcd67e92616013ac
Author: Thomas Gleixner <tglx@...utronix.de>
Date:   Mon Jun 9 19:15:00 2008 +0200

    x86, clockevents: add C1E aware idle function
    
    C1E on AMD machines is like C3 but without control from the OS. Up to
    now we disabled the local apic timer for those machines as it stops
    when the CPU goes into C1E. This excludes those machines from high
    resolution timers / dynamic ticks, which hurts especially X2 based
    laptops

[...]
"""

 Now, what puzzles me though is that if you do:

$ git checkout -b bla aa276e1cafb3ce9d01d1e837bcd67e92616013ac

 and edit the Makefile you will see that it is a 2.6.26-rc4
kernel! When I saw this I thought 'wth? git bisect went backwards?'
(I specified 2.6.26 as good and 2.6.27-rc1 as bad).

 I don't know if this is known (it should be) but it seems that you
have changed the Makefile during the merge of that commit... But
I'm quite sure that this commit has been introduced in 2.6.27-rc1.

 I would try to revert it from current Linus' tree to see if it
really fix the problem but turns out that it will take some time
to work on the conflicts.

 I'm attaching the 2.6.26.3 (Mandriva kernel) and 2.6.27-rc5 (with
hpet=disable) dmesg files.

 Also, this _seems_ to be the same as reported in:

http://bugzilla.kernel.org/show_bug.cgi?id=11191

 But I'm still compiling the kernel with the appropriate config
options to confirm this.

 Please, let me know if there's anything else I can do to
help you debug this.

 Thanks.

-- 
Luiz Fernando N. Capitulino

View attachment "dmesg-2.6.26.3mdv.txt" of type "text/plain" (22417 bytes)

View attachment "dmesg-2.6.27-rc5.txt" of type "text/plain" (22141 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ