From: Greg KH <gregkh@suse.de>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: axboe@kernel.dk, kay.sievers@vrfy.org,
"David S. Miller" <davem@davemloft.net>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.6.38.8] Bisected to commit 5fb46ae7b8c51b05a12c6a66108e8d398c20ee09
Date: Thu, 7 Jul 2011 06:33:44 -0700 [thread overview]
Message-ID: <20110707133344.GB26301@suse.de> (raw)
In-Reply-To: <4E1534DC.3020306@t-online.de>
On Thu, Jul 07, 2011 at 06:23:56AM +0200, Knut Petersen wrote:
> Am 07.07.2011 02:33, schrieb Greg KH:
> > On Mon, Jul 04, 2011 at 03:06:40PM +0200, Knut Petersen wrote:
> >> Hi everybody!
> >>
> >> An openSuse 11.2 system reliably refused to boot properly with kernel 2.6.38.8
> >> although the prior 2.6.38.y kernels worked fine. After a few seconds booting
> >> stopped. Several <ctrl-c> did help, but a lot of services were not started properly,
> >> only the root partition was available. Nothing unusual could be found in the
> >> kernel messages.
> >>
> >> I bisected the problem to commit 5fb46ae7b8c51b05a12c6a66108e8d398c20ee09.
> >>
> >> That gave me the idea to disconnect the Plextor PX-755A dvd drive and to
> >> try 2.6.38.8 again. It booted without problem.
> > Does the 2.6.39.2 kernel work properly for you?
> >
> Yes. Kernel 2.6.38[,1,2,3,4,5,6,7] 2.6.39[1,2] 3.0-git are ok, only 2.6.38.8 is broken in the
> way described above.
Good. You do know that 2.6.38.y is end-of-life and you should move on
to 2.6.39, right? There's nothing I can do right now for the .38 series
to resolve this, sorry.
greg k-h
prev parent reply other threads:[~2011-07-07 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 13:06 [BUG 2.6.38.8] Bisected to commit 5fb46ae7b8c51b05a12c6a66108e8d398c20ee09 Knut Petersen
2011-07-07 0:33 ` Greg KH
2011-07-07 4:23 ` Knut Petersen
2011-07-07 4:43 ` Gene Heskett
2011-07-07 13:33 ` Greg KH [this message]
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=20110707133344.GB26301@suse.de \
--to=gregkh@suse.de \
--cc=Knut_Petersen@t-online.de \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=kay.sievers@vrfy.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).