[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#918107: marked as done (Random boot failure using VMware Paravirtual Adapter)

Your message dated Sat, 29 May 2021 01:56:13 -0700 (PDT)
with message-id <60b201ad.1c69fb81.210eb.e255@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #918107,
regarding Random boot failure using VMware Paravirtual Adapter
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
918107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918107
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-4.19.0-1-amd64
Version: 4.19.12-1

Random boot failures on VMware when VM uses the Paravirtual Adapter. I drop into a busybox shell after the first line from the kernel. No disk found. Normally the 2nd line mentions the disk - this line doesn’t appear on failing boots - no disk is accessible. Rebooting sometimes works.

Kernel 4.18.0-3-amd64 work all the time. 4.19.3-1 is also broken.

LSI SCSI controller works fine on every reboot.

I have looked through the changelog of 4.19.12. it mentions code re-arrangement in pv_scsi driver - maybe something broke there?

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: