PS. ignore the 'disable stack unwinding' at the beginning of the listing. It's just copy&paste mistake.
On 23 February 2014 23:30, Gregory Dymarek <[email protected]> wrote: > Gilles, > > I will give it a try with stack unwinding disabled and report back. > > Why I picked up this warning was because I mostly get kernel panics when > unplugging usb devices: > http://pastebin.com/uAhDGuzm > > I thought this is to do with the warning when booting the kernel. > > > > > On 23 February 2014 23:08, Adam Vaughan <[email protected]> wrote: > >> * I also missed that it was a warning. Sorry about that. >> >> >> On Sun, Feb 23, 2014 at 5:37 PM, Adam Vaughan <[email protected]> wrote: >> >>> I haven't tried using the official Xenomai Raspberry Pi 3.8.13 patch for >>> a few months now because I had some issue disabling the USB FIQ and I >>> needed to run alternate FIQ code. I can't remember exactly what error I >>> was seeing, but my stopgap solution was to fall back to 3.5.7 (detailed >>> below). I believe the USB FIQ disable issue I was seeing has been fixed in >>> more recent RPi kernels [1], but I haven't had a chance yet to try out that >>> patch with the Xenomai RPi 3.8.13 kernel. It is curious that your 3.8.13 >>> kernel log throws the exception at the same location just after the hub >>> detection as in [1] and involves the same USB code. Perhaps they're >>> related? >>> >>> If any kernel will work and you need to get up and going now, I had the >>> most success with the set of 3.5.7 patches at [2] (Google translate does a >>> good job translating the French, but it can also change acronyms in the >>> text such as RTDM to TDGR). I did, however, have occasional 3.5.7 kernel >>> crashes at ext4 code with two different SD cards which haven't occurred >>> again since moving to the 3.10.11 Raspian distro (I'm working on frontend >>> code right now, and it's just easier doing it with vetted binaries). These >>> infrequent crashes seemed to be associated with heavy file system accesses, >>> but it wasn't enough of issue that I needed to find a solution right then. >>> >>> [1] https://github.com/raspberrypi/linux/issues/355 >>> [2] >>> http://www.blaess.fr/christophe/2013/02/15/raspberry-pi-interruptions-gpio-avec-rtdm/ >>> >>> >>> On Sun, Feb 23, 2014 at 4:27 PM, Gregory Dymarek >>> <[email protected]>wrote: >>> >>>> Hi, >>>> >>>> >>>> I compiled a fresh rpi-3.8 kernel using the following patches (from >>>> xenomai-2.6.3): >>>> - ipipe-core-3.8.13-raspberry-pre-2.patch >>>> - ipipe-core-3.8.13-arm-3.patch >>>> - ipipe-core-3.8.13-raspberry-post-2.patch >>>> >>>> All compiled well, but when booting this kernel it reports an exception. >>>> The entire boot log is here: http://pastebin.com/K7v44nPw >>>> >>>> I am still not very faimiliar with the architecture so I am not really >>>> able >>>> to sort it myself... >>>> Any advise please? >>>> >>>> [ 1.915956] hub 1-0:1.0: 1 port detected >>>> [ 1.923672] ------------[ cut here ]------------ >>>> [ 1.931807] WARNING: at kernel/irq/handle.c:146 >>>> handle_irq_event_percpu+0x190/0x1b4() >>>> [ 1.943148] irq 32 handler usb_hcd_irq+0x0/0x7c enabled interrupts >>>> [ 1.952840] Modules linked in: >>>> [ 1.959469] [<c00141ec>] (unwind_backtrace+0x0/0xec) from >>>> [<c00204fc>] >>>> (warn_slowpath_common+0x4c/0x64) >>>> [ 1.972561] [<c00204fc>] (warn_slowpath_common+0x4c/0x64) from >>>> [<c0020544>] (warn_slowpath_fmt+0x30/0x40) >>>> [ 1.985872] [<c0020544>] (warn_slowpath_fmt+0x30/0x40) from >>>> [<c0077838>] >>>> (handle_irq_event_percpu+0x190/0x1b4) >>>> [ 1.999671] [<c0077838>] (handle_irq_event_percpu+0x190/0x1b4) from >>>> [<c00778c0>] (handle_irq_event+0x64/0x94) >>>> [ 2.013394] [<c00778c0>] (handle_irq_event+0x64/0x94) from >>>> [<c007a6c4>] >>>> (handle_level_irq+0x78/0x108) >>>> [ 2.026432] [<c007a6c4>] (handle_level_irq+0x78/0x108) from >>>> [<c0077010>] >>>> (generic_handle_irq+0x1c/0x30) >>>> [ 2.039690] [<c0077010>] (generic_handle_irq+0x1c/0x30) from >>>> [<c000eacc>] (handle_IRQ+0x30/0x84) >>>> [ 2.052361] [<c000eacc>] (handle_IRQ+0x30/0x84) from [<c008036c>] >>>> (__ipipe_do_sync_stage+0x25c/0x278) >>>> [ 2.065548] [<c008036c>] (__ipipe_do_sync_stage+0x25c/0x278) from >>>> [<c00083c4>] (__ipipe_grab_irq+0x2c/0x70) >>>> [ 2.079312] [<c00083c4>] (__ipipe_grab_irq+0x2c/0x70) from >>>> [<c0422d14>] >>>> (__irq_svc+0x34/0xc0) >>>> [ 2.091773] Exception stack(0xcd82de00 to 0xcd82de48) >>>> [ 2.100766] de00: f2980008 00000000 00000000 00000000 00000000 >>>> 00000000 >>>> cd99ec00 c05db7c4 >>>> [ 2.112995] de20: cd9ed380 c05bbfc0 c0523a7c c05db8a4 00000030 >>>> cd82de48 >>>> c02f947c c02f8e44 >>>> [ 2.125241] de40: 60000113 ffffffff >>>> [ 2.132818] [<c0422d14>] (__irq_svc+0x34/0xc0) from [<c02f8e44>] >>>> (dwc_otg_driver_probe+0x114/0x7e0) >>>> [ 2.146103] [<c02f8e44>] (dwc_otg_driver_probe+0x114/0x7e0) from >>>> [<c02aa504>] (really_probe+0x60/0x1e8) >>>> [ 2.159771] [<c02aa504>] (really_probe+0x60/0x1e8) from [<c02aa778>] >>>> (__driver_attach+0x98/0x9c) >>>> [ 2.172812] [<c02aa778>] (__driver_attach+0x98/0x9c) from >>>> [<c02a8b70>] >>>> (bus_for_each_dev+0x60/0x94) >>>> [ 2.186145] [<c02a8b70>] (bus_for_each_dev+0x60/0x94) from >>>> [<c02a9cb8>] >>>> (bus_add_driver+0xac/0x244) >>>> [ 2.199589] [<c02a9cb8>] (bus_add_driver+0xac/0x244) from >>>> [<c02aae20>] >>>> (driver_register+0x78/0x140) >>>> [ 2.213103] [<c02aae20>] (driver_register+0x78/0x140) from >>>> [<c05a0074>] >>>> (dwc_otg_driver_init+0x20/0xe0) >>>> [ 2.226973] [<c05a0074>] (dwc_otg_driver_init+0x20/0xe0) from >>>> [<c00086e0>] (do_one_initcall+0x114/0x180) >>>> [ 2.241020] [<c00086e0>] (do_one_initcall+0x114/0x180) from >>>> [<c058c86c>] >>>> (kernel_init_freeable+0xf8/0x1b8) >>>> [ 2.255236] [<c058c86c>] (kernel_init_freeable+0xf8/0x1b8) from >>>> [<c041c210>] (kernel_init+0x8/0x150) >>>> [ 2.268963] [<c041c210>] (kernel_init+0x8/0x150) from [<c000dc40>] >>>> (ret_from_fork+0x18/0x38) >>>> [ 2.282034] ---[ end trace 6e968ac9df7b1cbe ]--- >>>> [ 2.291589] dwc_otg: FIQ enabled >>>> _______________________________________________ >>>> Xenomai mailing list >>>> [email protected] >>>> http://www.xenomai.org/mailman/listinfo/xenomai >>>> >>> >>> >> > _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
