View previous topic :: View next topic |
Author |
Message |
rowbin hod n00b
Joined: 08 Jan 2005 Posts: 50
|
Posted: Tue Mar 01, 2005 6:43 pm Post subject: ISA fast scsi2 adapter and tape drive woes... |
|
|
Hi all.
I'm a bit of a scsi noob, so please forgive me if i supply incomplete information. I recently acquired an Adaptec ISA fast scsi2 adapter AHA-1520B, and a Seagate STD224000N DDS3 tape drive (internal), with the intention of using an old p133 machine as a tape backup machine. Not because it's any better than dvd-r or another hard disk, but because it's there and it's a new challenge
I set the card up with on board termination enabled and a scsi ID of 7 (default). The tape drive also has on board termination enabled and a scsi id of 0. They are connected directly together with a 50pin ribbon cable. I compiled in the aha152x module for my card. On the local screen I do "modprobe aha150x" and because it takes a long time, i view the dmesg results through a ssh session.....
Code: |
Mar 1 19:08:23 optimus aha152x: BIOS test: passed, auto configuration: ok, 1 controller(s) configured
Mar 1 19:08:23 optimus aha152x: resetting bus...
Mar 1 19:08:24 optimus aha152x0: vital data: rev=3, io=0x340 (0x340/0x340), irq=10, scsiid=7, reconnect=enabled, parity=enabled, synchronous=enabled, delay=1000, extended translation=disabled
Mar 1 19:08:25 optimus aha152x0: trying software interrupt, ok.
Mar 1 19:08:25 optimus scsi0 : Adaptec 152x SCSI driver; $Revision: 2.7 $
Mar 1 19:08:40 optimus (scsi0:0:0) cannot reuse command
Mar 1 19:08:40 optimus scheduling while atomic: scsi_eh_0/0x00000001/6083
Mar 1 19:08:40 optimus [<c0355ae6>] schedule+0x516/0x520
Mar 1 19:08:40 optimus [<c0115356>] release_console_sem+0xc6/0xd0
Mar 1 19:08:40 optimus [<c03553c9>] __down+0x99/0x120
Mar 1 19:08:40 optimus [<c0111ad0>] default_wake_function+0x0/0x20
Mar 1 19:08:40 optimus [<c011c7cf>] __mod_timer+0xdf/0x1a0
Mar 1 19:08:40 optimus [<c03555a7>] __down_failed+0x7/0xc
Mar 1 19:08:40 optimus [<c48333a3>] .text.lock.aha152x+0x22/0x2f [aha152x]
Mar 1 19:08:40 optimus [<c482e9e0>] timer_expired+0x0/0xb0 [aha152x]
Mar 1 19:08:40 optimus [<c028e1d4>] scsi_try_bus_device_reset+0x44/0x80
Mar 1 19:08:40 optimus [<c028e406>] scsi_eh_bus_device_reset+0x56/0xd0
Mar 1 19:08:40 optimus [<c028ea7a>] scsi_eh_ready_devs+0x2a/0x60
Mar 1 19:08:40 optimus [<c028ebe9>] scsi_unjam_host+0xb9/0xd0
Mar 1 19:08:40 optimus [<c028ec9a>] scsi_error_handler+0x9a/0xc0
Mar 1 19:08:40 optimus [<c028ec00>] scsi_error_handler+0x0/0xc0
Mar 1 19:08:40 optimus [<c0101275>] kernel_thread_helper+0x5/0x10
|
here it sits for maybe a minute or so, then on the local screen a huge error blurb is shown, including lots of numbers in hex, followed lastly by the obligatory kernel panic message...
Code: | <0> Kernel panic - not syncing, fatal exception in interrupt
|
As i said, I'm a bit of a scsi noob, so i'd appreciate and help. I'm running gentoo sources 6.6.10-r6 (EDIT: 2.6.10-r6 even ).
thanks
Last edited by rowbin hod on Tue Mar 01, 2005 7:08 pm; edited 1 time in total |
|
Back to top |
|
|
adaptr Watchman
Joined: 06 Oct 2002 Posts: 6730 Location: Rotterdam, Netherlands
|
Posted: Tue Mar 01, 2005 7:06 pm Post subject: |
|
|
Quote: | I'm running gentoo sources 6.6.10-r6 |
I'd like a copy of that, please
What you have is a classic ISA IRQ conflict - either configure the board physically to use another IRQ or use the BIOS to assign another one.
This last is most easily accomplished by setting the IRQ in question to reserved in the BIOS; that way, no onboard devices will attempt to use it.
If you need more help, post the output of
Code: | cat /proc/interrupts |
but check the BIOS first. _________________ >>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
Back to top |
|
|
rowbin hod n00b
Joined: 08 Jan 2005 Posts: 50
|
Posted: Tue Mar 01, 2005 7:18 pm Post subject: |
|
|
Had a look through the BIOS, and it's very old and covers everything in 2 pages. Sadly no IRQ managment available. Have disabled things like parallel port, serial port, usb, sound. Hopefully that might feee up IRQ 10, which the card appears to use.
thanks for the help, i'll report on how it goes
EDIT: lol, i'm sure your post said lspci -v before, so i'm now emerging pciutils will try the interrupts when that's done. |
|
Back to top |
|
|
adaptr Watchman
Joined: 06 Oct 2002 Posts: 6730 Location: Rotterdam, Netherlands
|
Posted: Tue Mar 01, 2005 7:35 pm Post subject: |
|
|
Yes, it did say that
That was before I realised that, although it might conceivably tell you what onboard device is using IRQ 10, it won't ever tell you which IRQ the ISA card is using ... _________________ >>> emerge (3 of 7) mcse/70-293 to /
Essential tools: gentoolkit eix profuse screen |
|
Back to top |
|
|
rowbin hod n00b
Joined: 08 Jan 2005 Posts: 50
|
Posted: Tue Mar 01, 2005 7:52 pm Post subject: |
|
|
Well, my disabling of various onboard devices didn't seem to work. When the SCSI card is initiated at the start, just after the pc boots, it gives the followinf information:
IRQ = 10
BIOS address = C8000h
port = 340h
when i log in i did as you suggested...
Code: |
optimus root # more /proc/interrupts
CPU0
0: 1164065 XT-PIC timer
1: 16 XT-PIC i8042
2: 0 XT-PIC cascade
11: 291 XT-PIC eth0
14: 2348 XT-PIC ide0
NMI: 0
ERR: 1
|
Then i load the module on the local screen, and have a look at the interrupts again over the ssh session (before the kernel panics)...
Code: |
optimus root # more /proc/interrupts
CPU0
0: 1433640 XT-PIC timer
1: 136 XT-PIC i8042
2: 0 XT-PIC cascade
10: 1 XT-PIC aha152x
11: 339 XT-PIC eth0
14: 2388 XT-PIC ide0
NMI: 0
ERR: 1
|
On the face of it there appears not to be an IRQ conflict.
/me does some more prodding |
|
Back to top |
|
|
rowbin hod n00b
Joined: 08 Jan 2005 Posts: 50
|
Posted: Tue Mar 01, 2005 8:27 pm Post subject: |
|
|
OMG, feel like the biggest nub ever.
went into the bios on the card itself at boot, and it tried to start scanning the scsi ids for devices. It just sat at id #0, which didn't seem right to me. I unplugged the cable from the card and plugged it in "upside down" and it worked :
Code: |
aha152x: BIOS test: passed, auto configuration: ok, 1 controller(s) configured
aha152x: resetting bus...
aha152x0: vital data: rev=3, io=0x340 (0x340/0x340), irq=10, scsiid=7, reconnect
=enabled, parity=enabled, synchronous=enabled, delay=1000, extended translation=
disabled
aha152x0: trying software interrupt, ok.
scsi0 : Adaptec 152x SCSI driver; $Revision: 2.7 $
(scsi0:0:0) 01 03 01 32 08 00
Vendor: SEAGATE Model: DAT 04106-XXX Rev: 743B
Type: Sequential-Access ANSI SCSI revision: 02
Attached scsi tape st0 at scsi0, channel 0, id 0, lun 0
st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 1
|
now for some fun with mt. thanks for the suggestions. The cable i've got is a bit annoying as it has no alignment tabs. guess i'll have to remember for future! |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|