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

[Bjørn Mork <bjorn@mork.no>]

Per Foreby <per@foreby.se> writes:
> On 2012-10-02 00:45, Bjørn Mork wrote:
>
>> 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


>From Documentation/sysctl/kernel.txt :
<quote>

printk:

The four values in printk denote: console_loglevel,
default_message_loglevel, minimum_console_loglevel and
default_console_loglevel respectively.

These values influence printk() behavior when printing or
logging error messages. See 'man 2 syslog' for more info on
the different loglevels.

- console_loglevel: messages with a higher priority than
  this will be printed to the console
- default_message_loglevel: messages without an explicit priority
  will be printed with this priority
- minimum_console_loglevel: minimum (highest) value to which
  console_loglevel can be set
- default_console_loglevel: default value for console_loglevel

</quote>

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

Odd.  Then there are other issues I don't understand here.

But the dmesg bug is quite obvious, so I sent off a fix upstream.  The
bug was introduced with the support for level names in July 2011.


Bjørn




>
> /Per