System hangs on PandaBoard ES

Bug #1068079 reported by Stefan Arentz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-ti-omap4 (Ubuntu)
New
High
Unassigned

Bug Description

The last thing I see on the serial console is this:

... more of the same messages about omap-hdmi-audio-dai omap-hdmi-audio-dai ...
[ 388.953765] omap-hdmi-audio-dai omap-hdmi-audio-dai: >audio not supported
[ 388.960937] omap-hdmi-audio-dai omap-hdmi-audio-dai: >can't open interface omap-hdmi-audio-dai: -19
[ 3775.478820] logitech-djreceiver 0003:046D:C52B.0005: >can't reset device, ehci-omap.0-1.2.4/input2, status -71
[ 3775.493988] usb 1-1.2: >clear tt 1 (0060) error -71
[ 3775.499755] hid-generic 0003:04D9:4250.0001: >can't reset device, ehci-omap.0-1.2.1/input0, status -71
[ 3775.514007] usb 1-1.2: >clear tt 1 (0050) error -71
[ 3775.519836] logitech-djreceiver 0003:046D:C52B.0005: >can't reset device, ehci-omap.0-1.2.4/input2, status -71
[ 3775.534393] usb 1-1.2: >clear tt 1 (0060) error -71
[ 3775.539825] hid-generic 0003:04D9:4250.0002: >can't reset device, ehci-omap.0-1.2.1/input1, status -71
[ 3775.553955] logitech-djreceiver 0003:046D:C52B.0005: >can't reset device, ehci-omap.0-1.2.4/input2, status -71
[ 3775.564758] usb 1-1.2: >clear tt 1 (0050) error -71
[ 3775.574401] hid-generic 0003:04D9:4250.0001: >can't reset device, ehci-omap.0-1.2.1/input0, status -71
[ 3775.584442] usb 1-1.2: >clear tt 1 (0060) error -71
[ 3775.594024] logitech-djreceiver 0003:046D:C52B.0005: >can't reset device, ehci-omap.0-1.2.4/input2, status -71
[ 3775.604797] usb 1-1.2: >clear tt 1 (0050) error -71
[ 3775.610076] usb 1-1.2: >clear tt 1 (0060) error -19
[ 3775.619262] hid-generic 0003:04D9:4250.0002: >can't reset device, ehci-omap.0-1.2.1/input1, status -71
[ 3775.629302] usb 1-1.2: >clear tt 1 (0050) error -19
[ 3775.638610] hid-generic 0003:04D9:4250.0001: >can't reset device, ehci-omap.0-1.2.1/input0, status -71
[ 3775.648651] usb 1-1.2: >clear tt 1 (0050) error -19

The audio errors happen earlier and are probably not relevant.

The logitech-djreceiver could be my wireless mouse. I did unplug my keyboard from the PandaBoard earlier, which has a USB HUB and also a little Logitech receiver. Maybe this is a red herring.

What else can I report to give more details? Is there a way to break the kernel and find out where it is hanging? I'm willing to do some debugging.

Revision history for this message
Stefan Arentz (stefan-arentz-ca) wrote :

This is what my USB setup looks like:

stefan@pandaboard:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-omap3/3p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-omap/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/5p, 480M
        |__ Port 1: Dev 3, If 0, Class=vend., Driver=smsc95xx, 480M
        |__ Port 2: Dev 5, If 0, Class=hub, Driver=hub/4p, 480M
            |__ Port 1: Dev 6, If 0, Class=HID, Driver=usbhid, 1.5M
            |__ Port 1: Dev 6, If 1, Class=HID, Driver=usbhid, 1.5M
            |__ Port 4: Dev 7, If 0, Class=HID, Driver=usbhid, 12M
            |__ Port 4: Dev 7, If 1, Class=HID, Driver=usbhid, 12M
            |__ Port 4: Dev 7, If 2, Class=HID, Driver=usbhid, 12M
        |__ Port 3: Dev 4, If 0, Class=stor., Driver=usb-storage, 480M

Revision history for this message
Stefan Arentz (stefan-arentz-ca) wrote :

The USB thing might be a red herring. I just unplugged my keyboard/hub and wireless mouse receiver and I immediately see the messages from my first message. The system still works fine though. I can remote login and the clock is ticking on the screen.

Changed in linux-ti-omap4 (Ubuntu):
importance: Undecided → Critical
importance: Critical → High
Revision history for this message
Paolo Pisati (p-pisati) wrote :

do you have serial access to the board? and what did you do to trigger the hang?

Revision history for this message
Stefan Arentz (stefan-arentz-ca) wrote :

I do have serial access to the board. The kernel output that I posted earlier is all from the serial console.

I did not do anything specifically to trigger it. I basically let my PandaBoard idle for a while and then it usually hangs.

Right now it is hanging after I did the following:

Booted up, logged in.
Unplugged my keyboard + wireless mouse dongle
Switched my display from HDMI (PandaBoard) to DVI (my other machine)

... wait a day ...

Switched the display to HDMI
What I see now is Xscreensaver, but it hangs
PandaBoard is also not pingable
Nothing on Serial Console

Is there anything I can enable to get more diagnostic output on the serial port?

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.