No crash when idle so far, but it did blow up quite spectacularly after I did
the following:
1. Booted 12.04 beta from USB stick
2. Installed lirc, configured lirc for generic Windows Media remote with no
transmitter
3. Unplugged IR dongle
Unfortunately, I was not able to record the error messag
Hmm...looks like testing on the E-350 machine is currently a no-go. The
version of XBMC I have on there depends on FGLRX, and since it's what
uses the IR dongle, I'm not sure the problem will happen without it
running. Besides, I don't want to go to the trouble of removing FGLRX
(I seriously doub
I think this is related to AMD hardware. I just got a new AMD E-350
machine, which has had some mysterious crashes with the 3.0.0-16-generic
x86_64 kernel. After disconnecting the IR dongle, it has gone nearly 24
hours without a crash. Annoyingly, I haven't been able to get a proper
backtrace be
Would it be possible for you to test the latest upstream kernel? It
will allow additional upstream developers to examine the issue. Refer to
https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test
the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once
you've tested
The usb device in question:
1784:0008 TopSeed Technology Corp. eHome Infrared Transceiver
I will try this out on an 11.10 machine and see if I get any oopses
there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891890
Title:
Kernel oops when accessing file in sysfs
To manage notifications about this
Yep, it looks like the USB IR remote control device is to blame. I just
confirmed that no file or directory called rc0 exists in /sys until I
plug in the USB IR device. I got the same kernel oops immediately upon
unplugging the device.
--
You received this bug notification because you are a mem
Judging by the presence of "usb" and "rc", I suspect my USB remote
control device may be to blame. I will do a bit more investigation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891890
Title:
Ke
** Attachment added: "kernel oops message"
https://bugs.launchpad.net/bugs/891890/+attachment/2600386/+files/kernel-oops.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891890
Title:
Kernel oo
