Red Hat Bugzilla – Bug 829425
unable to handle kernel NULL pointer dereference at 00000040 - kernel panic when using signotec sigma usb signature tablet
Last modified: 2012-09-12 12:37:59 EDT
Created attachment 589957 [details]
bug report created by abrt
Description of problem:
When fetching a signature from a signotec sigma signature tablet there is a high chance of a kernel panic on a fresh f17 live-usb boot. No such problem was found on a fresh f16 live-usb boot but an updated f16 install also shows this behaviour - as does an updated f17 install.
The application used for testing was their Java Demo which accesses a native linux .so (running as root or with udev 0666 rule for usb).
Version-Release number of selected component (if applicable):
The number of attempts needed to get a crash varies but after a few dozen
a kernel panic is a near certainty.
Steps to Reproduce:
1. boot fresh live
2. install java and signotec demo
3. run and fetch signature a few times
- this unfortunately requires the tablet
Created attachment 589958 [details]
Another backtrace of a crash
Created attachment 589959 [details]
another backtrace of a panic
Created attachment 590680 [details]
/var/log/messages of kernel 3.4.0-1.f17 problem
problem persists with new kernel update 3.4.0-1
As far as I can tell, there is no in-kernel driver for this device. It seems to have some kind of wrapper library to interface between the java demo and libusb, as you mentioned.
The crashes are all in very random areas with the exception that they all fail in allocating memory. You might try running a debug kernel by installing kernel-debug to see if that produces some more useful information. Additionally, you might try emailing this issue to the linux-usb mailing list. They might be able to help you more directly.
Hmm, something corrupts kmalloc (SLUB allocator) internal data. How does it happen, it's hard to tell from calltraces - corruption happens before that, or this is SLUB bug itself. If you install kernel-debug and try to reproduce the issue does it print some other WARNINGs/messages?
Do you have any logs from kernel-debug ?