[RESUME 11.580s] Panel Crashes

Bug #466118 reported by Robert Anderson
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Sorry, I'm a Linux newbee but here it goes. After upgrading to 9.10 Panel does not completely load at boot. The Desktop icon and trash appear on the bottom bar and work. Only Applications, Places, System and the Firefox, Evolution Mail icon and Help icon appear. None of these work or display any further drop down menus. Nothing else ever loads to right side of panel. No date, time, sound, network, or even name/logoff/poweroff icon. I have to push the power button on the PC to select shut down, log off etc.. From here when it goes to shut down a new window appears telling me Panel has crashed. This has happened on 3 of my 5 power ups since upgrading to the new distro.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rob 1614 F.... pulseaudio
 /dev/snd/controlC1: rob 1614 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Live'/'SB Live! Value [CT4780] (rev.8, serial:0x80221102) at 0xc800, irq 19'
   Mixer name : 'Cirrus Logic CS4297A rev 4'
   Components : 'AC97a:43525914'
   Controls : 221
   Simple ctrls : 42
Card1.Amixer.info:
 Card hw:1 'U0x46d0x8ca'/'USB Device 0x46d:0x8ca at usb-0000:00:1d.7-4, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:08ca'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined
   Capture channels: Mono
   Limits: Capture 0 - 3072
   Mono: Capture 3072 [100%] [18.00dB] [on]
Date: Fri Oct 30 23:21:24 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=1de4f208-3c33-458d-9c6f-2234c5faf239
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Micro-Star Inc. MS-6566E
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: root=UUID=724c7d75-a621-4f0e-9c60-ff8202dbfe68 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/kernel/power/suspend_test.c:52 suspend_test_finish+0x80/0x90()
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:

dmi.bios.date: 04/02/01
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 07.00T
dmi.board.name: MS-6566E
dmi.board.vendor: Micro-Star Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0123ABC
dmi.chassis.type: 3
dmi.chassis.vendor: Uknown Chassis Manufacture
dmi.chassis.version: Version 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr07.00T:bd04/02/01:svnMicro-StarInc.:pnMS-6566E:pvr1.0:rvnMicro-StarInc.:rnMS-6566E:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00:
dmi.product.name: MS-6566E
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star Inc.

Revision history for this message
Robert Anderson (rob503) wrote :
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Robert,

The warning reported here typically indicates that it took longer for your system to resume from suspend than expected. I believe there is a 5 sec barrier which your system likely exceeded. Based on your dmesg output I see PM: resume devices took 11.580 seconds. I'm setting this to traiged for further investigation. Thanks!

[This is an automated message. Apologies if it has reached you inappropriately.]

tags: added: suspend-test-finish
Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Robert Anderson (rob503) wrote :

I have a couple questions about this being a "resume issue".

This issue always occurred on initial boot. Never made it to a point where the system entered resume mode. I ended up resolving the issue by the following:

   1. Booted in Recovery Mode to update packages. This worked for 1 boot and then same constant boot up "panel no responding" error error would occur.
   2. Doing a google search found did the following:
         1. kill gnome-panel
         2. had to rm the gnome related folders.

After this the system has booted flawlessly every time. Only noticeable change is my wired icon on the panel changed from a female ethernet connector to two diagonal cable plugged into each other.

Hope to get the laptops behaving now. Sony Vio PCG-F560 Couldn't report errors from Gnome and XFCE, it tried but window popped back saying system was unstable and could not report error. Thinkpad T20 much more stable. On shutdown linux closes out but fails to power down laptop.

Anyway thanks for looking into the above issue, I'll try to copy this into the forum.

Thanks Again,

Rob Anderson

Revision history for this message
Robert Anderson (rob503) wrote : Re: [Bug 466118] Re: Panel Crashes
Download full text (5.0 KiB)

I have a couple questions about this being a "resume issue".

This issue always occurred on initial boot. Never made it to a point where the system entered resume mode. I ended up resolving the issue by the following:

    1. Booted in Recovery Mode to update packages. This worked for 1 boot and then same constant boot up "panel no responding" error error would occur.
    2. Doing a google search found did the following:

        1. kill gnome-panel
        2. had to rm the gnome related folders.

