libreboot
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libreboot] X60 freezes with kernel > 4.0.7


From: Francis Rowe
Subject: Re: [Libreboot] X60 freezes with kernel > 4.0.7
Date: Tue, 18 Aug 2015 13:58:13 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 18/08/15 13:18, Robert Alessi wrote:
> Thanks Denis,
> 
> On Fri, Aug 14, 2015 at 12:27:08AM +0200, Denis 'GNUtoo' Carikli
> wrote:
>> Background info on my X60: I've some heat issues: After
>> disassembling and reassembling it a lot, it got less efficient in
>> heat-cooling. So I'll try to fix it by putting back some thermal
>> paste, as soon as possible.
> 
> No heat issues on my own: xsensors reports temps that are always
> below 60°C.

Is that on idle, or on stress? Try stressing it (use "stress -c 2"
because you have dual-core, and run "watch sensors" or "xsensors" to
monitor temps. They should usually be below 80C when the CPU is at
100% load - 80 to 90 is borderline acceptable, but not ideal. above 90
is overheating)

sudo apt-get install xsensors stress

>> That said, I can reproduce the freeze when making cpu-intensive
>> work. I use parabola with linux-libre (I don't remember the exact
>> version), and I didn't try linux-libre-lts recently.
> 
> I reported the issue to bugzilla.kernel.org 
> (https://bugzilla.kernel.org/show_bug.cgi?id=101621), but 
> unfortunately I didn't got any answer since then.
> 
> However, https://bugs.archlinux.org/task/45784 reports the same
> issue, with exactly the same symptoms as mine: computer freezes
> within an hour or so of uptime, and the last kernel version which
> didn't cause the computer to freeze was 4.0.7.
> 
> Matt Leach (the author of this report) also notified the kernel
> guys and did a bisect: see the comments, and in particular 
> http://www.mail-archive.com/address@hidden/msg949703.html
>
> 
>>> - What can I do to report this properly?
>> You probably  want to identify which commit broke it, you'll need
>> to either test fast, or test few revisions.
>> 
>> Test fast: try to find how to reproduce the problem faster, then
>> you can bisect with git-bisect.
>> 
>> Test fewer revisions: try to narrow it down more using older
>> parabola linux-libre kernels.
>> 
>> An automated way to do that could be done thanks to the
>> watchdog(s).
> 
> Ok, but where can I find the git repositories of the linux-libre 
> kernel?  Do I have to do the bisect from kernel.org, then deblob
> it every time?
> 

For the git repository, this would probably require manually
maintaining the scripts for each run in the bisect.

For testing purposes, it doesn't matter since those blobs won't be
loaded on your system (unless you have the Intel wifi or something, or
some device you inserted that might use them). Just make sure to
switch back to linux-libre afterwards.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJV0yvkAAoJEP9Ft0z50c+UsWgH/1Q3nHV9dchTh92bT0+byfnp
yaM3v3otHF1QStXOx1VuD56Lfv/MudqlaBrM2T5PriR8SY6rGtoi+uuy/08PT7HY
x4X7qt1Rl0U0R1MQ5UL71STrNIJN/p6Znn4LzrblBeKkeVinIoZLiJPZd60Mj4mH
hm/PQc8Pq4o7h1Voc6M7vZKfTZj4ft7Lu1A/Os0rKvlWrthl+9yMEIlN+ao+XmMn
7DKsokh4J03im6YkK7/JhOeAZ7aVtNOuQfRdL5NaY45tZabgCDj2bEwVlblJkxux
lhoym27FPcgnT44oPoyei0FfA/dLJD1hUijwKQVspuPveJa9QPAEHhORCOiCToI=
=zvf3
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]