Created attachment 166651 [details] 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
Created attachment 166661 [details] dmesg for JVC MP-XV941
Created attachment 166671 [details] Xorg.0.log for JVC MP-XV941 running xorg-video-vesafb
Addendum: The installation report for Debian can be found here: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778296 It may contain additional hardware information besides what "lspci -vvv" and "dmesg" provide.
Did you actually see the oops? Can we see it too? ;)
(In reply to Jani Nikula from comment #4) > Did you actually see the oops? Can we see it too? ;) Sorry, I should have elaborated on that a bit more. I can't currently see the oops since apparently the machine panics in such a way that the kernel is unable to print the oops. I assumed it was panicing as you can see from the keyboard LEDs flashing the usual way. I am attaching a photo which shows how far the kernel boots until it panics. I would love to debug the issue using the serial port but the laptop doesn't have one, even on the external port expander I have. Do you know whether there are other ways to debug it? Probably over USB, Firewire or a PCCard/PCMCIA card? Adrian
Created attachment 167101 [details] Screenshot of the moment the machine panics.
(In reply to John Paul Adrian Glaubitz from comment #5) > Do you know whether there are other ways to debug it? Probably over USB, > Firewire or a PCCard/PCMCIA card? netconsole might work https://www.kernel.org/doc/Documentation/networking/netconsole.txt
Amazing tip, that worked at first attempt and I got the OOPS :). See attached output retrieved through netconsole.
Created attachment 167171 [details] Kernel OOPS logged with netconsole
(In reply to John Paul Adrian Glaubitz from comment #8) > Amazing tip, that worked at first attempt and I got the OOPS :). Awesome! > See attached output retrieved through netconsole. Ugh, a GPU hang immediately followed by a NULL pointer dereference. I suppose we should fix the oops first to be able to get the error state... unless Chris has some better ideas.
Hi there! Just a short heads-up: I updated to kernel 4.0.0 and the panic is gone, the machine now boots fine with modesetting enabled. There are still some more error messages from the DRM driver in the dmesg though which I am attaching. The graphics seem to work fine so far, there were some artifacts in the desktop wallpaper of the loaded MATE desktop which might be related to the error messages though. Let me know if you need more, but in any case, this issue is at least partially resolved, in the sense that the kernel doesn't panic anymore. Adrian
Created attachment 177071 [details] dmesg with kernel 4.0.0; system no longer panics
Panics seem to be fixed, closing. Please file any new bug reports at the freedesktop.org bugzilla [1]. Thank you. [1] https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel