1 |
I think I found the reason for a long standing problem I've had with |
2 |
the machine locking up. |
3 |
|
4 |
I see no evidence of a cdrom link or device name in /dev. |
5 |
|
6 |
dmesg seems to show that it is recognized on boot, but I'm not smart |
7 |
enough to know what the lines from dmesg really mean: |
8 |
|
9 |
Just showing the key lines here but the full dmesg output can be views |
10 |
if so desired at this link: www.jtan.com/~reader/dmesg-101204.txt |
11 |
|
12 |
dmesg|grep -2 hdc |
13 |
|
14 |
[ 1.416847] hdb: UDMA/100 mode selected |
15 |
[ 1.417357] Probing IDE interface ide1... |
16 |
[ 2.089165] hdc: LITE-ON CD-ROM LTN-5291S, ATAPI CD/DVD-ROM drive |
17 |
[ 2.395008] hdd: WDC WD1600JB-00EVA0, ATA DISK drive |
18 |
[ 2.395666] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 |
19 |
[ 2.395835] hdc: UDMA/33 mode selected |
20 |
[ 2.396473] hdd: host max PIO4 wanted PIO255(auto-tune) selected PIO4 |
21 |
[ 2.397464] hdd: UDMA/100 mode selected |
22 |
-- |
23 |
[ 2.951543] hdd: hdd1 hdd2 < hdd5 hdd6 hdd7 hdd8 > |
24 |
[ 3.046492] ide-cd driver 5.00 |
25 |
[ 3.076761] ide-cd: hdc: ATAPI 52X CD-ROM drive, 96kB Cache |
26 |
[ 3.106578] Uniform CD-ROM driver Revision: 3.20 |
27 |
[ 3.142316] Intel(R) PRO/1000 Network Driver - version 7.3.21-k5-NAPI |
28 |
|
29 |
------- --------- ---=--- --------- -------- |
30 |
|
31 |
Where should I see evidence of the device being created... some output |
32 |
from udev I guess, but where to look for it and how to recognize what |
33 |
is happening regarding the creation of the device. |
34 |
|
35 |
I do collect a massive /var/log/debug.log by directing all syslog output |
36 |
into it in syslog.conf... but I still would like a clue to grep for. |
37 |
|
38 |
What I've found so far is massive quantities of lines like these: |
39 |
|
40 |
,---- |
41 |
| Dec 3 19:05:22 reader kernel: [14670.594825] hdc: status error: |
42 |
| status=0x00 { } |
43 |
| |
44 |
| Dec 3 19:05:22 reader kernel: [14670.594828] hdc: possibly failed |
45 |
| opcode: 0xa0 |
46 |
| |
47 |
| Dec 3 19:05:22 reader kernel: [14670.594831] ide-atapi: hdc: Strange, |
48 |
| packet command initiated yet DRQ isn't asserted |
49 |
`---- |
50 |
|
51 |
I think there are somekind of hardware problem with it since I cannot |
52 |
open it even when booting and in the first few moments after the cdrom |
53 |
light comes on. |
54 |
|
55 |
Sounds like it tries to open... I'm too chicken to force it though I |
56 |
have pried at it a bit, and stuck a wire in the hole. Maybe not deep |
57 |
enough but I haven't seen any good results of any of that yet. |
58 |
|
59 |
I'm thinking somewhere there has been output that if I were a little |
60 |
smarter I'd be able to tell what is happening when udev tries to |
61 |
create a device ... or if it does. |
62 |
|
63 |
I'm not even sure how that is supposed to work. |