from:"Stan"

[Kernel-packages] [Bug 1964373] [NEW] Dell latitude e65640 touchpad and display problem.

2022-03-09 Thread bart stan

Public bug reported:

After upgrade from Ubuntu 18 to 20, touch-pad and display stop working
correctly. touchepad works only from time to time, but I can't find
pattern why. On the other hand display just after upgrade worked
correctly, but lately I have to work in recovery mode because on normal
drivers refreshing is terrible and from time to time display turn black
and it is impossible to switch it to normal mode.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-100-generic 5.4.0-100.113
ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
Uname: Linux 5.4.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  b  2538 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar  9 17:09:05 2022
HibernationDevice: RESUME=UUID=2e023d39-8015-4527-93d8-ec2dacb4572a
InstallationDate: Installed on 2016-09-07 (2008 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. Latitude E6540
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-100-generic 
root=UUID=2e8b2947-a5a7-4df7-9248-aca535b07d8c ro recovery nomodeset 
dis_ucode_ldr nomodeset
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-100-generic N/A
 linux-backports-modules-5.4.0-100-generic  N/A
 linux-firmware 1.187.27
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2022-03-02 (7 days ago)
dmi.bios.date: 02/18/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0CYT5F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6540
dmi.product.sku: Latitude E6540
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "devices"
   https://bugs.launchpad.net/bugs/1964373/+attachment/5567410/+files/devices

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

Title:
  Dell latitude e65640 touchpad and display problem.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from Ubuntu 18 to 20, touch-pad and display stop working
  correctly. touchepad works only from time to time, but I can't find
  pattern why. On the other hand display just after upgrade worked
  correctly, but lately I have to work in recovery mode because on
  normal drivers refreshing is terrible and from time to time display
  turn black and it is impossible to switch it to normal mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-100-generic 5.4.0-100.113
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  b  2538 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  9 17:09:05 2022
  HibernationDevice: RESUME=UUID=2e023d39-8015-4527-93d8-ec2dacb4572a
  InstallationDate: Installed on 2016-09-07 (2008 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude E6540
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-100-generic 
root=UUID=2e8b2947-a5a7-4df7-9248-aca535b07d8c ro recovery nomodeset 
dis_ucode_ldr nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-100-generic N/A
   linux-backports-modules-5.4.0-100-generic  N/A
   linux-firmware 1.187.27
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-03-02 (7 days ago)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0CYT5F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0CYT5F:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6540
  dmi.product.sku: Latitude E6540
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964373/+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 1956461] Re: Creative HD720p webcam doesn't work

2022-01-31 Thread Stan

Does it work with 5.4.0-97.110 kernel?

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

Title:
  Creative HD720p webcam doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing kernel 5.4.0-92 the webcam Creative HD720p stop to be seen 
by the system. There is no  /dev/vl4/ folder
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  piotr  3094 F pulseaudio
   /dev/snd/controlC0:  piotr  3094 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.2
  InstallationDate: Installed on 2020-06-07 (578 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-92-generic 
root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-92-generic N/A
   linux-backports-modules-5.4.0-92-generic  N/A
   linux-firmware1.187.24
  RfKill:
   
  Tags:  uma
  Uname: Linux 5.4.0-92-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: 10/27/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H67MA-USB3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67MA-USB3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956461/+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 1957112] Re: webcam doesn't work

2022-01-20 Thread Stan

I did not find any workaround either. So far I can work with 5.4.0-91.
Anyway I hope that this bug will be fixed, but I can see that it is
still "Unassigned" with "Undecided" importance, which doesn't lift my
hopes.

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

Title:
  webcam doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My 
webcam doesn't work
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  piotr  2920 F pulseaudio
   /dev/snd/controlC0:  piotr  2920 F pulseaudio
   /dev/snd/controlC1:  piotr  2920 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2020-06-07 (583 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic 
root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-91-generic N/A
   linux-backports-modules-5.4.0-91-generic  N/A
   linux-firmware1.187.24
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-91-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: 10/27/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H67MA-USB3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67MA-USB3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+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 1957112] Re: webcam doesn't work

2022-01-18 Thread Stan

Thank you for the information. I hope that this bug will be fixed soon,
because I need the camera for online work and I can't use Windows :/

Have you found any workarounds other than using older kernel? Maybe some
USB settings in BIOS or the OS?

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

Title:
  webcam doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My 
webcam doesn't work
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  piotr  2920 F pulseaudio
   /dev/snd/controlC0:  piotr  2920 F pulseaudio
   /dev/snd/controlC1:  piotr  2920 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2020-06-07 (583 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic 
root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-91-generic N/A
   linux-backports-modules-5.4.0-91-generic  N/A
   linux-firmware1.187.24
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-91-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: 10/27/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H67MA-USB3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67MA-USB3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+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 1957112] Re: webcam doesn't work

2022-01-18 Thread Stan

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

Title:
  webcam doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My 
webcam doesn't work
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  piotr  2920 F pulseaudio
   /dev/snd/controlC0:  piotr  2920 F pulseaudio
   /dev/snd/controlC1:  piotr  2920 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2020-06-07 (583 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic 
root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-91-generic N/A
   linux-backports-modules-5.4.0-91-generic  N/A
   linux-firmware1.187.24
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-91-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: 10/27/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H67MA-USB3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67MA-USB3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+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 1957112] Re: webcam doesn't work

2022-01-18 Thread Stan

I have the same problem. Kernel 5.4.0-96 is just out. Can somebody
confirm if something has changed in 5.4.0-96?

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

Title:
  webcam doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As I wrote in [Bug 1956461] the same is happening with kernel 5.4.0-94. My 
webcam doesn't work
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  piotr  2920 F pulseaudio
   /dev/snd/controlC0:  piotr  2920 F pulseaudio
   /dev/snd/controlC1:  piotr  2920 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 20.3
  InstallationDate: Installed on 2020-06-07 (583 days ago)
  InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213
  IwConfig:
   enp3s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-91-generic 
root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-91-generic N/A
   linux-backports-modules-5.4.0-91-generic  N/A
   linux-firmware1.187.24
  RfKill:
   
  Tags:  una
  Uname: Linux 5.4.0-91-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: 10/27/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: H67MA-USB3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67MA-USB3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957112/+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 1953199] Re: 0-byte files created in overlay filesystem

2021-12-08 Thread Stan Hu

FYI, Linux v5.10.84
(https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y)
has now been tagged with the fixes for the overlay filesystem:

1. 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.10.y&id=dca4f9a581967a81cf4420bdd26162112d546031
1. 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.10.y&id=bcce010f92308368ac27248342e6ccd058e8c596

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

Title:
  0-byte files created in overlay filesystem

Status in linux-base package in Ubuntu:
  New

Bug description:
  Copied from
  
https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/:

  A number of users have reported that under certain conditions using
  the overlay filesystem, copy_file_range() can unexpectedly create a
  0-byte file. [0]

  This bug can cause significant problems because applications that copy
  files expect the target file to match the source immediately after the
  copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based
  CI tests started failing due to this bug, since Ruby's IO.copy_stream
  uses this system call. We have worked around the problem by touching
  the target file before using it, but this shouldn't be necessary.
  Other projects, such as Rust, have added similar workarounds. [1]

  As discussed in the linux-fsdevel mailing list [2], the bug appears to
  be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be
  able to cherry-pick the following upstream patches to fix this. Could
  you cherry-pick them to 5.10.x stable? I've confirmed that these
  patches, applied from top to bottom to that branch, pass the
  reproduction test [3]:

  82a763e61e2b601309d696d4fa514c77d64ee1be
  9b91b6b019fda817eb52f728eb9c79b3579760bc

  The diffstat:

   fs/overlayfs/file.c | 59
  +++
   1 file changed, 31 insertions(+), 28 deletions(-)

  Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable.

  [0] https://github.com/docker/for-linux/issues/1015
  [1] 
https://github.com/rust-lang/rust/blob/342db70ae4ecc3cd17e4fa6497f0a8d9534ccfeb/library/std/src/sys/unix/kernel_copy.rs#L565-L569
  [2] https://marc.info/?l=linux-fsdevel&m=163847383311699&w=2
  [3] https://github.com/docker/for-linux/issues/1015#issuecomment-841915668

  ---

  I reproduced this bug in Ubuntu 18.04:

  ```
  # bash test.sh
  Sending build context to Docker daemon  43.05kB
  Step 1/2 : FROM debian:10.8-slim
   ---> 115566c891d1
  Step 2/2 : RUN apt update && apt install -y gcc strace
   ---> Using cache
   ---> 0dfb7ffcd427
  Successfully built 0dfb7ffcd427
  Successfully tagged strace:latest

  Local:
  OK

  Docker - mounted:
  Copy failed

  Docker - copied:
  OK
  ```

  ```
  root@stanhu-ubuntu-18:/home/stanhu# lsb_release -rd
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04
  root@stanhu-ubuntu-18:/home/stanhu# uname -r
  5.4.0-1057-gcp
  ```

  Per [the latest update on the kernel stable mailing
  list](https://lore.kernel.org/stable/yanx6kobwiqob...@kroah.com), the
  kernel backport fix for 5.10 has been queued for review and should
  land in the [`stable-5.10.y`
  
branch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y)
  soon.

  To avoid this bug, I'd suggest avoid Linux v5.6.0 - v5.10.83 for now,
  unless you backport the two patches below:

  1. 
https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be
  1. 
https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc

  I've confirmed that 5.5.19 does NOT have this bug, and it was
  introduced in 5.6.0 via
  
https://github.com/torvalds/linux/commit/1a980b8cbf0059a5308eea61522f232fd03002e2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1953199/+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 1953199] Re: 0-byte files created in overlay filesystem

2021-12-06 Thread Stan Hu

Yes.

It's worth checking Ubuntu 20.04. 20.04.3 seems to have upgraded to
kernel 5.11, but I'm not sure if this is just because it's the HWE
version.

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

Title:
  0-byte files created in overlay filesystem

Status in linux-base package in Ubuntu:
  New

Bug description:
  Copied from
  
https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/:

  A number of users have reported that under certain conditions using
  the overlay filesystem, copy_file_range() can unexpectedly create a
  0-byte file. [0]

  This bug can cause significant problems because applications that copy
  files expect the target file to match the source immediately after the
  copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based
  CI tests started failing due to this bug, since Ruby's IO.copy_stream
  uses this system call. We have worked around the problem by touching
  the target file before using it, but this shouldn't be necessary.
  Other projects, such as Rust, have added similar workarounds. [1]

  As discussed in the linux-fsdevel mailing list [2], the bug appears to
  be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be
  able to cherry-pick the following upstream patches to fix this. Could
  you cherry-pick them to 5.10.x stable? I've confirmed that these
  patches, applied from top to bottom to that branch, pass the
  reproduction test [3]:

  82a763e61e2b601309d696d4fa514c77d64ee1be
  9b91b6b019fda817eb52f728eb9c79b3579760bc

  The diffstat:

   fs/overlayfs/file.c | 59
  +++
   1 file changed, 31 insertions(+), 28 deletions(-)

  Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable.

  [0] https://github.com/docker/for-linux/issues/1015
  [1] 
https://github.com/rust-lang/rust/blob/342db70ae4ecc3cd17e4fa6497f0a8d9534ccfeb/library/std/src/sys/unix/kernel_copy.rs#L565-L569
  [2] https://marc.info/?l=linux-fsdevel&m=163847383311699&w=2
  [3] https://github.com/docker/for-linux/issues/1015#issuecomment-841915668

  ---

  I reproduced this bug in Ubuntu 18.04:

  ```
  # bash test.sh
  Sending build context to Docker daemon  43.05kB
  Step 1/2 : FROM debian:10.8-slim
   ---> 115566c891d1
  Step 2/2 : RUN apt update && apt install -y gcc strace
   ---> Using cache
   ---> 0dfb7ffcd427
  Successfully built 0dfb7ffcd427
  Successfully tagged strace:latest

  Local:
  OK

  Docker - mounted:
  Copy failed

  Docker - copied:
  OK
  ```

  ```
  root@stanhu-ubuntu-18:/home/stanhu# lsb_release -rd
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04
  root@stanhu-ubuntu-18:/home/stanhu# uname -r
  5.4.0-1057-gcp
  ```

  Per [the latest update on the kernel stable mailing
  list](https://lore.kernel.org/stable/yanx6kobwiqob...@kroah.com), the
  kernel backport fix for 5.10 has been queued for review and should
  land in the [`stable-5.10.y`
  
branch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y)
  soon.

  To avoid this bug, I'd suggest avoid Linux v5.6.0 - v5.10.83 for now,
  unless you backport the two patches below:

  1. 
https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be
  1. 
https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc

  I've confirmed that 5.5.19 does NOT have this bug, and it was
  introduced in 5.6.0 via
  
https://github.com/torvalds/linux/commit/1a980b8cbf0059a5308eea61522f232fd03002e2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1953199/+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 1953199] Re: 0-byte files created in overlay filesystem

2021-12-03 Thread Stan Hu

* Ubuntu 18.04.6 LTS appears affected.
* Ubuntu 20.04.3 LTS does NOT appear affected with the Linux 5.11 kernel.

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

Title:
  0-byte files created in overlay filesystem

Status in linux-base package in Ubuntu:
  New

Bug description:
  Copied from
  
https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/:

  A number of users have reported that under certain conditions using
  the overlay filesystem, copy_file_range() can unexpectedly create a
  0-byte file. [0]

  This bug can cause significant problems because applications that copy
  files expect the target file to match the source immediately after the
  copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based
  CI tests started failing due to this bug, since Ruby's IO.copy_stream
  uses this system call. We have worked around the problem by touching
  the target file before using it, but this shouldn't be necessary.
  Other projects, such as Rust, have added similar workarounds. [1]

  As discussed in the linux-fsdevel mailing list [2], the bug appears to
  be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be
  able to cherry-pick the following upstream patches to fix this. Could
  you cherry-pick them to 5.10.x stable? I've confirmed that these
  patches, applied from top to bottom to that branch, pass the
  reproduction test [3]:

  82a763e61e2b601309d696d4fa514c77d64ee1be
  9b91b6b019fda817eb52f728eb9c79b3579760bc

  The diffstat:

   fs/overlayfs/file.c | 59
  +++
   1 file changed, 31 insertions(+), 28 deletions(-)

  Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable.

  [0] https://github.com/docker/for-linux/issues/1015
  [1] 
https://github.com/rust-lang/rust/blob/342db70ae4ecc3cd17e4fa6497f0a8d9534ccfeb/library/std/src/sys/unix/kernel_copy.rs#L565-L569
  [2] https://marc.info/?l=linux-fsdevel&m=163847383311699&w=2
  [3] https://github.com/docker/for-linux/issues/1015#issuecomment-841915668

  ---

  I reproduced this bug in Ubuntu 18.04:

  ```
  # bash test.sh
  Sending build context to Docker daemon  43.05kB
  Step 1/2 : FROM debian:10.8-slim
   ---> 115566c891d1
  Step 2/2 : RUN apt update && apt install -y gcc strace
   ---> Using cache
   ---> 0dfb7ffcd427
  Successfully built 0dfb7ffcd427
  Successfully tagged strace:latest

  Local:
  OK

  Docker - mounted:
  Copy failed

  Docker - copied:
  OK
  ```

  ```
  root@stanhu-ubuntu-18:/home/stanhu# lsb_release -rd
  Description:  Ubuntu 18.04.6 LTS
  Release:  18.04
  root@stanhu-ubuntu-18:/home/stanhu# uname -r
  5.4.0-1057-gcp
  ```

  Per [the latest update on the kernel stable mailing
  list](https://lore.kernel.org/stable/yanx6kobwiqob...@kroah.com), the
  kernel backport fix for 5.10 has been queued for review and should
  land in the [`stable-5.10.y`
  
branch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y)
  soon.

  To avoid this bug, I'd suggest avoid Linux v5.6.0 - v5.10.83 for now,
  unless you backport the two patches below:

  1. 
https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be
  1. 
https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc

  I've confirmed that 5.5.19 does NOT have this bug, and it was
  introduced in 5.6.0 via
  
https://github.com/torvalds/linux/commit/1a980b8cbf0059a5308eea61522f232fd03002e2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1953199/+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 1953199] [NEW] 0-byte files created in overlay filesystem

2021-12-03 Thread Stan Hu

Public bug reported:

Copied from
https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/:

A number of users have reported that under certain conditions using
the overlay filesystem, copy_file_range() can unexpectedly create a
0-byte file. [0]

This bug can cause significant problems because applications that copy
files expect the target file to match the source immediately after the
copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based
CI tests started failing due to this bug, since Ruby's IO.copy_stream
uses this system call. We have worked around the problem by touching
the target file before using it, but this shouldn't be necessary.
Other projects, such as Rust, have added similar workarounds. [1]

As discussed in the linux-fsdevel mailing list [2], the bug appears to
be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be
able to cherry-pick the following upstream patches to fix this. Could
you cherry-pick them to 5.10.x stable? I've confirmed that these
patches, applied from top to bottom to that branch, pass the
reproduction test [3]:

82a763e61e2b601309d696d4fa514c77d64ee1be
9b91b6b019fda817eb52f728eb9c79b3579760bc

The diffstat:

 fs/overlayfs/file.c | 59
+++
 1 file changed, 31 insertions(+), 28 deletions(-)

Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable.

[0] https://github.com/docker/for-linux/issues/1015
[1] 
https://github.com/rust-lang/rust/blob/342db70ae4ecc3cd17e4fa6497f0a8d9534ccfeb/library/std/src/sys/unix/kernel_copy.rs#L565-L569
[2] https://marc.info/?l=linux-fsdevel&m=163847383311699&w=2
[3] https://github.com/docker/for-linux/issues/1015#issuecomment-841915668

---

I reproduced this bug in Ubuntu 18.04:

```
# bash test.sh
Sending build context to Docker daemon  43.05kB
Step 1/2 : FROM debian:10.8-slim
 ---> 115566c891d1
Step 2/2 : RUN apt update && apt install -y gcc strace
 ---> Using cache
 ---> 0dfb7ffcd427
Successfully built 0dfb7ffcd427
Successfully tagged strace:latest

Local:
OK

Docker - mounted:
Copy failed

Docker - copied:
OK
```

```
root@stanhu-ubuntu-18:/home/stanhu# lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04
root@stanhu-ubuntu-18:/home/stanhu# uname -r
5.4.0-1057-gcp
```

Per [the latest update on the kernel stable mailing
list](https://lore.kernel.org/stable/yanx6kobwiqob...@kroah.com), the
kernel backport fix for 5.10 has been queued for review and should land
in the [`stable-5.10.y`
branch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y)
soon.

To avoid this bug, I'd suggest avoid Linux v5.6.0 - v5.10.83 for now,
unless you backport the two patches below:

1. 
https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be
1. 
https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc

I've confirmed that 5.5.19 does NOT have this bug, and it was introduced
in 5.6.0 via
https://github.com/torvalds/linux/commit/1a980b8cbf0059a5308eea61522f232fd03002e2.

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

** Package changed: linux (Ubuntu) => linux-base (Ubuntu)

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

Title:
  0-byte files created in overlay filesystem

Status in linux-base package in Ubuntu:
  New

Bug description:
  Copied from
  
https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/:

  A number of users have reported that under certain conditions using
  the overlay filesystem, copy_file_range() can unexpectedly create a
  0-byte file. [0]

  This bug can cause significant problems because applications that copy
  files expect the target file to match the source immediately after the
  copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based
  CI tests started failing due to this bug, since Ruby's IO.copy_stream
  uses this system call. We have worked around the problem by touching
  the target file before using it, but this shouldn't be necessary.
  Other projects, such as Rust, have added similar workarounds. [1]

  As discussed in the linux-fsdevel mailing list [2], the bug appears to
  be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be
  able to cherry-pick the following upstream patches to fix this. Could
  you cherry-pick them to 5.10.x stable? I've confirmed that these
  patches, applied from top to bottom to that branch, pass the
  reproduction test [3]:

  82a763e61e2b601309d696d4fa514c77d64ee1be
  9b91b6b019fda817eb52f728eb9c79b3579760bc

  The diffstat:

   fs/overlayfs/file.c | 59
  +++
   1 file changed, 31 insertions(+), 28 deletions(-)

  Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable.

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume

2019-10-09 Thread Stan Janssen

I am running into exactly the same problem as Bas Zoetekouw. I added the
enable_autosuspend=0 option:

stan@stan-desktop:~$ cat /etc/modprobe.d/btusb.conf 
options btusb enable_autosuspend=0

But I see the following in dmesg after reboot:

[4.026743] btusb: unknown parameter 'enable_autosuspend' ignored

And the problem still occurs.

Do I need to do something else beside adding this line to
/etc/modprobe.d/btusb.conf?

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

Title:
  Bluetooth (btintel) stops working after suspend/resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I run cosmic on my Dell Latitude E7470, which has an intel usb
  bluetooth device (8087:0a2b).

  Sometimes (not every time) after a suspend/resume cycle, my laptop's
  bluetooth stops working.  hciconfig shows:

  hci0: Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

  and dmesg tells me (various combinations of):

  [237660.728312] Bluetooth: hci0: command tx timeout
  [237732.339965] Bluetooth: hci0: command 0xfc05 tx timeout
  [237925.202500] Bluetooth: hci0: Reading Intel version information failed 
(-110)

  
  Trying to reinitialize the device by reloading the driver has no effect:

  ╰─▶ modprobe -r btusb; modprobe -r btintel; modprobe btintel; modprobe
  btusb

  shows in dmesg:

  [237938.219190] usbcore: deregistering interface driver btusb
  [237938.601731] usbcore: registered new interface driver btusb
  [237940.626392] Bluetooth: hci0: Reading Intel version information failed 
(-110)
  [237940.626426] Bluetooth: hci0: command tx timeout

  Strangely enough, reloading the module sometimes does work, upon which the 
kernel tells me :
  aug 20 15:36:08 regan kernel: usbcore: deregistering interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Bootloader revision 0.0 build 
2 week 52 2014
  aug 20 15:36:30 regan kernel: usbcore: registered new interface driver btusb
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Device revision is 5
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Secure boot is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: OTP lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: API lock is enabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Debug lock is disabled
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
  aug 20 15:36:30 regan kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-11-5.sfi
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for firmware download 
to complete
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Firmware loaded in 1590852 
usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Waiting for device to boot
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Device booted in 11654 usecs
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-11-5.ddc
  aug 20 15:36:31 regan kernel: Bluetooth: hci0: Applying Intel DDC parameters 
completed

  
  Looking further back in the kernel log, the difference between failed and 
successful resumes seems to be this:

  Resume with broken bt:
  [236481.370814] Restarting tasks ... 
  [236491.580841] Bluetooth: hci0: Reading Intel boot parameters failed (-110)

  Resume with working bt:
  [16562.706263] Restarting tasks ... 
  [16562.709034] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
  [16562.716050] Bluetooth: hci0: Device revision is 5
  [16562.716052] Bluetooth: hci0: Secure boot is enabled
  [16562.716053] Bluetooth: hci0: OTP lock is enabled
  [16562.716054] Bluetooth: hci0: API lock is enabled
  [16562.716055] Bluetooth: hci0: Debug lock is disabled
  [16562.716056] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [16562.716404] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
  [16564.202470] Bluetooth: hci0: Waiting for firmware download to complete
  [16564.203017] Bluetooth: hci0: Firmware loaded in 1459449 usecs
  [16564.203091] Bluetooth: hci0: Waiting for device to boot
  [16564.215021] Bluetooth: hci0: Device booted in 11693 usecs
  [16564.215080] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
  [16564.219033] Bluetooth: hci0: Applying Intel DDC parameters completed

  
  and everything works fine after that.


  The first kernel on which this error occurred was 4.17.0-6-generic.  Before 
that, I used 4.15.0-25-generic which works perfectly.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bas4871 F...m pulseaudio
   /dev/snd/controlC0:  bas4871 F pulseaudio
  CurrentDesktop: GNOME
  DistroReleas

[Kernel-packages] [Bug 1775131] Re: Ubuntu 18.04 networking issue (connection drops after approx. 15 minutes)

2019-09-18 Thread Stan Scholtz

i have the same problem over here, i posted more details over here: 
https://github.com/mailcow/mailcow-dockerized/issues/2918

i believe to reproduce the problem you can: 
- set up multiple subnets under the same interface name
- make sure systemd-networkd is the only system to handle public interface (no 
NetworkManager or netplan)
- install somesoftware which uses networkd-dispatcher (like mailcow on docker)

- wait a week to see 1 minute downtime upon hitting the concurrency described 
above
OR
- my interfaces also restart (causing disconnets) upon systemd updates (via apt 
upgrade), or systemd re-install (with chances of 4 to 5 of hitting disconnect)

pls understand that to hit the concurrency problem you probably need to
have lot's of IPs or subnets in your network configuration file in
/etc/systemd/network/enpXXX.network  (i got 7 ipv4 addresses there)

best regards, stan

** Bug watch added: github.com/mailcow/mailcow-dockerized/issues #2918
   https://github.com/mailcow/mailcow-dockerized/issues/2918

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

Title:
  Ubuntu 18.04 networking issue (connection drops after approx. 15
  minutes)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently troubleshooting some network issues on Ubuntu 18.04 LTS Bionic. 
After checking a few logs I noticed that the networkd-dispatcher is generating 
errors. I'm unsure if this is a bug but I'd like to report it over here just to 
be sure:
   
  ```
  Jun 04 18:14:21 [servername] systemd-networkd-wait-online[2079]: managing: br2
  Jun 04 18:14:22 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 
7 seen, reloading interface list
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 
8 seen, reloading interface list
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: ERROR:Unknown 
interface index 8 seen even after reload
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: WARNING:Unknown index 
8 seen, reloading interface list
  Jun 04 18:14:23 [servername] networkd-dispatcher[1890]: ERROR:Unknown 
interface index 8 seen even after reload
  ```

  These issues occur consistently on several servers. The problem is
  that I lose the connection  specifically towards the internet after
  approx. 15 minutes. Internal facing interfaces (same hardware and
  driver) seem to behave differently and remain properly connected to
  the internal network. These network-dispatcher errors seem to occur
  simultanously when the connection on the external interface
  permanently drops.

  The physical network links still appears to be online when the
  connection is lost.

  I'm still also able to ping the default gateway from my provider to
  access the Internet. But all IP addresses beyond this gateway on the
  Internet seem to be unreachable.

  I have disabled TCP offloading and firewalls to eliminate any influences. But 
that didn't work.
  The ARP table shows that my gateway is a STALE record after the connection 
drops. So it seems related to the ARP-table or something likewise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775131/+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 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle

2019-01-25 Thread Stan Hu

Looks good to me!

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

Title:
  NFS v4.0: Stale data after file is renamed while another process has
  an open file handle

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  NOTE: This bug has been fixed in the upstream mainline kernel via
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1
  and merged in the latest NFS client patches in
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13.

  The full patchset is here: https://marc.info/?l=linux-
  nfs&m=153816500525563&w=2

  I'm repeating the report I sent to the NFS maintainers on the mailing
  list:

  On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where
  stale data is shown if a file remains open on one machine, and the
  file is overwritten via a rename() on another. Here's my test:

  1. On node A, create two different files on a shared NFS mount:
  "test1.txt" and "test2.txt".
  2. On node B, continuously show the contents of the first file: "while
  true; do cat test1.txt; done"
  3. On node B, run a process that keeps "test1.txt" open. For example,
  with Python, run:
   f = open('/nfs-mount/test1.txt', 'r')
  4. Rename test2.txt via "mv -f test2.txt test1.txt"

  On node B, I see the contents of the original test1.txt indefinitely,
  even after I disabled attribute caching and the lookup cache. I can
  make the while loop in step 2 show the new content if I perform one of
  these actions:

  1. Run "ls /nfs-mount"
  2. Close the open file in step 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+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 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle

2018-11-09 Thread Stan Hu

** Attachment added: "apport.linux.PkXffd.apport"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+attachment/5210974/+files/apport.linux.PkXffd.apport

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

Title:
NFS v4.0: Stale data after file is renamed while another process has
an open file handle

Status in linux package in Ubuntu:
Confirmed

Bug description:
NOTE: This bug has been fixed in the upstream mainline kernel via

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1
and merged in the latest NFS client patches in

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13.

The full patchset is here: https://marc.info/?l=linux-
nfs&m=153816500525563&w=2

I'm repeating the report I sent to the NFS maintainers on the mailing
list:

On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where
stale data is shown if a file remains open on one machine, and the
file is overwritten via a rename() on another. Here's my test:

1. On node A, create two different files on a shared NFS mount:
"test1.txt" and "test2.txt".
2. On node B, continuously show the contents of the first file: "while
true; do cat test1.txt; done"
3. On node B, run a process that keeps "test1.txt" open. For example,
with Python, run:
f = open('/nfs-mount/test1.txt', 'r')
4. Rename test2.txt via "mv -f test2.txt test1.txt"

On node B, I see the contents of the original test1.txt indefinitely,
even after I disabled attribute caching and the lookup cache. I can
make the while loop in step 2 show the new content if I perform one of
these actions:

1. Run "ls /nfs-mount"
2. Close the open file in step 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585/+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 1802585] [NEW] NFS v4.0: Stale data after file is renamed while another process has an open file handle

2018-11-09 Thread Stan Hu

Public bug reported:

NOTE: This bug has been fixed in the upstream mainline kernel via
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1
and merged in the latest NFS client patches in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13.

The full patchset is here: https://marc.info/?l=linux-
nfs&m=153816500525563&w=2

I'm repeating the report I sent to the NFS maintainers on the mailing
list:

On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where
stale data is shown if a file remains open on one machine, and the
file is overwritten via a rename() on another. Here's my test:

1. Run "ls /nfs-mount"
2. Close the open file in step 3

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

** Tags: client nfs

** Summary changed:

- Stale data after file is renamed while another process has an open file
handle
+ NFS: Stale data after file is renamed while another process has an open file
handle

** Summary changed:

- NFS: Stale data after file is renamed while another process has an open file
handle
+ NFS v4.0: Stale data after file is renamed while another process has an open
file handle

** Description changed:

NOTE: This bug has been fixed in the upstream mainline kernel via

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1
and merged in the latest NFS client patches in

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13.

The full patchset is here: https://marc.info/?l=linux-
nfs&m=153816500525563&w=2

I'm repeating the report I sent to the NFS maintainers on the mailing
list:

- On both kernels in Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an
issue where
+ On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where
stale data is shown if a file remains open on one machine, and the
file is overwritten via a rename() on another. Here's my test:

1. On node A, create two different files on a shared NFS mount:
"test1.txt" and "test2.txt".
2. On node B, continuously show the contents of the first file: "while
true; do cat test1.txt; done"
3. On node B, run a process that keeps "test1.txt" open. For example,
with Python, run:
- f = open('/nfs-mount/test1.txt', 'r')
+ f = open('/nfs-mount/test1.txt', 'r')
4. Rename test2.txt via "mv -f test2.txt test1.txt"

1. Run "ls /nfs-mount"
2. Close the open file in step 3

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

Title:
NFS v4.0: Stale data after file is renamed while another process has
an open file handle

Status in linux package in Ubuntu:
New

Bug description:
NOTE: This bug has been fixed in the upstream mainline kernel via

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1
and merged in the latest NFS client patches in

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13.

The full patchset is here: https://marc.info/?l=linux-
nfs&m=153816500525563&w=2

I'm repeating the report I sent to the NFS maintainers on the mailing
list:

On Ubuntu 16.04 (4.4.0-130) with NFS v4.0, I'm seeing an issue where
stale data is shown if a file remains open on one machine, and the
file is overwritten via a rename() on another. Here's my test:

On node B, I see the contents of the original test1.txt indefinitely,

[Kernel-packages] [Bug 1757008] Re: bcmwl-kernel-source: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’]

2018-07-03 Thread Stan Varlamov

@Sami: the compilation is done automatically by the installer. You can
either plug in Ethernet or reboot and chose Advanced Ubuntu boot option,
scroll down to the previous ver. of the Kernel (4.13) and boot with it
normally to get the WiFi connection back. Then "See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed" - just a couple of steps that don't affect
your overall system if you "Create the file /etc/apt/preferences.d
/proposed-updates with this content:...". Then sudo apt-get update and
sudo apt-get install broadcom-sta-dkms/xenial-proposed. This should
successfully compile for both 4.13 and 4.15 kernels. Then reboot
normally and forget about this incident till the kernel testing flow
breaks again next year or whenever.

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

Title:
  bcmwl-kernel-source: bcmwl kernel module failed to build [error:
  implicit declaration of function ‘init_timer’]

Status in bcmwl package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Ubuntu:
  Confirmed

Bug description:
  The module fails to build, as it is missing the necessary patches for
  the latest HWE kernel.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-13-generic
  Date: Mon Mar 19 15:02:46 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-06-05 (287 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1757008/+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 1521982] Re: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/le

2015-12-11 Thread Stan

Translation (best effort):


package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to 
install/upgrade: Extract Data for 
»./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« 
can not be copied to 
»/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new«
 : unexpected end of file or stream.

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

Title:
  package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to
  install/upgrade: Extrahierte Daten für
  »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko«
  können nicht nach
  »/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko
  .dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des
  Datenstroms

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-extra-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carsten1741 F pulseaudio
   /dev/snd/controlC1:  carsten1741 F pulseaudio
  Date: Tue Dec  1 21:46:29 2015
  DpkgHistoryLog:
   
  DpkgTerminalLog:
   
  ErrorMessage: Extrahierte Daten für 
»./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« 
können nicht nach 
»/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new«
 kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms
  HibernationDevice: RESUME=UUID=55b16c37-9a10-448a-8d4e-f59a0ed550ea
  InstallationDate: Installed on 2015-11-19 (12 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P67A-UD3-B3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=9c54422a-2851-4e1a-b9f6-28e6374aa754 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-29
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to 
install/upgrade: Extrahierte Daten für 
»./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« 
können nicht nach 
»/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new«
 kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P67A-UD3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P67A-UD3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521982/+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 1521982] [NEW] package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/

2015-12-02 Thread Stan

Public bug reported:

none

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: linux-image-extra-4.2.0-19-generic 4.2.0-19.23
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  carsten1741 F pulseaudio
 /dev/snd/controlC1:  carsten1741 F pulseaudio
Date: Tue Dec  1 21:46:29 2015
DpkgHistoryLog:
 
DpkgTerminalLog:
 
ErrorMessage: Extrahierte Daten für 
»./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« 
können nicht nach 
»/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new«
 kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms
HibernationDevice: RESUME=UUID=55b16c37-9a10-448a-8d4e-f59a0ed550ea
InstallationDate: Installed on 2015-11-19 (12 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
 enp4s0no wireless extensions.
 
 lono wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P67A-UD3-B3
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=9c54422a-2851-4e1a-b9f6-28e6374aa754 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-29
RfKill:
 
SourcePackage: linux
Title: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to 
install/upgrade: Extrahierte Daten für 
»./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« 
können nicht nach 
»/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new«
 kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: P67A-UD3-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P67A-UD3-B3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package wily

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

Title:
  package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to
  install/upgrade: Extrahierte Daten für
  »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko«
  können nicht nach
  »/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko
  .dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des
  Datenstroms

Status in linux package in Ubuntu:
  New

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-extra-4.2.0-19-generic 4.2.0-19.23
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  carsten1741 F pulseaudio
   /dev/snd/controlC1:  carsten1741 F pulseaudio
  Date: Tue Dec  1 21:46:29 2015
  DpkgHistoryLog:
   
  DpkgTerminalLog:
   
  ErrorMessage: Extrahierte Daten für 
»./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« 
können nicht nach 
»/lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko.dpkg-new«
 kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms
  HibernationDevice: RESUME=UUID=55b16c37-9a10-448a-8d4e-f59a0ed550ea
  InstallationDate: Installed on 2015-11-19 (12 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P67A-UD3-B3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=9c54422a-2851-4e1a-b9f6-28e6374aa754 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-29
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to 
install/upgrade: Extrahierte Daten für 
»./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/legacy/gadgetfs.ko« 
können nicht na

[Kernel-packages] [Bug 1490214] Re: Does not detect hotplugged USB device

2015-09-14 Thread Stan

This error kind of affects me also when i use 3.19.0-28-generic. It does not 
occur under 3.19.0-26-generic.
I get messages in the dmesg, a delay after login and when I use usb-creator-gtk 
i  get error messages.

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

Title:
  Does not detect hotplugged USB device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I cannot explain why my Ubuntu 15.04 setup is suddenly not capable of
  recognizing my USB 8GB stick. It worked yesterday, but not today.
  Didn't change anything except ran an apt-get upgrade.

  Hope the attached logs can help you identifying the cause. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udisks2 2.1.5-1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  Date: Sun Aug 30 11:42:53 2015
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HotplugNewDevices: /dev/sdd1 /dev/sdd
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-10-31 (302 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=b5b38333-3694-4441-8a13-50bf4dbf2f41 ro quiet
  SourcePackage: udisks2
  Symptom: storage
  Title: Does not detect hotplugged storage device
  UDisksDump: Error: command ['udisksctl', 'dump'] failed with exit code 1: 
Error connecting to the udisks daemon: Error calling StartServiceByName for 
org.freedesktop.UDisks2: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: 
Activation of org.freedesktop.UDisks2 timed out
  UdisksMonitorLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6X58D-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd08/06/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Re: [Kernel-packages] [Bug 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux

2014-04-08 Thread Stan Osborne

a todos:  Gracias por la ayuda!

Stan

On Tue, April 8, 2014 1:03 pm, Luiz Angelo Daros de Luca wrote:
> @l-colin,
>
> 14.04 works flawlessly in Celeron/Pentium M processor systems. You just
> need to add forcepae do the kernel command line (at boot)
> On a livecd, press anykey as soon as it loads (the first purple screen).
> Use the F6 option to add the forcepae. You'll have something like:
>
>  "...initrd.lz quiet splash -- forcepae"
>
>

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

Title:
  Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
  x86 Laptop due to bug in PAE kernel, initramfs or syslinux

Status in “linux” package in Ubuntu:
  Fix Released
Status in “syslinux” package in Ubuntu:
  Invalid
Status in Baltix GNU/Linux:
  Triaged

Bug description:
  Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot
  loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error
  message about missing PAE feature in CPU, but *the same* *Ubuntu
  12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE
  kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB
  with GRUB boot loader, like Multisystem
  (http://liveusb.info/dotclear/index.php?pages/install ) is used!

  The error message is:
  "This kernel requires the following features not present on the CPU: pae.
  Unable to boot - please use a kernel appropriate for you CPU."

  THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully 
use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with 
Pentium M 1700Mhz processor, but the bug in syslinux (or something related) 
forbids Ubuntu 12.04 installation.
  This bug is reproducible on lots of computers, there are several log files 
and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen 
this bug.

  ---
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  MachineType: IBM 2373PPU
  dmi.bios.date: 06/18/2007
  dmi.bios.vendor: IBM
  dmi.bios.version: 1RETDRWW (3.23 )
  dmi.board.name: 2373PPU
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2373PPU
  dmi.product.version: ThinkPad T42
  dmi.sys.vendor: IBM

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

Re: [Kernel-packages] [Bug 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux

2014-02-12 Thread Stan Osborne

Roland,

Thanks for trying.

In 2012 an Ubuntu developer made a private version of 12.04 with PAE
support, so I am still using Ubuntu with my old laptop.

The Ubuntu team has people who could fix this the right way, but as you
said, they are lazy.

Stan


On Wed, February 12, 2014 4:39 pm, roland aus kÃ¶ln wrote:
> bugticket closed, as ubuntu team is ignorant and will not fix this.  sad
> but true.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (993939).
> https://bugs.launchpad.net/bugs/930447
>
> Title:
>   Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
>   x86 Laptop due to bug in PAE kernel, initramfs or syslinux
>
> Status in âlinuxâ package in Ubuntu:
>   Confirmed
> Status in âsyslinuxâ package in Ubuntu:
>   Invalid
> Status in Baltix GNU/Linux:
>   Triaged
>
> Bug description:
>   Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot
>   loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error
>   message about missing PAE feature in CPU, but *the same* *Ubuntu
>   12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE
>   kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB
>   with GRUB boot loader, like Multisystem
>   (http://liveusb.info/dotclear/index.php?pages/install ) is used!
>
>   The error message is:
>   "This kernel requires the following features not present on the CPU:
> pae.
>   Unable to boot - please use a kernel appropriate for you CPU."
>
>   THIS IS AN IMPORTANT REGRESSION! People are able to install and
> successfully use Ubuntu 12.04 on such pretty new hardware, like IBM
> Thinkpad T42 laptop with Pentium M 1700Mhz processor, but the bug in
> syslinux (or something related) forbids Ubuntu 12.04 installation.
>   This bug is reproducible on lots of computers, there are several log
> files and /proc/cpuinfo file attached to this bugreport, AFAIK it's
> enough to reopen this bug.
>
>   ---
>   ApportVersion: 1.23-0ubuntu4
>   Architecture: i386
>   CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13
> --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm:
> /var/log/dmesg: Permission denied
>   MachineType: IBM 2373PPU
>   dmi.bios.date: 06/18/2007
>   dmi.bios.vendor: IBM
>   dmi.bios.version: 1RETDRWW (3.23 )
>   dmi.board.name: 2373PPU
>   dmi.board.vendor: IBM
>   dmi.board.version: Not Available
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: IBM
>   dmi.chassis.version: Not Available
>   dmi.modalias:
> dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
>   dmi.product.name: 2373PPU
>   dmi.product.version: ThinkPad T42
>   dmi.sys.vendor: IBM
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930447/+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/930447

Title:
  Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M
  x86 Laptop due to bug in PAE kernel, initramfs or syslinux

Status in “linux” package in Ubuntu:
  Confirmed
Status in “syslinux” package in Ubuntu:
  Invalid
Status in Baltix GNU/Linux:
  Triaged

Bug description:
  Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot
  loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error
  message about missing PAE feature in CPU, but *the same* *Ubuntu
  12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE
  kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB
  with GRUB boot loader, like Multisystem
  (http://liveusb.info/dotclear/index.php?pages/install ) is used!

  The error message is:
  "This kernel requires the following features not present on the CPU: pae.
  Unable to boot - please use a kernel appropriate for you CPU."

  THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully 
use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with 
Pentium M 1700Mhz processor, but the bug in syslinux (or something related) 
forbids Ubuntu 12.04 installation.
  This bug is reproducible on lots of computers, there are several log files 
and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen 
this bug.

  ---
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission

[Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

2013-08-28 Thread Stan Schymanski

After half a day of working on 3.8.13-030813-generic, got the
"[drm:i915_hangcheck_hung]" again. At least it was sort-of recoverable,
as I was able to log into another tty and backup i915_error_state
(attached). Hope it helps someone for diagnosing the problem. When
returning to tty7, Screen was still flackering whenever I moved the
mouse, and it didn't seem to respond to any clicks, so I had to logout
by CTRL+ALT+DEL and then I could log back in without problems.

** Attachment added: "i915_error_state"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/946899/+attachment/3792231/+files/i915_error_state

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

Title:
  [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU
  hung

Status in The Linux Kernel:
  Incomplete
Status in The Linux Mint Distribution:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” package in Fedora:
  Unknown

Bug description:
  Since upgrading to 12.04 beta, I've seen this happen twice. The
  symptoms are:

  - The screen freezes
  - The backlight turns off

  At that point I have to reboot to get my display back. In syslog, i
  see:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.612064] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
  Mar  4 23:09:18 perseus kernel: [ 3751.612076] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
  Mar  4 23:09:18 perseus kernel: [ 3751.613658] [drm:i915_wait_request] 
*ERROR* i915_wait_request returns -11 (awaiting 114040 at 114004, next 114118)
  Mar  4 23:09:18 perseus kernel: [ 3751.637049] [drm:init_ring_common] *ERROR* 
render ring initialization failed ctl  head  tail  
start 

  followed by a lot of things like:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.700662] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:793 
intel_enable_pipe+0x14a/0x150 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.700667] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.700670] PLL state assertion failure 
(expected on, current off)

  Mar  4 23:09:18 perseus kernel: [ 3751.812158] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:930 
assert_pipe+0x75/0x80 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.812165] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.812170] pipe B assertion failure 
(expected on, current off)

  then:

  
  Mar  4 23:09:19 perseus kernel: [ 3753.044086] [drm:intel_lvds_enable] 
*ERROR* timed out waiting for panel to power on
  Mar  4 23:09:20 perseus kernel: [ 3753.671451] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.684603] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.704594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.724594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.744595] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.764606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.784607] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.804618] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.824606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-17-generic 3.2.0-17.27
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdz2458 F pulseaudio
   /dev/snd/controlC1:  mdz2458 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 49'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,17aa20bb,00100400'
 Controls  : 31
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-:00:1a.7-3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0990'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0

[Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

2013-08-28 Thread Stan Schymanski

Oops, wrong copy and paste, sorry!
3.11.0-031100rc5-generic from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc5-saucy/ crashes several 
times a day
3.11.0-994-generic from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/current/ 
crashes every couple of days on my machine

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

Title:
  [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU
  hung

Status in The Linux Kernel:
  Incomplete
Status in The Linux Mint Distribution:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” package in Fedora:
  Unknown

Bug description:
  Since upgrading to 12.04 beta, I've seen this happen twice. The
  symptoms are:

  - The screen freezes
  - The backlight turns off

  At that point I have to reboot to get my display back. In syslog, i
  see:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.612064] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
  Mar  4 23:09:18 perseus kernel: [ 3751.612076] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
  Mar  4 23:09:18 perseus kernel: [ 3751.613658] [drm:i915_wait_request] 
*ERROR* i915_wait_request returns -11 (awaiting 114040 at 114004, next 114118)
  Mar  4 23:09:18 perseus kernel: [ 3751.637049] [drm:init_ring_common] *ERROR* 
render ring initialization failed ctl  head  tail  
start 

  followed by a lot of things like:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.700662] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:793 
intel_enable_pipe+0x14a/0x150 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.700667] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.700670] PLL state assertion failure 
(expected on, current off)

  Mar  4 23:09:18 perseus kernel: [ 3751.812158] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:930 
assert_pipe+0x75/0x80 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.812165] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.812170] pipe B assertion failure 
(expected on, current off)

  then:

  
  Mar  4 23:09:19 perseus kernel: [ 3753.044086] [drm:intel_lvds_enable] 
*ERROR* timed out waiting for panel to power on
  Mar  4 23:09:20 perseus kernel: [ 3753.671451] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.684603] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.704594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.724594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.744595] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.764606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.784607] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.804618] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.824606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-17-generic 3.2.0-17.27
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdz2458 F pulseaudio
   /dev/snd/controlC1:  mdz2458 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 49'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,17aa20bb,00100400'
 Controls  : 31
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-:00:1a.7-3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0990'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 3072
 Mono: Capture 0 [0%] [18.00dB] [off]
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7KHT24WW-1.08'
 Mixer name : 'ThinkPad EC 7KHT2

[Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

2013-08-28 Thread Stan Schymanski

Just confirming that the kernel under http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.11-rc5-saucy/ is not usable to me. My laptop crashes
unrecoverably within hours and does not leave any traces in syslog.
About to remove it again from the kernel list.

3.11.0-031100rc5-generic from http://kernel.ubuntu.com/~kernel-
ppa/mainline/drm-intel-nightly/current/ works slightly better for me,
but I still get similar crashes every couple of days.

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

Title:
  [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU
  hung

Status in The Linux Kernel:
  Incomplete
Status in The Linux Mint Distribution:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” package in Fedora:
  Unknown

Bug description:
  Since upgrading to 12.04 beta, I've seen this happen twice. The
  symptoms are:

  - The screen freezes
  - The backlight turns off

  At that point I have to reboot to get my display back. In syslog, i
  see:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.612064] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
  Mar  4 23:09:18 perseus kernel: [ 3751.612076] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
  Mar  4 23:09:18 perseus kernel: [ 3751.613658] [drm:i915_wait_request] 
*ERROR* i915_wait_request returns -11 (awaiting 114040 at 114004, next 114118)
  Mar  4 23:09:18 perseus kernel: [ 3751.637049] [drm:init_ring_common] *ERROR* 
render ring initialization failed ctl  head  tail  
start 

  followed by a lot of things like:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.700662] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:793 
intel_enable_pipe+0x14a/0x150 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.700667] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.700670] PLL state assertion failure 
(expected on, current off)

  Mar  4 23:09:18 perseus kernel: [ 3751.812158] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:930 
assert_pipe+0x75/0x80 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.812165] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.812170] pipe B assertion failure 
(expected on, current off)

  then:

  
  Mar  4 23:09:19 perseus kernel: [ 3753.044086] [drm:intel_lvds_enable] 
*ERROR* timed out waiting for panel to power on
  Mar  4 23:09:20 perseus kernel: [ 3753.671451] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.684603] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.704594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.724594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.744595] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.764606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.784607] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.804618] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.824606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-17-generic 3.2.0-17.27
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdz2458 F pulseaudio
   /dev/snd/controlC1:  mdz2458 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 49'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,17aa20bb,00100400'
 Controls  : 31
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-:00:1a.7-3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0990'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 3072
 Mono: Capture 0 [0%] [18.00dB] [off]
  Card2

Re: [Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

2013-08-22 Thread Stan Schymanski

Thanks, peterbo. Sorry, got confused. Of course, I'm running it on 
13.04, too. I have had these really weird crashes before (rebooting by 
itself) and they went away after one of the kernel upgrades, maybe even 
when upgrading from 12.10 to 13.04. Got the Hangcheck timer elapsed ones 
instead. That is, sometimes, when I return to my laptop, it is turned 
off even when I'm pretty sure I left it on, so maybe they have just been 
happening while idle. Now with the rc5 kernel I got the original crash 
(without error log) within hours again, so I got discouraged from trying 
any further. It's my work laptop, running dual monitors, and I really 
can't afford to experiment too much as I need it to run and do its job. 
I still can't believe that this is such a persistent bug (several 
bugs?). The Linux kernel used to be considered bomb-proof! Apparently 
its bugs, too...


On 21/08/13 16:04, peterbo wrote:
> schymans: I am running 13.04 so have not tested on 12.10. The crash you
> describe sounds a bit worse than the gpu hang but I obviously cannot be
> sure. My laptop never rebooted when the hang occurred though.
>
> I must admit that I had one hang with rc5 after 7 days, however the
> error message was different than the usual "Hangcheck timer elapsed". It
> was something with a "ring" - cannot remember any more of it. It
> happened after having dual monitors connected, suspending my laptop and
> then opening it without any monitors connected. Am on rc6 now and no
> problems yet.
>
> I cannot seem to force the hang, neither by running glxspheres, dragging
> windows fast across the desktop or playing with compiz effetcs/settings.
>

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

Title:
  [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU
  hung

Status in The Linux Kernel:
  Incomplete
Status in The Linux Mint Distribution:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” package in Fedora:
  Unknown

Bug description:
  Since upgrading to 12.04 beta, I've seen this happen twice. The
  symptoms are:

  - The screen freezes
  - The backlight turns off

  At that point I have to reboot to get my display back. In syslog, i
  see:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.612064] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
  Mar  4 23:09:18 perseus kernel: [ 3751.612076] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
  Mar  4 23:09:18 perseus kernel: [ 3751.613658] [drm:i915_wait_request] 
*ERROR* i915_wait_request returns -11 (awaiting 114040 at 114004, next 114118)
  Mar  4 23:09:18 perseus kernel: [ 3751.637049] [drm:init_ring_common] *ERROR* 
render ring initialization failed ctl  head  tail  
start 

  followed by a lot of things like:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.700662] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:793 
intel_enable_pipe+0x14a/0x150 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.700667] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.700670] PLL state assertion failure 
(expected on, current off)

  Mar  4 23:09:18 perseus kernel: [ 3751.812158] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:930 
assert_pipe+0x75/0x80 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.812165] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.812170] pipe B assertion failure 
(expected on, current off)

  then:

  
  Mar  4 23:09:19 perseus kernel: [ 3753.044086] [drm:intel_lvds_enable] 
*ERROR* timed out waiting for panel to power on
  Mar  4 23:09:20 perseus kernel: [ 3753.671451] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.684603] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.704594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.724594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.744595] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.764606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.784607] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.804618] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.824606] [drm:i915_wait_request] 
*ERROR* something (li

[Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

2013-08-20 Thread Stan Schymanski

Thanks, peterbo, for the link incl. installation instructions! 
Unfortunately after two days, I had another crash with the new kernel on Ubuntu 
12.10. The mouse and keyboard stopped responding and before I could try to do 
CTRL+ALT+F4 or CTRL+ALT+SysRq+REISUB, the laptop just turned itself off. No 
traces left in syslog. Very annoying.

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

Title:
  [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU
  hung

Status in The Linux Kernel:
  Incomplete
Status in The Linux Mint Distribution:
  Confirmed
Status in “linux” package in Ubuntu:
  Triaged
Status in “linux” package in Fedora:
  Unknown

Bug description:
  Since upgrading to 12.04 beta, I've seen this happen twice. The
  symptoms are:

  - The screen freezes
  - The backlight turns off

  At that point I have to reboot to get my display back. In syslog, i
  see:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.612064] [drm:i915_hangcheck_elapsed] 
*ERROR* Hangcheck timer elapsed... GPU hung
  Mar  4 23:09:18 perseus kernel: [ 3751.612076] [drm] capturing error event; 
look for more information in /debug/dri/0/i915_error_state
  Mar  4 23:09:18 perseus kernel: [ 3751.613658] [drm:i915_wait_request] 
*ERROR* i915_wait_request returns -11 (awaiting 114040 at 114004, next 114118)
  Mar  4 23:09:18 perseus kernel: [ 3751.637049] [drm:init_ring_common] *ERROR* 
render ring initialization failed ctl  head  tail  
start 

  followed by a lot of things like:

  
  Mar  4 23:09:18 perseus kernel: [ 3751.700662] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:793 
intel_enable_pipe+0x14a/0x150 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.700667] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.700670] PLL state assertion failure 
(expected on, current off)

  Mar  4 23:09:18 perseus kernel: [ 3751.812158] WARNING: at 
