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: Sun, 30 Aug 2015 10:45:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1508301033010.29851@comporellon> (raw)
In-Reply-To: <CAJ1xhMWC46ZHddfQGDY7YD_Fu5YrYvjuEF=_-SasKmwoOYXG2w@mail.gmail.com>
On Sat, 29 Aug 2015, Alexander Kapshuk wrote:
> You probably did look into this yourself, but did you double-check
> your /etc/lilo.conf? Is everything fine there?
At least it's identical between 4.0.5 and 4.1.6:
image=/boot/kernel-genkernel-x86_64-4.0.5
label=Linux405
read-only # read-only for checking
root=/dev/ram0
append="init=/linuxrc keymap=de ramdisk=8192 real_root=/dev/sda6
splash=verbose,theme:default console=tty1 quiet
radeon.modeset=1 video=radeon:mtrr:3,ywrap,1680x1050-32@60
ahci.marvell_enable=0"
initrd=/boot/initramfs-genkernel-x86_64-4.0.5
Don't ask me where all those options came from, they grew with time...
> Here are my RCU kernel config options. What do yours look like?
> % uname -r
> 4.1.6-vanilla
> % grep RCU .config
> # RCU Subsystem
> CONFIG_TREE_RCU=y
> CONFIG_SRCU=y
> # CONFIG_TASKS_RCU is not set
> CONFIG_RCU_STALL_COMMON=y
> CONFIG_RCU_FANOUT=32
> CONFIG_RCU_FANOUT_LEAF=16
> # CONFIG_RCU_FANOUT_EXACT is not set
> # CONFIG_RCU_FAST_NO_HZ is not set
> # CONFIG_TREE_RCU_TRACE is not set
> CONFIG_RCU_KTHREAD_PRIO=0
> # CONFIG_RCU_NOCB_CPU is not set
> # CONFIG_RCU_EXPEDITE_BOOT is not set
> # RCU Debugging
> # CONFIG_PROVE_RCU is not set
> # CONFIG_SPARSE_RCU_POINTER is not set
> # CONFIG_RCU_TORTURE_TEST is not set
> CONFIG_RCU_CPU_STALL_TIMEOUT=21
> # CONFIG_RCU_CPU_STALL_INFO is not set
> # CONFIG_RCU_TRACE is not set
Thanks. The only difference to my config there is that I have
CONFIG_RCU_FANOUT=64 and CONFIG_RCU_CPU_STALL_TIMEOUT=60 (don't ask me
where the values come from, I don't remember ever setting them different
from the default). But since that is all the same between 4.0.5 and
4.1.6, I don't think it has anything to do with my problem. Could the
RCU message just be telling me that since the machine doesn't properly
boot, it doesn't have anything to do?
Cheers,
Peter.
next prev parent reply other threads:[~2015-08-30 8:46 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
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 [this message]
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.1508301033010.29851@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