From: Mike Galbraith <efault@gmx.de>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@suse.de>
Subject: Re: 2.6.17-rc4-mm3 cfq oops->panic w. fs damage
Date: Sun, 28 May 2006 10:03:04 +0200 [thread overview]
Message-ID: <1148803384.8757.7.camel@homer> (raw)
In-Reply-To: <1148802491.8083.7.camel@homer>
On Sun, 2006-05-28 at 09:48 +0200, Mike Galbraith wrote:
> On Sun, 2006-05-28 at 08:00 +0200, Mike Galbraith wrote:
> > On Sun, 2006-05-28 at 06:25 +0100, Al Viro wrote:
> > > On Sun, May 28, 2006 at 07:12:03AM +0200, Mike Galbraith wrote:
> > > > Greetings,
> > > >
> > > > I tried to boot 2.6.17-rc4-mm3 twice yesterday, and received the below
> > > > both times. Both times, the oops->panic occurred while X/KDE was
> > > > starting. KDE would not run thereafter, and had to be reinstalled.
> > >
> > > Can you reproduce that with mainline?
> >
> > Virgin rc4 has been working fine, but I've been using UP kernels. I'll
> > try the same config as SMP.
>
> She's running fine. Guess I'll go prod mm3 again.
Yup, mm3 makes reliable kaboom.
I suppose the first thing to do is see if it's cfq, and then maybe toss
a dart at the patch list.
-Mike
next prev parent reply other threads:[~2006-05-28 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 5:12 2.6.17-rc4-mm3 cfq oops->panic w. fs damage Mike Galbraith
2006-05-28 5:25 ` Al Viro
2006-05-28 6:00 ` Mike Galbraith
2006-05-28 7:48 ` Mike Galbraith
2006-05-28 8:03 ` Mike Galbraith [this message]
2006-05-28 8:24 ` Mike Galbraith
2006-05-29 11:00 ` Mike Galbraith
2006-05-30 12:36 ` Jens Axboe
2006-05-30 13:27 ` Mike Galbraith
2006-05-30 13:30 ` Jens Axboe
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=1148803384.8757.7.camel@homer \
--to=efault@gmx.de \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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.