public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: |TEcHNO| <techno@punkt.pl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [SCSI] Driver broken in 2.6.x?
Date: Mon, 30 May 2005 10:19:23 +0200	[thread overview]
Message-ID: <429ACC8B.5040503@punkt.pl> (raw)
In-Reply-To: <20050529180747.18b7fd9e.akpm@osdl.org>

Hi,

> You cunningly removed linux-scsi from cc and replaced it with linux-kernel.
> Please don't do that.
Sorry, I forgot I sent it to scsi mailing list too. I'm realy sorry.

> As things have changed we'd need a new bug description please.
Ok.

> Please provide more details about the "hang".
I was scanning with xsane, there were two types of hang:
1. Acuire Preview
	This happend once, after it finished (or it seemd so), it was still in 
"waiting", as if something not happened to tell it finished.
So I chodes "cancel", and a few seconds later it hanged.

2. Scanning
	Once or twice it hanged at the begining or the end of scanning. No 
message, just hanged. XMMS was running so it juste entered the ususal 
sound hanged-and-looping. No reaction to any key.

3. Not a hang, but an instability.
	Basicly the beggining of accuire and scanning locks the machine up for 
a few seconds. Then teh scanning makes the computer less responsive. The 
X system is running at a few frames (around 3 to 8), there is noticable 
time before something happens on the screen. Sometimes the mouse starts 
moving in a mirrored way (left=right and/or up=down).

This sometimes leaves messages as this (the number is variable):
May 27 17:49:28 techno kernel: psmouse.c: Wheel Mouse at 
isa0060/serio1/input0 lost synchronization, throwing
3 bytes away.

> Under what circumstances? 
> 
> Does it oops?
Nothing left in the logs.

> What hardware and which driver?
2.6.12-rc5
00:0c.0 SCSI storage controller: DTC Technology Corp. Domex 536
         Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
         Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium 
 >TAbort- <TAbort- <MAbort- >SERR- <PERR-
         Interrupt: pin A routed to IRQ 11
         Region 0: I/O ports at d800 [size=32]

Scanner: ScanMagic 9636 S Plus (Xsane reports it to be Mustek ScanMagic 
12000 SP Plus)


> After it has "hung" is any information available from sysrq-P or sysrq-T?
Not checked, was in X anyway.


And yes, I'm using nvidia binary driver, but atleast 3rd "bug" on the 
list ir the same. It's also worh mentioning that the 3rd is sometimes 
jumpint into 2nd, so the first "lockup" part never ends.

Hope I can help you in any way possible.

-- 
pozdrawiam     |"Help me master, I felt the burning twilight behind
techno@punkt.pl|those gates of stell..." --Perihelion, Prophecy Sequence

      reply	other threads:[~2005-05-30  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <424EB65A.8010600@punkt.pl>
     [not found] ` <Pine.LNX.4.62.0504022301430.2525@dragon.hyggekrogen.localhost>
     [not found]   ` <424F0BFF.6020402@punkt.pl>
     [not found]     ` <Pine.LNX.4.62.0504022322150.2525@dragon.hyggekrogen.localhost>
2005-04-03 18:03       ` [Fw linux-kernel:] Re: [SCSI] Driver broken in 2.6.x? |TEcHNO|
2005-05-26  4:40 ` Andrew Morton
     [not found]   ` <4298FD42.10608@punkt.pl>
2005-05-30  1:07     ` Andrew Morton
2005-05-30  8:19       ` |TEcHNO| [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=429ACC8B.5040503@punkt.pl \
    --to=techno@punkt.pl \
    --cc=akpm@osdl.org \
    --cc=linux-scsi@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