Messages in this thread | | | Date | Wed, 15 Mar 2000 21:19:44 +0000 (GMT) | From | James <> | Subject | Kernel 2.3.51 AIC7XXX SCSI driver not working right |
| |
I've got an Adaptec 2920C SCSI card which uses the AIC7XXX scsi driver. My Traxdata CDR4120 SCSI CD-Writer doesn't work. The SCSI bus is properly terminated and also contains an HP Scanjet 4p and an HP Surestore 2GB DAT drive.
This machine also has Windows98 inflicted on it and i can write CDs fine in that. The scanner works properly using SANE and the Gimp, and i assume the DAT drive works (i have no tapes to put in it, but 'mt' only fails with 'No medium present' and not a screenful of scsi errors).
The attached files show what is output when the scsi modules are loaded, and what happens when i try and mount a cd.
Anyone know why this is happening? When i was using the 2.2.x kernels it all used to work, i'm using the 2.3.x kernels so my USB stuff works.
More interesting debugging output available if you want it...
-- MCSE: Minesweeper Consultant and Solitaire Expert root@kermit.globalnet.co.uk http://www.penguinpowered.com/~a_out
bigbird:~# mount /dev/scd0 /cdrom /dev/scd0: Input/output error invalid operand: 0000 CPU: 0 EIP: 0010:[<c0132079>] EFLAGS: 00010282 eax: 0000001f ebx: cbf4d320 ecx: c01de398 edx: c01de398 esi: 00000b00 edi: ffffffea ebp: cb331c00 esp: ca05df50 ds: 0018 es: 0018 ss: 0018 Process mount (pid: 224, stackpage=ca05d000) Stack: c01b91c7 c01b9379 000001aa 00000000 c0130d83 cbf4d320 c01e3020 00000000 00000000 ca05dfbc c01e1bc0 c01e3020 0b00ffff c0131271 cbf4d320 08057ed8 08057ee8 c01c04c2 00000000 00000000 ca05c000 c0ed0000 00000000 cbf4d320 Call Trace: [<c01b91c7>] [<c01b9379>] [<c0130d83>] [<c0131271>] [<c01c04c2>] [<c010ad0c>] Code: 0f 0b 83 c4 0c 89 f6 8b 53 04 8b 03 89 50 04 89 02 53 a1 c0 Segmentation fault [from 'dmesg'] VFS: Disk change detected on device sr(11,0) scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 1, lun 0 Read (10) 00 00 00 00 00 00 00 01 00 SCSI host 0 abort (pid 0) timed out - resetting SCSI bus is being reset for host 0 channel 0. (scsi0:0:1:0) Synchronous at 10.0 Mbyte/sec, offset 15. Device b00 not ready. I/O error: dev 0b:00, sector 0 VFS: Disk change detected on device sr(11,0) MSDOS: Hardware sector size is 2048 fatfs: bogus cluster size VFS: Can't find a valid MSDOS filesystem on dev 0b:00. kernel BUG at block_dev.c:426! invalid operand: 0000 CPU: 0 EIP: 0010:[<c0132079>] EFLAGS: 00010282 eax: 0000001f ebx: cbf4d320 ecx: c01de398 edx: c01de398 esi: 00000b00 edi: ffffffea ebp: cb331c00 esp: ca05df50 ds: 0018 es: 0018 ss: 0018 Process mount (pid: 224, stackpage=ca05d000) Stack: c01b91c7 c01b9379 000001aa 00000000 c0130d83 cbf4d320 c01e3020 00000000 00000000 ca05dfbc c01e1bc0 c01e3020 0b00ffff c0131271 cbf4d320 08057ed8 08057ee8 c01c04c2 00000000 00000000 ca05c000 c0ed0000 00000000 cbf4d320 Call Trace: [<c01b91c7>] [<c01b9379>] [<c0130d83>] [<c0131271>] [<c01c04c2>] [<c010ad0c>] Code: 0f 0b 83 c4 0c 89 f6 8b 53 04 8b 03 89 50 04 89 02 53 a1 c0 ksymoops 2.3.3 on i686 2.3.51. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.3.51/ (default) -m /usr/src/linux/System.map (default)
Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options.
Reading Oops report from the terminal invalid operand: 0000 CPU: 0 EIP: 0010:[<c0132079>] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010282 eax: 0000001f ebx: cbf4d320 ecx: c01de398 edx: c01de398 esi: 00000b00 edi: ffffffea ebp: cb331c00 esp: ca05df50 ds: 0018 es: 0018 ss: 0018 Process mount (pid: 224, stackpage=ca05d000) Stack: c01b91c7 c01b9379 000001aa 00000000 c0130d83 cbf4d320 c01e3020 00000000 00000000 ca05dfbc c01e1bc0 c01e3020 0b00ffff c0131271 cbf4d320 08057ed8 08057ee8 c01c04c2 00000000 00000000 ca05c000 c0ed0000 00000000 cbf4d320 Call Trace: [<c01b91c7>] [<c01b9379>] [<c0130d83>] [<c0131271>] [<c01c04c2>] [<c010ad0c>] Code: 0f 0b 83 c4 0c 89 f6 8b 53 04 8b 03 89 50 04 89 02 53 a1 c0
>>EIP; c0132079 <bdput+29/54> <===== Trace; c01b91c7 <tvecs+4583/5a7c> Trace; c01b9379 <tvecs+4735/5a7c> Trace; c0130d83 <do_mount+297/320> Trace; c0131271 <sys_mount+1f5/244> Trace; c01c04c2 <cprt+5e02/93e0> Trace; c010ad0c <system_call+34/38> Code; c0132079 <bdput+29/54> 00000000 <_EIP>: Code; c0132079 <bdput+29/54> <===== 0: 0f 0b ud2a <===== Code; c013207b <bdput+2b/54> 2: 83 c4 0c addl $0xc,%esp Code; c013207e <bdput+2e/54> 5: 89 f6 movl %esi,%esi Code; c0132080 <bdput+30/54> 7: 8b 53 04 movl 0x4(%ebx),%edx Code; c0132083 <bdput+33/54> a: 8b 03 movl (%ebx),%eax Code; c0132085 <bdput+35/54> c: 89 50 04 movl %edx,0x4(%eax) Code; c0132088 <bdput+38/54> f: 89 02 movl %eax,(%edx) Code; c013208a <bdput+3a/54> 11: 53 pushl %ebx Code; c013208b <bdput+3b/54> 12: a1 c0 00 00 00 movl 0xc0,%eax
1 warning issued. Results may not be reliable.
| |