[Kernel-packages] [Bug 2054866] Re: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to install/upgrade: installed linux-headers-6.5.0-21-generic package post-installation script subprocess r

2024-02-26 Thread Joe Zhou
Find the problem, it isn't a broken/unsupported DKMS module for my case.

The system's default gcc/g++ version is 13. While installing CUDA 11.8,
I used update-alternatives to change the gcc/g++ version to 11. Switch
back to gcc/g++ 13 solved this issue.

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

Title:
  package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to
  install/upgrade: installed linux-headers-6.5.0-21-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  plese slove this
  .

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-21-generic 6.5.0-21.21
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  almamunpc   2365 F wireplumber
   /dev/snd/controlC1:  almamunpc   2365 F wireplumber
   /dev/snd/seq:almamunpc   2355 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Feb 24 12:40:52 2024
  ErrorMessage: installed linux-headers-6.5.0-21-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-02-10 (14 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB:
   0 EFI VGA
   1 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=6adb3052-5462-40b3-a845-fe252d1d312e ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to 
install/upgrade: installed linux-headers-6.5.0-21-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F16
  dmi.board.asset.tag: Default string
  dmi.board.name: B760M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF16:bd12/14/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnB760MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB760MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B760 MB
  dmi.product.name: B760M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054866/+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 2054866] Re: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to install/upgrade: installed linux-headers-6.5.0-21-generic package post-installation script subprocess r

2024-02-24 Thread Joe Zhou
Same problem. From /var/log/dpkg.log, Ubuntu 23.10 seems to
automatically install kernel 6.5.0-21-generic today. However, it fails
with a half-installed status.

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

Title:
  package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to
  install/upgrade: installed linux-headers-6.5.0-21-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  plese slove this
  .

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-headers-6.5.0-21-generic 6.5.0-21.21
  ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  almamunpc   2365 F wireplumber
   /dev/snd/controlC1:  almamunpc   2365 F wireplumber
   /dev/snd/seq:almamunpc   2355 F pipewire
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sat Feb 24 12:40:52 2024
  ErrorMessage: installed linux-headers-6.5.0-21-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2024-02-10 (14 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  IwConfig:
   lono wireless extensions.
   
   enp5s0no wireless extensions.
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB:
   0 EFI VGA
   1 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=6adb3052-5462-40b3-a845-fe252d1d312e ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc N/A
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-6.5.0-21-generic 6.5.0-21.21 failed to 
install/upgrade: installed linux-headers-6.5.0-21-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F16
  dmi.board.asset.tag: Default string
  dmi.board.name: B760M DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF16:bd12/14/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnB760MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB760MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B760 MB
  dmi.product.name: B760M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054866/+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 1896350] Re: nbd locks system?

2022-04-01 Thread Tom Zhou
** Tags added: sts

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

Title:
  nbd locks system?

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to use nbd on ubuntu 20.04 like so:

  qemu-img create -f qcow2 foo.img 500M
  sudo modprobe nbd
  sudo qemu-nbd --disconnect /dev/nbd15 || true
  sudo qemu-nbd --connect=/dev/nbd15 --cache=writeback --format=qcow2 foo.img
  sudo mkfs.ext4 -L root -O "^64bit" -E nodiscard /dev/nbd15
  sudo qemu-nbd --disconnect /dev/nbd15

  It seems to work on some systems, but even on those systems, strange things 
show up
  in syslog, e.g.

  Sep 19 15:46:02 thinky kernel: [27042.757768] block nbd15: Possible stuck 
request dd2d7f93: control (read@135168,126976B). Runtime 450 seconds
  Sep 19 15:46:26 thinky kernel: [27067.333867] INFO: task systemd-udevd:17364 
blocked for more than 241 seconds.

  and in kern.log, e.g.

  ...
  Sep 19 16:17:27 thinky kernel: [   71.676026] Buffer I/O error on dev nbd15, 
logical block 7, async page read
  Sep 19 16:17:27 thinky kernel: [   71.676049] blk_update_request: I/O error, 
dev nbd15, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
  Sep 19 16:17:27 thinky kernel: [   71.676051] Buffer I/O error on dev nbd15, 
logical block 0, async page read
  Sep 19 16:17:27 thinky kernel: [   71.676061] blk_update_request: I/O error, 
dev nbd15, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
  Sep 19 16:17:27 thinky kernel: [   71.676063] Buffer I/O error on dev nbd15, 