After this the system has booted flawlessly every time. Only noticeable change is my wired icon on the panel changed from a female ethernet connector to two diagonal cable plugged into each other.

Hope to get the laptops behaving now. Sony Vio PCG-F560 Couldn't report errors from Gnome and XFCE, it tried but window popped back saying system was unstable and could not report error. Thinkpad T20 much more stable. On shutdown linux closes out but fails to power down laptop.

Anyway thanks for looking into the above issue, I'll try to copy this into the forum.

Thanks Again,

Rob Anderson

----- Original Message -----
From: "Leann Ogasawara" <email address hidden>
To: <email address hidden>
Sent: Monday, November 2, 2009 5:44:28 PM GMT -08:00 US/Canada Pacific
Subject: [Bug 466118] Re: Panel Crashes

Hi Robert,

The warning reported here typically indicates that it took longer for
your system to resume from suspend than expected. I believe there is a
5 sec barrier which your system likely exceeded. Based on your dmesg
output I see PM: resume devices took 11.580 seconds. I'm setting this
to traiged for further investigation. Thanks!

[This is an automated message. Apologies if it has reached you
inappropriately.]

** Tags added: suspend-test-finish

** Changed in: linux (Ubuntu)
Status: New => Triaged

** Changed in: linux (Ubuntu)
Importance: Undecided => Medium

--
Panel Crashes
https://bugs.launchpad.net/bugs/466118
You received this bug notification because you are a direct subscriber
of the bug.

Status in “linux” package in Ubuntu: Triaged

Bug description:
Sorry, I'm a Linux newbee but here it goes. After upgrading to 9.10 Panel does not completely load at boot. The Desktop icon and trash appear on the bottom bar and work. Only Applications, Places, System and the Firefox, Evolution Mail icon and Help icon appear. None of these work or display any further drop down menus. Nothing else ever loads to right side of panel. No date, time, sound, network, or even name/logoff/poweroff icon. I have to push the power button on the PC to select shut down, log off etc.. From here when it goes to shut down a new window appears telling me Panel has crashed. This has happened on 3 of my 5 power ups since upgrading to the new distro.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: rob 1614 F.... pulseaudio
/dev/snd/controlC1: rob 1614 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Live'/'SB Live! Value [CT4780] (rev.8, ser...

Read more...

Revision history for this message
Bubba (kprohn) wrote : Re: Panel Crashes

Does anyone, besides me think that these 10 bugs are related? They affect at least 27 people.

454794
466118
474495
476251
482690
483090
496714
499054
500958
500962

All of them mention that their upper gnome-panel freezes intermittently on boot with some visible app icons, but no response to any mouse manipulation.

I had this trouble on my primary pc immediately after upgrading to 9.10. I finally had to do a clean reinstall of 9.04 and reload my backup files. I have been very satisfied with 9.04 Jaunty.

 I can replicate this bug almost at will on my “test pc” on which I did a clean install of 9.10.

 Searching all the other bugs the best method that I have found for recovery from the frozen panel is to access a terminal Ctl-Alt-F1 and execute;

 $ killall gnome-panel

The next step is to return to the desktop Ctl-Alt-F7 . I find that there will be no visible app icons on the panels, but they are present and in “stealth” mode. Invisible but functional. They will respond to mouse manipulation. To make the apps reappear I open a “Run application” window with Alt-F2.** See note below.
Then execute the command;

 $ gnome-panel --replace

My panels are now fully functional, except the weather apps are missing. I have found that I can even add new apps at this time, but not weather report or disk mounter apps.

** It is important that this command is not run in an open terminal. The procedure will work and then hang in the terminal window. When the terminal window is closed, all panels will disappear and I am left with an unusable desktop requiring another reboot.

I am quite new at this, but enjoy working at it. I am willing to provide whatever assistance I can to help fix this.

Andy Whitcroft (apw)
summary: - Panel Crashes
+ [RESUME 11.580s] Panel Crashes
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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