linux-kernel - Re: ACPI Regression on Dell E1501

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, 21 Jun 2007 16:05:59 -0600
From:	Tim Gardner <tim.gardner@...onical.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	Chuck Ebbert <cebbert@...hat.com>, lenb@...nel.org,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: ACPI Regression on Dell E1501

Thomas Gleixner wrote:
> On Thu, 2007-06-21 at 17:47 -0400, Chuck Ebbert wrote:
>> On 06/21/2007 05:04 PM, Tim Gardner wrote:
>>> Hi,
>>>
>>> Commit e9e2cdb412412326c4827fc78ba27f410d837e6e breaks boot on a Dell
>>> E1501 unless 'acpi=off' is specified (also tried nolapic and nohpet but
>>> it made no substantive difference). This laptop is an 'AMD Turion(tm) 64
>>> X2 Mobile Technology TL-50' CPU, but its booting 32 bit SMP (make
>>> defconfig). No kernel built after this commit works for this platform.
>>>
>>> There is no crash output, it just wedges after 'NET: Registered protocol
>>> family 2'.
>>>
>>> How can I debug this problem?
>> That'll be fun.
>>
>> That's:
>>
>> 	[PATCH] clockevents: i386 drivers
>>
>> [Author cc: added]
> 
> I'm going nuts on this. 
> 
> Tim, 
> 
> 1.) are you booting a 32bit or a 64 bit kernel ?
> 
> 2.) Can you please try 2.6.22-rc5 + 
> http://www.tglx.de/projects/hrtimers/2.6.22-rc5/patch-2.6.22-rc5-hrt1.patch
> 	whether this makes any difference 
> 
> Thanks,
> 
> 	tglx
> 
Thomas,

Its CONFIG_X86_32=y and CONFIG_SMP=y (make defconfig). I'll try your
patch later this evening.

rtg
-- 
Tim Gardner tim.gardner@...ntu.com
-
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/