linux-kernel - Re: 2.6.20.6 vanilla does't boot

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:	Wed, 18 Apr 2007 15:39:25 -0400
From:	Len Brown <lenb@...nel.org>
To:	Michal Jaegermann <michal@...pspace.math.ualberta.ca>
Cc:	Denis Kirjanov <kirjanov@...il.com>,
	Marat Buharov <marat.buharov@...il.com>,
	Marc Donner <Marc.Donner@...-breitband.de>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.20.6 vanilla does't boot

On Sunday 15 April 2007 11:50, Michal Jaegermann wrote:
> On Fri, Apr 13, 2007 at 03:38:18PM +0400, Denis Kirjanov wrote:
> > I updated the BIOS to the latest version, but the problem persists.
> > Boots option pci = noacpi not solved the problem. Reporting bios bug
> > disappears when setting pci = nommconf, But the kernel is still not
> > loaded (

The 2.6.15 dmesg do not give any clues to why 2.6.20.6 would not boot.
Can you boot 2.6.20.6 with "debug" and capture the serial console log,
or take a photo of what is on the screen when the boot hangs?

Did anything between 2.6.15 and 2.6.20.6 work properly?
Can you bisect where the failure started?

> On x86_64 hardware using ata_piix I was unable to boot kernels
> based on the current 2.6.20.x either.  Regardless of extra kernel
> parameters used I was getting consistently 'hdc: lost interrupt',
> and/or similar and after something like that the whole machine
> was dead.  The only differences were if I could still reboot
> from a keyboard or if I really have to pull a plug.
> 
> A kernel derived from 2.6.21-rc6-git1 (2.6.20-1.3053.fc7.x86_64 from
> Fedora "rawhide" to be more precise) did boot on the hardware in
> question, though; but only when I gave it 'acpi=off'.  Without that
> parameter it was getting stuck apparently when starting hotplug.
> In that kernel case disks were accessed using pata_atiixp driver.

If "acpi=off" is necessary to boot the latest kernel, please
report an ACPI bug:
http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
Please mention in the bug report what the latest working kernel was.

thanks,
-Len

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