From: Jan Kara <jack@suse.cz>
To: Mitch <Mitch@0Bits.COM>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 SMP bug ? PANIC in __d_find_alias
Date: Thu, 13 Dec 2007 12:25:14 +0100 [thread overview]
Message-ID: <20071213112514.GC15541@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <475FD03A.7080401@0Bits.COM>
> Can anyone help with this ? This seems to be a true SMP bug - the same
> kernel on another UP machine is working fine (although different h/w).
> Seems like stress (find for example) can easily trigger this. Does it
> look like i have a bad filesystem ? Can anyone help me figure out which
> one ? The fact that this is tainted (due to nvidia) is a red herring i
> think because both my machines (the SMP and UP one) are using the same
> nvidia module and the panic is in ext3 code.
>
> Help
> Mitch
>
> Dec 10 03:02:43 home kernel: BUG: unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> Dec 10 03:02:43 home kernel: printing eip:
> Dec 10 03:02:43 home kernel: c01761fc
> Dec 10 03:02:43 home kernel: *pdpt = 00000000198a6001
> Dec 10 03:02:43 home kernel: *pde = 0000000000000000
> Dec 10 03:02:43 home kernel: Oops: 0000 [#1]
> Dec 10 03:02:43 home kernel: PREEMPT SMP
> Dec 10 03:02:43 home kernel: Modules linked in: loop nls_iso8859_1
> nls_cp437 vfat fat tun iptable_nat nvidia(P) appletalk psnap llc nfsd expo
> rtfs lockd sunrpc xt_limit xt_tcpudp iptable_mangle ipt_LOG
> ipt_MASQUERADE nf_nat ipt_TOS ipt_REJECT nf_conntrack_irc
> nf_conntrack_ftp nf_con
> ntrack_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables
> ftdi_sio usbserial forcedeth snd_hda_intel snd_seq_oss snd_seq_midi_event
> snd_seq snd_seq_device snd_pcm_oss snd_pcm snd_timer snd_page_alloc
> snd_mixer_oss snd usb_storage ehci_hcd ohci_hcd it87 hwmon_vid i2c_dev i
> 2c_core
> Dec 10 03:02:43 home kernel: CPU: 1
> Dec 10 03:02:43 home kernel: EIP: 0060:[__d_find_alias+44/192]
Looks like inode->i_dentry.next has been NULL. But I don't really
understand how that could be ever NULL because list_heads are always
cyclic lists... Can you try enabling "Debug linked list manipulation" and
also "Debug slab memory allocations" in Kernel hacking menu and see
whether some other errors appear?
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
next prev parent reply other threads:[~2007-12-13 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 12:12 Mitch
2007-12-12 19:36 ` Rafael J. Wysocki
2007-12-13 11:25 ` Jan Kara [this message]
2007-12-12 21:43 Mitch
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=20071213112514.GC15541@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=Mitch@0Bits.COM \
--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
all inboxes | Powered by JetHome®