Bug#933981: cdrom: USB, KVM create connect/disconnect loop in level1 (repair) install

Daniel Hedstrom <[email protected]>
Newsgroups gmane.linux.debian.devel.cd
Message-ID <EC17672F-9029-4DE0-AF4D-C676A70A7F96__7424.43227661482$1704697953$gmane$org@icloud.com>
On Mon, 05 Aug 2019 14:28:47 -0400 Tom Sullivan <[email protected]> wrote:
> Package: cdrom
> Severity: grave
> Tags: d-i
> Justification: renders package unusable
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> I had another machine that gave kernel panic while upgrading from Stretch to
> Buster. Use of Graphical install was also a problem during re-install due to
> destroyed system. (I reported this issue in another report.) Thus, I chose to
> upgrade an identical machine from level 1 (Debain Repair in GRUB2 boot menu).
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> The scrolling log in the command line display showed repeated
> connect/disconnect loops for USB devices (of many kinds). This applied also to
> USB mice and keyboards connected via KVM.
>
> For what it was worth, I used a local cache of the DVDs on the machine's hard
> drive.
>
> Unplugged all USB, plugged in single USB keyboard only, and directly, not via
> KVM.
>
> * What was the outcome of this action?
>
> Upgraded fine with just the keyboard directly plugged into USB.
>
> * What outcome did you expect instead?
>
> Correct handling of USB, without issues.
>
>
>
>
> -- System Information:
> Debian Release: 10.0
> APT prefers stable
> APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
>

Sent from my iPhone
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.