[Bug 93181] New: i915: Kernel panic on JVC MP-XV941 (ASUS J3N platform) unless booted with nomodeset

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Fri Feb 13 06:26:43 PST 2015


https://bugzilla.kernel.org/show_bug.cgi?id=93181

            Bug ID: 93181
           Summary: i915: Kernel panic on JVC MP-XV941 (ASUS J3N platform)
                    unless booted with nomodeset
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.18.6
          Hardware: i386
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: glaubitz at physik.fu-berlin.de
                CC: intel-gfx-bugs at lists.freedesktop.org
        Regression: No

Created attachment 166651
  --> https://bugzilla.kernel.org/attachment.cgi?id=166651&action=edit
lspci for JVC MP-XV941

Hello!

I recently installed Debian unstable on a JVC MP-XV941 subnotebook which is
apparently based on the J3N platform by ASUS according to the kernel messages
(asus_laptop driver). The laptop has already the latest BIOS version (0203).

After rebooting the laptop after the installation, I got a kernel panic which
turned out to be related to the modesetting. The machine is based around the
Intel 855 graphics chipset which means it's using the i915 kernel module.

I have tried both kernel 3.16.7 from Debian unstable as well as kernel 3.18.6
which is the most current kernel we currently have in Debian, both kernel panic
unless I adding "nomodeset" to the kernel command line. Thus, I need to resort
to running X.Org using the VESA driver since I can't use the Intel driver.

I have the laptop sitting here on my desk running Debian unstable and can
install kernels compiled from git to test any patches, so I am open to helping
to debug this issue.

Please let me know if you need to know anything else.

Cheers,
Adrian

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the intel-gfx-bugs mailing list