public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.6.9-rc1-bk16 Still cdrom/DVD oops
Date: Fri, 10 Sep 2004 13:27:37 +0100	[thread overview]
Message-ID: <41419DB9.4010201@blueyonder.co.uk> (raw)
In-Reply-To: <1094810774.15407.9.camel@krustophenia.net>

Lee Revell wrote:

>On Thu, 2004-09-09 at 20:59, Sid Boyce wrote:
>  
>
>>Lee Revell wrote:
>>    
>>
>>>Your kernel is tainted.  Please reproduce with an untainted kernel and
>>>report.
>>>
>>>      
>>>
>>The only tainted module is "nvidia", the results are the same without 
>>that module loaded in -bk15, i.e in runlevel 3. I've seen this problem 
>>on all kernels from 2.6.8.1 including -mm?. It's fine with 
>>2.6.8-rc4-mm1, the earliest kernel I currently have around.
>>    
>>
>
>Understood.  No one is suggesting the nvidia module caused the Oops,
>it's just that as long as there's a binary module loaded, the Oops can't
>be interpreted fully.
>
>If you can reproduce without nvidia loaded, then post one of these.
>
>Lee
>
>
>
>  
>
My second posting today has it appended.
Regards
Sid.

-- 
Sid Boyce .... Hamradio G3VBV and keen Flyer
=====LINUX ONLY USED HERE=====


  reply	other threads:[~2004-09-10 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-10  0:21 linux-2.6.9-rc1-bk16 Still cdrom/DVD oops Sid Boyce
2004-09-10  0:32 ` Lee Revell
2004-09-10  0:59   ` Sid Boyce
2004-09-10  8:51     ` Sid Boyce
2004-09-10 10:06     ` Lee Revell
2004-09-10 12:27       ` Sid Boyce [this message]
2004-09-10 22:55         ` linux-2.6.9-rc1-bk16 Still cdrom/DVD oops ** FIXED ** 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=41419DB9.4010201@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /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