[ale] [Fwd: NCR rel 17 panic]
andy
dread at atlcom.net
Sun Apr 28 16:21:57 EDT 1996
This is a multi-part message in MIME format.
--------------D577D40E4E
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
This might be helpful
--------------D577D40E4E
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Received: from mroe.cs.colorado.edu by future.atlcom.net with SMTP (5.65/1.2-eef)
id AA01945; Fri, 26 Apr 96 04:20:33 -0400
X-UIDL: 830646509.002
Return-Path: <owner-ncr53c810 at mroe.cs.colorado.edu>
Received: (from daemon at localhost) by mroe.cs.colorado.edu (8.7.5/8.7.3) id UAA15510 for ncr53c810-list; Thu, 25 Apr 1996 20:08:32 -0600 (MDT)
Received: from boulder.Colorado.EDU (root at boulder.Colorado.EDU [128.138.238.18]) by mroe.cs.colorado.edu (8.7.5/8.7.3) with SMTP id UAA15507 for <ncr53c810-alias at cs.Colorado.EDU>; Thu, 25 Apr 1996 20:08:31 -0600 (MDT)
Received: from tyrell.lf.net (tyrell.lf.net [194.195.220.226]) by boulder.Colorado.EDU (8.6.13/8.6.12/UnixOps) with SMTP id UAA24459 for <ncr53c810 at Colorado.EDU>; Thu, 25 Apr 1996 20:07:59 -0600
Received: by tyrell.lf.net (Smail3.1.28.1/tyrell)
via Tyrell Stuttgart, FRG (Public access
Internet system; Call +49 711 2567904)
from amiuni.tynet.sub.org with UUCP
for boulder.Colorado.EDU
id m0uCcwp-000RpFA; Fri, 26 Apr 96 04:07 WET DST
Received: by amiuni.tynet.sub.org (V1.17-beta/Amiga)
id <61oo at amiuni.tynet.sub.org>; Thu, 25 Apr 96 22:00:08 GMT
Received: from localhost (karsten at localhost) by addx.tynet.sub.org (8.6.12/8.6.9) with SMTP id UAA00175 for <ncr53c810 at Colorado.EDU>; Thu, 25 Apr 1996 20:33:50 +0200
Date: Thu, 25 Apr 1996 20:33:50 +0200 (MET DST)
Message-Id: <Pine.LNX.3.93.960425203252.171A-100000 at addx.tynet.sub.org>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
From: Karsten Weiss <karsten at addx.tynet.sub.org>
To: ncr53c810 at Colorado.EDU
Subject: NCR rel 17 panic
X-Mozilla-Status: 0001
Hi!
Today I got the following kernel messages (running 1.3.95) while
extracting an tar.gz file on one of my harddisks:
Apr 25 16:10:28 addx kernel: scsi0 : WARNING : INTFLY with no completed commands.
Apr 25 16:10:43 addx kernel: scsi : aborting command due to timeout : pid 8866, scsi0, channel 0, id 1, lun 0 Read (6) 09 dd c2 04 00
Apr 25 16:10:43 addx kernel: scsi0 : DANGER : command running, can not abort.
Apr 25 16:10:43 addx kernel: scsi : aborting command due to timeout : pid 8867, scsi0, channel 0, id 1, lun 0 Read (6) 09 df 14 26 00
Apr 25 16:10:43 addx kernel: scsi0 : found command 8867 in Linux issue queue
Apr 25 16:10:43 addx kernel: scsi : aborting command due to timeout : pid 8868, scsi0, channel 0, id 1, lun 0 Read (6) 0a 4f 5e 36 00
Apr 25 16:10:43 addx kernel: scsi0 : found command 8868 in Linux issue queue
Apr 25 16:10:59 addx kernel: scsi : aborting command due to timeout : pid 8866, scsi0, channel 0, id 1, lun 0 Read (6) 09 dd c2 04 00
Apr 25 16:10:59 addx kernel: scsi0 : DANGER : command running, can not abort.
Apr 25 16:10:59 addx kernel: SCSI host 0 abort (pid 8866) timed out - resetting
Apr 25 16:10:59 addx kernel: SCSI bus is being reset for host 0.
Apr 25 16:10:59 addx kernel: scsi0 : DCMD|DBC=0x50000000, DNAD=0x88c5c (virt 0x00088c5c)
Apr 25 16:10:59 addx kernel: DSA=0xdbc1e8 (virt 0x00dbc1e8)
Apr 25 16:10:59 addx kernel: DSPS=0x88d6c, TEMP=0x888ec (virt 0x000888ec), DMODE=0x88
Apr 25 16:10:59 addx kernel: SXFER=0x88, SCNTL3=0x13
Apr 25 16:10:59 addx kernel: phase=MSGIN, 0 bytes in SCSI FIFO
Apr 25 16:10:59 addx kernel: STEST0=0x6
Apr 25 16:10:59 addx kernel: scsi0 : DSP 0x88c54 (virt 0x00088c54) ->
Apr 25 16:10:59 addx kernel: 0x88c54 (virt 0x00088c54) : 0x50000000 0x00088d6c (virt 0x00088d6c)
Apr 25 16:10:59 addx kernel: 0x88c5c (virt 0x00088c5c) : 0x60000200 0x00000000 (virt 0x00000000)
Apr 25 16:11:00 addx kernel: 0x88c64 (virt 0x00088c64) : 0x78388800 0x00000000 (virt 0x00000000)
Apr 25 16:11:00 addx kernel: 0x88c6c (virt 0x00088c6c) : 0x0f000001 0x000885d8 (virt 0x000885d8)
Apr 25 16:11:00 addx kernel: 0x88c74 (virt 0x00088c74) : 0x78389800 0x00000000 (virt 0x00000000)
Apr 25 16:11:00 addx kernel: 0x88c7c (virt 0x00088c7c) : 0xc0000004 0x000885d4 (virt 0x000885d4) 0x0000e834 (virt 0x0000e834)
Apr 25 16:11:00 addx kernel: scsi0 : issue queue
Apr 25 16:11:00 addx kernel: scsi0 : dsa at phys 0xdbe080 (virt 0x00dbe080)
Apr 25 16:11:00 addx kernel: + 64 : dsa_msgout length = 558564, data = 0x0 (virt 0x00000000)
Apr 25 16:11:00 addx kernel: + 60 : select_indirect = 0xc0000004
Apr 25 16:11:00 addx kernel: + 56 : dsa_cmnd = 0x0
Apr 25 16:11:00 addx kernel: + 48 : dsa_next = 0x0
Apr 25 16:11:00 addx kernel: scsi0 : dsa at phys 0xdb4080 (virt 0x00db4080)
Apr 25 16:11:00 addx kernel: + 64 : dsa_msgout length = 558564, data = 0x0 (virt 0x00000000)
Apr 25 16:11:00 addx kernel: + 60 : select_indirect = 0xc0000004
Apr 25 16:11:00 addx kernel: + 56 : dsa_cmnd = 0x0
Apr 25 16:11:00 addx kernel: + 48 : dsa_next = 0x0
Apr 25 16:11:00 addx kernel: scsi0 : schedule dsa array :
Apr 25 16:11:00 addx kernel: scsi0 : end schedule dsa array
Apr 25 16:11:00 addx kernel: scsi0 : reconnect_dsa_head :
Apr 25 16:11:00 addx kernel: scsi0 : end reconnect_dsa_head
Apr 25 16:11:00 addx kernel: The sti() implicit in a printk() prevents hangs
Apr 25 16:11:00 addx kernel: scsi : aborting command due to timeout : pid 8867, scsi0, channel 0, id 1, lun 0 Read (6) 09 df 14 26 00
Apr 25 16:11:03 addx syslogd: exiting on signal 15
Here's my SCSI configuration:
: scsi-ncr53c7,8xx : at PCI bus 0, device 1, function 0
: scsi-ncr53c7,8xx : NCR53c810 at memory 0xfbfef000, io 0xe800, irq 12
: scsi0 : burst length 8
: scsi0 : reset ccf to 3 from 0
: NCR code relocated to 0x88600 (virt 0x00088600)
: scsi0 : test 1 started
: scsi0 : NCR53c{7,8}xx (rel 17)
: scsi : 1 host.
: scsi0 : target 0 accepting period 200ns offset 8 5.00MHz synchronous SCSI
: scsi0 : setting target 0 to period 200ns offset 8 5.00MHz synchronous SCSI
: Vendor: IBM OEM Model: 0662S12 Rev: 3 30
: Type: Direct-Access ANSI SCSI revision: 02
: Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
: scsi0 : target 1 accepting period 200ns offset 8 5.00MHz synchronous SCSI
: scsi0 : setting target 1 to period 200ns offset 8 5.00MHz synchronous SCSI
: Vendor: IBM Model: DPES-31080 Rev: S31K
: Type: Direct-Access ANSI SCSI revision: 02
: Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
: scsi0 : target 2 accepting period 248ns offset 8 4.03MHz synchronous SCSI
: scsi0 : setting target 2 to period 248ns offset 8 4.03MHz synchronous SCSI
: Vendor: SONY Model: CD-ROM CDU-8003A Rev: 1.9a
: Type: CD-ROM ANSI SCSI revision: 02
: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 2, lun 0
: scsi0 : target 4 accepting period 200ns offset 8 5.00MHz synchronous SCSI
: scsi0 : setting target 4 to period 200ns offset 8 5.00MHz synchronous SCSI
: Vendor: HP Model: HP35480A Rev: 1009
: Type: Sequential-Access ANSI SCSI revision: 02
: Detected scsi tape st0 at scsi0, channel 0, id 4, lun 0
: scsi : detected 1 SCSI tape 1 SCSI cdrom 2 SCSI disks total.
: SCSI device sda: hdwr sector= 512 bytes. Sectors= 2055035 [1003 MB] [1.0 GB]
: SCSI device sdb: hdwr sector= 512 bytes. Sectors= 2118144 [1034 MB] [1.0 GB]
My computer is a 486/100 on an ASUS SP3G motherboard.
I had the following kernel options enabled:
CONFIG_SCSI_NCR53C7xx=y
CONFIG_SCSI_NCR53C7xx_sync=y
CONFIG_SCSI_NCR53C7xx_DISCONNECT=y
(BTW: Somebody who knows exactly should write an help text for
the DISCONNECT option for the kernel Configure.help file.)
Does anyone have an explantion? I've been running my system for a very
long time now with kernel 1.2.13 and had no problems at all. After
upgrading to 1.3.9x from some reasons I already got this error
twice (the first time I was making a system backup to my DAT drive
when it happened. This was on kernel 1.3.94 I believe).
Feel free to contact be if you need some more information to track down
the bug.
Take care,
Karsten
A small notes at the end:
- There is a compiler warning in the file drivers/scsi/hosts.c in line
235 when I compile the latest kernels. It has someting to do with
the NCR driver. The (harmless?) warning says:
"warning: initialization from incompatible pointer type"
This should be fixed before 2.0.
- Wouldn't it be a good idea to display the above syslog output which
contains additional information about the SCSI devices in
/proc/scsi/scsi instead of the current output?
Karsten Weiss
-
UUCP: karsten at addx.tynet.sub.org
FIDONET: 2:246/1416.37
GERNET: 21:492/1616.37
STUDBOX: knweiss at studbox.uni-stuttgart.de
INTERNET: knweiss at trick.informatik.uni-stuttgart.de
--------------D577D40E4E--
More information about the Ale
mailing list