All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Habersack <grendel@caudium.net>
To: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: XFS problems (hard lockup and oops on startup) with 2.5.5{6,7}
Date: Wed, 15 Jan 2003 22:59:40 +0100	[thread overview]
Message-ID: <20030115215940.GA1441@thanes.org> (raw)
In-Reply-To: <20030115202134.A25143@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

On Wed, Jan 15, 2003 at 08:21:34PM +0000, Christoph Hellwig scribbled:
[snip]
> > check the first filesystem the kernel oopses with Oops code 0002, in the
> > interrupt handler. Nothing gets logged, of course, so I can't provide the
> > full backtrace right now - I'll try to get it logged through the serial console
> > if it happens again with 2.5.58. I have copied some values by hand from the
> > screen (until I lost patience... :)):
> > 
> > Unable to handle kernel paging request at virtual address 000500074
> >  printing EIP
> 
> Hmm, that's really no much info.  And there weren't any XFS changes from
> 2.5.52 to 2.5.58..
Yep, that's why I wrote about something that affected XFS - at first I
thought it might have been preemption but then I checked I had it on also on
2.5.55. I'm running 2.5.58 currently and should the oops happen again, I'll
either transcribe the screen or get a screenshot via serial console. The
only thing I added in my > .55 config was the freebsd slice support and the
UFS support (as the module), but I doubt that would be the cause, although,
who knows?

thanks,

marek

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-01-15 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14 17:55 XFS problems (hard lockup and oops on startup) with 2.5.5{6,7} Marek Habersack
2003-01-15 20:21 ` Christoph Hellwig
2003-01-15 21:59   ` Marek Habersack [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=20030115215940.GA1441@thanes.org \
    --to=grendel@caudium.net \
    --cc=hch@infradead.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 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.