Ubuntu

display keyboard non-responsive

Bug #349671 reported by Chris Hermansen
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Running Jaunty Beta of 26 March 2009, twice very soon after boot the display has appeared to "freeze" and the keyboard and mouse do not seem to trigger any action (visible or audible). Fans are running. No obvious disk activity.

The first time was while trying to run the system testing module during the mouse test.

The second time was just after login while the wireless was trying to link up.

I had to power-cycle to recover.

This is on an older Toshiba A70 laptop with an ATI 9100 IGP video card and shared memory.

Other factors which may be related:
- no sign of any problems in syslog prior to power cycle
- suspend works but resume doesn't
- in Intrepid, usplash sometimes hangs during boot but boot is always OK with nosplash option
- the laptop has the following problem which used to be linked to random hang-ups in Gutsy
   .MP-BIOS bug: 8254 timer not connected to IO-APIC
   ...trying to set up timer (IRQ0) through the 8259A ...
   ..... (found apic 0 pin 2) ...
   ....... works.
- as the laptop is hung at the problem point and as there are no messages or crash reports
  upon re-boot, I can't say for sure what package the problem occurs in.

Revision history for this message
Chris Hermansen (c-hermansen) wrote :

Please see bug 350026 which I filed today and has apport info.

Revision history for this message
Chris Hermansen (c-hermansen) wrote :

More on this frozen display / keyboard / mouse problem in Jaunty Beta. System is up-to-date as of last night. Both yesterday morning and this morning the system hung just after login, in apparently the same way. I had to power cycle. In both cases this "fixed" the problem.

Also in both cases the wireless "two green LEDs" icon was "circulating" and stopped as the system hung.

Revision history for this message
Chris Hermansen (c-hermansen) wrote :

I should have added that there are no obvious signs of misbehaviour prior to the re-boot in syslog

Revision history for this message
David Tombs (dgtombs) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. If you could test the current Ubuntu version, this would help us a lot. Thanks.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.