Kernel panic with docking station

Bug #319968 reported by Giampiero Salvi
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I saw this bug before on the ubuntu forum, but I read it was fixed in my kernel version (2.6.28). Here are the scenarios:

1) I start on the docking station and everything is fine.
   I] I press the undock button and lift the laptop -> kernel panic, need to disconnect the battery
   II] I press the undock button and disable the gigabit network card in the station with
       echo 0 >/sys/bus/pci/slots/4/power
       then it works to lift the laptop, BUT if I hibernate (undocked) and resume the laptop (undocked) I get the kernel panic again

2) I start the laptop undocked
    I] If I dock it it seems to work (I don't recall if it finds the network card)
    II] If I hibernate undocked and resume in the docking station -> kernel panic

I believe you get all the relevant technical info from the crash report program.
Thanks,
Giampiero

ProblemType: KernelOops
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
FlagFile: hibernate

InterpreterPath: /usr/bin/python2.5
OopsText: Suspend/Resume or hibernate problem

Originator: Steve Conklin <email address hidden>
Package: linux-image-2.6.28-4-generic 2.6.28-4.11
ProcAttrCurrent: unconfined
ProcCmdLine: User Name=UUID=ad35a164-92ec-42de-b89e-5d3462dc325b ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-4.11-generic
SourcePackage: linux
Tags: suspend resume hibernate
Title: Suspend/Resume or hibernate problem
UserGroups:

Revision history for this message
Giampiero Salvi (giampisalvi) wrote :
description: updated
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks Giampiero,

Would you be able to capture and attach the kernel panic you are seeing? Even if you have to take a digital photo of your screen with the panic and attach it to the bug report that would be great. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Giampiero Salvi (giampisalvi) wrote :

Hi,
I can take a picture/video tomorrow (the docking station is in my office). From what I recall, I see the Ubuntu splash screen with the progress bar that stops progressing and the num lock and caps lock (?) start blinking. This is the same behaviour that was reported in an earlier bug. After that only disconnecting the battery works.

Giampiero

Revision history for this message
Giampiero Salvi (giampisalvi) wrote :

This is the on of the previous bug reports I was referring to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/163211
The only reason why I started a new one (besides the claim that the bug was solved after a certain version of the kernel, which isn't true for me), is because I was following the instruction of the crash report program that started the next time I successfully booted the machine.

Giampiero

Revision history for this message
Andy Whitcroft (apw) wrote :

@Giampiero -- the apport program does call this a crash which it really isn't. It is a hibernate/resume failure. If you didn't see a specific panic then it is likley this is only reporting that you hibernated and then that was not resume before the machine next was booted normally.

If you are seeing a flashing keyboard lights that does imply a panic, if that is occuring with the usplash progress bar on the screen you can remove that by removing usplash from the kernel command line before resuming.

Andy Whitcroft (apw)
Changed in linux:
status: Incomplete → In Progress
status: In Progress → Incomplete
Revision history for this message
kernel-janitor (kernel-janitor) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.