logical block 1, async page read
  Sep 19 16:17:27 thinky kernel: [   71.676147] ldm_validate_partition_table(): 
Disk read failed.
  Sep 19 16:17:27 thinky kernel: [   71.676324] Dev nbd15: unable to read RDB 
block 0
  Sep 19 16:17:27 thinky kernel: [   71.676473]  nbd15: unable to read 
partition table
  Sep 19 16:17:27 thinky kernel: [   71.678340] nbd15: detected capacity change 
from 0 to 524288000
  Sep 19 16:17:27 thinky kernel: [   71.678536] ldm_validate_partition_table(): 
Disk read failed.
  Sep 19 16:17:27 thinky kernel: [   71.678719] Dev nbd15: unable to read RDB 
block 0
  Sep 19 16:17:27 thinky kernel: [   71.678947]  nbd15: unable to read 
partition table
  Sep 19 16:17:27 thinky kernel: [   71.679985] ldm_validate_partition_table(): 
Disk read failed.
  Sep 19 16:17:27 thinky kernel: [   71.680172] Dev nbd15: unable to read RDB 
block 0
  Sep 19 16:17:27 thinky kernel: [   71.680366]  nbd15: unable to read 
partition table
  Sep 19 16:17:27 thinky kernel: [   71.680647] block nbd15: Attempted send on 
