Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Linux SMP  - kernel: scsi : aborting command due to timeout

Posted on 2003-11-04
4
Medium Priority
?
1,200 Views
Last Modified: 2013-12-06
Hi,

My Linux version 2.4.20-20.9smp (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)),

Whats wrong, how m i going to fix it .?

from /var/log/messages.* , this error messages appear everyday ::-

Oct 26 04:23:04 gs kernel: scsi : aborting command due to timeout : pid 28374, scsi1, channel 0, id 0, lun 0 Read (10) 00 00 47 4b 8
8 00 00 08 00
Oct 26 04:23:04 gs kernel: sym53c8xx_abort: pid=28374 serial_number=28375 serial_number_at_timeout=28375
Oct 26 04:23:06 gs kernel: SCSI host 1 abort (pid 28374) timed out - resetting
Oct 26 04:23:06 gs kernel: SCSI bus is being reset for host 1 channel 0.
Oct 26 04:23:06 gs kernel: sym53c8xx_reset: pid=28374 reset_flags=2 serial_number=28375 serial_number_at_timeout=28375
Oct 26 04:23:06 gs kernel: sym53c1010-33-1: restart (scsi reset).
Oct 26 04:23:06 gs kernel: sym53c1010-33-1: handling phase mismatch from SCRIPTS.
Oct 26 04:23:06 gs kernel: sym53c1010-33-1: Downloading SCSI SCRIPTS.
Oct 26 04:23:06 gs kernel: sym53c1010-33-1-<0,*>: FAST-80 WIDE SCSI 160.0 MB/s (12.5 ns, offset 62)



>chopped from /var/log/dmesg for reference ::-

SCSI subsystem driver Revision: 1.00
sym53c8xx: at PCI bus 4, device 2, function 1
sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
sym53c8xx: 53c1010-33 detected with Symbios NVRAM
sym53c8xx: at PCI bus 4, device 2, function 0
sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
sym53c8xx: 53c1010-33 detected with Symbios NVRAM
sym53c1010-33-0: rev 0x1 on pci bus 4 device 2 function 1 irq 53
sym53c1010-33-0: Symbios format NVRAM, ID 7, Fast-80, Parity Checking
sym53c1010-33-0: on-chip RAM at 0xfe9fc000
sym53c1010-33-0: restart (scsi reset).
sym53c1010-33-0: handling phase mismatch from SCRIPTS.
sym53c1010-33-0: Downloading SCSI SCRIPTS.
sym53c1010-33-1: rev 0x1 on pci bus 4 device 2 function 0 irq 52
sym53c1010-33-1: Symbios format NVRAM, ID 7, Fast-80, Parity Checking
sym53c1010-33-1: on-chip RAM at 0xfe9fa000
sym53c1010-33-1: restart (scsi reset).
sym53c1010-33-1: handling phase mismatch from SCRIPTS.
sym53c1010-33-1: Downloading SCSI SCRIPTS.
scsi0 : sym53c8xx-1.7.3c-20010512
scsi1 : sym53c8xx-1.7.3c-20010512
blk: queue c35dea18, I/O limit 1048575Mb (mask 0xffffffffff)
  Vendor: SEAGATE   Model: ST336607LW        Rev: 0006
  Type:   Direct-Access                      ANSI SCSI revision: 03
blk: queue c35de818, I/O limit 1048575Mb (mask 0xffffffffff)
sym53c1010-33-1-<0,0>: tagged command queue depth set to 8
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
sym53c1010-33-1-<0,*>: FAST-80 WIDE SCSI 160.0 MB/s (12.5 ns, offset 62)
SCSI device sda: 71687372 512-byte hdwr sectors (36704 MB)
0
Comment
Question by:qazakax
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 40

Accepted Solution

by:
jlevie earned 60 total points
ID: 9684573
I've got a couple of systems that have that same SCSI controller and Seagate disk and they don't exhibit the problem you are observing. One runs RH 8.0 and the other RH 9 with the same kernel you have. So I believe it is safe to say that the problem is not generic to that combination. Accordingly, it stands to reason that this problem is some sort of hardware fault with your particular devices. I'd look first at the cable & terminator and then at the disk as the cause.
0
 

Author Comment

by:qazakax
ID: 9684951
Hi,

"then at the disk as the cause" ?
you mean the SCSI hardisk got error, "bad sector" ? Need to change the whole SCSI hardisk ..!?


Rdgs,
-Qaz
0
 
LVL 40

Expert Comment

by:jlevie
ID: 9686195
Well it actualy sounds more like a problem with the disk interface electronics than a problem with a bad sector. I'd expect a different error from a bad spot on the drive.
0
 
LVL 40

Expert Comment

by:jlevie
ID: 9686296
Another possibiltiy, now that I've just noticed that you are running an SMP kernel, is that you have a problem with the motherboard on this system and interrupts aren't being correctly handled. That could could result in this sort of error being reported. You could boot the system into uni-processor mode for a while and see if the errors persist. I'd also suggest checking to see if there's a later system BIOS available for your motherboard.
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You ever wonder how to backup Linux system files just like Windows System Restore?  Well you can use Timeshift in Linux to perform those similar action.  This tutorial will show you how to backup your system files and keep regular intervals. Note…
In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Learn how to navigate the file tree with the shell. Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory names: Use ../ to move…
Suggested Courses

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question