Public bug reported:

lsb_release -rd
Description:    Ubuntu precise (development branch)
Release:        12.04

apt-cache policy linux-image-generic
linux-image-generic:
  Installed: 3.2.0.21.23
  Candidate: 3.2.0.21.23
  Version table:
 *** 3.2.0.21.23 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

When booting Alienware m17x with Precise beta (updated twice a day), all
versions of kernel after 3.2.0-17 (3.2.0-18 through -21, 3.3.0-999
dailies, 3.3.0rc7precise, 3.4.0rc1precise) panic about 7 seconds into
the boot sequence.  I, instead, expect linux to boot. -17 boots cleanly
every time on the same hardware.

Managed to capture a photograph of the stack trace. Photo and background
available at
http://ubuntuforums.org/showpost.php?p=11813173&postcount=14

The trace is

                ?  ite_cir_isr
                ?  wakeup_preempt_entitity.isra
                handle_irqevent_percpu
                ?  check_preempt_curr
                handle_irq_event
                handle_edge_irq
                handle_irq
                do_IRQ
                common_interrupt
                ?  system_call_fastpath
RIP value
 (null)>]       (null)

io- not syncing: Fatal exception in interrupt
comm: upstart-udev-br Tainted: G   D    3.

                panic
                oops_end
                no_context
                __bad_area_nosemaphore
                ? native_send_call_func_single_ipi
                bad_area_nosemaphore
                do_page_fault
                ?  scsi_request_fn
                ?  blk_complete_request
                ?  scsi_done
                ?  ata_scsi_go_complete
                page_fault
                ?  ite+cir_isr
                ?  wakeup_preempt_entity.isra
                handle_irqevent_percpu
                ?  check_preempt_curr
                handle_irq_event
                handle_edge_irq
                handle_irq
                do_IRQ
                common_interrupt
                ?  system_call_fastpath

The actual stack traces for 3.3 and 3.4 kernels are different; all the
versions of 3.2 produce similar traces to that given (actually used -21,
I believe).  apport does not want to accept a bug report on the current
configuration, claiming there is a problem with support for the current
configuration. Let me know what I can do to help.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to