Date: Wed, 14 Nov 2001 14:54:30 -0800 From: Nick Pasich <npasich@crash.cts.com> To: aic7xxx@freebsd.org Subject: kernel panic with 29160 during tape backup Message-ID: <20011114145430.A19316@204.210.46.203>
next in thread | raw e-mail | index | archive | help
I'm running a dual Pentium III using an adaptec 29160 with
5 quantum Ultra 160's and a DAT tape unit.
I'm using ReiserFS version 3.6.25.
I have 1.5 gb of memory.
I'm using Linux version 2.4.14-pre8.
Here's the 2.4.14-pre8 kernel scsi info:
*******************************************************************************
*******************************************************************************
kernel: SCSI subsystem driver Revision: 1.00
kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.4
kernel: <Adaptec 29160 Ultra160 SCSI adapter>
kernel: aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
kernel:
kernel: Vendor: QUANTUM Model: ATLAS10K2-TY092L Rev: DDD6
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: (scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
kernel: Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DDD6
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: (scsi0:A:1): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
kernel: Vendor: QUANTUM Model: ATLAS10K2-TY092L Rev: DDD6
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: (scsi0:A:2): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
kernel: Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DDD6
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: (scsi0:A:3): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
kernel: Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DDD6
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: (scsi0:A:4): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
kernel: Vendor: ARCHIVE Model: Python 04106-XXX Rev: 7350
kernel: Type: Sequential-Access ANSI SCSI revision: 02
kernel: (scsi0:A:5): 10.000MB/s transfers (10.000MHz, offset 15)
kernel: scsi0:A:0:0: Tagged Queuing enabled. Depth 253
kernel: scsi0:A:1:0: Tagged Queuing enabled. Depth 253
kernel: scsi0:A:2:0: Tagged Queuing enabled. Depth 253
kernel: scsi0:A:3:0: Tagged Queuing enabled. Depth 253
kernel: scsi0:A:4:0: Tagged Queuing enabled. Depth 253
kernel: st: Version 20011003, bufsize 32768, wrt 30720, max init. bufs 4, s/g segs 16
kernel: Attached scsi tape st0 at scsi0, channel 0, id 5, lun 0
kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
kernel: Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
kernel: Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
kernel: Attached scsi disk sdd at scsi0, channel 0, id 3, lun 0
kernel: Attached scsi disk sde at scsi0, channel 0, id 4, lun 0
kernel: SCSI device sda: 17938985 512-byte hdwr sectors (9185 MB)
kernel: Partition check:
kernel: sda: sda1 sda2
kernel: SCSI device sdb: 35860910 512-byte hdwr sectors (18361 MB)
kernel: sdb: sdb1 sdb2
kernel: SCSI device sdc: 17938985 512-byte hdwr sectors (9185 MB)
kernel: sdc: sdc1 sdc2
kernel: SCSI device sdd: 35860910 512-byte hdwr sectors (18361 MB)
kernel: sdd: sdd1 sdd2
kernel: SCSI device sde: 35860910 512-byte hdwr sectors (18361 MB)
kernel: sde: sde1
*******************************************************************************
*******************************************************************************
mount info:
/dev/sda2 on / type reiserfs (rw)
/dev/sdb1 on /usr type reiserfs (rw)
/dev/sde1 on /zSRC type reiserfs (rw)
none on /proc type proc (rw)
/dev/sda1 on /dosc type msdos (rw)
/dev/c1 and /dev/d1 are used for emergency situations and hold a nightly
backup of / and /usr -- no problems with the nightly backup.
I periodically do full system backup to tape which includes a msdos partition.
During my last full backup to tape, I had a kernel panic, which of course
locked-up the system. I hadn't done a full backup in a couple of months
because I do critical data backups nightly.
The panic message:
kernel panic: Too few segs for dma mapping. Increase AHC_NSEG
I recompiled the kernel after increasing the AHC_NSEG's to 512 in
aic7xxx_osm.h, but that didn't help.
Not having a clue as to what the problem was, I started rebooting with
older kernels. I tried 2.4.14-pre8, 2.4.13-ac4, 2.4.12-ac5 and
2.4.10-ac12. All of them gave the same panic message....
I finally tried 2.4.7, which gave me an error message, but completed
the backup.
The error message for 2.4.7:
Saw underflow (4096 of 4096 bytes). Treated as error
Saw underflow (4096 of 4096 bytes). Treated as error
Saw underflow (4096 of 4096 bytes). Treated as error
Saw underflow (4096 of 4096 bytes). Treated as error
Saw underflow (4096 of 4096 bytes). Treated as error
Saw underflow (4096 of 4096 bytes). Treated as error
SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 70000
I/O error: dev 08:01, sector 59591
Here's the 2.4.7 kernel scsi info:
*******************************************************************************
*******************************************************************************
kernel: SCSI subsystem driver Revision: 1.00
kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.1.13
kernel: <Adaptec 29160 Ultra160 SCSI adapter>
kernel: aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs
kernel:
kernel: Vendor: QUANTUM Model: ATLAS10K2-TY092L Rev: DDD6
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: (scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
kernel: Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DDD6
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: (scsi0:A:1): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
kernel: Vendor: QUANTUM Model: ATLAS10K2-TY092L Rev: DDD6
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: (scsi0:A:2): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
kernel: Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DDD6
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: (scsi0:A:3): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
kernel: Vendor: QUANTUM Model: ATLAS10K2-TY184L Rev: DDD6
kernel: Type: Direct-Access ANSI SCSI revision: 03
kernel: (scsi0:A:4): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
kernel: Vendor: ARCHIVE Model: Python 04106-XXX Rev: 7350
kernel: Type: Sequential-Access ANSI SCSI revision: 02
kernel: (scsi0:A:5): 10.000MB/s transfers (10.000MHz, offset 15)
kernel: scsi0:0:0:0: Tagged Queuing enabled. Depth 253
kernel: scsi0:0:1:0: Tagged Queuing enabled. Depth 253
kernel: scsi0:0:2:0: Tagged Queuing enabled. Depth 253
kernel: scsi0:0:3:0: Tagged Queuing enabled. Depth 253
kernel: scsi0:0:4:0: Tagged Queuing enabled. Depth 253
kernel: st: bufsize 32768, wrt 30720, max init. buffers 4, s/g segs 16.
kernel: Attached scsi tape st0 at scsi0, channel 0, id 5, lun 0
kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
kernel: Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
kernel: Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0
kernel: Attached scsi disk sdd at scsi0, channel 0, id 3, lun 0
kernel: Attached scsi disk sde at scsi0, channel 0, id 4, lun 0
kernel: SCSI device sda: 17938985 512-byte hdwr sectors (9185 MB)
kernel: Partition check:
kernel: sda: sda1 sda2
kernel: SCSI device sdb: 35860910 512-byte hdwr sectors (18361 MB)
kernel: sdb: sdb1 sdb2
kernel: SCSI device sdc: 17938985 512-byte hdwr sectors (9185 MB)
kernel: sdc: sdc1 sdc2
kernel: SCSI device sdd: 35860910 512-byte hdwr sectors (18361 MB)
kernel: sdd: sdd1 sdd2
kernel: SCSI device sde: 35860910 512-byte hdwr sectors (18361 MB)
kernel: sde: sde1
*******************************************************************************
*******************************************************************************
This message pointed to the msdos partition. Finally with a clue as to what
was happening, I rebooted with 2.4.14-pre8 kernel, unmounted the msdos
partition and did a successful full system tape backup-up without any errors.
I did reboot into msdos and ran norton diskdoctor which didn't report any
sector errors. I also ran "badblocks -n /dev/sda1" and no errors were reported.
So I really don't know what the problem is.......
Needless to say, I would much rather have system that reports errors and
keeps running, than one that does a kernel panic and freezes.
I also don't want to have to boot kernel 2.4.7 to be able to include the
msdos partition in my system backup....
Your help would be very much appricated....
-----( Nick Pasich )-----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011114145430.A19316>