public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Weilbacher <newsspam@Weilbacher.org>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Problems booting vanilla kernel 4.1.x
Date: Tue, 25 Aug 2015 18:40:01 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1508251832400.7048@comporellon> (raw)
In-Reply-To: <CAJ1xhMVx4k6vM6e2GSnKdA=0bSBamYwcTW5qJOc1v1UPB=huLQ@mail.gmail.com>

Hi Alexander,

On Sun, 23 Aug 2015, Alexander Kapshuk wrote:

> On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher <newsspam@weilbacher.org> wrote:
> >
> > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
> > upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of
> > them. On the screen I see
> >
> >    Decompressing Linux... Parsing ELF... done.
> >    Booting the kernel.
> >
> > as the last thing, then it just sits there.
>
> I am running vanilla-sources 4.1.6, and so far I have not had any
> trouble booting it.
>
> Are you able to boot some of your previous kernels? If so, what does
> your '/boot/grub/grub.cfg' look like?
> What is the output of 'cat /etc/fstab' and 'ls -1 /boot'?

I can still boot 4.0.5 fine, with the same setup. I use lilo, and I
checked that I changed the two/four digits correctly in /etc/lilo.conf.

By chance I left the boot sit there for more than the typical minute,
and got multiple messages like

  INFO: rcu_sched self-detected stall on CPU { 3}  (t=60000 jiffies g=-256 c=-257 q=193)
  rcu_sched kthread starved for 50027 jiffies!

right after the above "Booting the kernel." line.

Do I need to activate a different kind of clocking or a CPU feature in
4.1.x?

   Peter.


  reply	other threads:[~2015-08-25 16:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-23 13:08 [gentoo-user] Problems booting vanilla kernel 4.1.x Peter Weilbacher
2015-08-23 13:23 ` Alexander Kapshuk
2015-08-25 16:40   ` Peter Weilbacher [this message]
2015-08-25 17:54     ` Alexander Kapshuk
2015-08-29 12:09       ` Peter Weilbacher
2015-08-29 14:30         ` Alexander Kapshuk
2015-08-30  8:45           ` Peter Weilbacher
2015-08-30 19:16     ` Fernando Rodriguez
2015-08-30 20:51       ` Peter Weilbacher
2015-08-30 21:54         ` [gentoo-user] " James
2015-08-30 22:11         ` [gentoo-user] " Fernando Rodriguez
2015-08-30 22:15           ` Fernando Rodriguez
2015-08-31 19:19             ` Peter Weilbacher

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=alpine.DEB.2.11.1508251832400.7048@comporellon \
    --to=newsspam@weilbacher.org \
    --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