linux-kernel - Re: pcibios_scanned needs to be set in ACPI? (was Re: 2.6.25-rc5: Reported regressions from 2.6.24)

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]

Message-ID: <Pine.LNX.4.64.0803130012470.14097@axis700.grange>
Date:	Thu, 13 Mar 2008 00:17:32 +0100 (CET)
From:	Guennadi Liakhovetski <g.liakhovetski@....de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Greg KH <greg@...ah.com>, "Rafael J. Wysocki" <rjw@...k.pl>,
	Jeff Garzik <jeff@...zik.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Adrian Bunk <bunk@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Natalie Protasevich <protasnb@...il.com>,
	Ingo Molnar <mingo@...e.hu>, Len Brown <len.brown@...el.com>
Subject: Re: pcibios_scanned needs to be set in ACPI?  (was Re: 2.6.25-rc5:
 Reported regressions from 2.6.24)

On Wed, 12 Mar 2008, Linus Torvalds wrote:

> On Wed, 12 Mar 2008, Greg KH wrote:
> > 
> > What happend in .25-rc was that we now catch these kinds of problems
> > (watching for duplicate kobjects to be registered and such.)  So this
> > might have always been happening, but no warning was ever produced.
> 
> It's not the warning that worries me. It's the apparent oops (keyboard 
> leds blinking?) at shutdown/poweroff!

No, no oops, no blinking LEDs. The machine just stays there after syncing 
SCSI disks. I can still call sysrqs, and I've captured them with the 
serial console - see complete dumps here: 
http://bugzilla.kernel.org/attachment.cgi?id=15057

> Since there is at least a patch worth trying now, I'll hold off reverting 
> it and wait for Guennardi to test the patch, but the fact is, we shouldn't 
> have a known-broken kernel for several weeks, when there is a known fix 
> for it in reverting a single commit!

I'll test it in about 12 hours.

Thanks
Guennadi
---
Guennadi Liakhovetski
--
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/