Hi, actually I have no scsi problems with kernel 2.4., but 2.6 shows hundreds of lines in the log files:
May 5 21:37:10 localhost kernel: sym0:0:0:M_REJECT to send for : 1-2-3-1. May 5 21:37:14 localhost last message repeated 42 times and a few times I saw them also from sym0:3:0: May 5 21:30:37 localhost kernel: sym0:3:0:M_REJECT to send for : 1-2-3-1. Is this somehow a timing problem? My oldest harddisk sym0:1:0 doesn't throw these messages, but the newer ones 0:0:0 and 0:3:0 do it. I've tried debian packages 2.6.8-2-generic and 2.6.11-1-generic, but both show the same behaviour. OTOH, 2.4.27-2-generic is wonderful quiet, it's usable and doesn't report such messages. I'm happy with 2.4, but I want to switch to 2.6. I have also found a message on LKML about it, but no solution. http://www.xy1.org/linux-kernel@vger.kernel.org/msg04526.html Here are more details about my SCSI stuff: May 5 21:39:32 localhost kernel: SCSI subsystem driver Revision: 1.00 May 5 21:39:32 localhost kernel: sym0: <810a> rev 0x11 on pci bus 0 device 9 function 0 irq 28 May 5 21:39:32 localhost kernel: sym0: No NVRAM, ID 7, Fast-10, SE, parity checking May 5 21:39:32 localhost kernel: sym0: SCSI BUS has been reset. May 5 21:39:32 localhost kernel: scsi0 : sym-2.1.17a May 5 21:39:32 localhost kernel: blk: queue fffffc00013faca8, no I/O memory limit May 5 21:39:32 localhost kernel: Vendor: IBM Model: DPSS-309170N Rev: S96H May 5 21:39:32 localhost kernel: Type: Direct-Access ANSI SCSI revision: 03 May 5 21:39:32 localhost kernel: blk: queue fffffc00013faea8, no I/O memory limit May 5 21:39:32 localhost kernel: Vendor: IBM Model: DORS-32160 Rev: WA0A May 5 21:39:32 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02 May 5 21:39:32 localhost kernel: blk: queue fffffc00013fb0a8, no I/O memory limit May 5 21:39:32 localhost kernel: Vendor: IBM Model: DDRS-39130W Rev: S97B May 5 21:39:32 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02 May 5 21:39:32 localhost kernel: blk: queue fffffc00013fb2a8, no I/O memory limit May 5 21:39:32 localhost kernel: Vendor: TOSHIBA Model: CD-ROM XM-5401TA Rev: 3605 May 5 21:39:32 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 May 5 21:39:32 localhost kernel: blk: queue fffffc00013fb4a8, no I/O memory limit May 5 21:39:32 localhost kernel: sym0:0:0: tagged command queuing enabled, command queue depth 16. May 5 21:39:32 localhost kernel: sym0:1:0: tagged command queuing enabled, command queue depth 16. May 5 21:39:32 localhost kernel: sym0:3:0: tagged command queuing enabled, command queue depth 16. May 5 21:39:32 localhost kernel: sym53c8xx: at PCI bus 0, device 9, function 0 May 5 21:39:32 localhost kernel: sym53c8xx: IO region 0x9000[0..127] is in use May 5 21:39:32 localhost kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 May 5 21:39:32 localhost kernel: Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0 May 5 21:39:32 localhost kernel: Attached scsi disk sdc at scsi0, channel 0, id 3, lun 0 May 5 21:39:32 localhost kernel: sym0:0: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 8) May 5 21:39:32 localhost kernel: SCSI device sda: 17916240 512-byte hdwr sectors (9173 MB) May 5 21:39:32 localhost kernel: Partition check: May 5 21:39:32 localhost kernel: /dev/scsi/host0/bus0/target0/lun0: p1 p2 May 5 21:39:32 localhost kernel: sym0:1: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 8) May 5 21:39:32 localhost kernel: SCSI device sdb: 4226725 512-byte hdwr sectors (2164 MB) May 5 21:39:32 localhost kernel: /dev/scsi/host0/bus0/target1/lun0: p1 p2 p3 May 5 21:39:32 localhost kernel: sym0:3: FAST-10 SCSI 10.0 MB/s ST (100.0 ns, offset 8) May 5 21:39:32 localhost kernel: SCSI device sdc: 17850000 512-byte hdwr sectors (9139 MB) May 5 21:39:32 localhost kernel: /dev/scsi/host0/bus0/target3/lun0: p1 p2 My onboard SCSI controller (in an Alpha XL300) is: 0000:00:09.0 SCSI storage controller: LSI Logic / Symbios Logic 53c810 (rev 11) Flags: bus master, medium devsel, latency 32, IRQ 28 I/O ports at 9000 [size=256] Memory at 0000000002231000 (32-bit, non-prefetchable) [size=256] I'm afraid there's nobody else here with similar problems. Am I right? bye martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]