summaryrefslogtreecommitdiff
path: root/meta/recipes-kernel/sysprof/files
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2013-04-10 16:48:16 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-10 18:00:29 +0100
commitb7b7ebe57bd6fd248e80be0b7e517a3ceb7cfd11 (patch)
tree56f5d1a2aa8233641c75cb58973cf567bc267f6a /meta/recipes-kernel/sysprof/files
parent3d88f61b59f0a07e199306bf3a15ab023e77e17d (diff)
downloadopenembedded-core-b7b7ebe57bd6fd248e80be0b7e517a3ceb7cfd11.tar.gz
openembedded-core-b7b7ebe57bd6fd248e80be0b7e517a3ceb7cfd11.tar.bz2
openembedded-core-b7b7ebe57bd6fd248e80be0b7e517a3ceb7cfd11.zip
linux-yocto/3.8: qemumips graphical boot
Updating the meta SRCREV to fix and illegal instruction that is seen when launching X with USB pointing devices. meta/qemumips: build USB_UHCI_HCD into the kernel When booting qemumips and USB_UHCI_HCD built as a module, the following trace is seen, and then prevents X from starting: qemumips user.warn kernel: Call Trace: qemumips user.warn kernel: [<c0028000>] uhci_check_bandwidth+0x0/0x160 [uhci_hcd] qemumips user.warn kernel: [<c002e08c>] uhci_urb_enqueue+0xba4/0xc48 [uhci_hcd] qemumips user.warn kernel: [<8058092c>] usb_hcd_submit_urb+0xdc/0x848 qemumips user.warn kernel: [<805b8fbc>] wacom_open+0x44/0x8c qemumips user.warn kernel: [<805a1990>] input_open_device+0xac/0xec qemumips user.warn kernel: [<805a8cec>] evdev_open+0x188/0x1bc qemumips user.warn kernel: [<802331d8>] chrdev_open+0xc8/0x1c4 qemumips user.warn kernel: [<8022b338>] do_dentry_open+0x248/0x2e4 qemumips user.warn kernel: [<8022b418>] finish_open+0x44/0x68 qemumips user.warn kernel: [<8023e51c>] do_last.isra.29+0x2c0/0xcbc qemumips user.warn kernel: [<8023efd8>] path_openat+0xc0/0x52c qemumips user.warn kernel: [<8023f840>] do_filp_open+0x4c/0xbc qemumips user.warn kernel: [<8022cc3c>] do_sys_open+0x128/0x20c qemumips user.warn kernel: [<8010c07c>] stack_done+0x20/0x44 qemumips user.warn kernel: Code: (Bad address in epc) qemumips user.warn kernel: ---[ end trace 8a48c6046870f8c2 ]--- Building the module into the kernel fixes the problem, but the root cause is still under investigation. The pipelines around jumps to module addresses seem to be triggering invalid instructions. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-kernel/sysprof/files')
0 files changed, 0 insertions, 0 deletions