Public bug reported:
It was observed that after a SD card is used, the computer can have a
kernel BUG or kernel panic after a partition from removable media is
unmounted.
Steps to reproduce:
1) Insert a SD card;
2) Mount the SD card;
3) Unmount the SD card;
4) Eject the SD card;
5) Try mount or
Public bug reported:
I tried to start Lakka (http://www.lakka.tv/) using QEMU with Intel
GVT-g and, when the graphics should start loading, the system freezes.
The command line used was:
The command line I used to start QEMU was:
sudo qemu-system-x86_64 -m 1024 -cpu Skylake-Client -vga none
Public bug reported:
I was deleting a large amount of files from an exFAT USB pendrive and at
45% of the file deletion, the system became degraded: USB disks were no
longer possible to mount or dismount, no new USB devices were detected,
systemd-journal and syslog were using 100% CPU on htop
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1880049
Title:
Using Lakka with Intel GVT-g freezes the host system
I tested 5.7.0-050700-generic, and the system didn't crash. I'm able to
use Lakka from QEMU most of the times. Once, a GPU hang happened, but I
was able to restart LightDM to fix it.
The attached file is the card0/error after the GPU hang.
** Attachment added: "card0/error"
I'm not able to reproduce this using 5.4.0-37-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1824175
Title:
iGVT-g guest does not load graphics: kernel WARNING and wedged GPU
Using the kernel from comment 10, I did not observe an improvement: the
devices connected to the hub aren't detected as often as before,
requiring the same workaround.
** Attachment added: "Two dmesg with the test kernel"
Here are two dmesg with the arguments added. On first dmesg I connected
the USB hub 3 times. The two devices connected to the hub were:
045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
25a7:fa23 Compx 2.4G Receiver
On the first attempt, all devices were detected. On the second and third
Public bug reported:
The USB hub identified as: "214b:7000 USB2.0 HUB" presents a problem on
Linux where often it is only detected after another device (for example
a mouse) is connected to it.
On the computer's firmware screen and configuration, and on Windows, the
hub works fine: once
Disabling the autosuspend from the USB device fixed the problem.
However, I did not want to disable it for all USB devices, so I added an
udev rule:
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="214b",
ATTR{idProduct}=="7000", ATTR{product}=="USB2.0 HUB",
TEST=="power/control",
Using 5.10-rc4, the same problem was observed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1904953
Title:
USB2.0 HUB only works after an USB device is connected
Status in linux
** Also affects: linux-signed-hwe-5.11 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1925263
Title:
TL-WN821N V5
Public bug reported:
A Windows 10 iGVT-g guest is crashing if left idle for too long. "Too
long" can mean hours or even minutes with no load. The QEMU command line
is:
/usr/bin/qemu-system-x86_64 -name Windows 10 -nodefaults -M pc,usb=true
-machine kernel_irqchip=on -enable-kvm -mem-prealloc
Public bug reported:
If the microphone volume is set the same for both left and right
channels, it's nearly silent, being unusable, as if the left and right
channel cancel each other.
The workaround I had on Focal was to create a remapped source only with
the right channel. However, on jammy,
Public bug reported:
When resizing the terminal window, intel_gpu_top may crash if the window
become small enough. The output when it crashes is:
intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
`max_len > 0' failed.
Abortado
I was able to reproduce this crash with
Public bug reported:
It was observed that linux-firmware upgrade started failing now. At the
end of the apt upgrade process, the following message appeared (messages
are in Portuguese):
Erros foram encontrados durante o processamento de:
16 matches
Mail list logo
