Re: PROBLEM: tmscsim driver on test11-pre7 stops working when starting X
On Mon, Nov 20, 2000 at 03:03:03AM +0100, Malte Cornils wrote: > my Dawicontrol 2974 SCSI-adapter fails with kernel 2.4.0-test10 > with pre-11 and reiserfs for kernel test-10 patched in: > > -- > Nov 20 01:30:23 wh36-b407 kernel: scsi : aborting command due to timeout : pid 0, >scsi0, channel 0, id 0, lun 0 Read (10) 00 00 08 c0 6c 00 00 f8 00 > Nov 20 01:30:23 wh36-b407 kernel: DC390: Abort command (pid 0, DCB c12c11c0, SRB >) > Nov 20 01:30:23 wh36-b407 kernel: DC390: Status of last IRQ (DMA/SC/Int/IRQ): >0890cc20 > Nov 20 01:30:23 wh36-b407 kernel: DC390: Register dump: SCSI block: > Nov 20 01:30:23 wh36-b407 kernel: DC390: XferCnt Cmd Stat IntS IRQS FFIS Ctl1 Ctl2 >Ctl3 Ctl4 > Nov 20 01:30:23 wh36-b407 kernel: DC390: 00 44 10 cc 00 80 17 48 > 18 04 > Nov 20 01:30:23 wh36-b407 kernel: DC390: Register dump: DMA engine: > Nov 20 01:30:23 wh36-b407 kernel: DC390: Cmd STrCntSBusAWrkBCWrkAC >Stat SBusCtrl > Nov 20 01:30:23 wh36-b407 kernel: DC390: 80 1000 051a4000 051a5000 >00 0308 > Nov 20 01:30:23 wh36-b407 kernel: DC390: Register dump: PCI Status: 0200 > Nov 20 01:30:23 wh36-b407 kernel: DC390: In case of driver trouble read >linux/drivers/scsi/README.tmscsim > Nov 20 01:30:23 wh36-b407 kernel: DC390: Aborted pid 0 with status 0 pid 0: So, already the device scan fails? I'll have to look up the register dump to analyze it. Would you test the patch I sent you on top of 2.0e5, please? > This happened on the second bootup with the new kernel, when kdm > was starting Xfree 4.0.1 from Debian woody. > Nov 20 01:29:34 wh36-b407 kernel: Bad boy: tmscsim (at 0xc02bf732) called us without >a dev_id! Fixed in 2.0eX, BTW. > I noted there's a new version of the driver on the maintainer's (Kurt > Garloff) homepage, but last time I tested it and reported an oops with > 2.4.test-something he didn't reply at all (that's not an offense, it's > understandable with the amount of work he's doing for KDE2 etc). I tend to answer mails, where I know a solution very quickly, but tend to not send messages like "Thanks I got your mail, I'll look into it!" Actually, when I got some time to do some work, I look for yet unanswered mails. > So should I > a) try with his patch again; my oops report for that is attached below > b) wait you can make of this bugreport > c) provide any further info/testing? Test the patch on 2.0e5 I sent you, please. > BTW, 2.2.17 with the stock tmscsim works fine everytime; with that kernel > (and no other changes) the system is excessively stable :) That's at least something! > CU, Yours Malte #8-) > > PS: Please cc me, I'm usually watching the lists I report bugs to, but LKML > is a bit... excessive; I'll monitor the list from time to time, but can't > guarantee timely responses... Nor can I. Actually, messages concerning drivers I maintain are sorted by procmailrc to a different folder :-) > The next boot, while in the fsck-Phase for the SCSI drive (SysRq > didn't work *that* well obviously :)) I got the oops. There were > some lines scrolling by which I unfortunately couldn't write down > fast enough, but I did copy the oops: > > Oops: Should be fixed in 2.0e5 and later. > Also, the oops occured when I was sharing interrupts (but this is > PCI, so there should be no problems, right?). That's correct only if level triggered IRQs are used. > I just fear that Linus might avoid large patches for the now > imminent 2.4... :-? The 2.0d driver does not work correctly with 2.4, and I'm trying to make sure 2.0f will be perfect. I don't see why Linus should refuse to accept a patch. Regards, -- Kurt Garloff <[EMAIL PROTECTED]> Eindhoven, NL GPG key: See mail header, key servers Linux kernel development SuSE GmbH, Nuernberg, FRG SCSI, Security PGP signature
PROBLEM: tmscsim driver on test11-pre7 stops working when starting X
Hi, my Dawicontrol 2974 SCSI-adapter fails with kernel 2.4.0-test10 with pre-11 and reiserfs for kernel test-10 patched in: -- Nov 20 01:30:23 wh36-b407 kernel: scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 08 c0 6c 00 00 f8 00 Nov 20 01:30:23 wh36-b407 kernel: DC390: Abort command (pid 0, DCB c12c11c0, SRB ) Nov 20 01:30:23 wh36-b407 kernel: DC390: Status of last IRQ (DMA/SC/Int/IRQ): 0890cc20 Nov 20 01:30:23 wh36-b407 kernel: DC390: Register dump: SCSI block: Nov 20 01:30:23 wh36-b407 kernel: DC390: XferCnt Cmd Stat IntS IRQS FFIS Ctl1 Ctl2 Ctl3 Ctl4 Nov 20 01:30:23 wh36-b407 kernel: DC390: 00 44 10 cc 00 80 17 48 18 04 Nov 20 01:30:23 wh36-b407 kernel: DC390: Register dump: DMA engine: Nov 20 01:30:23 wh36-b407 kernel: DC390: Cmd STrCntSBusAWrkBCWrkAC Stat SBusCtrl Nov 20 01:30:23 wh36-b407 kernel: DC390: 80 1000 051a4000 051a5000 00 0308 Nov 20 01:30:23 wh36-b407 kernel: DC390: Register dump: PCI Status: 0200 Nov 20 01:30:23 wh36-b407 kernel: DC390: In case of driver trouble read linux/drivers/scsi/README.tmscsim Nov 20 01:30:23 wh36-b407 kernel: DC390: Aborted pid 0 with status 0 Nov 20 01:30:23 wh36-b407 kernel: SCSI host 0 abort (pid 0) timed out - resetting Nov 20 01:30:23 wh36-b407 kernel: SCSI bus is being reset for host 0 channel 0. Nov 20 01:30:23 wh36-b407 kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 2504 Nov 20 01:30:23 wh36-b407 kernel: I/O error: dev 08:02, sector 448928 Nov 20 01:30:27 wh36-b407 kernel: SysRq: Emergency Sync Nov 20 01:30:27 wh36-b407 kernel: Syncing device 03:08 ... OK Nov 20 01:30:27 wh36-b407 kernel: Syncing device 03:01 ... OK Nov 20 01:30:29 wh36-b407 kernel: Syncing device 09:00 ... OK Nov 20 01:30:29 wh36-b407 kernel: Done. Nov 20 01:31:46 wh36-b407 kernel: Kernel logging (proc) stopped. Nov 20 01:31:46 wh36-b407 kernel: Kernel log daemon terminating. Nov 20 01:31:46 wh36-b407 exiting on signal 15 -- This happened on the second bootup with the new kernel, when kdm was starting Xfree 4.0.1 from Debian woody. the tmscsim driver is initialized with: -- Nov 20 01:29:34 wh36-b407 kernel: SCSI subsystem driver Revision: 1.00 Nov 20 01:29:34 wh36-b407 kernel: DC390_init: No EEPROM found! Nov 20 01:29:34 wh36-b407 kernel: DC390_init: Trying default EEPROM settings: Nov 20 01:29:34 wh36-b407 kernel: DC390: Used defaults: AdaptID=7, SpeedIdx=1 (8.0 MHz), DevMode=0x1f, AdaptMode=0x0f, TaggedCmnds=3 (16) Nov 20 01:29:34 wh36-b407 kernel: Bad boy: tmscsim (at 0xc02bf732) called us without a dev_id! Nov 20 01:29:34 wh36-b407 kernel: DC390: 1 adapters found Nov 20 01:29:34 wh36-b407 kernel: scsi0 : Tekram DC390/AM53C974 V2.0d 1998/12/25 Nov 20 01:29:34 wh36-b407 kernel: DC390: Target 0: Sync transfer 8.0 MHz, Offset 15 Nov 20 01:29:34 wh36-b407 kernel: Vendor: IBM Model: DCAS-34330Rev: S61A Nov 20 01:29:34 wh36-b407 kernel: Type: Direct-Access ANSI SCSI revision: 02 Nov 20 01:29:34 wh36-b407 kernel: DC390: Target 5: Sync transfer 8.0 MHz, Offset 15 Nov 20 01:29:34 wh36-b407 kernel: Vendor: RICOH Model: MP6200S Rev: 2.40 Nov 20 01:29:34 wh36-b407 kernel: Type: CD-ROM ANSI SCSI revision: 02 Nov 20 01:29:34 wh36-b407 kernel: Detected scsi disk sda at scsi0, channel 0, id 0, lun 0 Nov 20 01:29:34 wh36-b407 kernel: SCSI device sda: 8467200 512-byte hdwr sectors (4335 MB) Nov 20 01:29:34 wh36-b407 kernel: sda: sda1 sda2 sda3 sda4 Nov 20 01:29:34 wh36-b407 kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 5, lun 0 Nov 20 01:29:34 wh36-b407 kernel: sr0: scsi3-mmc drive: 6x/6x writer cd/rw xa/form2 cdda tray Nov 20 01:29:34 wh36-b407 kernel: Uniform CD-ROM driver Revision: 3.11 -- I noted there's a new version of the driver on the maintainer's (Kurt Garloff) homepage, but last time I tested it and reported an oops with 2.4.test-something he didn't reply at all (that's not an offense, it's understandable with the amount of work he's doing for KDE2 etc). So should I a) try with his patch again; my oops report for that is attached below b) wait you can make of this bugreport c) provide any further info/testing? BTW, 2.2.17 with the stock tmscsim works fine everytime; with that kernel (and no other changes) the system is excessively stable :) CU, Yours Malte #8-) PS: Please cc me, I'm usually watching the lists I report bugs to, but LKML is a bit... excessive; I'll monitor the list from time to time, but can't guarantee timely responses... System specs: AMD K6-2 333 on a TX430-based Mainboard, not overclocked; additional cards are: ISA - CL Soundblaster 16 PnP ISA - NE2k-clone PCI - Dawicontrol 2974 Fast-SCSI, based on AMD53... chip - ATI Rage Pro LT PCI 8 MB - Hauppauge WinTV Theatre (bttv878) now the bug report with Garloff's new driver (I was using a scanner in addition, but the ker
