Hide Forgot
Created attachment 505715 [details] F15 x86_64 panic Description of problem: Dell Precision M6600 with built-in DuoSense N-trig multitouch digitizer. When booting any F15 kernel (i686/x86_64), after detection of the N-trig device, the kernel panics in the 'ntrig_event' : "BUG : unable to handle kernel NULL pointer dereference at 0000000000000018". This renders installation of F15 impossible (hence severity -> urgent). Version-Release number of selected component (if applicable): - All F15 kernels (tested with 2.6.38.6-26.rc1.fc15.x86_64 and 2.6.38.8-33.fc15.i686) - All F14 kernels (tested with 2.6.35.13-93.fc14.i686) How reproducible: Always Steps to Reproduce: Boot F14/F15 installation medium --> kernel panic. Additional info: F13 : kernel-2.6.34.8-68.fc13.i686 = OK RHEL6 : kernel-2.6.32-131.0.15.el6.x86_64 = OK Rawhide : kernel-3.0-0.rc3.git5.1.fc16.i686 = OK (not fully tested, but kernel boots more or less in F13) In attach, an F13 dmesg and a screendump of the F15 i686 & x86_64 panics.
Created attachment 505716 [details] F15 i686 panic
Created attachment 505717 [details] F13 i686 dmesg
Don't want to spam, but could this lead to something (disclaimer: I am not a kernel coder) ? https://patchwork.kernel.org/patch/617301/ and https://lkml.org/lkml/2011/2/25/6
Confirmed : 1. Recompiling kernel-2.6.38.8-32.fc15.x86_64 with CONFIG_HID_NTRIG=m allows the kernel to boot on a Dell Precision M6600 ; 2. A subsequent "insmod hid-ntrig.ko" yields the expected kernel panic. RFE : is it feasible to change "CONFIG_HID_NTRIG" from "=y" to "=m" in the next F15 kernel ? This would allow the newest Dell M6600's (and M4600's, and probably all systems equipped with a DuoSense N-trig digitizer) to boot/install F15. Much obliged...
we could change it (or just apply that patch), but it won't make much difference for the install case, because we don't respin the install media after release. So it'll only really help people who update via yum. The patch you mentioned is in 3.0rc already, so this is fixed for f16.
Thanks for replying, Dave. 1. I guess an official 3.0 is unfortunately out of the question for F15, with the new policy ? 2. Recompiling each kernel release is "much pain". As you already mention, it would certainly help the yum updaters. Static -> module is IMHO painless, and would certainly get us steadfast rolling in the F15 track, not to mention being 'compliant' for Fedora support (I have this gut feeling I'll be good for some more Dell M6600 ACPI,sleep/resume,etc. BZ reports). Pretty please ? :)
we'll reassess 3.0 for f15 when it's out. I added the patch for the next build of an f15 update.
Thank you, most appreciated.
Dell Precision M6600 with built-in DuoSense N-Trig MultiTouch digitizer now boots perfectly with kernel-2.6.38.8-34.fc15.x86_64 (and blacklisted 'hid-ntrig' module). (I'll evaluate actual digitizer functionality with kernel-3.0.0)
We don't close bugs until the errata kernel is officially released.
kernel-2.6.38.8-35.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/kernel-2.6.38.8-35.fc15
Package kernel-2.6.38.8-35.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-2.6.38.8-35.fc15' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/kernel-2.6.38.8-35.fc15 then log in and leave karma (feedback).
kernel-2.6.38.8-35.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.