invalid socket

  and the system seems to hang on reboot.

  Also, on another system (an up to date mac, running ubuntu 20.04 in 
virtualbox), 
  the mkfs.ext4 fails, complaining the device is zero size.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-47-generic 5.4.0-47.51
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dank   2948 F pulseaudio
   /dev/snd/controlC2:  dank   2948 F pulseaudio
   /dev/snd/controlC0:  dank   2948 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 19 16:28:43 2020
  HibernationDevice: RESUME=UUID=7aecd5d3-2f5b-4c07-8867-801e63868a0f
  InstallationDate: Installed on 2017-04-29 (1239 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO ThinkServer TS140
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=ff9a24e4-277d-4baf-819b-826a33d5bb5e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-47-generic N/A
   linux-backports-modules-5.4.0-47-generic  N/A
   linux-firmware1.187.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-05-01 (141 days ago)
  dmi.bios.date: 09/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKT99AUS
  dmi.board.name: ThinkServer TS140
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKT99AUS:bd09/19/2014:svnLENOVO:pnThinkServerTS140:pvr70A4000HUX:rvnLENOVO:rnThinkServerTS140:rvrNotDefined:cvnLENOVO:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: ThinkServer TS140
  dmi.product.sku: LENOVO_PN_ThinkServer TS140
  dmi.product.version: 70A4000HUX
  dmi.sys.vendor: LENOVO

To manage 

[Kernel-packages] [Bug 1966007] Re: Flood of Bluetooth Malicious advertisind data

2022-03-31 Thread Frank Zhou
seems fixed on 5.4.0-107-generic:

frankzhou@pluto:~$ dmesg | grep Bluetooth | wc -l
62
frankzhou@pluto:~$ uptime
 11:06:54 up  3:58,  2 users,  load average: 0.28, 0.23, 0.25
frankzhou@pluto:~$ uname -a
Linux pluto 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 
2022 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Flood of Bluetooth Malicious advertisind data

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  This problem occurred with the  ugrade of the kernel to patch level
  105.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-terminal 3.36.2-1ubuntu1~20.04
  ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174
  Uname: Linux 5.4.0-105-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:48:22 2022
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2018-06-21 (1370 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   LANG=en_AU.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1966007/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-02-24 Thread Joe Zhou
Works fine after installing hwe kernel using apt.(5.8.0.44 Ubuntu 20.04
Lenovo R7000P)

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 2020
  InstallationDate: Installed on 2020-07-02 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, 

[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05

2021-01-21 Thread Joe Zhou
Lenovo R7000P Laptop. Sadly, still not a good solution. The touch pad
now works with kernel 5.11.0, but it has problem with Nvidia GPU and the
brightness control is not working. I can have Nvidia GPU working and
manually do some fixes to enable brightness control with 5.8.0, though
touch pad is not working.

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

Title:
  MSFT Touchpad not working on Lenovo Legion-5 15ARH05

Status in Pop!_OS:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Committed
Status in linux package in Fedora:
  Confirmed
Status in linux package in openSUSE:
  New

Bug description:
  Update (based on #296)
  =

  The latest kernel tree
  (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
  has the complete solution to fix this bug. So we can expect kernel
  v5.11 to fix this issue without any additional work.

  Before the release of v5.11, you are suggested to use #189 to save your 
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd 
driver is built into the initramfs. So you have to rebuild the initramfs after 
replacing the old module with new one.
  On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs 
-u`.

  The complete solution is three patches,
   - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce 
filter setting in IRQ type setting")
   - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way 
to disable debounce filter")
   - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into 
account debounce settings")

  The first two patches has reached the stable tree. If the last one is
  also backported to LTS kernel, you won't need to install kernel 5.11.
  But I don't know when this will happen.

  Original bug report
  ===

  Hello

  The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at 
all (pointer and click never move when touchpad is touched). This has been 
reported by other users in various websites, with various linux systems 
including other Ubuntu systems, but I saw no launchpad bug so I post one. 
Example of websites covering the issue :
  - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly 
the same laptop)
  - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar 
laptop)

  xinput indentifies it as MSFT0001:00 04F3:3140

  Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Touchpad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ MSFT0001:00 04F3:3140 Mouse id=16   [slave  pointer 
 (2)]
  ⎜   ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12   [slave  
pointer  (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Ideapad extra buttons   id=15   [slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Integrated Camera: Integrated C id=10   [slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19   [slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control  id=13   [slave  
keyboard (3)]
  ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=18   [slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]

  Thanks a lot for your time. It does not help, but I can confirm what
  was reported on askubuntu by another user : the touchpad does work on
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-40-generic 5.4.0-40.44
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1567 F pulseaudio
   /dev/snd/controlC1:  nicolas1567 F pulseaudio
   /dev/snd/controlC2:  nicolas1567 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 20:14:25 

[Kernel-packages] [Bug 1909381] [NEW] ubuntu 20.04 frozen randomly

2020-12-26 Thread Simon Zhou
Public bug reported:

I am using Ubuntu 20.04 (dual boot with windows 10) on Dell vostro 7500,
the whole system crashes randomly, the symptom is the whole screen
frozen, the time on the screen is stuck, mouse cannot move, keyboard
input is invalid. I think it is a kernel crash because sysrq does not
work, which works in normal time, and /var/log/syslog contains no lines
after the crash.

I tried reinstalling the os and switching my kernel version from
5.4.0-58-generic to 5.4.0-42-generic, but the problem persists. The
frequency of crashing is one time per week before reinstalling and one
time per day after reinstalling.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 described
the same problems as me but it is about 18.10 and is closed.

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:  simon  7165 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 27 10:57:10 2020
InstallationDate: Installed on 2020-12-19 (7 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Vostro 7500
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=691b73da-2f14-4067-99eb-f7ade1c6ce10 ro 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: No upgrade log present (probably fresh install)
dmi.bios.date: 09/25/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.1
dmi.board.name: 034VHF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/25/2020:svnDellInc.:pnVostro7500:pvr:rvnDellInc.:rn034VHF:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 7500
dmi.product.sku: 09F0
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

** Attachment added: "kern12250808.log"
   
https://bugs.launchpad.net/bugs/1909381/+attachment/5447075/+files/kern12250808.log

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

Title:
  ubuntu 20.04 frozen randomly

Status in linux package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 20.04 (dual boot with windows 10) on Dell vostro
  7500, the whole system crashes randomly, the symptom is the whole
  screen frozen, the time on the screen is stuck, mouse cannot move,
  keyboard input is invalid. I think it is a kernel crash because sysrq
  does not work, which works in normal time, and /var/log/syslog
  contains no lines after the crash.

  I tried reinstalling the os and switching my kernel version from
  5.4.0-58-generic to 5.4.0-42-generic, but the problem persists. The
  frequency of crashing is one time per week before reinstalling and one
  time per day after reinstalling.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 described
  the same problems as me but it is about 18.10 and is closed.

  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:  simon  7165 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 27 10:57:10 2020
  InstallationDate: Installed on 2020-12-19 (7 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 7500
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=691b73da-2f14-4067-99eb-f7ade1c6ce10 ro 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: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 034VHF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/25/2020:svnDellInc.:pnVostro7500:pvr:rvnDellInc.:rn034VHF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 7500
  dmi.product.sku: 09F0
  

[Kernel-packages] [Bug 1909382] [NEW] ubuntu 20.04 frozen randomly

2020-12-26 Thread Simon Zhou
Public bug reported:

I am using Ubuntu 20.04 (dual boot with windows 10) on Dell vostro 7500,
the whole system crashes randomly, the symptom is the whole screen
frozen, the time on the screen is stuck, mouse cannot move, keyboard
input is invalid. I think it is a kernel crash because sysrq does not
work, which works in normal time, and /var/log/syslog contains no lines
after the crash.

I tried reinstalling the os and switching my kernel version from
5.4.0-58-generic to 5.4.0-42-generic, but the problem persists. The
frequency of crashing is one time per week before reinstalling and one
time per day after reinstalling.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 described
the same problems as me but it is about 18.10 and is closed.

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:  simon  7165 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 27 10:57:10 2020
InstallationDate: Installed on 2020-12-19 (7 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Vostro 7500
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=691b73da-2f14-4067-99eb-f7ade1c6ce10 ro 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: No upgrade log present (probably fresh install)
dmi.bios.date: 09/25/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.1
dmi.board.name: 034VHF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/25/2020:svnDellInc.:pnVostro7500:pvr:rvnDellInc.:rn034VHF:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 7500
dmi.product.sku: 09F0
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

** Attachment added: "/var/log/kern.log after crash at 2020.12.25, 08:08"
   
https://bugs.launchpad.net/bugs/1909382/+attachment/5447096/+files/kern12250808.log

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

Title:
  ubuntu 20.04 frozen randomly

Status in linux package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 20.04 (dual boot with windows 10) on Dell vostro
  7500, the whole system crashes randomly, the symptom is the whole
  screen frozen, the time on the screen is stuck, mouse cannot move,
  keyboard input is invalid. I think it is a kernel crash because sysrq
  does not work, which works in normal time, and /var/log/syslog
  contains no lines after the crash.

  I tried reinstalling the os and switching my kernel version from
  5.4.0-58-generic to 5.4.0-42-generic, but the problem persists. The
  frequency of crashing is one time per week before reinstalling and one
  time per day after reinstalling.

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961 described
  the same problems as me but it is about 18.10 and is closed.

  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:  simon  7165 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 27 10:57:10 2020
  InstallationDate: Installed on 2020-12-19 (7 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 7500
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=691b73da-2f14-4067-99eb-f7ade1c6ce10 ro 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: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.1
  dmi.board.name: 034VHF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd09/25/2020:svnDellInc.:pnVostro7500:pvr:rvnDellInc.:rn034VHF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 7500
  

[Kernel-packages] [Bug 1774359] Re: could not find module by name='off'

2018-09-12 Thread Zhou
Ubuntu 18.04 On Precision 5530 Quadro P1000
Confirm the issue with nvidai 396.

I solve it by using Rocko (rockorequin)'s solution
Commenting out lines in /etc/modprobe.d/.conf fixed it:

alias  off

Original post:
https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1438106

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

Title:
  could not find module by name='off'

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  When I try to load the nvidia module it doesn't load.

  $ sudo modprobe nvidia
  modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module() 
could not find module by name='off'
  modprobe: ERROR: could not insert 'off': Unknown symbol in module, or unknown 
parameter (see dmesg)
  $ sudo prime-select query
  intel
  $ sudo prime-offload
  $ cat /var/log/prime-supported.log 
  Requires offloading 
  $ cat /var/log/prime-offload.log 
  Sorry the nvidia kernel module is not is loaded

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-kernel-common-390 390.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 09:42:42 2018
  Dependencies:
   
  InstallationDate: Installed on 2018-05-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1774359/+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 1786906] Re: "ACPI unsupported"

2018-08-21 Thread Zhou
** 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/1786906

Title:
  "ACPI unsupported"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While I'm using Ubuntu Server version on my laptop(HP omen 15, 
CPU:i5-8300H,GPU:GTX1050Ti), it always says "[ time.time] acpi INT3400:00: 
Unsupported event [0x86]",
  In Ubuntu Desktop version, after I turn on my computer, it'll not going on 
but stay at a screen and says "[ time.time] acpi INT3400:00: Unsupported event 
[0x86]"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786906/+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 1512815] Re: read() from pty doesn't finish.

2015-12-10 Thread Tom Zhou
Hello,

One of our customer tested 3.19.0-41.46 on Ubuntu 15.04 by running test
program.

Proposed kernel(3.19.0-41.46 kernel): 
The problem occurred 0 time in 10 running. 

Conventional kernel: 
The problem occurred 32 times in 4917 running.

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

Title:
  read() from pty doesn't finish.

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed

Bug description:
  It has been brought to my attention

  By the attached test program pty, a pair of process repeats writing
  and reading only '\n' to a master pseudoterminal device (/dev/ptmx)
  and a slave pseudoterminal device (/dev/pts/N) each. When we carry out
  the following 30 pairs 10,000 times, in a pair each process doesn't
  finish reading.

  $ pty 30
  The following message will be usually indicated immediately.
  #name copy num/sec usec/num
  pty_switch 30 1541842 0.648575

  When a message wasn't indicated any more, we got the attached dump file. 
  A kernel was 3.13.0-45.74. 
  A system was Ubuntu 14.04 LTS.

  The same problem occurred in case of 3.13.0-55.92 kernel and the following 
kernel have been tested as well:
  2.6.32, 3.10: not reproduces.
  3.19, 4.0.0, 4.1.3: reproduces.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512815/+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 1354234] [NEW] 14.04: PANIC with dcache shrink list corruption? problem

2014-08-07 Thread Tom Zhou
Public bug reported:

Hello,

14.04 kernel linux_3.13.0-32.57 panicked because of dcache shrink list 
corruption? problem. Please see followings: 
- details at https://lkml.org/lkml/2014/5/2/555. 
- argument at https://lkml.org/lkml/2014/4/29/402 
- patch set at https://lkml.org/lkml/2014/5/4/7 

One of 9 patches has been applied to linux_3.13.0-32.57 already. 
Could you apply other 8 patches to the next 14.04 kernel ? 
We will need the kernel at the beginning of August badly. If we will not 
be able to get it, we will not be able to start tests before service in. 
Could you release it as soon as possible ? 

We applied other 8 patches to linux_3.13.0-32.57 and now the panic does 
not occur. 

Public Bug URL: 
https://lkml.org/lkml/2014/5/2/555

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1354234

Title:
  14.04: PANIC with dcache shrink list corruption? problem

Status in “linux” package in Ubuntu:
  New

Bug description:
  Hello,

  14.04 kernel linux_3.13.0-32.57 panicked because of dcache shrink list 
  corruption? problem. Please see followings: 
  - details at https://lkml.org/lkml/2014/5/2/555. 
  - argument at https://lkml.org/lkml/2014/4/29/402 
  - patch set at https://lkml.org/lkml/2014/5/4/7 

  One of 9 patches has been applied to linux_3.13.0-32.57 already. 
  Could you apply other 8 patches to the next 14.04 kernel ? 
  We will need the kernel at the beginning of August badly. If we will not 
  be able to get it, we will not be able to start tests before service in. 
  Could you release it as soon as possible ? 

  We applied other 8 patches to linux_3.13.0-32.57 and now the panic does 
  not occur. 

  Public Bug URL: 
  https://lkml.org/lkml/2014/5/2/555

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354234/+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 1354234] Re: 14.04: PANIC with dcache shrink list corruption? problem

2014-08-07 Thread Tom Zhou
Hey there,

The log files are being collected, I'll attach them later.

Thanks,
Tom

** 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/1354234

Title:
  14.04: PANIC with dcache shrink list corruption? problem

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  14.04 kernel linux_3.13.0-32.57 panicked because of dcache shrink list 
  corruption? problem. Please see followings: 
  - details at https://lkml.org/lkml/2014/5/2/555. 
  - argument at https://lkml.org/lkml/2014/4/29/402 
  - patch set at https://lkml.org/lkml/2014/5/4/7 

  One of 9 patches has been applied to linux_3.13.0-32.57 already. 
  Could you apply other 8 patches to the next 14.04 kernel ? 
  We will need the kernel at the beginning of August badly. If we will not 
  be able to get it, we will not be able to start tests before service in. 
  Could you release it as soon as possible ? 

  We applied other 8 patches to linux_3.13.0-32.57 and now the panic does 
  not occur. 

  Public Bug URL: 
  https://lkml.org/lkml/2014/5/2/555

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1354234/+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 1246981] Re: Bluetooth mouse failes to re-connect after sleep.

2013-12-04 Thread Terry Zhou
This should be the same issue with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1256747

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

Title:
  Bluetooth mouse failes to re-connect after sleep.

Status in “bluez” package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1246981] Re: Bluetooth mouse failes to re-connect after sleep.

2013-12-04 Thread Terry Zhou
Also the similar issue
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213239. There is a
workaround here http://ubuntuforums.org/showthread.php?t=1387211

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

Title:
  Bluetooth mouse failes to re-connect after sleep.

Status in “bluez” package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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