Messages in this thread | | | Date | Thu, 3 Dec 1998 01:36:09 +0100 | From | Martin Maciaszek <> | Subject | problems with scsi stuff in 2.1.130 |
| |
FInally I tried to use the 2.1.130 kernel. With the iminent release of 2.2 I thought 2.1.130 should be stable enough. Unfortunately I ran into problems with some scsi stuff. While trying to record a cd, I got an oops:
Dec 3 01:17:18 nexus kernel: Unable to handle kernel paging request at virtual address 840f0000 Dec 3 01:17:18 nexus kernel: current->tss.cr3 = 006e7000, Dec 3 01:17:18 nexus kernel: *pde = 00000000 Dec 3 01:17:18 nexus kernel: Oops: 0000 Dec 3 01:17:18 nexus kernel: CPU: 0 Dec 3 01:17:18 nexus kernel: EIP: 0010:[<c012846a>] Dec 3 01:17:18 nexus kernel: EFLAGS: 00010286 Dec 3 01:17:18 nexus kernel: eax: 840f0000 ebx: 0009c7ea ecx: 00000812 edx: 840f0000 Dec 3 01:17:18 nexus kernel: esi: 00000400 edi: 00000400 ebp: 0009c7ea esp: c0e0be20 Dec 3 01:17:18 nexus kernel: ds: 0018 es: 0018 ss: 0018 Dec 3 01:17:18 nexus kernel: Process cdrecord (pid: 484, process nr: 42, stackpage=c0e0b000) Dec 3 01:17:18 nexus kernel: Stack: c01284a3 00000812 0009c7ea 00000400 00000812 c27406c0 c0e0bed8 00000000 Dec 3 01:17:18 nexus kernel: c01299f1 00000812 0009c7ea 00000400 c0e0bee4 0000f6a8 00000000 c0795860 Dec 3 01:17:18 nexus kernel: 0009c7ea c0795860 c17ec620 c27406c0 00000812 00000100 c27406c0 c17e0812 Dec 3 01:17:18 nexus kernel: Call Trace: [<c01284a3>] [<c01299f1>] [<c013d8b9>] [<c0129d0f>] [<c011e38d>] [<c011e7ae>] [<c011eb5c>] Dec 3 01:17:18 nexus kernel: [<c011eaa8>] [<c012700e>] [<c0108bd4>] Dec 3 01:17:18 nexus kernel: Code: 8b 12 39 58 04 75 f3 39 70 08 75 ee 66 39 48 0c 75 e8 89 c2
Since it is my first oops, I have no idea what to do with it.
Another problem occurred when I tried to do "cdparanoia -d /dev/scd2 -g /dev/sg4 -Q" on a Mixed-Mode CD. The kernel paniced! Here is a short description of the hardware I use: P133 on a Gigabyte GA-586ATE, Adaptec AHA-2940UW Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: CONNER Model: CFP2105S 2.14GB Rev: 2D4D Type: Direct-Access ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: QUANTUM Model: FIREBALL_TM2110S Rev: 300X Type: Direct-Access ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: NEC Model: CD-ROM DRIVE:501 Rev: 2.2 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 03 Lun: 00 Vendor: SCSI-CD Model: ReWritable-2x2x6 Rev: 2.00 Type: CD-ROM ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: PLEXTOR Model: CD-ROM PX-6XCS Rev: 2.05 Type: CD-ROM ANSI SCSI revision: 02
So far everything worked fine under 2.0.36. I thought I it could be interesting for some kernel hackers.
Regards Martin -- Each new user of a new system uncovers a new class of bugs. -- Kernighan
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |