From: Stas Sergeev <stsp@aknet.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-rc1-mm5 (and ide-cd)
Date: Mon, 15 Nov 2004 22:19:20 +0300 [thread overview]
Message-ID: <41990138.7080008@aknet.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
Hi.
There seem to be the grave bug in that
kernel. When either process is trying
to access the cdrom, it gets stuck in
the kernel forever. Even "eject" locks
up. This started to happen somewhere
around -mm4 I think. Specifying
"pci=routeirq" makes the kernel to
deadlock at boot, right after detecting
the cdrom. Sometimes there are the
"ide1: lost interrupt" messages on console.
Attached are the different bits of info
I found usefull for that report. It
includes the Alt-PrtSc-t trace and the
random info about my cdrom.
Any suggestions on getting this fixed?
This one is really severe I suppose.
[-- Attachment #2: trace --]
[-- Type: text/plain, Size: 1504 bytes --]
Nov 15 14:21:38 stas kernel: eject D C046C148 2500 3426 3363 (NOTLB)
Nov 15 14:21:38 stas kernel: db4c8cc4 00000086 c046c0b8 c046c148 db4c8dd0 db4c8ca4 c0290e9c c0290c90
Nov 15 14:21:38 stas kernel: 00001388 dfce797c c046c0b8 df778028 c046c148 00000000 db4c8cb4 c1405f60
Nov 15 14:21:38 stas kernel: 00068a1b 5a045780 000f420a df9a3c10 db4c8d48 db4c8d44 db4c8000 db4c8d18
Nov 15 14:21:38 stas kernel: Call Trace:
Nov 15 14:21:38 stas kernel: [<c031cee4>] wait_for_completion+0x94/0x100
Nov 15 14:21:38 stas kernel: [<c0285698>] ide_do_drive_cmd+0x118/0x150
Nov 15 14:21:38 stas kernel: [<c0291b44>] cdrom_queue_packet_command+0x44/0xb0
Nov 15 14:21:38 stas kernel: [<c02926a4>] cdrom_check_status+0x74/0x90
Nov 15 14:21:39 stas kernel: [<c029359d>] ide_cdrom_check_media_change_real+0x1d/0x40
Nov 15 14:21:39 stas kernel: [<c029616a>] media_changed+0x5a/0x90
Nov 15 14:21:39 stas kernel: [<c016a902>] check_disk_change+0x32/0x80
Nov 15 14:21:39 stas kernel: [<c02956db>] cdrom_open+0x6b/0x100
Nov 15 14:21:39 stas kernel: [<c02944fd>] idecd_open+0x5d/0x80
Nov 15 14:21:39 stas kernel: [<c016aad8>] do_open+0xe8/0x370
Nov 15 14:21:39 stas kernel: [<c016ae18>] blkdev_open+0x28/0x60
Nov 15 14:21:39 stas kernel: [<c0161a66>] dentry_open+0x156/0x280
Nov 15 14:21:39 stas kernel: [<c016190d>] filp_open+0x4d/0x50
Nov 15 14:21:39 stas kernel: [<c0161d4c>] sys_open+0x3c/0xa0
Nov 15 14:21:39 stas kernel: [<c0105175>] sysenter_past_esp+0x52/0x71
[-- Attachment #3: driver --]
[-- Type: text/plain, Size: 23 bytes --]
ide-cdrom version 4.61
[-- Attachment #4: model --]
[-- Type: text/plain, Size: 15 bytes --]
ASUS CD-S500/A
[-- Attachment #5: piix --]
[-- Type: text/plain, Size: 523 bytes --]
Controller: 0
Intel PIIX4 Ultra 100 Chipset.
--------------- Primary Channel ---------------- Secondary Channel -------------
enabled enabled
--------------- drive0 --------- drive1 -------- drive0 ---------- drive1 ------
DMA enabled: yes no yes no
UDMA enabled: yes no yes no
UDMA enabled: 5 X 2 X
UDMA
DMA
PIO
next reply other threads:[~2004-11-15 19:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 19:19 Stas Sergeev [this message]
[not found] ` <41990138.7080008-D1TkPCJej5s@public.gmane.org>
2004-11-23 6:09 ` Fw: ACPI bug causes cd-rom lock-ups (2.6.10-rc2) Len Brown
2004-11-23 6:09 ` Len Brown
2004-11-24 18:12 ` Stas Sergeev
2004-11-24 18:12 ` Stas Sergeev
[not found] ` <41A4CF1C.6090503-D1TkPCJej5s@public.gmane.org>
2004-11-24 22:44 ` Len Brown
2004-11-24 22:44 ` Len Brown
2004-11-25 18:18 ` Stas Sergeev
2004-11-25 18:18 ` Stas Sergeev
[not found] ` <41A621DD.8060102-D1TkPCJej5s@public.gmane.org>
2004-12-01 5:41 ` Len Brown
2004-12-01 5:41 ` [ACPI] " Len Brown
2004-12-01 5:44 ` Len Brown
2004-12-01 5:44 ` [ACPI] " Len Brown
2004-12-02 16:52 ` Stas Sergeev
2004-12-02 16:52 ` [ACPI] " Stas Sergeev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41990138.7080008@aknet.ru \
--to=stsp@aknet.ru \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.