Re: i1915drmkms system crash in NetBSD 7.0
On 5/7/2016 10:34 AM, Chuck Zmudzinski wrote: On 5/7/2016 9:37 AM, co...@sdf.org wrote: On Fri, May 06, 2016 at 10:42:29PM -0400, Chuck Zmudzinski wrote: Hello friends... I have a system with ASROCK B85M Pro4 Board and Intel Core i5-4590S processor which has Intel HD 4600 integrated graphics. I thought I would try booting NetBSD/amd64 7.0 on it, since I read on the web that NetBSD plans to support Intel integrated graphics up to Haswell in NetBSD 7.0. It crashed using the GENERIC kernel a few seconds after the bootloader loaded the kernel. On the console screen I could see that the i915drmkms driver crashed the system and the screen immediately went blank at that time. To get this system to boot I built a GENERIC kernel without the i915drmkms option, and used it to install and run on the system, and when running startx the system crashes immediately with the screen going blank. I thought maybe it would at least run X11 with the generic VESA driver. But it totally crashed the system. Obviously the support for Intel integrated graphics on the Haswell microarchitcture is hit and miss and NetBSD 7.0 does not support all configurations. I also tried the legacy i915drm driver without kms which by default is disabled in the GENERIC kernel config, but that kernel config would not build without compilation errors. Any ideas of what to try? NetBSD/i386 7.0? or NetBSD current? Tweak some BIOS settings such as amount of shared videoram (mine was set to 256 MB)? Thanks Chuck --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus Try -current, at least. You can get an image from nyftp.netbsd.org, no need to build your own. Feel free to file a bug report, especially if -current fails too: http://netbsd.org/cgi-bin/sendpr.cgi?gndb=netbsd I will try -current and maybe some other things and report my findings probably by early next week when I have time... Actually I found out that the system is not crashing at all. After setting up networking and sshd with my custom GENERIC 7.0/amd64 kernel with the i915drmkms support disabled, I tested the 7.0/amd64 GENERIC kernel again and even though the console screen powered off and I could not get it to power on by pressing a key on the keyboard, I could access the system remotely using ssh. So it is not really a system crash at all even though that is how it appeared at the console before I had sshd configured for remote access. I also tried a recent -current kernel with the 7.0 userland and got the same behavior, a blank screen at the console but able to sshd remotely over the network. With a little more experimenting I found out that the screen goes blank with the i915drmkms support enabled only with an HDMI cable connected to the display. When using a VGA cable, the screen does not go blank even with the i915drmkms support enabled and I can login at the console after the booting process completes and I can run startx and the system works as expected. Is there any reason NetBSD 7.0/amd64 cannot output to a display connected with an HDMI cable but can output to the same display connected with a VGA cable? Although the i915drmkms support in NetBSD 7.0/amd64 does seem to work on my system with a VGA cable, it is not without errors. On the console after ending the X11 session there is an error reported nine times, (also reported by dmesg): DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt DRM error in intel_uncore_check_errors: Unclaimed register before interrupt Chuck --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: i1915drmkms system crash in NetBSD 7.0
Hi Olaf, On 08/05/2016 23:05, Rhialto wrote: No doubt that message comes from Linux. I've always found it a very worrying message. The whole idea of this kernel mode setting stuff was to*prevent* userland bugs (or malicious programs) to affect the system in a bad way. (If I've misunderstood that, the whole thing is even more nonsensical than I already thought). But now you need the correct graphics drivers in the kernel*and* in userland, whereas before you only needed them in X. I don't see the progress. On the contrary. I understand and share your rant! X drivers are quite an issue. At least here with Intel they should work without any further nuiseance, at least, so it is on Linux. For ATI or nVidia you need proprietary stuff to have decent performance or rely on clang. One or the other way a nightmare. Gone are the easy days of NeoMagic :) Stopping the rant... I think the kernel side seems to have an issue. If there is a lock problem in the kernel and then I have issues in X11 itself, I thought those warnings could be of interest. If they are meaningful they should be solved. So I share your rant, but don't know what your point is ! Riccardo
Re: i1915drmkms system crash in NetBSD 7.0
On Sun 08 May 2016 at 19:12:14 +0200, Riccardo Mottola wrote: > drm: GPU hangs can indicate a bug anywhere in the entire gfx stack, > including userspace. No doubt that message comes from Linux. I've always found it a very worrying message. The whole idea of this kernel mode setting stuff was to *prevent* userland bugs (or malicious programs) to affect the system in a bad way. (If I've misunderstood that, the whole thing is even more nonsensical than I already thought). But now you need the correct graphics drivers in the kernel *and* in userland, whereas before you only needed them in X. I don't see the progress. On the contrary. -Olaf. -- ___ Olaf 'Rhialto' Seibert -- The Doctor: No, 'eureka' is Greek for \X/ rhialto/at/xs4all.nl-- 'this bath is too hot.' signature.asc Description: PGP signature
Re: i1915drmkms system crash in NetBSD 7.0
Hi, Chuck Zmudzinski wrote: I have a system with ASROCK B85M Pro4 Board and Intel Core i5-4590S processor which has Intel HD 4600 integrated graphics. I thought I would try booting NetBSD/amd64 7.0 on it, since I read on the web that NetBSD plans to support Intel integrated graphics up to Haswell in NetBSD 7.0. it might be related, it might be not since I am using a different card but still the 915 driver.. but while running both 7.0 release and current, i get a message that an interrupt storm. WHile running a lock-debug kernel, the kernel crashes. drm: GPU HANG: ecode -1:0x, reason: Command parser error, iir 0x8010, action: continue drm: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. <...> drm: HPD interrupt storm detected on connector DP-2: switching from hotplug detection to polling have you seen something like this in your boot messages? Riccardo
Re: i1915drmkms system crash in NetBSD 7.0
On 5/7/2016 9:37 AM, co...@sdf.org wrote: On Fri, May 06, 2016 at 10:42:29PM -0400, Chuck Zmudzinski wrote: Hello friends... I have a system with ASROCK B85M Pro4 Board and Intel Core i5-4590S processor which has Intel HD 4600 integrated graphics. I thought I would try booting NetBSD/amd64 7.0 on it, since I read on the web that NetBSD plans to support Intel integrated graphics up to Haswell in NetBSD 7.0. It crashed using the GENERIC kernel a few seconds after the bootloader loaded the kernel. On the console screen I could see that the i915drmkms driver crashed the system and the screen immediately went blank at that time. To get this system to boot I built a GENERIC kernel without the i915drmkms option, and used it to install and run on the system, and when running startx the system crashes immediately with the screen going blank. I thought maybe it would at least run X11 with the generic VESA driver. But it totally crashed the system. Obviously the support for Intel integrated graphics on the Haswell microarchitcture is hit and miss and NetBSD 7.0 does not support all configurations. I also tried the legacy i915drm driver without kms which by default is disabled in the GENERIC kernel config, but that kernel config would not build without compilation errors. Any ideas of what to try? NetBSD/i386 7.0? or NetBSD current? Tweak some BIOS settings such as amount of shared videoram (mine was set to 256 MB)? Thanks Chuck --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus Try -current, at least. You can get an image from nyftp.netbsd.org, no need to build your own. Feel free to file a bug report, especially if -current fails too: http://netbsd.org/cgi-bin/sendpr.cgi?gndb=netbsd I will try -current and maybe some other things and report my findings probably by early next week when I have time... --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: i1915drmkms system crash in NetBSD 7.0
On Fri, May 06, 2016 at 10:42:29PM -0400, Chuck Zmudzinski wrote: > Hello friends... > > I have a system with ASROCK B85M Pro4 Board and Intel Core i5-4590S > processor which has Intel HD 4600 integrated graphics. I thought I would try > booting NetBSD/amd64 7.0 on it, since I read on the web that NetBSD plans to > support Intel integrated graphics up to Haswell in NetBSD 7.0. > > It crashed using the GENERIC kernel a few seconds after the bootloader > loaded the kernel. On the console screen I could see that the i915drmkms > driver crashed the system and the screen immediately went blank at that > time. > > To get this system to boot I built a GENERIC kernel without the i915drmkms > option, and used it to install and run on the system, and when running > startx the system crashes immediately with the screen going blank. I thought > maybe it would at least run X11 with the generic VESA driver. But it totally > crashed the system. Obviously the support for Intel integrated graphics on > the Haswell microarchitcture is hit and miss and NetBSD 7.0 does not support > all configurations. > > I also tried the legacy i915drm driver without kms which by default is > disabled in the GENERIC kernel config, but that kernel config would not > build without compilation errors. > > Any ideas of what to try? NetBSD/i386 7.0? or NetBSD current? Tweak some > BIOS settings such as amount of shared videoram (mine was set to 256 MB)? > > Thanks > > Chuck > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > Try -current, at least. You can get an image from nyftp.netbsd.org, no need to build your own. Feel free to file a bug report, especially if -current fails too: http://netbsd.org/cgi-bin/sendpr.cgi?gndb=netbsd
i1915drmkms system crash in NetBSD 7.0
Hello friends... I have a system with ASROCK B85M Pro4 Board and Intel Core i5-4590S processor which has Intel HD 4600 integrated graphics. I thought I would try booting NetBSD/amd64 7.0 on it, since I read on the web that NetBSD plans to support Intel integrated graphics up to Haswell in NetBSD 7.0. It crashed using the GENERIC kernel a few seconds after the bootloader loaded the kernel. On the console screen I could see that the i915drmkms driver crashed the system and the screen immediately went blank at that time. To get this system to boot I built a GENERIC kernel without the i915drmkms option, and used it to install and run on the system, and when running startx the system crashes immediately with the screen going blank. I thought maybe it would at least run X11 with the generic VESA driver. But it totally crashed the system. Obviously the support for Intel integrated graphics on the Haswell microarchitcture is hit and miss and NetBSD 7.0 does not support all configurations. I also tried the legacy i915drm driver without kms which by default is disabled in the GENERIC kernel config, but that kernel config would not build without compilation errors. Any ideas of what to try? NetBSD/i386 7.0? or NetBSD current? Tweak some BIOS settings such as amount of shared videoram (mine was set to 256 MB)? Thanks Chuck --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
