From: Chris Largret <largret@gmail.com>
To: John Stoffel <john@stoffel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel panic related to ReiserFS (v3)
Date: Tue, 18 Jul 2006 17:41:15 -0700 [thread overview]
Message-ID: <1153269675.9726.3.camel@localhost> (raw)
In-Reply-To: <17596.57854.569394.880757@stoffel.org>
On Tue, 2006-07-18 at 09:28 -0400, John Stoffel wrote:
> 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.
Even though the back-trace doesn't touch the video drivers? I wish I
could reproduce this easily. I have been using this kernel and firefox
for several weeks, and this is the first time it has panic'd on me.
Thanks, I'll see what I can do.
--
Chris Largret <http://www.largret.com>
next prev parent reply other threads:[~2006-07-19 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 7:39 kernel panic related to ReiserFS (v3) Chris Largret
2006-07-18 13:28 ` John Stoffel
2006-07-19 0:41 ` Chris Largret [this message]
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=1153269675.9726.3.camel@localhost \
--to=largret@gmail.com \
--cc=john@stoffel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox