| 1 |
Am 20.03.2014 11:24, schrieb Tom Wijsman: |
| 2 |
> On Thu, 20 Mar 2014 11:39:58 +0400 |
| 3 |
> Gleb Klochkov <glebiuskv@×××××.com> wrote: |
| 4 |
> |
| 5 |
>> Tom, thank you for your answer. |
| 6 |
>> |
| 7 |
>> $ dmesg >> http://bpaste.net/show/187533/ |
| 8 |
> There this can be seen: |
| 9 |
> |
| 10 |
> [ 18.074574] [drm] Wrong MCH_SSKPD value: 0x16040307 |
| 11 |
> [ 18.074575] [drm] This can cause pipe underruns and display |
| 12 |
> issues. |
| 13 |
> [ 18.074575] [drm] Please upgrade your BIOS to fix this. |
| 14 |
> [ 18.148162] [drm] GMBUS [i915 gmbus vga] timed out, falling back |
| 15 |
> to bit banging on pin 2 |
| 16 |
> |
| 17 |
> Above your messages seem interesting; some expected value is wrong, it |
| 18 |
> also times out on a bus and then goes to use a pin instead. Not sure |
| 19 |
> how much of this is intended, but try to upgrade your BIOS as suggested. |
| 20 |
> |
| 21 |
>> $ cat /proc/interrupts >> http://bpaste.net/show/187537/ |
| 22 |
> So, that would be this: |
| 23 |
> |
| 24 |
> 8: 63 0 0 0 IO-APIC-edge rtc0 |
| 25 |
> |
| 26 |
> Hmm, nothing about it in the dmesg; also, 63 seems low (on my system, |
| 27 |
> however, it's only 1 as I think my system uses something different). |
| 28 |
> |
| 29 |
> You can try a different timer using this kernel parameter: |
| 30 |
> |
| 31 |
> clocksource=hpet |
| 32 |
> |
| 33 |
> Another note-worthy thing: |
| 34 |
> |
| 35 |
> 9: 699799454 0 0 0 IO-APIC-fasteoi acpi |
| 36 |
> |
| 37 |
> That there are ~700 million ACPI interrupts seems abnormally high; |
| 38 |
> maybe the count is off by one, and 8 refers to 9? On my system, that's |
| 39 |
> been running for a while by now, it's only at ~6000 (six thousand). |
| 40 |
|
| 41 |
uptime |
| 42 |
11:29:37 up 49 days, 15:48, 16 users, load average: 0,38, 0,31, 0,39 |
| 43 |
|
| 44 |
8: 0 0 0 48 IO-APIC-edge rtc0 |
| 45 |
9: 0 0 0 0 IO-APIC-fasteoi acpi |
| 46 |
|
| 47 |
|
| 48 |
> |
| 49 |
> Changing the ACPI related kernel parameters to try to get it supported |
| 50 |
> differently might be one thing to do here; other than that, it might be |
| 51 |
> something going on with the hardware (try disconnecting things?) so the |
| 52 |
> BIOS upgrade is certainly of interest. |
| 53 |
> |
| 54 |
> Try the BIOS upgrade first, then play around with the parameters; if |
| 55 |
> things don't work out, I suggest you look for support on one of the |
| 56 |
> Linux kernel mailing lists (perhaps acpi-devel*). Good luck. |
| 57 |
> |
| 58 |
> * https://lists.sourceforge.net/lists/listinfo/acpi-devel |
| 59 |
> |
| 60 |
imho he should first use a recent VANILLA kernel. 2.12 or 2.13. |
| 61 |
|
| 62 |
And build a config without all that unneeded garbage. Also increase the |
| 63 |
dmesg buffer. Most interesting stuff is missing. |
Archives