From: Len Brown <lenb@kernel.org>
To: Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
Cc: Denis Kirjanov <kirjanov@gmail.com>,
Marat Buharov <marat.buharov@gmail.com>,
Marc Donner <Marc.Donner@dbd-breitband.de>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.20.6 vanilla does't boot
Date: Wed, 18 Apr 2007 15:39:25 -0400 [thread overview]
Message-ID: <200704181539.26105.lenb@kernel.org> (raw)
In-Reply-To: <20070415155016.GA14489@ellpspace.math.ualberta.ca>
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
next prev parent reply other threads:[~2007-04-18 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 5:34 2.6.20.6 vanilla does't boot Денис Кирьянов
[not found] ` <C244E4A2.1CF94%Marc.Donner@dbd-breitband.de>
2007-04-13 5:46 ` Денис Кирьянов
2007-04-13 6:35 ` Marat Buharov
2007-04-13 11:38 ` Denis Kirjanov
2007-04-15 15:50 ` Michal Jaegermann
2007-04-18 19:39 ` Len Brown [this message]
2007-04-19 0:01 ` Michal Jaegermann
2007-04-18 19:32 ` Len Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200704181539.26105.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=Marc.Donner@dbd-breitband.de \
--cc=kirjanov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marat.buharov@gmail.com \
--cc=michal@ellpspace.math.ualberta.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox