Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
 

Hi,

Per Foreby wrote:

> This always happens on interactive input. So far these four events:
>
> - close a window
> - click a link in firefox
> - ctrl-r to reload a page in firefox
> - ctrl-k to delete a line in thunderbird's composer
>
> The computer is completely frozen. The cpu probably stops working since the
> fan spins down to it's lowest rpm, I can't ping the interface, caps lock
> doesn't light up, has to be power cycled. And no clues in the logs.

Can you get a log from this happening with netconsole[1] or a serial
console[2]? (It's ok if it doesn't catch the freeze --- it's just
that as full a log as possible of the context would be useful.)

If you can reproduce this with 3.5.y from experimental as well, please
report this upstream following instructions from [3] and let us know
the bug number so we can track it.

Thanks and hope that helps,
Jonathan

[1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt
[2] http://www.kernel.org/doc/Documentation/serial-console.txt
[3] http://intellinuxgraphics.org/how_to_report_bug.html


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20121001084539.GB8056@elie.Belkin

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
 

Hi,

serial ports are rare these days, but I have netconsole running now
(logging to syslogd on my server).


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?


I'll wait for the freeze to happen once more, and if it does, I will try
the latest kernel from experimental.


/Per


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 5069D238.5040307@foreby.se">http://lists.debian.org/5069D238.5040307@foreby.se

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
 

Per Foreby wrote:

> serial ports are rare these days, but I have netconsole running now (logging
> to syslogd on my server).

Thanks!

> 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?

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.

Jonathan


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20121001175222.GA16391@elie.Belkin

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


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 506A07DB.8080106@foreby.se">http://lists.debian.org/506A07DB.8080106@foreby.se

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
 

Per Foreby wrote:

> The debug logging from drm isn't forwarded via netconsole, so I suppose it
> isn't supposed to?

Oh, that's because of the console_loglevel setting[1]. You can change
it by running "dmesg -n 8" (or by adding the word "debug" or a
loglevel= parameter to the kernel command line).

Thanks again for your help and patience.

[1] see http://www.kernel.org/doc/Documentation/networking/netconsole.txt


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20121001212953.GA28294@elie.Belkin

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
 

Hi,

Sébastien Dinot wrote:

> The last log before a freeze is always like this:
>
> ------------------------------------------------------------------------
> [ 8276.625165] usb 2-1.5: USB disconnect, device number 8
> [ 8276.830839] usb 2-1.5: new low-speed USB device number 9 using ehci_hcd
> [ 8276.928992] usb 2-1.5: New USB device found, idVendor=045e, idProduct=00a4
> [ 8276.928997] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 8276.928999] usb 2-1.5: Product: Microsoft(R) Compact Optical Mouse
> [ 8276.929001] usb 2-1.5: Manufacturer: Microsoft
> [ 8276.934076] input: Microsoft Microsoft(R) Compact Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input17
> [ 8276.934434] hid-generic 0003:045E:00A4.0007: input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft(R) Compact Optical Mouse] on usb-0000:00:1d.0-1.5/input0
> ------------------------------------------------------------------------
>
> Of course, I did not disconnect the mouse or shake its USB cable. :(

Based on the timestamps, does that message come immediately before the
freeze or just some time before it? (If the latter, it's hopefully a
red herring.)


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20121001214439.GA13457@elie.Belkin

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
 

Sébastien Dinot wrote:

> Except in rare cases, the system is alive. I can open a remote SSH
> session and if I push the power button (on the computer case), the
> logout dialog appears.

This seems like a different problem than Per experienced, since
Per's locks up the machine, so please file a separate bug. If
they turn out to have the same cause, we can merge them later.

Thanks,
Jonathan


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20121001214801.GB13457@elie.Belkin

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
 

On 2012-10-01 23:29, Jonathan Nieder wrote:

Per Foreby wrote:


The debug logging from drm isn't forwarded via netconsole, so I suppose it
isn't supposed to?


Oh, that's because of the console_loglevel setting[1]. You can change
it by running "dmesg -n 8" (or by adding the word "debug" or a
loglevel= parameter to the kernel command line).


Ah, RTFM :)

However, it looks like the netconsole documentation and the dmesg man
page should be updated:


# dmesg -n 8
dmesg: unknown level '8'

Instead I tried

# dmesg -n debug
# dmesg -E

but still nothing at the remote end. Instead I added remote logging of
kern.* in rsyslog.conf, so now I have everything at the server.


/Per


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 506A1078.4020403@foreby.se">http://lists.debian.org/506A1078.4020403@foreby.se

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
 

Per Foreby <per@foreby.se> writes:

> On 2012-10-01 23:29, Jonathan Nieder wrote:
>> Per Foreby wrote:
>>
>>> The debug logging from drm isn't forwarded via netconsole, so I suppose it
>>> isn't supposed to?
>>
>> Oh, that's because of the console_loglevel setting[1]. You can change
>> it by running "dmesg -n 8" (or by adding the word "debug" or a
>> loglevel= parameter to the kernel command line).
>
> Ah, RTFM :)
>
> However, it looks like the netconsole documentation and the dmesg man
> page should be updated:
>
> # dmesg -n 8
> dmesg: unknown level '8'
>
> Instead I tried
>
> # dmesg -n debug
> # dmesg -E
>
> but still nothing at the remote end.

Yes, I vaguely remember having struggled with the same issue the last
time I use netconsole. Try

echo 8 >/proc/sys/kernel/printk

instead.

I believe the bug is in the dmesg utility. It should shift all values
by one. Setting "dmesg -n debug" will currently log all messages with a
level *higher* than debug.

> Instead I added remote logging of
> kern.* in rsyslog.conf, so now I have everything at the server.

As long as you don't crash anything...



Bjørn


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 871uhhu7zp.fsf@nemi.mork.no">http://lists.debian.org/871uhhu7zp.fsf@nemi.mork.no

Bug#689268: Intel HD 4000 (Ivy Bridge) graphics freeze
 

On 2012-10-02 00:45, Bjørn Mork wrote:

Per Foreby <per@foreby.se> writes:


On 2012-10-01 23:29, Jonathan Nieder wrote:

Per Foreby wrote:


The debug logging from drm isn't forwarded via netconsole, so I suppose it
isn't supposed to?


Oh, that's because of the console_loglevel setting[1]. You can change
it by running "dmesg -n 8" (or by adding the word "debug" or a
loglevel= parameter to the kernel command line).


Ah, RTFM :)

However, it looks like the netconsole documentation and the dmesg man
page should be updated:

# dmesg -n 8
dmesg: unknown level '8'

Instead I tried

# dmesg -n debug
# dmesg -E

but still nothing at the remote end.


Yes, I vaguely remember having struggled with the same issue the last
time I use netconsole. Try

echo 8 >/proc/sys/kernel/printk

instead.

I believe the bug is in the dmesg utility. It should shift all values
by one. Setting "dmesg -n debug" will currently log all messages with a
level *higher* than debug.


You're probably right about the bug. I don't know what the four values
in /proc/sys/kernel/printk are, but the first value was 7, not 8:


# cat /proc/sys/kernel/printk
7 4 1 7
# echo 8 > /proc/sys/kernel/printk
# cat /proc/sys/kernel/printk
8 4 1 7

However, this did not affect the remote logging, so I'm back to the
remote syslog approach.


/Per


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 506A291A.20800@foreby.se">http://lists.debian.org/506A291A.20800@foreby.se