From: Michal Jaegermann <michal@ellpspace.math.ualberta.ca>
To: Len Brown <lenb@kernel.org>
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 18:01:50 -0600 [thread overview]
Message-ID: <20070419000150.GA8797@ellpspace.math.ualberta.ca> (raw)
In-Reply-To: <200704181539.26105.lenb@kernel.org>
On Wed, Apr 18, 2007 at 03:39:25PM -0400, Len Brown wrote:
> On Sunday 15 April 2007 11:50, Michal Jaegermann wrote:
> >
> > 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
I now travel and what I can do at this moment is somewhat limited.
In particular I cannot gain an access to the hardware in question.
But please see
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=232490
and the most recent comments there in particular.
> Please mention in the bug report what the latest working kernel was.
This is mentioned in the referenced report as well.
Michal
next prev parent reply other threads:[~2007-04-19 0:03 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
2007-04-19 0:01 ` Michal Jaegermann [this message]
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=20070419000150.GA8797@ellpspace.math.ualberta.ca \
--to=michal@ellpspace.math.ualberta.ca \
--cc=Marc.Donner@dbd-breitband.de \
--cc=kirjanov@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marat.buharov@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.