Bug 203807

Summary:	5.2-rc3 stalls booting
Product:	Other	Reporter:	Elimar Riesebieter (riesebie)
Component:	Modules	Assignee:	other_klibc-kinit
Status:	RESOLVED CODE_FIX
Severity:	high	CC:	chaostya, jwrdegoede, rockorequin
Priority:	P1
Hardware:	Intel
OS:	Linux
Kernel Version:	5.2-rc3	Subsystem:
Regression:	No	Bisected commit-id:
Attachments:	syslog of boot

Description Elimar Riesebieter 2019-06-04 12:59:36 UTC

Did a make oldconfig of a running 5.1.6 to 5.2-rc3. Boot process stalls at loading initramfs. It takes about 3 minutes till the kernel comes up. Randomly there are problems to configure network.

Init system: systemd
Arch: amd64
Filesystem: xfs on lvm
Distro: Debian sid

BTW on powerpc the kernel runs fine, though.

I don't know really how to debug. So please give me some hints on how to.

Thanks in advance
Elimar

Comment 1 rocko 2019-06-10 03:45:24 UTC

I'm getting the same issue with the vanilla Ubuntu amd64 Linux 5.2-rc3 and -rc4 kernels on a Dell XPS 15. I haven't left it 3 minutes yet to see if it every comes up. It never gets far enough to log anything in /var/log/syslog about the boot.

This bug might also be related: https://bugzilla.kernel.org/show_bug.cgi?id=203839

Comment 2 rocko 2019-06-10 07:33:13 UTC

Created attachment 283169 [details]
syslog of boot

So, I can confirm that 5.2-rc4 does indeed eventually complete booting after a 3 minute stall. I've attached /var/log/syslog covering the shutdown and reboot sequence. Boot started at around 15:23, but the first syslog messages appear at 15:26.

Comment 3 Kostiantyn Miklevskyi 2019-06-10 14:11:11 UTC

Same here.
For me the clear cause is a Logitech Wireless Mouse USB receiver. When it is plugged in - I'm sitting and waiting for boot for ~3 minutes. When I boot my Dell E5510 laptop without it plugged in there's no boot delay. 5.2 rc4, Ubuntu 19.04.

Comment 4 Elimar Riesebieter 2019-06-10 17:40:50 UTC

I can confirm that unplugging Logitech Wireless Mouse USB receiver seems to fix the boot itself fine. 

Plugin the receiver after booting takes another 2-3 minutes to get the mouse (gpm) working again.

Well compiling hid, usbhid directly into the kernel (not as a module) gets me a running system within a fingersnip including my mouse ;-)

So where we do have to file the bug now? klibs/kinit seemdst be the wron place here?

Comment 5 Kostiantyn Miklevskyi 2019-06-10 18:55:00 UTC

This might be a related or a duplicate bug https://bugzilla.kernel.org/show_bug.cgi?id=203741

Comment 6 Elimar Riesebieter 2019-06-10 20:20:34 UTC

Reverting 

git revert 4ceabaf79
git revert a025a18fe

as recommended in https://bugzilla.kernel.org/show_bug.cgi?id=203741 solved the problem too.

Comment 7 Hans de Goede 2019-06-11 08:41:29 UTC

(In reply to Elimar Riesebieter from comment #6)
> Reverting 
> 
> git revert 4ceabaf79
> git revert a025a18fe
> 
> as recommended in https://bugzilla.kernel.org/show_bug.cgi?id=203741 solved
> the problem too.

Good, those 2 reverts are queued up in: https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/log/?h=for-5.2/fixes

So they should show up in an upcoming 5.2-rc# release.

Comment 8 Elimar Riesebieter 2019-06-17 10:15:03 UTC

(In reply to Hans de Goede from comment #7)
> (In reply to Elimar Riesebieter from comment #6)
> > Reverting 
> > 
> > git revert 4ceabaf79
> > git revert a025a18fe
> > 
> > as recommended in https://bugzilla.kernel.org/show_bug.cgi?id=203741 solved
> > the problem too.
> 
> Good, those 2 reverts are queued up in:
> https://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git/log/?h=for-5.2/
> fixes
> 
> So they should show up in an upcoming 5.2-rc# release.

5.2-rc5 works like a charm ;-)

Thanks for cooperation
Elimar