Messages in this thread | | | From | "Stephen Costaras" <> | Subject | Re: Scsi timeout / kernel panic | Date | Sat, 20 Nov 1999 14:54:13 -0600 |
| |
I've had similar problems w/ my setup here. (Tyan S1668D MB, w/ Mylex BT-958 controllers going to Seagate drives.) I've managed to mitigate the problem by lowering down the controllers to 10MB/sec from the optimum of 40MB/sec.
This has been an issue ever since switching to 2.2.* series but it appears to be insiduous. I've swapped out every component on the system (MB, cpus, cards, drives, et al) and it still happends but on a similar system (same MB, et al) it doesn't have a problem.
Cables are the same (all granite digital, so I know that they're fine).
If you happen to find anything I'd be interested as well.
Steve ----- Original Message ----- From: "Steven Sparks" <sparks@socketware.com> To: "David Edwards" <gecker@offbeatmedia.com> Cc: <linux-kernel@vger.rutgers.edu> Sent: Saturday, November 20, 1999 14:27 Subject: Re: Scsi timeout / kernel panic
> With the exception of the buslogic stuff, these are identical to the > errors I'm receiving with my quantum drives. This is three people > talking about at least four machines with quantum scsi drives locking > up in the same manner. this has begun happening since going from 2.0.x > to 2.2.x. I'm beginning to think that this is valid, not just an > anomaly of my system. > > -S > > > David Edwards wrote: > > > > I was wondering if someone can offer some advice as to how I can track this > > scsi error down. Below is the message printed to the console before the > > system locked up. > > > > scsi : aborting command due to timeout : pid 236637, scsi0, channel 0, id > > 0, lun > > 0 Write (10) 00 00 3a b0 1b 00 00 02 00 > > scsi0: Unable to Abort Command to Target 0 - CCB Reset > > SCSI host 0 abort (pid 236615) timed out - resetting > > SCSI bus is being reset for host 0 channel 0. > > scsi0: Resetting BusLogic BT-930 due to Target 0 > > scsi0: *** BusLogic BT-930 Initialized Successfully *** > > Kernel panic: scsi_free:Trying to free unused memory > > In swapper task - not syncing > > > > Thanks, David > > > > >Hello, > > > > > >I have a couple servers experiencing some lockup problems. I get these > > >types of messages printed to the console. Can anyone offer some advise as > > >to what might be causing this? I ran memtest extensively on these servers > > >and did not find any memory errors. Here's the info. Thanks. > > > > > >[gecker@ns1 gecker]$ uname -a > > >Linux ns1.reliablehosting.com 2.2.10 #1 Thu Nov 4 11:55:20 PST 1999 i686 > > >unknown > > > > > >scsi0 : BusLogic BT-930 > > > Vendor: QUANTUM Model: FIREBALL SE6.4S Rev: PJ09 > > > Type: Direct-Access ANSI SCSI revision: 02 > > > > > >And the errors. > > >scsi : aborting command due to timeout : pid 4062 > > >29, scsi0, channel 0, id 0, lun 0 Write (6) 01 00 93 02 00 > > >scsi0: Aborting CCB #406236 to Target 0 > > > > > >scsi0 channel 0 : resetting for second half of retries. > > >SCSI bus is being reset for host 0 channel 0. > > >scsi0: Sending Bus Device Reset CCB #406320 to Target 0 > > >scsi : aborting command due to timeout : pid 406230, scsi0, channel 0, id > > >0, lun > > > 0 Write (6) 01 40 47 04 00 > > >scsi0: Unable to Abort Command to Target 0 - CCB Reset > > > > > > > > >- > > >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > >the body of a message to majordomo@vger.rutgers.edu > > >Please read the FAQ at http://www.tux.org/lkml/ > > > > - > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to majordomo@vger.rutgers.edu > > Please read the FAQ at http://www.tux.org/lkml/ > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.rutgers.edu > Please read the FAQ at http://www.tux.org/lkml/ >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |