from:"Jérôme"

[Kernel-packages] [Bug 1979886] Re: xHCI race conditions 5.15.0-40-generic

2023-01-03 Thread Jérôme Poulin

I can confirm the same kind of behavior on a ASMedia Technology Inc.
ASM2142/ASM3142 USB 3.1 Host Controller.

It has been plaguing me for years, xhci_hcd seems broken when using USB
hubs such as the one used by the Valve Index (VR headset).  I have to
use my reset_usb script once in a while to rebind xhci_hcd and reset the
whole thing.  At least I don't have to reboot anymore but it is more
than annoying.

Same behavior as yours, USB works then suddenly one or more device
behind the hub stops responding.  Then everything is frozen until I
unplug a device, then it loops with

[46588.094379] hub 3-2:1.0: hub_ext_port_status failed (err = -110)

This script is able to reset the driver to make everything working again
but, of course, will crash my virtual reality session.

```
#!/bin/bash
[ `id -u` -ne 0 ] && exec sudo "$0"
cd /sys/bus/pci/drivers/xhci_hcd
BUS=":b3:00.0"
echo "$BUS" > unbind
sleep 5
echo "$BUS" > bind
sleep 5
find "$BUS/" -name control -exec /bin/sh -c "echo on > {}" \;
```

-- 
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/1979886

Title:
  xHCI race conditions 5.15.0-40-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 22.04 there are plenty of usb troubles from xHCI

  Some hardware gets the xHCI dead and complete usb shutdown
  other hardware works better with first tier of hubs
  second hub tier is still unreliable, pointing to race conditions

  troubled devices seems to be VIA 2109:0822 2109:0715

  Here I have a 5 Gb/port, hub then hub 2109:0822

  echoed to console:
  Jun 19 23:51:15  kernel: [29817.094981] hub 2-5:1.0: hub_ext_port_status 
failed (err = -110)
  Jun 19 23:51:17  kernel: [29819.142955] usb 2-5.3: Port disable: can't 
disable remote wake
  Jun 19 23:51:18  kernel: [29820.166925] usb 2-5-port3: cannot disable (err = 
-110)
  Jun 19 23:51:20  kernel: [29822.374883] usb 1-8: Failed to suspend device, 
error -110
  Jun 19 23:51:23  kernel: [29825.286836] hub 2-5:1.0: hub_ext_port_status 
failed (err = -110)

  key here: Port disable: can't disable remote wake
  -110 is ETIMEDOUT which when plugged in direct host produces xHCI dead

  If the device is unplugged, unplug is undetected and leads to infinite errors 
-110 -71
  — missed unplug has also been seen with usb storage 2109:0715

  other key errors:
  LPM exit latency is zeroed, disabling LPM.
  usb_reset_and_verify_device Failed to disable LPM

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-40-generic 5.15.0-40.43
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  Date: Sat Jun 25 08:49:26 2022
  HibernationDevice: RESUME=none
  MachineType: Apple Inc. Macmini8,1
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=screen
   PATH=(custom, no user)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: root=ZFS=rpool/ROOT/ubuntu_mc4at7 ro 
initrd=EFI\hostname\initrd.img
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-40-generic N/A
   linux-backports-modules-5.15.0-40-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2022
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 1731.120.10.0.0 (iBridge: 19.16.15071.0.0,0)
  dmi.board.name: Mac-7BA5B2DFE22DDD8C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini8,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-7BA5B2DFE22DDD8C
  dmi.modalias: 
dmi:bvnAppleInc.:bvr1731.120.10.0.0(iBridge19.16.15071.0.0,0):bd04/24/2022:br0.1:svnAppleInc.:pnMacmini8,1:pvr1.0:rvnAppleInc.:rnMac-7BA5B2DFE22DDD8C:rvrMacmini8,1:cvnAppleInc.:ct9:cvrMac-7BA5B2DFE22DDD8C:sku:
  dmi.product.family: Mac mini
  dmi.product.name: Macmini8,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1979886/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.n

Re: [Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend

2022-02-27 Thread Jérôme Blanchard

Hi, using latest 5.16 kernel version fixed the problem for me. Actually it
was a problem with amdgpu so i'm not sure it is the same for your
architecture but new kernel always comes with latest drivers support. Maybe
tout could give a try ti thé Dev version of Ubuntu 22.04 to see...

Le dim. 27 févr. 2022 à 16:40, David <1909...@bugs.launchpad.net> a
écrit :

> Same issue for me on a new Dell Inspiron 14" laptop on Ubuntu 20.04,
> kernal version 5.13.0-30-generic.
>
>
> 16 GB DDR, 512 SSD.
> i7, Intel graphics.
>
> Usually I get to the unlock screen and the mouse pointer can be moved,
> but I can't click on anything and the keyboard doesn't work. Sometimes
> it seems like unplugging and reconnecting power and/or a usb mouse
> transceiver makes it recover and allow me to recover; sometime not.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1909005
>
> Title:
>   Ubuntu does not resume (wake up) from suspend
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions
>
>

-- 
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/1909005

Title:
  Ubuntu does not resume (wake up) from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Whenever Ubuntu gets into suspend state, I cannot wake it up. 
  -Keystrokes start the fans but screen does not turn on and Ubuntu still seems 
to be suspended because in my teamviewer account the computer is still offline.
  -Power button clicks do not help
  -I always have to turn off computer by holding power button and then turn it 
on again.

  The only kernel that works is the following: "linux-
  image-5.0.0-1070-oem-osp1". But with this old kernel I run into
  different problems.

  I have the latest BIOS version from Dell (released 2020-11-27) and the
  latest updates in Ubuntu 20.04.

  I will post logs during suspend and important logs (found in Logs gui
  tool)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-58-generic 5.4.0-58.64
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philip 2340 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 13:59:14 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18
  InstallationDate: Installed on 2019-12-04 (383 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
   Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3593
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep 
tsc=reliable quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-58-generic N/A
   linux-backports-modules-5.4.0-58-generic  N/A
   linux-firmware1.187.6
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 04N9HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3593
  dmi.product.sku: 0979
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled

2020-07-06 Thread Jérôme de Bretagne

Hi You-Sheng,

Sorry for this very late feedback, I just saw your message a few minutes
ago as I was not subscribed to this bug.

I've now tested your backport of the patches and I can confirm that it
is indeed working on my machine (Dell Latitude 7275).

FYI, I was also pointed out that there is an on-going discussion about suspend 
failures following these patches, details here: 
https://bugzilla.kernel.org/show_bug.cgi?id=207629
but I'm not seeing this issue in my case.

Cheers,
Jérôme

** Bug watch added: Linux Kernel Bug Tracker #207629
   https://bugzilla.kernel.org/show_bug.cgi?id=207629

-- 
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/1823076

Title:
  System wakes up immediately after suspend if Bluetooth is still
  enabled

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1882890] Re: Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

2020-06-10 Thread Jérôme

Here is the output of "dmesg | microcode:" obtained from Ubuntu 20.04
live USB disk:

--8<--
[0.00] microcode: microcode updated early to revision 0xd6, date = 
2019-10-03
[1.177905] microcode: sig=0x406e3, pf=0x80, revision=0xd6
[1.177938] microcode: Microcode Update Driver: v2.2.
-->8--

-- 
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/1882890

Title:
  Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  This morning I applied the latest updates on my Ubuntu 16.04 (kernel
  4.15.0-106-generic + intel-microcode 3.20200609.0ubuntu0.16.04.0) and
  rebooted as usual to boot on the new kernel but the system won't boot:
  black screen.

  I tried booting the previous kernel 4.15.0-101 and it seems to be the
  same : in grub I select the 4.15.0-101 kernel, press enter, a message
  "Loading initrd..." is printed but nothing else happens.

  Tried even older kenrel 4.4.0-184-generic : same problem, "Loading
  initrd...", and nothing happens.

  I managed to boot a 4.4.0-142-generic, but bluetooth and wifi are non-
  functionnal.

  I mounted the /boot partition from a USB rescue drive, and it seems that all 
the initrd images that got updated this morning are not bootable anymore :
  - initrd.img-4.15.0-106-generic
  - initrd.img-4.15.0.101-generic
  - initrd.img-4.4.0-184-generic

  I tried regenerating the images with update-initramfs but it's the
  same : "Loading initrd" message but nothing happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882890/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1882890] Re: Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

2020-06-10 Thread Jérôme

I forced a downgrade of intel-microcode from
"3.20200609.0ubuntu0.16.04.0" to "3.20151106.1", regenerated the initrd
images, and now they seems to boot correctly!

So, the problem seems to be with latest intel-microcode?

-- 
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/1882890

Title:
  Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  This morning I applied the latest updates on my Ubuntu 16.04 (kernel
  4.15.0-106-generic + intel-microcode 3.20200609.0ubuntu0.16.04.0) and
  rebooted as usual to boot on the new kernel but the system won't boot:
  black screen.

  I tried booting the previous kernel 4.15.0-101 and it seems to be the
  same : in grub I select the 4.15.0-101 kernel, press enter, a message
  "Loading initrd..." is printed but nothing else happens.

  Tried even older kenrel 4.4.0-184-generic : same problem, "Loading
  initrd...", and nothing happens.

  I managed to boot a 4.4.0-142-generic, but bluetooth and wifi are non-
  functionnal.

  I mounted the /boot partition from a USB rescue drive, and it seems that all 
the initrd images that got updated this morning are not bootable anymore :
  - initrd.img-4.15.0-106-generic
  - initrd.img-4.15.0.101-generic
  - initrd.img-4.4.0-184-generic

  I tried regenerating the images with update-initramfs but it's the
  same : "Loading initrd" message but nothing happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882890/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1882890] Re: Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

2020-06-10 Thread Jérôme

I forced a downgrade of intel-microcode from "" to "", regenerated the
initrd images, and now they seems to boot correctly!

So, the problem seems to be with latest intel-microcode?

-- 
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/1882890

Title:
  Cannot boot initrd.img-4.15.0-106-generic on Ubuntu 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  This morning I applied the latest updates on my Ubuntu 16.04 (kernel
  4.15.0-106-generic + intel-microcode 3.20200609.0ubuntu0.16.04.0) and
  rebooted as usual to boot on the new kernel but the system won't boot:
  black screen.

  I tried booting the previous kernel 4.15.0-101 and it seems to be the
  same : in grub I select the 4.15.0-101 kernel, press enter, a message
  "Loading initrd..." is printed but nothing else happens.

  Tried even older kenrel 4.4.0-184-generic : same problem, "Loading
  initrd...", and nothing happens.

  I managed to boot a 4.4.0-142-generic, but bluetooth and wifi are non-
  functionnal.

  I mounted the /boot partition from a USB rescue drive, and it seems that all 
the initrd images that got updated this morning are not bootable anymore :
  - initrd.img-4.15.0-106-generic
  - initrd.img-4.15.0.101-generic
  - initrd.img-4.4.0-184-generic

  I tried regenerating the images with update-initramfs but it's the
  same : "Loading initrd" message but nothing happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882890/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled

2020-05-12 Thread Jérôme de Bretagne

A fix for this issue is planned for v5.7, included from rc1 up to rc5 so
far, with this patch series:
https://lore.kernel.org/patchwork/cover/1208369/ and the 4 commits from
9952d90ea2885d7cbf80cd233f694f09a9c0eaec up to
4867bd007d25a8dfd4ffc558534f7aec8b361789

I had created a bug about this a while ago here: 
https://bugzilla.kernel.org/show_bug.cgi?id=198993
and I've just confirmed that the patch series is indeed fixing this issue on my 
system (a Dell Latitude 7275).

I'm expecting this will cover most/all of the other systems mentioned in
this discussion too. I hope this sharing will be useful for some of you.

Cheers,
Jérôme

** Bug watch added: Linux Kernel Bug Tracker #198993
   https://bugzilla.kernel.org/show_bug.cgi?id=198993

-- 
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/1823076

Title:
  System wakes up immediately after suspend if Bluetooth is still
  enabled

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1813663] Re: External monitors does not work anymore 4.15.0-44

2019-01-30 Thread Jérôme Steunou

I have the same issue with a Dell Vostro & business dock WD15

4.15.0-43 works well, I saved that choice on GRUB to be safe.

Dell Vostro
Intel® Core™ i5-8250U CPU @ 1.60GHz × 8
Intel® UHD Graphics 620 (Kabylake GT2)

-- 
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/1813663

Title:
  External monitors does not work anymore 4.15.0-44

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed

Bug description:
  I am using a docking station for my laptop. After install the
  4.15.0-44 update my external monitors goes undetected after logging in
  or having the laptop closed.

  I am on 18.04.1 LTS with Intel® HD Graphics 620 (Kaby Lake GT2)
  Graphics.

  Going back to the 4.15.0-43 version makes it all work fine again.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jonas  2407 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=80397b76-2ded-4f7d-adbf-dfdface8e2d4
  InstallationDate: Installed on 2018-10-17 (103 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20HF004MMX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=64cf1582-d574-4e2f-a40a-7942c40caf5d ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HF004MMX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HF004MMX:pvrThinkPadT470s:rvnLENOVO:rn20HF004MMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HF004MMX
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1813795] Re: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel

2019-01-30 Thread Jérôme Steunou

*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663

I have the same issue with a Dell Vostro & business dock WD15

4.15.0-43 works well, I saved that choice on GRUB to be safe.

Dell Vostro
Intel® Core™ i5-8250U CPU @ 1.60GHz × 8
Intel® UHD Graphics 620 (Kabylake GT2)

--
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/1813795

Title:
Dell tablet crashes when plugged into docking station with 4.15.0-44
kernel

Status in linux package in Ubuntu:
Confirmed

Bug description:
I have a Dell 5290 2-in-1 tablet that has been running Ubuntu 18.04
successfully for several months. Today I upgraded the kernel from
4.15.0-43 to 4.15.0-44. The tablet functions normally until it is
plugged into its docking station, then the screen freezes.

Technically, the screen flickers a few times, then goes blank, leaving
only the frozen mouse pointer. The system is still running, though as
I can ssh into my tablet. sudo reboot will not reboot the tablet, but
sudo reboot -f will.

When I force the tablet to load 4.15.0-43, the tablet functions
normally. i.e. even when I plug it into its docking station, it
continues to perform properly. It's only with 4.15.0-44 that it
freezes.

As you can see from the linked question and forum thread, this appears to be
affecting many Dell tablets and laptops. It also appears clear that the bug is
not present in 4.15.0-43.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rybu 1971 F pulseaudio
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=35ab6535-9677-4ec9-9b70-33d75778947f
InstallationDate: Installed on 2018-11-09 (81 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: Dell Inc. Latitude 5290 2-in-1
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-44-generic N/A
linux-backports-modules-4.15.0-44-generic N/A
linux-firmware 1.173.3
Tags: bionic
Uname: Linux 4.15.0-44-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 08/27/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.3
dmi.board.name: 0M27Y3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 32
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.4.3:bd08/27/2018:svnDellInc.:pnLatitude52902-in-1:pvr:rvnDellInc.:rn0M27Y3:rvrA00:cvnDellInc.:ct32:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5290 2-in-1
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions

--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1662003] Re: /sbin/crda failed with exit code 249

2018-03-02 Thread Jérôme

** Tags removed: 1386
** Tags added: i386

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crda in Ubuntu.
https://bugs.launchpad.net/bugs/1662003

Title:
  /sbin/crda failed with exit code 249

Status in crda package in Ubuntu:
  Confirmed

Bug description:
  /var/log/syslog tells :
  ---
  kernel: [0.144719] ACPI: PCI Root Bridge [PCI0] (domain  [bus 00-ff])
  systemd-udevd:  Process '/sbin/crda' failed with exit code 249.
  kernel: [0.144728] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig 
ASPM ClockPM Segments MSI]
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: crda 3.13-1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb  5 20:18:42 2017
  InstallationDate: Installed on 2017-02-01 (3 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: crda
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1662003/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1662003] [NEW] /sbin/crda failed with exit code 249

2017-02-05 Thread Jérôme

Public bug reported:

/var/log/syslog tells :
---
kernel: [0.144719] ACPI: PCI Root Bridge [PCI0] (domain  [bus 00-ff])
systemd-udevd:  Process '/sbin/crda' failed with exit code 249.
kernel: [0.144728] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM 
ClockPM Segments MSI]
---

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: crda 3.13-1
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Feb  5 20:18:42 2017
InstallationDate: Installed on 2017-02-01 (3 days ago)
InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: crda
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: crda (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crda in Ubuntu.
https://bugs.launchpad.net/bugs/1662003

Title:
  /sbin/crda failed with exit code 249

Status in crda package in Ubuntu:
  New

Bug description:
  /var/log/syslog tells :
  ---
  kernel: [0.144719] ACPI: PCI Root Bridge [PCI0] (domain  [bus 00-ff])
  systemd-udevd:  Process '/sbin/crda' failed with exit code 249.
  kernel: [0.144728] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig 
ASPM ClockPM Segments MSI]
  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: crda 3.13-1
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb  5 20:18:42 2017
  InstallationDate: Installed on 2017-02-01 (3 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: crda
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1662003/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time

2016-11-27 Thread Jérôme Poulin

That new file could be added to the thin-provisioning-tools which would
trigger an initramfs update.

I forgot to remove cache_dump, cache_restore and cache_metadata_size
which are not needed to boot.

-- 
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/1423796

Title:
  Unable to mount lvmcache root device at boot time

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I'm experimenting with Vivid Vervet on a virtual machine and tried a
  new LVM feature, lvmcache. I made a cache for the root file system,
  rebuilt the initrd and rebooted the VM.

  At boot time, the system failed to activate the root LV. After some
  investigation, I found out, it's because the initrd is missing some
  essential stuff needed for activating a cached LV.

  The initrd was missing the dm-cache module. I regenerated the initrd
  with explicitly listing dm-cache in /etc/initramfs-tools/modules, but
  the system still can't boot up, because now it is missing the
  /usr/sbin/cache_check utility.

  As SSDs are becoming more and more common, I think it will be common
  to use them as cache for root file systems, thus it is mandatory to
  make sure that an initrd can mount an lvmcached root device when
  necessary, preferably without /etc/initramfs-tools/modules and other
  manual initrd hacking.

  System details:

  Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
  2015 x86_64 x86_64 x86_64 GNU/Linux

  Distributor ID:   Ubuntu
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  Codename: vivid

  LVM version: 2.02.111(2) (2014-09-01)
  Library version: 1.02.90 (2014-09-01)
  Driver version:  4.28.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time

2016-11-27 Thread Jérôme Poulin

After making my system work again, which took a while since most live
media and even the installer don't support LVM cache, I had it working
for writeback on my system with the following.

/etc/initramfs-tools/hooks/lvm2_cache
{{{
#!/bin/sh

PREREQ="lvm2"

prereqs()
{
echo "$PREREQ"
}

case $1 in
prereqs)
prereqs
exit 0
;;
esac

if [ ! -x /sbin/lvm ]; then
exit 0
fi

. /usr/share/initramfs-tools/hook-functions

copy_exec /usr/sbin/cache_check
copy_exec /usr/sbin/cache_dump
copy_exec /usr/sbin/cache_metadata_size
copy_exec /usr/sbin/cache_repair
copy_exec /usr/sbin/cache_restore

for x in dm_cache_cleaner dm_cache_smq dm_cache dm_persistent_data dm_bio_prison
do
manual_add_modules ${x}
done
}}}

-- 
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/1423796

Title:
  Unable to mount lvmcache root device at boot time

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I'm experimenting with Vivid Vervet on a virtual machine and tried a
  new LVM feature, lvmcache. I made a cache for the root file system,
  rebuilt the initrd and rebooted the VM.

  At boot time, the system failed to activate the root LV. After some
  investigation, I found out, it's because the initrd is missing some
  essential stuff needed for activating a cached LV.

  The initrd was missing the dm-cache module. I regenerated the initrd
  with explicitly listing dm-cache in /etc/initramfs-tools/modules, but
  the system still can't boot up, because now it is missing the
  /usr/sbin/cache_check utility.

  As SSDs are becoming more and more common, I think it will be common
  to use them as cache for root file systems, thus it is mandatory to
  make sure that an initrd can mount an lvmcached root device when
  necessary, preferably without /etc/initramfs-tools/modules and other
  manual initrd hacking.

  System details:

  Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
  2015 x86_64 x86_64 x86_64 GNU/Linux

  Distributor ID:   Ubuntu
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  Codename: vivid

  LVM version: 2.02.111(2) (2014-09-01)
  Library version: 1.02.90 (2014-09-01)
  Driver version:  4.28.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

67 matches

Mail list logo