imx51 oops after watchdog call

[Oliver Grawert]

several networking probs on imx51 made me look at dmesg output and showed an oops directly after the watchdog call on eth0

ProblemType: Bug
Architecture: armel
DistroRelease: Ubuntu 9.04
Lspci:
 Error: command ['lspci', '-vvnn'] failed with exit code 1: pcilib: Cannot open /proc/bus/pci
 lspci: Cannot find any working access method.
Package: linux-image-2.6.28-11-imx51 2.6.28-11.40
ProcCmdLine: root=UUID=f1421717-c4ee-4b4a-a263-7e366147ae5a ro quiet
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.40-imx51
SourcePackage: linux

[Brad Figg (brad-figg)]

Were there specific steps taken which cause this oops to occure?

[Oliver Grawert (ogra)]

NM was compiled in a way that it doesnt ignore virtual devices (our eth0 isnt attched to USB or PCI, so NM currently ignores it)... after enabling support for devices attached to teh virtual bus in hal (bug 356517) the oops showed up.

running "sudo ifconfig eth0 up" and "sudo dhclient eth0" in a terminal doesnt seem to trigger it. i assume that hal or NM try to additionally request info from the watchdog if they handle the device which then causes the oops.

[Brad Figg (brad-figg)]

I've not been able to reproduce this. However, looking at similar bugs reported upstream (there are several) it looks like this oops generally point to driver in various drivers.

[Oliver Grawert (ogra)]

given that it only shows up if the device is used by NM and a fix for bug 356517 is pending upload it should be reproducable soon.

[Oliver Grawert (ogra)]

i'm seeing the very same issue on karmic during alternate installation, bringing up the network needs about 5-10 attempts, then teh watchdog warning appaears in dmesg and networking starts to function just fine.

opening a task for linux-fsl-imx51 (since thats what we use in karmic)

[Bryan Wu (cooloney)]

Do we still meet this bug in Lucid?

[Steve Langasek (vorlon)]

Package not in natty.

Does this bug affect karmic, lucid versions of linux-fsl-imx51?