/build/buildd/linux-3.2.0/drivers/gpu/drm/i915/intel_display.c:930 
assert_pipe+0x75/0x80 [i915]()
  Mar  4 23:09:18 perseus kernel: [ 3751.812165] Hardware name: 6465CTO
  Mar  4 23:09:18 perseus kernel: [ 3751.812170] pipe B assertion failure 
(expected on, current off)

  then:

  
  Mar  4 23:09:19 perseus kernel: [ 3753.044086] [drm:intel_lvds_enable] 
*ERROR* timed out waiting for panel to power on
  Mar  4 23:09:20 perseus kernel: [ 3753.671451] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.684603] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.704594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.724594] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.744595] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.764606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.784607] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.804618] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling
  Mar  4 23:09:20 perseus kernel: [ 3753.824606] [drm:i915_wait_request] 
*ERROR* something (likely vbetool) disabled interrupts, re-enabling

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-17-generic 3.2.0-17.27
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mdz2458 F pulseaudio
   /dev/snd/controlC1:  mdz2458 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 49'
 Mixer name : 'Analog Devices AD1984'
 Components : 'HDA:11d41984,17aa20bb,00100400'
 Controls  : 31
 Simple ctrls  : 19
  Card1.Amixer.info:
   Card hw:1 'Q9000'/'Logitech, Inc. QuickCam Pro 9000 at usb-:00:1a.7-3, 
