Re: v4.10-rc6 boot regression on Intel desktop, does not boot after cold boots, boots after reboot

From: Pavel Machek <pavel@ucw.cz>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org, gregkh@linuxfoundation.org,
	bhelgaas@google.com, linux-pci@vger.kernel.org
Subject: Re: v4.10-rc6 boot regression on Intel desktop, does not boot after cold boots, boots after reboot
Date: Fri, 3 Feb 2017 21:51:29 +0100	[thread overview]
Message-ID: <20170203205129.GA3791@amd> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1702031415140.1794-100000@iolanthe.rowland.org>

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

Hi!

> > Hmm. I moved keyboard between USB ports, and now 4.10-rc6 no longer
> > boots. v4.6 works ok. Let me try with keyboard unplugged... no, I
> > could not get it to work. I believe v4.9 and some v4.10-rc's worked,
> > but I'll have to double check.
> 
> But all the kernel versions worked when the keyboard was plugged into
> its original USB port?

Aha. So it looks difference is probably in "where is keyboard plugged
in" but in "reboot" vs. "cold boot". I did not do a cold boot in quite
a while :-(.

Booting to grub, then hitting ctrl-alt-del is enough to make it work. Ouch.

It happens with current Linus' tree.

"usbcore.nousb usbcore.nousb=1" on kernel command line does not
help. So maybe it is not USB after all. (Sorry).

> Last message I can see on console is something like:
>
> pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]

If I do the reboot dance with 4.10-rc6, messages around the hang are:

[    0.281948] RPC: Registered named UNIX socket transport module.
[    0.282009] RPC: Registered udp transport module.
[    0.282068] RPC: Registered tcp transport module.
[    0.282126] RPC: Registered tcp NFSv4.1 backchannel transport
module.
[    0.282205] pci 0000:00:02.0: Video device with shadowed ROM at
[mem 0x000c0000-0x000dffff]
[    0.316266] PCI: CLS 64 bytes, default 64
[    0.316330] PCI-DMA: Using software bounce buffering for IO
(SWIOTLB)
[    0.316395] software IO TLB [mem 0xb987e000-0xbd87e000] (64MB)
mapped at [ffff8800b987e000-ffff8800bd87dfff]
[    0.317912] futex hash table entries: 1024 (order: 5, 131072 bytes)
[    0.318646] workingset: timestamp_bits=62 max_order=20
bucket_order=0

So I guess this is something with PCI subsystem?

Ideas welcome...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

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