© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
OK, I've been keeping quiet for a bit because we have had no changes with my girlfriend's laptop until now. On average, she will go three to five days without a hard-lock, but when she gets them, she will receive two or three hard-locks in succession. This is interesting to me, so I decided to probe a bit further. If her terminal is open she is sometimes able to gracefully reboot, but each character she types takes upwards of 30 seconds to appear on the screen. This last time, however, she was able to perform a 'ps -ef' to see what was running at the time of the crash. I'm including that file with this report. My attention quickly went to the entry for 'trackerd'. I have experienced problems with a sluggish, unresponsive system before when trackerd would run in Gutsy, so I am inclined to wonder if this could be the smoking gun for this system.
In other news, I just received a development box in one of the university labs. The machine had been running Fedora 8 for several months without a problem, but since it is mine, I wanted to start fresh with Hardy. I finished the install yesterday afternoon, and left the machine running all night; when I came in today it was still fine. About an hour ago, however, I experienced a crash. I was able to successfully run an Alt-SysReq-S and an Alt-SysReq-O, but otherwise the system was completely unresponsive. The system is a run-of-the-mill Dell Optiplex 745. I don't know enough about the hardware configuration to give too many details here, but I do know that there is positively no wireless support with this machine. I'm sure that the attached log files should give enough hardware info for a diagnosis...
I will attach all of the necessary files to the next comment. I hope this somewhat helpful. Again, my sympathies are with the developers who are trying to track down this difficult bug.
Thanks,
Travis