Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
On 2012-10-01 19:52, Jonathan Nieder wrote:
So far the only log messages on the remote server are from netconsole
itself. Which leads me to this question: Are the default kernel debugging
options OK, or do I need to enable more debugging?
Does that mean it didn't capture the boot messages?
netconsole is compiled as a module, so I never rebooted, just loaded it
with modprobe.
Either way, if you can handle the log spew then drm.debug=0xe would be
great. But a log without that would already be interesting since it
would catch the basic setup at boot time and symptoms such as
assertion failures (kernel BUG or WARNING) near the time of the
freeze.
OK, now freshly rebooted with this config:
GRUB_CMDLINE_LINUX="netconsole=@/,514@192.168.201.1/ drm.debug=0xe"
The debug logging from drm isn't forwarded via netconsole, so I suppose
it isn't supposed to? (Even though I've been working with unix/linux for
the last 25 years, kernel debugging isn't my everyday trade.) But I have
removed the "minus" from /var/log/kern.log in the syslog config, so
hopefully everything should stick to the local log file. Or at least
everything but the last crucial line, which netconsole hopefully will catch.
So far i doesn't spew that much, it typically looks like this over and
over again:
[drm:i915_driver_open],
[drm:i915_getparam], Unknown parameter 16
[drm:i915_getparam], Unknown parameter 17
[drm:i915_getparam], Unknown parameter 17
[drm:intel_crtc_cursor_set],
[drm:intel_crtc_cursor_set], cursor off
[drm:intel_crtc_cursor_set],
[drm:intel_crtc_cursor_set],
[drm:intel_crtc_cursor_set], cursor off
Now we'll just have to wait and see. This is my workstation at home, and
during the weekdays I don't use it as much as on weekends, so it might
take longer to trigger the bug the next time.
/Per
Reply to: