public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Freeze after suspend-to-ram with kernel 3.10
Date: Mon, 5 Aug 2013 12:17:40 +0200	[thread overview]
Message-ID: <20130805101740.GA18655@nukleus.lan> (raw)
In-Reply-To: <CAEH5T2PTuc0Su=b5+ojnhcM8m+Otr_GpET9vuAS3XwpM4R=TPg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]

On Fri, Aug 02, 2013 at 10:02:05AM -0500, Paul Hartman wrote:

> >> I tried to confirm my oberservation by deliberately hibernating it multiple
> >> times yesterday -- it always woke up with 3.9. Now I booted it with 3.10 and
> >> it didn't come up on the first try.
> >> Do you have any suggestion how I might debug this? I can’t simply report to
> >> kernel blokes “3.10 is crap on my netbook, you put in a regression somewhere”.
> >>
> >> I don’t really have the time right now to go after hunches, such as the new
> >> tikless system, as building a kernel takes up to 45 minutes on that thing.
> > well, take your 3.9 config and don't change it.
> 
> If the config change doesn't reveal anything, you can do git bisect of
> the kernel to find out which patch broke it. When you do git bisect
> you don't need to recompile the whole kernel every time, it only
> compiles the changed files, which are usually not many. So even on a
> slower machine it's not so bad once the first compile is finished.
> 
> https://wiki.gentoo.org/wiki/Kernel_git-bisect

I didn't know one could have the git repo only for one subversion
(though I find it very handy for this huge codebase).

Anyhoo, I cleaned out my build dir and oldconfig'ed my 3.9 config, this
time saying no to everything new. As it turned out, the resulting config
was almost identical to my old 3.10 config (except for some crypto stuff
built as a module instead of built-in).
Now I don't have the freezes anymore. One possible reason is that I'm
now using 3.10.4 instead of 3.10.1. Another (more probable) reason is
that I may have forgotten to make clean the first time, which left over
some interfering cruft.
-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any Facebook service.

I am never drunk, I always keel over before that.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-08-05 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 10:47 [gentoo-user] Freeze after suspend-to-ram with kernel 3.10 Frank Steinmetzger
2013-08-02 11:21 ` Volker Armin Hemmann
2013-08-02 15:02   ` Paul Hartman
2013-08-05 10:17     ` Frank Steinmetzger [this message]
2013-08-03  3:12 ` William Kenworthy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130805101740.GA18655@nukleus.lan \
    --to=warp_7@gmx.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox