From: "John Stoffel" <john@stoffel.org>
To: largret@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel panic related to ReiserFS (v3)
Date: Tue, 18 Jul 2006 09:28:30 -0400 [thread overview]
Message-ID: <17596.57854.569394.880757@stoffel.org> (raw)
In-Reply-To: <1153208388.8074.18.camel@localhost>
Chris> This kernel panic happened a few minutes ago, and it is
Chris> probably related to a firefox bug, but it shouldn't cause the
Chris> kernel to panic. I'm running the 2.6.16.16 kernel with the
Chris> latest squashfs (CVS) patch which supported this kernel
Chris> series. The distro is Slamd64, and is on a 64-bit AMD X2
Chris> system. As you can probably guess, my main filesystem is
Chris> ReiserFS. It is on an SATA drive. If more information is
Chris> needed, let me know.
Chris> Jul 17 23:42:49 localhost kernel: Modules linked in: usb_storage vmnet
Chris> parport_pc parport vmmon snd_pcm_oss snd_mixer_oss md5 ipv6 ipt_recent
Chris> ipt_REJECT xt_state iptable_filter nfs lockd nfs_acl sunrpc r8169
Chris> ohci1394 ieee1394 emu10k1_gp gameport snd_emu10k1 snd_rawmidi
Chris> snd_ac97_codec snd_ac97_bus snd_pcm snd_seq_device snd_timer
Chris> snd_page_alloc snd_util_mem snd_hwdep snd 8250_pci 8250 serial_core
Chris> tda9887 tuner cx8800 cx88xx video_buf ir_common tveeprom compat_ioctl32
Chris> v4l1_compat v4l2_common btcx_risc videodev nvidia forcedeth i2c_nforce2
Chris> pcmcia firmware_class yenta_socket rsrc_nonstatic pcmcia_core
Chris> Jul 17 23:42:49 localhost kernel: Pid: 7770, comm: firefox-bin Tainted:
Chris> P 2.6.16.16 #1
You've got a binary kernel module loaded here, please try to re-create
this crash without the nvidia module loaded. We (hah! Not me
actually... :-) can't debug this with such a module.
The key is the 'Tainted' flag.
John
next prev parent reply other threads:[~2006-07-18 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 7:39 Chris Largret
2006-07-18 13:28 ` John Stoffel [this message]
2006-07-19 0:41 ` Chris Largret
2006-07-19 3:52 ` Jim Crilly
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=17596.57854.569394.880757@stoffel.org \
--to=john@stoffel.org \
--cc=largret@gmail.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®