From: Tonnerre <tonnerre@thundrix.ch>
To: Sid Boyce <sboyce@blueyonder.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: -bk15 oops on mounting cdrom
Date: Wed, 8 Sep 2004 17:59:31 +0200 [thread overview]
Message-ID: <20040908155931.GB2726@thundrix.ch> (raw)
In-Reply-To: <413F2935.4020009@blueyonder.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
Salut,
On Wed, Sep 08, 2004 at 04:45:57PM +0100, Sid Boyce wrote:
> Modules linked in: nls_iso8859_1 nvidia parport_pc lp parport sg st sd_mod sr_mod scsi_mod thermal snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss sk98lin snd_intel8x0 processor ub usblp fan usbhid snd_ac97_codec snd_pcm snd_timer snd_page_alloc gameport snd_mpu 401_uart snd_rawmidi snd_seq_device snd button ipv6 soundcore ohci1394 ieee1394 ehci_hcd nvidia_agp agpgart ohci_hcd evdev usbcore forcedeth vfat fat dm_mod
> 0060:[cache_free_debugcheck+385/640] Tainted: P VLI
You may want to reproduce that bug without the nvidia module
loaded. This doesn't sound like much, but I even had strange problems
after registering a simple webcam to the kernel which kept it crashing
while accessing data structures that have clearly been there before
(but yet it claimed that the memory address wasn't assigned). It
turned out that my customer had the NVidia module loaded. Once he
unloaded it, everything was running fine.
So please consider a clean boot without ever loading nvidia, and try
to reproduce the bug.
Tonnerre
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-08 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 15:45 -bk15 oops on mounting cdrom Sid Boyce
2004-09-08 15:59 ` Tonnerre [this message]
2004-09-08 21:33 ` Sid Boyce
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=20040908155931.GB2726@thundrix.ch \
--to=tonnerre@thundrix.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
/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.