[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
A workaround which was suggested in the thread http://ubuntuforums.org/showthread.php?p=11819330 fixed the issue for me: echo blacklist ite-cir | sudo tee /etc/modprobe.d/ite-cir.conf sudo depmod -a 3.2.0-22-generic sudo update-initramfs -u -k 3.2.0-22-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972723 Title: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
Hi Brian et al, First, can you try booting the latest 3.2.0-22.35 kernel. I just want to confirm this isn't resolved before we investigate further. Assuming the issue remains, lets try and figure out the exact change which introduced this regression. Between the 3.2.0-17 and 3.2.0-18 kernels there were quite a few changes, most notably rebases to upstream stable Linux kernel v3.2.7, v3.2.8, and v3.2.9. 3.2.0-17.27 was actually based on upstream stable Linux kernel v3.2.6. So lets have you do the following set of tests: 1) Install and boot the upstream v3.2.6 kernel. Does it work (ie boot properly) or panic? If it works, proceed to step 2. Note that I would expect this kernel to work, but want confirmation. 2) Install and boot the upstream v3.2.7 kernel. Does it work (ie boot properly) or panic? If it works, proceed to step 3. 3) Install and boot the upstream v3.2.8 kernel. Does it work (ie boot properly) or panic? If it works, proceed to step 4 4) Install and boot the upstream v3.2.9 kernel. Does it work or panic? Let me know your results of the above. The above stable kernels can each be found at the following: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.6-precise/ http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.7-precise/ http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.8-precise/ http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.9-precise/ ** Changed in: linux (Ubuntu) Importance: Medium = High ** Changed in: linux (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972723 Title: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
The versions of the precise kernel installed on my machine are: linux-image-3.2.0-17-generic3.2.0-17.27 Linux kernel image for version 3.2.0 on 64bit x86 SMP linux-image-3.2.0-18-generic3.2.0-18.29 Linux kernel image for version 3.2.0 on 64bit x86 SMP linux-image-3.2.0-19-generic3.2.0-19.31 Linux kernel image for version 3.2.0 on 64bit x86 SMP linux-image-3.2.0-20-generic3.2.0-20.33 Linux kernel image for version 3.2.0 on 64bit x86 SMP linux-image-3.2.0-21-generic3.2.0-21.34 Linux kernel image for version 3.2.0 on 64bit x86 SMP All after -17 (the top one) exhibit the described behavior. I cannot gathter data on any newer kernel because they all fail to boot. They panic before logging to the drive is enabled. Below find the output of the commands lspci -vvvn lspnp -vvv cat /proc/interrupts Note: These were all run on -17 since none of the other kernels boot. 00:00.0 0600: 10de:0a82 (rev b1) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 00:00.1 0500: 10de:0a88 (rev b1) Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 00:03.0 0601: 10de:0aae (rev b2) Subsystem: 10de:cb79 Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: I/O ports at 1c00 [size=256] 00:03.1 0500: 10de:0aa4 (rev b1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- 00:03.2 0c05: 10de:0aa2 (rev b1) Subsystem: 10de:cb79 Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 10 Region 0: I/O ports at 3080 [size=64] Region 4: I/O ports at 3040 [size=64] Region 5: I/O ports at 2000 [size=64] Capabilities: access denied Kernel driver in use: nForce2_smbus Kernel modules: i2c-nforce2 00:03.3 0500: 10de:0a89 (rev b1) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- 00:03.5 0b40: 10de:0aa3 (rev b1) Subsystem: 10de:cb79 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin B routed to IRQ 19 Region 0: Memory at f060 (32-bit, non-prefetchable) [size=512K] Kernel driver in use: nvidia Kernel modules: nvidia, nvidia_current_updates, nvidia_current 00:04.0 0c03: 10de:0aa5 (rev b1) (prog-if 10 [OHCI]) Subsystem: 1028:02a1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 22 Region 0: Memory at f0886000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: ohci_hcd 00:04.1 0c03: 10de:0aa6 (rev b1) (prog-if 20 [EHCI]) Subsystem: 1028:02a1 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin B routed to IRQ 23 Region 0: Memory at f0889000 (32-bit, non-prefetchable) [size=256] Capabilities: access denied Kernel driver in use: ehci_hcd 00:06.0 0c03: 10de:0aa7 (rev b1) (prog-if 10 [OHCI]) Subsystem: 1028:02a1 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 21 Region 0: Memory at f0887000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in
[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
Hi Brad, This bug exists in all kernels up to and including mainline (which as of today was 3.4-rc1). The ite_probe() function in the ite-cir driver (drivers/media/rc/ite- cir.c) installs an interrupt service routine via request_irq() before properly initializing both the hardware and crucial function tables the ISR uses. As the documentation for request_irq() specifies, all initialization required for an ISR to function properly must before performed before calling request_irq(), as an interrupt may be dispatched even before request_irq() returns. Normally, this bug would be difficult to trigger and reproduce. However, now that CONFIG_IRQ_REMAPPING is on, the interrupt is being immediately triggered for remapping purposes. Since the function table has not yet been initialized by the ite_probe() function, the ISR, ite_cir_isr(), tries to call through the function table which immediately panics (since it tries to jump to vma 0). As the hardware does not perform a critical function, perhaps the best temporary solution is to blacklist it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972723 Title: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
Thank you for taking the time to file a bug report on this issue. However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request. We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not. You can update to the latest development kernel by simply running the following commands in a terminal window: sudo apt-get update sudo apt-get dist-upgrade If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released. If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging. Thank you for your help, we really do appreciate it. ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Tags added: kernel-request-3.2.0-22.35 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972723 Title: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
I suffer from an identical problem on dell xps studio 1340 with nvidia 9500m card. The 3.0.0-17 kernel boots fine, but the 3.2.0-22 (and all the former 3.2 I tried) leads to kernel panic. No logs are saved, and most of the data runs on the screen too fast to be read. It seems to be the same bug, although I cannot be sure of that. Another report of this problem on a different dell computer is found here: http://ubuntuforums.org/showthread.php?t=1928957 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags added: bot-stop-nagging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972723 Title: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972723 Title: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
** Changed in: linux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972723 Title: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
Attempting to run apport-collect and it crashes all over the place: apport-collect 972723 No packages found matching linux. ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/apport/report.py, line 718, in add_hoo ks_info symb['add_info'](self, ui) File /usr/share/apport/general-hooks/ubuntu.py, line 37, in add_info match_error_messages(report) File /usr/share/apport/general-hooks/ubuntu.py, line 121, in match_error_messages if report['ProblemType'] == 'Package': File /usr/lib/python2.7/UserDict.py, line 23, in __getitem__ raise KeyError(key) KeyError: 'ProblemType' Traceback (most recent call last): File /usr/share/apport/apport-gtk, line 493, in lambda GLib.idle_add(lambda: self.collect_info(on_finished=self.ui_update_view)) File /usr/lib/python2.7/dist-packages/apport/ui.py, line 861, in collect_info icthread.exc_raise() File /usr/lib/python2.7/dist-packages/apport/REThread.py, line 34, in run self._retval = self.__target(*self.__args, **self.__kwargs) File /usr/lib/python2.7/dist-packages/apport/ui.py, line 111, in thread_collect_info if report['ProblemType'] == 'Crash' and \ File /usr/lib/python2.7/UserDict.py, line 23, in __getitem__ raise KeyError(key) KeyError: 'ProblemType' That hangs the collector window and I cannot submit anything. Thus I don't know how to make the bug report complete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972723 Title: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972723 Title: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972723] Re: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x
Thank you for taking the time to file a bug report on this issue. However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request. We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not. You can update to the latest development kernel by simply running the following commands in a terminal window: sudo apt-get update sudo apt-get dist-upgrade If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released. If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging. Thank you for your help, we really do appreciate it. ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete ** Tags added: kernel-request-3.2.0-21.34 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972723 Title: linux 3.2.0-18 - 21 kernel panic on boot, Alienware m17x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
