From: Herbert Poetzl <herbert@13thfloor.at>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Jes Sorensen <jes@sgi.com>, Con Kolivas <kernel@kolivas.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
linux-xfs@oss.sgi.com, xfs-masters@oss.sgi.com,
stern@rowland.harvard.edu, sekharan@us.ibm.com, akpm@osdl.org,
David Chinner <dgc@sgi.com>
Subject: Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS)
Date: Fri, 14 Apr 2006 03:30:12 +0200 [thread overview]
Message-ID: <20060414013012.GB11178@MAIL.13thfloor.at> (raw)
In-Reply-To: <Pine.LNX.4.61.0604132049110.20938@yvahk01.tjqt.qr>
On Thu, Apr 13, 2006 at 08:52:05PM +0200, Jan Engelhardt wrote:
>
> >[ 3.583356] hda: QEMU HARDDISK, ATA DISK drive
> >[ 5.021521] hdc: QEMU HARDDISK, ATA DISK drive
>
> Maybe QEMU is involved in the Oops? What if used on a normal system?
well, might be, but a) it works perfectly fine with
2.6.16 and many older kernels, and b) sorry, I don't
have a real system for xfs crash testing right now
find the config in my reply to the previous email
best,
Herbert
> Jan Engelhardt
> --
prev parent reply other threads:[~2006-04-14 1:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 5:21 2.6.17-rc1 did break XFS Herbert Poetzl
2006-04-13 5:35 ` Nathan Scott
2006-04-13 9:23 ` Keith Owens
2006-04-13 14:17 ` Jan Engelhardt
2006-04-13 9:36 ` Keith Owens
2006-04-13 15:12 ` Alan Stern
2006-04-13 7:23 ` notifier chain problem? (was Re: 2.6.17-rc1 did break XFS) David Chinner
2006-04-13 8:40 ` Jes Sorensen
2006-04-13 13:50 ` Herbert Poetzl
2006-04-13 14:10 ` Jes Sorensen
2006-04-13 14:21 ` Jan Engelhardt
2006-04-13 14:32 ` Con Kolivas
2006-04-13 17:53 ` Herbert Poetzl
2006-04-13 18:38 ` Chandra Seetharaman
2006-04-14 1:39 ` Herbert Poetzl
2006-04-13 18:52 ` Jan Engelhardt
2006-04-14 1:30 ` Herbert Poetzl [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=20060414013012.GB11178@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=akpm@osdl.org \
--cc=dgc@sgi.com \
--cc=jengelh@linux01.gwdg.de \
--cc=jes@sgi.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=sekharan@us.ibm.com \
--cc=stern@rowland.harvard.edu \
--cc=xfs-masters@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®