From: Jiri Slaby <jirislaby@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: Jiri Kosina <jikos@jikos.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
mingo@redhat.com, linux-raid@vger.kernel.org
Subject: Re: oops on 2.6.19-rc6-mm2: deref of 0x28 at permission+0x7
Date: Tue, 12 Dec 2006 13:41:40 +0100 [thread overview]
Message-ID: <457EA384.2050402@gmail.com> (raw)
In-Reply-To: <17789.64240.879603.161637@cse.unsw.edu.au>
Neil Brown wrote:
> On Monday December 11, jikos@jikos.cz wrote:
>> On Mon, 11 Dec 2006, Neil Brown wrote:
>>
>>>> this nash thing is exactly the command which triggers a bit different
>>>> oops in my case. On my side, the oops is fully reproducible. If you
>>>> manage to make your case also reproducible, could you please try to
>>>> revert md-change-lifetime-rules-for-md-devices.patch? This made the
>>>> oops vanish in my case. I think Neil is working on it.
>>> Trying to work on it - not making a lot of progress. I find it hard to
>>> see how anything in md can cause the inode for a block-device file to
>>> disappear... It is a bit of a long-shot, but this patch might change
>>> things. It changes the order in which things are de-allocated. Jiri and
>>> Jiri: would either of both of you see if you can reproduce the bug with
>>> this patch on 2.6.19-rc6-mm2 ???
>> Hi Neil,
>>
>> sorry to say that, but it's still there after applying your patch.
>
> Not a big surprise, but thanks a lot for testing. I think I'm going
> to have to try harder to duplicate it myself.
Away from that machine now, so that I can't test anything till thursday.
> If I remember rightly you are using FC - which version exactly? (I've
> never installed FC before so this is going to be learning experience).
FC6 with latest updates.
> And you have no MD arrays at all - is that correct?
I do have. md1 md2 md3 -- raid0, 1, 0. But there is no md0 (removed in the past)
and 'raidautorun /dev/md0 | nash' causes the troubles.
> And you compile your own kernel. Is it monolithic, or are you using
> modules? Do you boot with an initrd or just the kernel?
Yup. Monolithic as much as possible (md is in the kernel and so dm is). / on the
lvm2 on the /dev/md1 with no initrd. All are sata disks, so sd_mod, sata_promise
and ata_piix are in the kernel.
> I'd like to duplicate your installation as closely as possible, so any
> relevant details or recipes would be greatly appreciated.
Hm, I have never seen FC6 installation process, so I can't say what special
option I have turned on -- it's 'yum upgrade'd from FC5, FC4...
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
prev parent reply other threads:[~2006-12-12 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 1:20 oops on 2.6.19-rc6-mm2: deref of 0x28 at permission+0x7 Jiri Slaby
2006-12-10 19:30 ` Jiri Kosina
2006-12-10 19:57 ` Jiri Kosina
2006-12-11 2:11 ` Neil Brown
2006-12-11 9:35 ` Jiri Kosina
2006-12-12 0:42 ` Neil Brown
2006-12-12 12:41 ` Jiri Slaby [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=457EA384.2050402@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@osdl.org \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@suse.de \
/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.