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