From: Sid Boyce <sboyce@blueyonder.co.uk>
To: Tonnerre <tonnerre@thundrix.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: -bk15 oops on mounting cdrom
Date: Wed, 08 Sep 2004 22:33:32 +0100 [thread overview]
Message-ID: <413F7AAC.2040004@blueyonder.co.uk> (raw)
In-Reply-To: <20040908155931.GB2726@thundrix.ch>
Tonnerre wrote:
>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
>
>
It's repeatable under anything other than 2.6.8-rc4-mm1, the earliest
kernel I have here. As a test, I attached another cdrom as hdd and got
the same oops under 2.6.9-rc1-bk15, same problem and as far as I can
tell anything from 2.6.8.1 onwards gives the same fault.
Now running under 2.6.8-rc4-mm1 without problems, so it looks like a
kernel bug.
barrabas:/ftp/sep04 # ls /media/dvd
. autorun.inf content COPYING.de directory.yast
gpg-pubkey-3d25d3d9-36e12d04.asc LIESMICH media.1 README.DOS
.. boot control.xml COPYRIGHT docu
gpg-pubkey-9c800aca-39eef481.asc LIESMICH.DOS pubring.gpg suse
ARCHIVES.gz ChangeLog COPYING COPYRIGHT.de dosutils
INDEX.gz ls-lR.gz README SuSEgo.ico
barrabas:/ftp/sep04 # ls /media/dvd/suse
. .. i586 i686 noarch setup
Regards
Sid.
--
Sid Boyce .... Hamradio G3VBV and keen Flyer
=====LINUX ONLY USED HERE=====
prev parent reply other threads:[~2004-09-08 21:33 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
2004-09-08 21:33 ` Sid Boyce [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=413F7AAC.2040004@blueyonder.co.uk \
--to=sboyce@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tonnerre@thundrix.ch \
/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