WARNING: at /build/buildd/linux-ti-omap4-2.6.38/drivers/tty/tty_mutex.c:31 tty_lock 0x30/0x4c()

Bug #758961 reported by Tobin Davis
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-ti-omap4 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Image date is 20110412.

ProblemType: KernelOops
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-1207-omap4 2.6.38-1207.10
ProcVersionSignature: Ubuntu 2.6.38-1207.10-omap4 2.6.38
Uname: Linux 2.6.38-1207-omap4 armv7l
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: armel
Date: Tue Apr 12 09:53:50 2011
Failure: oops
SourcePackage: linux-ti-omap4
Title: WARNING: at /build/buildd/linux-ti-omap4-2.6.38/drivers/tty/tty_mutex.c:31 tty_lock+0x30/0x4c()
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Tobin Davis (gruemaster) wrote :
tags: added: iso-testing
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Tobin,
   I know in the past it has been relatively difficult to get collected data from these machines. Is that still the case here?

Thanks!

~JFo

Changed in linux-ti-omap4 (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Tobin Davis (gruemaster) wrote :

What specific data outside of the oops text would you like to see that the kernel developers working on this platform need? I can't produce lspci info or dmidecode data. I could add dmesg output (not sure why that is missing as the failure is during kernel boot before launching init).

Revision history for this message
Paolo Pisati (p-pisati) wrote :

i don't see it happens in latest natty or oneiric kernel

Paolo Pisati (p-pisati)
Changed in linux-ti-omap4 (Ubuntu):
status: New → Fix Released
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.