1 |
Alan McKinnon <alan.mckinnon@×××××.com> writes: |
2 |
|
3 |
> On Wednesday 17 February 2010 00:36:42 Harry Putnam wrote: |
4 |
>> Hundreds, maybe thousands of lines like this (wrapped for mail): |
5 |
>> |
6 |
>> Feb 16 09:38:47 reader kernel: [162289.090685] usb 4-2.1:1.1: uevent |
7 |
>> |
8 |
>> Feb 16 09:38:48 reader kernel: [162289.467065] hdc: status error: |
9 |
>> status=0x00 { } |
10 |
>> |
11 |
>> Feb 16 09:38:48 reader kernel: [162289.467071] hdc: possibly failed |
12 |
>> opcode: 0xa0 |
13 |
>> |
14 |
>> Feb 16 09:38:48 reader kernel: [162289.467079] ide-atapi: hdc: |
15 |
>> Strange, packet command initiated yet DRQ isn't asserted |
16 |
>> |
17 |
>> When I noticed this output involving the cdrom I wondered if I might |
18 |
>> have left something in it but that was not the case. |
19 |
> |
20 |
> Do you have hal configured to poll your cdrom drive every two seconds, to see |
21 |
> if a disk is inserted? And if so, is the verbosity logging cranked up way |
22 |
> higher than it should be? |
23 |
> |
24 |
> I haven't personally had to fix this myself (so can't give pointers on where |
25 |
> to fix it), but it seems to be a common occurrence judging from posts I see |
26 |
> here and at other forums. |
27 |
|
28 |
I do have hald running, but made no special config regarding cdrom |
29 |
polling. At least not on purpose. |
30 |
|
31 |
The messages do appear to be continuous. I will execute a reboot soon |
32 |
but don't want to right now. |
33 |
|
34 |
Why I'm pondering and following this up, is that I experience a |
35 |
serious freeze after some unspecified amount of uptime. Mouse and |
36 |
keyboard become unresponsive... and eventually the OS cannot be |
37 |
accessed at all. |
38 |
|
39 |
SSH appears to stop and cannot contact remotely either. |
40 |
|
41 |
This began happening quite some time ago... on a different earlier |
42 |
install. I never could see anything in the logs that gave a clue to |
43 |
why. |
44 |
|
45 |
I created a script that ran from cron. It pinged a remote host, and |
46 |
logged a unique easily findable string into the log using `logger', |
47 |
every 5 minutes. With that I was able to narrow down the time frame |
48 |
of freeze to within the last 5 minutes (of log lines). |
49 |
|
50 |
Even then, there was nothing to indicate a problem. This was an OS |
51 |
that had been running a very long time with upgrade after upgrade. |
52 |
|
53 |
Though I hated having to rebuild all the customizations etc, I finally |
54 |
completely reinstalled from scratch hoping to catch the problem with |
55 |
the shotgun approach. |
56 |
|
57 |
In that earlier OS there were no log messages regarding hdc being |
58 |
generated (by the way). |
59 |
|
60 |
Shortly after completing the new install and a couple of weeks of |
61 |
getting setup the way I wanted, I began to experience the freezes |
62 |
again. |
63 |
|
64 |
I have caught the freeze in the early stages before completely losing |
65 |
the network when just mouse and keyboard became unresponsive, was able |
66 |
to ssh in and noticed that restarting hald held off the freeze for |
67 |
some (again unspecified) amount of time. |
68 |
|
69 |
So cutting the lengthy narrative down a bit, and briefly put, I'm |
70 |
looking for anything unusual that is causing this. The hdc messages |
71 |
is the only odd thing I'm seeing. |
72 |
|
73 |
Something appears to be jamming up the hal layer somehow, but not |
74 |
leaving findable tracks. At least not findable by an someone with |
75 |
many yrs experience with linux but not much real debugging of |
76 |
complicated problems under his belt. |