From: |TEcHNO| <techno@punkt.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: [SCSI] Driver broken in 2.6.x?
Date: Mon, 04 Apr 2005 10:38:32 +0200 [thread overview]
Message-ID: <4250FD08.1020509@punkt.pl> (raw)
In-Reply-To: <20050403235726.GE3953@stusta.de>
>>As told, I tested it w/o nvidia module loaded, here's what I found:
>>1. It now doesn't hang on scanning for devices.
>>2. It now hangs on acquiring preview, logs will follow.
>>...
>>Apr 3 15:54:27 techno kernel: Unable to handle kernel NULL pointer
>>dereference at virtual address 0000014c
>>Apr 3 15:54:27 techno kernel: printing eip:
>>Apr 3 15:54:27 techno kernel: c03d8143
>>Apr 3 15:54:27 techno kernel: *pde = 00000000
>>Apr 3 15:54:27 techno kernel: Oops: 0000 [#1]
>>Apr 3 15:54:27 techno kernel: PREEMPT
>>Apr 3 15:54:27 techno kernel: Modules linked in: nvidia
>>...
> Still with nvidia.
>
> An Oops with the nvidia module loaded since the last boot is simply not
> debuggable for anyone except nvidia.
Em, there's also the same (w/o oops) with out that module, each of that
situations was separated by a reset. It was working well in 2.4.x so I
guess it'a a problem with the card's (00:0c.0 SCSI storage controller:
DTC Technology Corp. Domex 536) driver.
--
pozdrawiam |"Help me master, I felt the burning twilight behind
techno@punkt.pl|those gates of stell..." --Perihelion, Prophecy Sequence
next prev parent reply other threads:[~2005-04-04 8:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 15:12 [SCSI] Driver broken in 2.6.x? |TEcHNO|
2005-04-02 21:07 ` Jesper Juhl
2005-04-02 21:17 ` |TEcHNO|
2005-04-02 21:24 ` Jesper Juhl
2005-04-03 17:58 ` |TEcHNO|
2005-04-03 23:57 ` Adrian Bunk
2005-04-04 8:38 ` |TEcHNO| [this message]
2005-04-03 18:03 ` [Fw linux-kernel:] " |TEcHNO|
2005-05-26 4:40 ` Andrew Morton
2005-05-28 23:22 ` |TEcHNO|
2005-05-30 1:07 ` Andrew Morton
2005-05-30 8:19 ` |TEcHNO|
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=4250FD08.1020509@punkt.pl \
--to=techno@punkt.pl \
--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 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.