mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: LKML <linux-kernel@vger.kernel.org>,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org
Subject: 4.7.0-rc7+: Oops during boot with USB pen drive inserted
Date: Fri, 22 Jul 2016 06:41:40 +0100	[thread overview]
Message-ID: <c5b8ac2b-23dd-a345-781f-26740afb21aa@googlemail.com> (raw)

Hi,

With Linus' latest and greatest, I get an opps when I boot my laptop with a pen drive inserted in any USB port. The oops
message is:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)

The oops seems to be 100% repeatable. If a USB pen drive is not inserted, the laptop boots successfully.

I've taken a photograph of the oops and you can view it at
http://s714.photobucket.com/user/chris2553/media/IMG_20160722_053841.jpg.html.

At the top of the picture, I notice that the partitions on my actual boot disk are being reported as being on /dev/sdb,
so it seems likely that, at this point, the pen drive is being seen as /dev/sda, although that has scrolled off the
screen. I don't boot via a ramdisk - my kernel has ext4 built in.  The grub2 entry is:

menuentry "Krisux, Linux 4.7.0-rc7+" {
    insmod ext2
    set root=(hd0,2)

    linux   /boot/vmlinuz-4.7.0-rc7+ ro root=/dev/sda2 resume=/dev/sda6 rootfstype=ext4 net.ifnames=0

}

(BTW, Krisux is not a real distro - it's just the name I have given Linux from Scratch system.)

The stack that is dumped is:

	dump_stack
	panic
	printk
	mount_block_root
	prepare_namespace
	kernel_init_freeable
	kernel_init
	ret_from_fork
	rest_init

I realise I could work around this by specifying the boot partition by, say, its UUID, but I thought you would want me
to report this anyway.

Of course, I'm happy to provide any other information required and to test any fix, but I will be out and about for the
next 14-16 hours, so it will be later tonight or maybe even tomorrow before I can respond.

Chris

                 reply	other threads:[~2016-07-22  5:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=c5b8ac2b-23dd-a345-781f-26740afb21aa@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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

all inboxes | Powered by JetHome®