My mistake, I know now how to add the files separately without using an
archive.
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5244341/+files/version.log
--
You received this bug notification because you are a member of Kernel
Pac
this kernel
bug.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: martin27966 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 19.1
+ HibernationDevice: R
ash.
I assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
CurrentDesk
assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
CurrentDesk
ion
crash.
I assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
Cu
assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
CurrentDesk
session
crash.
I assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
Cu
my user session
crash.
I assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F
assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
CurrentDesk
OMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 19.1
HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
InstallationDate: Installed on 2018-07-21 (228 days ago)
InstallationMedia: Linux Mint 19 "Tara&qu
assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
CurrentDesk
ion
crash.
I assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
Cu
ion
crash.
I assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
Cu
ion
crash.
I assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
Cu
assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
CurrentDesk
ash.
I assume that my attached external USB to SATA HDD could be cause this kernel
bug.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: martin27966 F pulseaudio
CurrentDesk
I've tested 17.04 and 17.10 and can confirmed that the BYD trackpad is
not detected at all anymore. I've had some success using the DKMS
version of the driver:
* https://github.com/jayk/psmouse-bydfull-dkms
--
You received this bug notification because you are a member of Kernel
Packages, whic
What detection was disabled and what was the good reason?
--
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/1424293
Title:
BYD trackpad detected as PS/2 mouse
Status in linux package in Ub
The other bluetooth bug is now here:
https://bugs.launchpad.net/ubuntu/+bug/1893299
** Description changed:
Pulseaudio has been super unstable since ubuntu 20.04.
bluetooth has multiple connectivity issues which sometimes can only be
resolved by unpairing and then pairing again.
- e..g Ve
** Attachment added: "lspci"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+attachment/5405336/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/189281
The headset is Avantree Audition
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1892814
Title:
pulseaudio bluetooth problems with profiles
Status in bluez package in Ubuntu:
Incomplet
but the problem happens with other bluetooth headsets as well
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1892814
Title:
pulseaudio bluetooth problems with profiles
Status in bluez p
just to mention that with the same chip in 18.04 it wasn't that unstable
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1892814
Title:
pulseaudio bluetooth problems with profiles
Status
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+attachment/5405338/+files/lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/18
This error is still happening and it is critical error which does not
allow me to start Ubuntu !
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
lC2: martin 2584 F pulseaudio
/dev/snd/controlC0: martin 2584 F pulseaudio
/dev/snd/controlC1: martin 2584 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-12-08 (217 days
Public bug reported:
Running the following docker image on Ubuntu 20.10/kernel 5.8 will hard-
freeze the computer:
docker run --rm -ti -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=myPASSWD123" -p
1433:1433 --name sqlserver mcr.microsoft.com/mssql/server:2017-latest-
ubuntu
I am unable to Alt+Sysrq+SUB to
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412875/+files/Lsusb-v.txt
--
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/1896
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412868/+files/CRDA.txt
--
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/1896446
Ti
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412881/+files/PulseList.txt
--
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/
apport information
** Tags added: apport-collected
** Description changed:
Running the following docker image on Ubuntu 20.10/kernel 5.8 will hard-
freeze the computer:
docker run --rm -ti -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=myPASSWD123" -p
1433:1433 --name sqlserver mcr.microsoft.com/
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412877/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412873/+files/Lsusb.txt
--
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/1896446
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412870/+files/IwConfig.txt
--
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/18
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412874/+files/Lsusb-t.txt
--
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/1896
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412872/+files/Lspci-vt.txt
--
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/18
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412876/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412871/+files/Lspci.txt
--
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/1896446
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412879/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412880/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412878/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412869/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412883/+files/UdevDb.txt
--
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/1896446
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412882/+files/RfKill.txt
--
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/1896446
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412884/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Changed the status of the bug to 'Confirmed' as asked by the apport
program.
--
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/1896446
Title:
Running mcr.microsoft.com/mssql/server:2017-lat
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1896446/+attachment/5412885/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, whic
For what it's worth, I've now had the exact same problem, which led me
here.
On a bare-metal 20.04 using full blank HDDs as OSDs (/dev/sda etc.),
installing using cephadm worked fine with an XFS root, but later on when
I reinstalled and tried ZFS root, I then got the same behaviour
described above
Follow up - it does seem to be the tmpfs mount that activate creates
that causes the problem.
I manually started the activate container by running the podman command
from unit.run for the activate step, but just ran "bash -l" instead of
the actual activate command
Then I prevented the mount tmpfs
I think the reason that ZFS behaves differently is because of this...
/usr/lib/python3.6/site-packages/ceph_volume/devices/raw/activate.py
from ceph_volume.util import system
# mount on tmpfs the osd directory
osd_path = '/var/lib/ceph/osd/%s-%s' % (conf.cluster, osd_id)
if not syste
-0ubuntu8.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: martin 2483 F pulseaudio
/dev/snd/controlC0: martin 2483 F pulseaudio
/dev/snd/controlC2: martin 2483 F pulseaudio
CurrentDesktop: ubuntu:GNOME
@chihchun see bug 1879389 for the apport dump.
Because the kernel logs fill up with
WARN_ON(intel_wait_for_register(...))/hsw_wait_for_power_well_enable
it's hard to find specific other issues.
I have observed the sound driver being crashy/sad on the same hardware
but it's possibly improved with
Public bug reported:
Ubuntu 20.04
uname -a:
Linux MartoBeast 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
Have been plagued with hard lockups for a while now. This is the most recent
ones
Hard lockup with this in the logs.
** Affects: linux (Ubunt
** Description changed:
+ Ubuntu 20.04
+ uname -a:
+ `Linux MartoBeast 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux`
+
Have been plagued with hard lockups for a while now. This is the most recent
ones
Hard lockup with this in the logs.
** Desc
one.
Hard lockup with this in the logs.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.4
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC2: martin 2584 F pulseaudio
+ /dev/snd/controlC0: martin 2584 F pulseaudio
kups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd
kups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd
rd lockups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
with hard lockups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
rd lockups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd/controlC
agued with hard lockups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F
or a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd/controlC
kups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd
ockups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd
rd lockups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
with hard lockups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
or a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd/controlC
or a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd/controlC
MMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd/controlC0: martin 2584 F pulseaudio
/dev/snd/controlC1: martin 2584 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed
kups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd
with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd/controlC0: martin 2584 F pulseaudio
/dev/snd/controlC1: m
kups for a while now. This is the most recent
one.
Hard lockup with this in the logs.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: martin 2584 F pulseaudio
/dev/snd
** Package changed: ubuntu => linux-oem-5.6 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1887723
Title:
mlx5_core: Error cqe on cqn
Status in linux-oem-5.6 package in
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-
-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64
x86_64 GNU/Linux
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.4
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: martin 2590 F pulseaudio
+ /dev/snd
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-
SS COMMAND
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on
SS COMMAND
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on
SS COMMAND
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed
PID ACCESS COMMAND
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate:
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-12-08 (22
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-12-08 (22
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-12-08 (22
SS COMMAND
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on
ND
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-12-08
ND
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2019-
SS COMMAND
/dev/snd/controlC1: martin 2590 F pulseaudio
/dev/snd/controlC0: martin 2590 F pulseaudio
/dev/snd/controlC2: martin 2590 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Install
I can reproduce the bug on 5.4.0-40-generic
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1887723
Titl
Problem vanished after second re-install. Unable to reproduce.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1888372
Ti
I am unable to run the command, because the bug triggers a panic.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux-oem-5.6 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which i
I confirm that this bug can be avoided by setting the kernel option:
iommu=pt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1887723
Title:
mlx5_core: Error cqe on cqn
Status in
Public bug reported:
I am using a USB 3.0 hub that works fine under windows or on my ubuntu desktop,
but when connected to my ubuntu laptop all devices connected to the usb hub get
disconnected after a few seconds. It I'm only connecting a mouse and keyboard
so it shouldn't be using up too much
The new 5.4.0-51 kernel has been released to focal-release today and
this includes the "routing" fix. Tested it on Mint 20 and it works for
me! I think this bug can be closed now
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-con
ubuntu-20.10-beta-desktop-amd64.iso does not boot as well. Ends with the
same kernel panic.
** Attachment added: "ubuntu_20_10.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878341/+attachment/5422660/+files/ubuntu_20_10.jpg
--
You received this bug notification because you are a
Adding boot parameter pci=nocrs makes no difference.
> If you happen to upgrade to focal via update-manager or do-release
upgrade it would be good to know does kernel still panic.
I'm staying with Ubuntu 19.10, I did not upgrade, I cannot risk
unbootable computer.
--
You received this bug notif
While it is something with PCI(?) I tried to remove both PCI cards:
* Tuner ASUS MyCinema P7131 Hybrid Analog/DVB TV card
* USB 3.1 adapter Kouwell UB-135-2
But the same kernel panic occurred.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
I downloaded files from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9/amd64/
and installed 5.9.0
sudo dpkg -i linux-headers-5.9.0-050900_5.9.0-050900.202010112230_all.deb
sudo dpkg -i
linux-headers-5.9.0-050900-generic_5.9.0-050900.202010112230_amd64.deb
sudo dpkg -i
linux-modules-5.9.0-0
501 - 600 of 2221 matches
Mail list logo
