2.6.14.5: segfault / oops with ide-scsi
- From: Grant Coady <grant_lkml@xxxxxxxxxxx>
- Date: Sun, 01 Jan 2006 08:44:30 +1100
Hi there,
Got this, trying to mount CDROM on a troublesome box I've not had
for long, Intel ICH 801 / 810 -- this with "hdc=ide-scsi":
root@niner:~# mount /dev/sr0 /mnt/cdrom/
mount: you must specify the filesystem type
root@niner:~# mount -t iso9660 /dev/sr0 /mnt/cdrom/
mount: /dev/sr0 is not a valid block device
root@niner:~# mount -t iso9660 /dev/sg0 /mnt/cdrom/
mount: /dev/sg0 is not a block device
root@niner:~# mount -t iso9660 /dev/hdc /mnt/cdrom/
Segmentation fault
Even if this be finger trouble, it should not oops?
Jan 1 08:29:15 niner kernel: ide-scsi is deprecated for cd burning! Use ide-cd and give dev=/dev/hdX as device
Jan 1 08:30:02 niner kernel: ide-scsi: unsup command: dev hdc: flags = REQ_CMD REQ_STARTED
Jan 1 08:30:02 niner kernel: sector 64, nr/cnr 2/2
Jan 1 08:30:02 niner kernel: bio c9e095e0, biotail c9e095e0, buffer c7feb000, data 00000000, len 0
Jan 1 08:30:02 niner kernel: end_request: I/O error, dev hdc, sector 64
Jan 1 08:30:02 niner kernel: isofs_fill_super: bread failed, dev=hdc, iso_blknum=16, block=32
Jan 1 08:30:02 niner kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Jan 1 08:30:02 niner kernel: printing eip:
Jan 1 08:30:02 niner kernel: c01d9206
Jan 1 08:30:02 niner kernel: *pde = 00000000
Jan 1 08:30:02 niner kernel: Oops: 0000 [#1]
Jan 1 08:30:02 niner kernel: Modules linked in: isofs zlib_inflate ide_scsi e100 3c59x
Jan 1 08:30:02 niner kernel: CPU: 0
Jan 1 08:30:02 niner kernel: EIP: 0060:[<c01d9206>] Not tainted VLI
Jan 1 08:30:02 niner kernel: EFLAGS: 00010246 (2.6.14.5a)
Jan 1 08:30:02 niner kernel: EIP is at get_kobj_path_length+0x26/0x40
Jan 1 08:30:02 niner kernel: eax: 00000000 ebx: 00000000 ecx: ffffffff edx: c91a826c
Jan 1 08:30:02 niner kernel: esi: 00000001 edi: 00000000 ebp: ffffffff esp: c7f9fdcc
Jan 1 08:30:02 niner kernel: ds: 007b es: 007b ss: 0068
Jan 1 08:30:02 niner kernel: Process mount (pid: 547, threadinfo=c7f9f000 task=c8fe2090)
Jan 1 08:30:02 niner kernel: Stack: c117c520 c927c200 ffffffea c91a826c c01d929f c91a826c 00000282 c7f65e14
Jan 1 08:30:02 niner kernel: 00000000 c117c520 c927c200 ffffffea 00000000 c01d9be8 c91a826c 000000d0
Jan 1 08:30:02 niner kernel: 00000020 00000064 fffffff4 c117c520 c927c200 ffffffea c7fd1000 c01d9cf8
Jan 1 08:30:02 niner kernel: Call Trace:
Jan 1 08:30:02 niner kernel: [<c01d929f>] kobject_get_path+0x1f/0x80
Jan 1 08:30:02 niner kernel: [<c01d9be8>] do_kobject_uevent+0x28/0x110
Jan 1 08:30:02 niner kernel: [<c01d9cf8>] kobject_uevent+0x28/0x30
Jan 1 08:30:02 niner kernel: [<c0158f0e>] bdev_uevent+0x2e/0x50
Jan 1 08:30:02 niner kernel: [<c01590a6>] kill_block_super+0x26/0x50
Jan 1 08:30:02 niner kernel: [<c01584a6>] deactivate_super+0x56/0x70
Jan 1 08:30:02 niner kernel: [<c0159051>] get_sb_bdev+0x121/0x150
Jan 1 08:30:02 niner kernel: [<c0168cd3>] dput+0x33/0x180
Jan 1 08:30:02 niner kernel: [<ca926fe0>] isofs_get_sb+0x30/0x40 [isofs]
Jan 1 08:30:02 niner kernel: [<ca925cd0>] isofs_fill_super+0x0/0x6e0 [isofs]
Jan 1 08:30:02 niner kernel: [<c015928f>] do_kern_mount+0x5f/0xe0
Jan 1 08:30:02 niner kernel: [<c016de6c>] do_new_mount+0x9c/0xe0
Jan 1 08:30:02 niner kernel: [<c016e457>] do_mount+0x157/0x1b0
Jan 1 08:30:02 niner kernel: [<c016e2a3>] copy_mount_options+0x63/0xc0
Jan 1 08:30:02 niner kernel: [<c016e84a>] sys_mount+0x9a/0xe0
Jan 1 08:30:02 niner kernel: [<c0102fd9>] syscall_call+0x7/0xb
Jan 1 08:30:02 niner kernel: Code: 90 8d 74 26 00 55 bd ff ff ff ff 57 56 be 01 00 00 00 53 8b 54 24 14 31 db 8d b6 00 00 00 00 8d bf 00 00 00 00 8b 3a 89 e9 89 d8 <f2> ae f7 d1 49 8b 52 24 8d 74 31 01 85 d2 75 ea 5b 89 f0 5e 5f
Box info" http://bugsplatter.mine.nu/test/boxen/niner/
Prior to adding the "hdc=ide-scsi" to lilo, the box is able to
boot from cdrom, then cannot read the cdrom. Trying to mount it
results in many of these in syslog:
Jan 1 08:14:12 niner kernel: hdc: attached ide-cdrom driver.
Jan 1 08:15:25 niner kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 1 08:15:25 niner kernel: hdc: command error: error=0x52
Jan 1 08:15:25 niner kernel: end_request: I/O error, dev 16:00 (hdc), sector 0
Jan 1 08:15:25 niner kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 1 08:15:25 niner kernel: hdc: command error: error=0x52
Jan 1 08:15:25 niner kernel: end_request: I/O error, dev 16:00 (hdc), sector 4
Jan 1 08:15:25 niner kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error }
Jan 1 08:15:25 niner kernel: hdc: command error: error=0x52
Jan 1 08:15:25 niner kernel: end_request: I/O error, dev 16:00 (hdc), sector 0
What next?
Thanks,
Grant.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Prev by Date: Re: [PATCH 1 of 3] Introduce __memcpy_toio32
- Next by Date: Re: system keeps freezing once every 24 hours / random apps crashing
- Previous by thread: Re: Why can setuid programs regain root after dropping it when using capabilities?
- Next by thread: [PATCH 0/4] stradis video driver rewritten to 2.6 pci api
- Index(es):
Relevant Pages
- Re: SUCCESS AT LAST
... >> "If the game wants to run from the CD, then your problem is that you ...
>> not mount the CDROM drive in the .conf file or manually. ... guess you
have to do two separate lines for the two drives.. ... (comp.sys.ibm.pc.games.adventure) - Re: cant mount drive
... > through the driver that runs the device. ... > mulfunctioning or something
else is fixing itself on the cdrom. ... When I bootup it is giving an error of mount
fd type ro is not ... The author of cdrecord should not be bothered with problems in ...
(Fedora) - cannot mount cdrom!
... This is a normal ATAPI IDE cdrom drive, ... This is what happens when I try
to mount ... Uniform CD-ROM driver Revision: 3.20 ... hdc: command
error: status=0x51 ... (Debian-User) - Re: SUCCESS AT LAST
... >> not mount the CDROM drive in the .conf file or manually. ...
>> where you put the correct drive letter for your system." ... (comp.sys.ibm.pc.games.adventure) - Re: SUCCESS AT LAST
... "If the game wants to run from the CD, then your problem is that you did not mount
the CDROM drive in the .conf file or manually. ... I guess in your example above,
you are saying if E was the hard drive you were installing the game on, and using f: as a Cdrom,
you would type the above. ... (comp.sys.ibm.pc.games.adventure)