Messages in this thread | | | Date | Thu, 15 Jul 1999 22:21:11 +0200 (CEST) | From | Bert Lindner <> | Subject | [BUGREPORT] 2.2.10-ac10: oops+panic when interrupting cdrecord session |
| |
Interrupting a burning session (laser on AND laser off/dummy mode) with cdrecord on 2.2.10-ac10, I think ac9 also, reproducably leads to a kernel oops and panic on my box.
The only way to interrupt without causing an oops seems to be to kill the cdrecord sub-process which fills the fifo buffer (I think this is cdrecord's fifo but it might be the recorder's), and to kill the 'main' cdrecord session only after the fifo has emptied.
My machine normally never crashes. An uninterrupted burning session is just fine.
linux 2.2.10-ac10 cdrecord release 1.8a23
scsi adapter info (from /proc/scsi/sym53c8xx/0): -- General information: Chip sym53c860, device id 0x6, revision id 0x2 IO port address 0xec00, IRQ number 11 Using memory mapped IO at virtual address 0xc4827f00 Synchronous period factor 12, max commands per lun 32 -- As you can see the driver used is sym53c8xx (in module form).
scsi device info (from /proc/scsi/scsi): -- Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: QUANTUM Model: FIREBALL1280S Rev: 630C Type: Direct-Access ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: PLEXTOR Model: CD-R PX-W4220T Rev: 1.02 Type: CD-ROM ANSI SCSI revision: 02 --
There is also one IDE drive in my system.
cd-recorder info (from cdrecord -inq): -- scsidev: '/dev/sg1' devname: '/dev/sg1' scsibus: -2 target: -2 lun: -2 Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : SYNC LINKED Vendor_info : 'PLEXTOR ' Identifikation : 'CD-R PX-W4220T' Revision : '1.02' Device seems to be: Generic mmc CD-RW. --
system info (from /usr/src/linux/scripts/ver_linux): -- Linux yenzi 2.2.10-ac10 #3 Tue Jul 13 19:21:07 CEST 1999 i686 unknown Kernel modules 2.1.121 Gnu C egcs-2.91.66 Binutils 2.8.1.0.23 Linux C Library 5.4.46 Dynamic linker ldd: version 1.9.9 Procps 2.0.2 Mount 2.7l Net-tools 1.51 Kbd 0.94 Sh-utils 1.16 Modules Loaded sg ip_masq_portfw ip_masq_quake ip_masq_raudio ip_masq_ftp opl3 cs4232 uart401 ad1848 sound soundcore sym53c8xx sd_mod scsi_mod --
Info on the screen after the system crashed (no response whatsover, not even with Alt-Fx or NumLock). I handwrited it on a piece of paper so pardon any typo's. Note that cdrecord says there are still 8 seconds to go before the write starts. The oops also happens when writing has already started, and also, like I already mentioned, in 'real', not dummy, write mode. -- Starting to write CD/DVD at speed 4 in dummy mode for single session. Last chance to quit, starting dummy write in 8 seconds. cdrecord: Interrupted system call. Cannot send SCSI cmd via ioctl [bert@yenzi:~/brandbaar] $ [bert@yenzi:~/brandbaar] $ [bert@yenzi:~/brandbaar] $ Unable to handle kernel paging request at virtual address 5a5a5a5a current -> tss.cr3 = 00101000, %cr3 = 00101000 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<c0110338>] EFLAGS: 00010887 eax: c0347808 ebx: 5a5a5a5a ecx: 00000001 edx: 00000001 esi: c0347804 edi: 00000001 ebp: c01cdeb4 esp: c01cdeb0 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, process nr: 0, stackpage = c01cd000) stack: c3818c00 c18fa158 c485f178 c3fd4420 c485ef5c 00000eea c01cdefc 00000001 c48107d3 c3818c00 00000000 00000286 c3818c00 00000246 00000000 c01dcf68 00000000 00000000 c3fd4400 c01cdf68 c4820d6d c3818c00 c3ff9f60 04000001 Call Trace: [<c485f178>] [<c485ef5c>] [<c48107d3>] [<c4820d6d>] [<c0109f69>] \ [<c0109cbf>] [<c01175d5>] [<c010a08c>] [<c0109d08>] [<c01077ad>] [<c0106000>] [<c01077d0>] \ [<c0108ec8>] [<c0106000>] [<c010607b>] [<c0106000>] [<c0100177>] Code: 8b 13 8b 5b 04 8b 02 85 c7 74 f1 39 f3 74 09 89 d0 e8 3e f9 Aiee, killing interrupt handler Kernel panic: Attemted to kill the idle task! In swapper task - not syncing. --
Hope this helps, I'm not on linux-kernel, for more information don't hesitate to mail me: bert@box.balpol.tudelft.nl .
Regards and thanks for linux,
-Bert.
- 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/
| |