high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB046d:0990'
 Controls  : 2
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
 Capture channels: Mono
 Limits: Capture 0 - 3072
 Mono: Capture 0 [0%] [18.00dB] [off]
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
7KHT24WW-1.0

[Kernel-packages] [Bug 1124933] Re: [Dell Latitude E6320] late resume failure

2013-08-08 Thread Stan Schymanski

Dear Chris, thanks for the tip. I upgraded my bios last night and will
see if the problem re-occurs. However, I have been having lots of other
problems and started using a newer kernel to keep my machine in working
condition, while I haven't been pointed to this bug report again. So I
won't be able to tell whether the bios update did the trick or a
different kernel, or whether it was a once-off problem. Sorry!

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

Title:
  [Dell Latitude E6320] late resume failure

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The computer was acting strange, so I clicked on "Shut down". An error
  message about Nautilus came up, I asked to force quit, then the
  shutdown proceeded very slowly until it hang on a black screen. No
  response to any shortcuts, so I had to do a hard reset. Got the crash
  report after reboot.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-24-generic 3.5.0-24.37
  ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
  Uname: Linux 3.5.0-24-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.  The resume processing hung very near the end and will have 
appeared to have completed normally.
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sschyman   2415 F pulseaudio
  Date: Thu Feb 14 08:14:37 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: late resume
  HibernationDevice: RESUME=UUID=c34c4140-0bc1-44ff-b072-6ebb317f1c95
  InstallationDate: Installed on 2011-06-28 (596 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  InterpreterPath: /usr/bin/python3.2mu
  MachineType: Dell Inc. Latitude E6320
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-24-generic 
root=UUID=5083e04c-1bad-44bf-a241-c839914a697a ro 
crashkernel=384M-2G:64M,2G-:128M
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-24-generic N/A
   linux-backports-modules-3.5.0-24-generic  N/A
   linux-firmware1.95
  RfKill:
   1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: linux
  Title: [Dell Inc. Latitude E6320] late resume failure
  UpgradeStatus: Upgraded to quantal on 2012-10-27 (109 days ago)
  UserGroups:
   
  dmi.bios.date: 08/15/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 087HK7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/15/2012:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn087HK7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6320
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1124933/+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 1964373] [NEW] Dell latitude e65640 touchpad and display problem.

[Kernel-packages] [Bug 1956461] Re: Creative HD720p webcam doesn't work

[Kernel-packages] [Bug 1957112] Re: webcam doesn't work

[Kernel-packages] [Bug 1957112] Re: webcam doesn't work

[Kernel-packages] [Bug 1957112] Re: webcam doesn't work

[Kernel-packages] [Bug 1957112] Re: webcam doesn't work

[Kernel-packages] [Bug 1953199] Re: 0-byte files created in overlay filesystem

[Kernel-packages] [Bug 1953199] Re: 0-byte files created in overlay filesystem

[Kernel-packages] [Bug 1953199] Re: 0-byte files created in overlay filesystem

[Kernel-packages] [Bug 1953199] [NEW] 0-byte files created in overlay filesystem

[Kernel-packages] [Bug 1790454] Re: Bluetooth (btintel) stops working after suspend/resume

[Kernel-packages] [Bug 1775131] Re: Ubuntu 18.04 networking issue (connection drops after approx. 15 minutes)

[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle

[Kernel-packages] [Bug 1802585] Re: NFS v4.0: Stale data after file is renamed while another process has an open file handle

[Kernel-packages] [Bug 1802585] [NEW] NFS v4.0: Stale data after file is renamed while another process has an open file handle

[Kernel-packages] [Bug 1757008] Re: bcmwl-kernel-source: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’]

[Kernel-packages] [Bug 1521982] Re: package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/le

[Kernel-packages] [Bug 1521982] [NEW] package linux-image-extra-4.2.0-19-generic 4.2.0-19.23 failed to install/upgrade: Extrahierte Daten für »./lib/modules/4.2.0-19-generic/kernel/drivers/usb/gadget/

[Kernel-packages] [Bug 1490214] Re: Does not detect hotplugged USB device

Re: [Kernel-packages] [Bug 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux

Re: [Kernel-packages] [Bug 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux

[Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

[Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

[Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

Re: [Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

[Kernel-packages] [Bug 946899] Re: [drm:i915_hangcheck_elapsed] ERROR Hangcheck timer elapsed... GPU hung

[Kernel-packages] [Bug 1124933] Re: [Dell Latitude E6320] late resume failure

27 matches

Site Navigation

Mail list logo

Footer information