[Kernel-packages] [Bug 2076048] Re: My system freezes after waking from suspend

2024-08-05 Thread Torsten Krah
Same here. Freeze after resume on my Lenovo ThinkPad T14 Gen 3, model
21CFCTO1WW.

Additionally, with this 6.8.0-x kernel, I can no longer boot without my LID 
open and just use the docking station monitors. It boots, docking station is 
working (both displays are working) - I can enter my decryption password and 
after that it just continues to boot and goes straight into suspend mode.
6.5.x does not show this strange behavior.

Boot log has:

Aug 05 20:43:15 TORSTENKNBL2 kernel: amdgpu :04:00.0: [drm] *ERROR* Failed 
to get ACT after 3000ms, last status: 00
Aug 05 20:43:15 TORSTENKNBL2 kernel: BUG: kernel NULL pointer dereference, 
address: 0008
Aug 05 20:43:15 TORSTENKNBL2 kernel: #PF: supervisor read access in kernel mode
Aug 05 20:43:15 TORSTENKNBL2 kernel: #PF: error_code(0x) - not-present page
Aug 05 20:43:15 TORSTENKNBL2 kernel: PGD 0 P4D 0 
Aug 05 20:43:15 TORSTENKNBL2 kernel: Oops:  [#1] PREEMPT SMP NOPTI


** Attachment added: "BUG: kernel NULL pointer dereference, address: 
0008"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076048/+attachment/5802996/+files/null-pointer.txt

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

Title:
  My system freezes after waking from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 24.04 on my Lenovo ThinkPad T14 Gen 3 (AMD
  Ryzen™ 7 PRO 6850U with Radeon™ Graphics × 16). Type - 21CF-003QAU

  Since installation, the following problem has occurred:

  - Whenever I suspend the system (e.g. power off menu > suspend), the system 
successfully goes into a suspended state.
  - When I wake the computer, the computer wakes and presents me with the login 
screen
  - I can log into the system, and the mouse and all previously open windows 
appear to be working, sound is working etc
  - I CAN'T seem to open any new applications or run any new commands at this 
time (no error messages, just nothing starting)
  - Approximately 30 seconds to 1 minute later, the system freezes completely. 
No error messages, and I can see everything on the screen. But mouse/keyboard 
input stops, sound stops, and I have to physically hard restart the laptop.
  - Example is caplock key light on keyboard stops responding. Interestingly 
the Esc/FnLock key light still works

  I have updated all the firmware / BIOS to the latest versions, and the
  issue still persists.

  I have run Ubuntu from a Live USB on the same machine, and when
  suspending, all appears to work OK.

  I have done a completely fresh install with default installation
  parameters, and system freeze as explained above occurs every time.

  Also reported to Lenovo here ->
  https://forums.lenovo.com/t5/Ubuntu/Lenovo-T14-Gen3-AMD-with-
  Ubuntu-24-04-System-freezes-30-seconds-after-waking-from-
  sleep/m-p/5324170?page=1#6404090

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: linux-image-6.8.0-39-generic 6.8.0-39.39
  ProcVersionSignature: Ubuntu 6.8.0-39.39-generic 6.8.8
  Uname: Linux 6.8.0-39-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 09:21:52 2024
  InstallationDate: Installed on 2024-08-01 (4 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: LENOVO 21CF003QAU
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-39-generic 
root=UUID=a12931b8-49e7-4226-b38f-3febeac4f41d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.8.0-39-generic N/A
   linux-backports-modules-6.8.0-39-generic  N/A
   linux-firmware20240318.git3b128b60-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2024
  dmi.bios.release: 1.53
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET77W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF003QAU
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF003QAU:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF003QAU:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF003QAU
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

2023-12-14 Thread Torsten Krah
** Also affects: linux-meta-hwe-6.5 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

  Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
  Moreover, in the mainline Linux source code, I do not find the lines where 
such a message could be printed.

  Therefore, those messages are probably caused by an Ubuntu patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off 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:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!

2023-12-14 Thread Torsten Krah
I do have the same messages (6.5.0-14-generic #14~22.04.1-Ubuntu) in the
dmesg after booting, but I don't use ceph nor do I have an usb drive
connected.

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

Title:
  evict_inodes inode xxx, i_count = 1, was skipped!

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
  New
Status in linux-oem-6.5 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  during boot the kernel logs the following messages:

  # dmesg | grep evict_inodes
  [   12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
  [   12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
  [   12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
  [   12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
  [   12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
  [   12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
  [   13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
  [   13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
  [   13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!

  Those messages are not displayed when I boot my system with a mainline Linux 
kernel.
  Moreover, in the mainline Linux source code, I do not find the lines where 
such a message could be printed.

  Therefore, those messages are probably caused by an Ubuntu patch.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-5-generic 6.5.0-5.5
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bonnaudl   4827 F wireplumber
   /dev/snd/seq:bonnaudl   4808 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Sep 24 14:39:10 2023
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
tpm_tis.interrupts=0 preempt=full split_lock_detect=off 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:
   linux-restricted-modules-6.5.0-5-generic N/A
   linux-backports-modules-6.5.0-5-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2022
  dmi.bios.release: 7.16
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.16NRTR4
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: NS50_70MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 1950515] Re: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others

2021-11-29 Thread Torsten Gilles
Wifi now works for me with my XPS 9310 when upgrading to new kernel
5.13.0-22.

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

Title:
  WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on
  Dell XPS 13 9310 and others

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In the 5.13.0-21 kernel, the device fails:

  $ lshw -c network
*-network 
 description: Network controller
 product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)]
 vendor: Qualcomm
 physical id: 0
 bus info: pci@:72:00.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 configuration: driver=ath11k_pci latency=0
 resources: irq:182 memory:a250-a25f

  $ lspci | grep Qualcomm
  72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter 
[AX500-DBS (2x2)] (rev 01)

  $ sudo modprobe ath11k_pci

  $ sudo dmesg | grep ath
  [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002)
  [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0
  [   10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110
  [   10.337692] ath11k_pci :72:00.0: failed to send qmi firmware 
indication: -110
  [   39.931711] ath11k_pci :72:00.0: link down error during global reset
  [   45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [   45.575668] ath11k_pci :72:00.0: qca6390 hw2.0
  [   45.630047] ath11k_pci :72:00.0: failed to set pcie link register 
0x01e0c0ac: 0x != 0x0010
  [   45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110
  [   45.650253] ath11k_pci :72:00.0: link down error during global reset

  $ rfkill list all
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  In the 5.13.0-20 kernel, the device works:

  $ sudo dmesg | grep ath
  [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002)
  [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0
  [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 
0xff soc_id 0x
  [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 
2020-06-24 19:50 fw_build_id
  [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0
  [ 351.080712] ath11k_pci :72:00.0: link down error during global reset
  [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-21-generic 5.13.0-21.21
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 15:23:07 2021
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-05-04 (190 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-21-generic N/A
   linux-backports-modules-5.13.0-21-generic  N/A
   linux-firmware 1.201.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 3.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.2.0
  dmi.board.name: 0MRT12
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1950515] Re: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others

2021-11-14 Thread Torsten Gilles
I have the same issue with XPS 9310 when upgrading from 5.13.0-19 or 5.13.0-20 
to 5.13.0-21.
5.13.0-19 or 5.13.0-20 work both fine for 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/1950515

Title:
  WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on
  Dell XPS 13 9310 and others

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In the 5.13.0-21 kernel, the device fails:

  $ lshw -c network
*-network 
 description: Network controller
 product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)]
 vendor: Qualcomm
 physical id: 0
 bus info: pci@:72:00.0
 version: 01
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list
 configuration: driver=ath11k_pci latency=0
 resources: irq:182 memory:a250-a25f

  $ lspci | grep Qualcomm
  72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter 
[AX500-DBS (2x2)] (rev 01)

  $ sudo modprobe ath11k_pci

  $ sudo dmesg | grep ath
  [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002)
  [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0
  [   10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110
  [   10.337692] ath11k_pci :72:00.0: failed to send qmi firmware 
indication: -110
  [   39.931711] ath11k_pci :72:00.0: link down error during global reset
  [   45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [   45.575668] ath11k_pci :72:00.0: qca6390 hw2.0
  [   45.630047] ath11k_pci :72:00.0: failed to set pcie link register 
0x01e0c0ac: 0x != 0x0010
  [   45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110
  [   45.650253] ath11k_pci :72:00.0: link down error during global reset

  $ rfkill list all
  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  In the 5.13.0-20 kernel, the device works:

  $ sudo dmesg | grep ath
  [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002)
  [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0
  [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 
0xff soc_id 0x
  [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 
2020-06-24 19:50 fw_build_id
  [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0
  [ 351.080712] ath11k_pci :72:00.0: link down error during global reset
  [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 
0xa250-0xa25f 64bit]
  [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-21-generic 5.13.0-21.21
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 15:23:07 2021
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2021-05-04 (190 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.13.0-21-generic N/A
   linux-backports-modules-5.13.0-21-generic  N/A
   linux-firmware 1.201.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago)
  dmi.bios.date: 09/30/2021
  dmi.bios.release: 3.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.2.0
  dmi.board.name: 0MRT12
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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


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

[Kernel-packages] [Bug 1924624] Re: After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7, Haswell/Ivy Bridge) a lot of glitches render screen unusable

2021-04-29 Thread Torsten Bronger
Is there a plan, roadmap, or experience values for when to expect -51
for focal without using the above mentioned – not recommended – PPA?
It’s not that I want to complain; it would be simply helpful for my own
planning.

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

Title:
  After upgrade to 5.8.0-49/5.8.0-50 with Intel graphics (gen7,
  Haswell/Ivy Bridge) a lot of glitches render screen unusable

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe-5.8 package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 5.8.0-49, on a laprtop with intel graphics, graphics was 
suddenly extremely glitchy.
  Icons from the desktop flash through the browser, windows top bar gets 
distorted, all sort of glitches appear, parts of characters are missing in 
terminal, scrolling is inconsistent and the whole desktop becomes unusable.
  Under wayland the graphics are a bit more stable, but lots of glitches appear 
anyway, video reproduction in browser is stuttering and wobbly.
  Booting with previous kernel 5.8.0-48 seems to fix the issues.
  5.8.0-50 is broken as well.

  this is the result of 'sudo lshw -c video' on my hp Elitebook 8470:

  *-display 
 description: VGA compatible controller
 product: 3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:33 memory:d400-d43f memory:c000-cfff 
ioport:4000(size=64) memory:c-d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924624/+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 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0

2021-03-29 Thread Torsten
Sounds good, I will wait till it is available on normal channel.
Thx everybody!

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

Title:
  Missing Commit for 5.4-Kernel breaks  xen Dom0

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Fix Committed

Bug description:
  You commited "xen: Fix event channel callback via INTX/GSI" for kernel 
5.4.0-67 for HWE 18.04 and 20.04.
  This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also 
Commit "xen: Fix XenStore initialisation for XS_LOCAL"

  See https://lkml.org/lkml/2021/1/28/1235
  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195

  Upstream:
  Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2
  Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1

  5.10:
  Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11)
  Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13)

  5.4:
  Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93)
  Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95)

  Without this patch you cannot start guests (DomU) on this machine!

  Error message while creating DomU:
  libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to 
add device with path /
  libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add 
disk devices

  See:
  - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14
  - 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f
  - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95
  - 
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1920660] Re: Missing Commit for 5.4-Kernel breaks xen Dom0

2021-03-24 Thread Torsten
Is this bug fixed in 5.4.0-70, which is available now?

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

Title:
  Missing Commit for 5.4-Kernel breaks  xen Dom0

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe-5.4 package in Ubuntu:
  Confirmed

Bug description:
  You commited "xen: Fix event channel callback via INTX/GSI" for kernel 
5.4.0-67 for HWE 18.04 and 20.04.
  This commit is incomplete and breaks Ubuntu as Dom0 for xen. You need also 
Commit "xen: Fix XenStore initialisation for XS_LOCAL"

  See https://lkml.org/lkml/2021/1/28/1235
  See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195

  Upstream:
  Commit: 3499ba8198cad47b731792e5e56b9ec2a78a83a2
  Fixing Commit: 5f46400f7a6a4fad635d5a79e2aa5a04a30ffea1

  5.10:
  Commit: fa5f2e04daa44961a1026e93f0cc88caa3c27d3d (5.10.11)
  Fixing Commit: 5f3d54c00f1f2682cee9c590c22655b0330ffd18 (5.10.13)

  5.4:
  Commit: a09d4e7acdbf276b2096661ee82454ae3dd24d2b (5.4.93)
  Fixing commit 2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f (5.4.95)

  Without this patch you cannot start guests (DomU) on this machine!

  Error message while creating DomU:
  libxl: error: libxl_device.c:1105:device_backend_callback: Domain X:unable to 
add device with path /
  libxl: error: libxl_create.c:1452:domcreate_launch_dm: Domain X:unable to add 
disk devices

  See:
  - https://lkml.org/lkml/2021/1/28/1231 and https://lkml.org/lkml/2021/1/29/14
  - 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.4.107=2c7b4b25293aebd2563188f7196f6e0ff0cb0f9f
  - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.95
  - 
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-hwe-5.4/linux-hwe-5.4_5.4.0-67.75~18.04.1/changelog
  - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915195

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920660/+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 1900886] [NEW] package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to install/upgrade: »installiertes linux-image-5.4.0-52-generic-Skript des Paketes pre-removal«-Unterproze

2020-10-21 Thread Torsten Pauleit
Public bug reported:

the problem starts after install complete ubuntu 20.04 until Oct 21,
2020

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-52-generic 5.4.0-52.57
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bluesky1191 F pulseaudio
CasperMD5CheckResult: skip
Date: Wed Oct 21 12:51:00 2020
ErrorMessage: »installiertes linux-image-5.4.0-52-generic-Skript des Paketes 
pre-removal«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2020-10-21 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
 lono wireless extensions.
 
 enp0s3no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
MachineType: innotek GmbH VirtualBox
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=eaa98966-b350-495e-aebe-3a6e65721ba6 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4
RfKill:
 
SourcePackage: linux
Title: package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to 
install/upgrade: »installiertes linux-image-5.4.0-52-generic-Skript des Paketes 
pre-removal«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-package focal

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

Title:
  package linux-image-5.4.0-52-generic 5.4.0-52.57 failed to
  install/upgrade: »installiertes linux-image-5.4.0-52-generic-Skript
  des Paketes pre-removal«-Unterprozess gab den Fehlerwert 1 zurück

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the problem starts after install complete ubuntu 20.04 until Oct 21,
  2020

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-52-generic 5.4.0-52.57
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bluesky1191 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Oct 21 12:51:00 2020
  ErrorMessage: »installiertes linux-image-5.4.0-52-generic-Skript des Paketes 
pre-removal«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2020-10-21 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=eaa98966-b350-495e-aebe-3a6e65721ba6 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.4.0-52-generic 5.4.0-52.57 

[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-05-02 Thread Torsten Römer
Unfortunately I have to confirm that the workaround from #42 only makes the 
hard freeze less frequent and doesn't solve it like I stated in #53.
I also have the impression that standby/resume increases the probability of a 
freeze, but I just had one about one hour after a fresh new start.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798961/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-04-23 Thread Torsten Römer
After uptime 15 days, 10:34 with countless standby/resume cycles, I
think it is pretty safe to say that the solution from #42 works for me
too.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

2019-04-13 Thread Torsten Römer
I just received Kernel 5.0.0-11-generic via Ubuntu update and the issue
seems to be solved :-)

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

Title:
  [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports
  "(EE) modeset(0): failed to set mode: Invalid argument" when using
  kernel 4.19.26 and later (but 4.19.25 and earlier works)

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Updated from kubuntu 18.10 to 19.04 beta without problems. After first
  reboot, first the kubuntu logo, then just a blank screen, no login
  screen. Switching to console and log in there possible. All seems
  fine, including wlan etc.

  systemd status sddm says sddm is running, any attempt to start KDE
  (including startkde) however fails with "could not connect to any x
  display".

  This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the
  login screen comes up and all is fine.

  Anything I can contribute?

  Description:Ubuntu Disco Dingo (development branch)
  Release:19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Mar 30 21:51:04 2019
  DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed
   tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
  InstallationDate: Installed on 2017-07-07 (631 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 78545HG
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L420
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1822441/+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 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but

2019-04-08 Thread Torsten Römer
Done: https://bugs.freedesktop.org/show_bug.cgi?id=110359

Thanks to all helping out!

** Bug watch added: freedesktop.org Bugzilla #110359
   https://bugs.freedesktop.org/show_bug.cgi?id=110359

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

Title:
  [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports
  "(EE) modeset(0): failed to set mode: Invalid argument" when using
  kernel 4.19.26 and later (but 4.19.25 and earlier works)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Updated from kubuntu 18.10 to 19.04 beta without problems. After first
  reboot, first the kubuntu logo, then just a blank screen, no login
  screen. Switching to console and log in there possible. All seems
  fine, including wlan etc.

  systemd status sddm says sddm is running, any attempt to start KDE
  (including startkde) however fails with "could not connect to any x
  display".

  This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the
  login screen comes up and all is fine.

  Anything I can contribute?

  Description:Ubuntu Disco Dingo (development branch)
  Release:19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Mar 30 21:51:04 2019
  DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed
   tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
  InstallationDate: Installed on 2017-07-07 (631 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 78545HG
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L420
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-04-02 Thread Torsten Römer
@teresaejunior Yes, currently trying it, will report back!

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798961/+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 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 5.0.0

2019-04-01 Thread Torsten Römer
Also with 4.19.26-generic there is the error:

[ 7.575] (EE) modeset(0): failed to set mode: Invalid argument

** Attachment added: "Xorg.0.log-4.19.26"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+attachment/5251780/+files/Xorg.0.log-4.19.26

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

Title:
  [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports
  "(EE) modeset(0): failed to set mode: Invalid argument" when using
  kernel 5.0.0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated from kubuntu 18.10 to 19.04 beta without problems. After first
  reboot, first the kubuntu logo, then just a blank screen, no login
  screen. Switching to console and log in there possible. All seems
  fine, including wlan etc.

  systemd status sddm says sddm is running, any attempt to start KDE
  (including startkde) however fails with "could not connect to any x
  display".

  This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the
  login screen comes up and all is fine.

  Anything I can contribute?

  Description:Ubuntu Disco Dingo (development branch)
  Release:19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Mar 30 21:51:04 2019
  DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed
   tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
  InstallationDate: Installed on 2017-07-07 (631 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 78545HG
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L420
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+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 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 5.0.0

2019-04-01 Thread Torsten Römer
So I tried a lot of kernels :-)

The latest it still works with was 4.19.25-generic (currently using it).
It fails starting with 4.19.26-generic.

I tried many versions older than 4.19.25-generic, they all worked, and
any version later than 4.19.26-generic failed as well.

So it seems something broke in 4.19.26-generic.

** Attachment added: "Xorg.0.log-4.19.26.old"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+attachment/5251779/+files/Xorg.0.log-4.19.26.old

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

Title:
  [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports
  "(EE) modeset(0): failed to set mode: Invalid argument" when using
  kernel 5.0.0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Updated from kubuntu 18.10 to 19.04 beta without problems. After first
  reboot, first the kubuntu logo, then just a blank screen, no login
  screen. Switching to console and log in there possible. All seems
  fine, including wlan etc.

  systemd status sddm says sddm is running, any attempt to start KDE
  (including startkde) however fails with "could not connect to any x
  display".

  This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the
  login screen comes up and all is fine.

  Anything I can contribute?

  Description:Ubuntu Disco Dingo (development branch)
  Release:19.04

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Mar 30 21:51:04 2019
  DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed
   acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed
   tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed
   virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21dd]
  InstallationDate: Installed on 2017-07-07 (631 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 78545HG
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic 
root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad L420
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-04-01 Thread Torsten Römer
Unfortunately I have to revoke my comment #44 - had again two freezes
with 4.18.0-16-generic in the last few 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/1798961

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798961/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2019-03-19 Thread Torsten Römer
For me on a DELL Latitude E5550 it seems the issue is solved since
update to 4.18.0-16-generic (kubuntu). Running for a week now with
several suspend/resume cycles - no more frost. Spring is coming  :-)

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798961/+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 1802691] Re: Slow send speed with Intel I219-V on Ubuntu 18.04.1

2019-01-07 Thread Torsten
I also encountered network performance degradation on my server, however I'm 
not running Ubuntu but Debian with a self-compiled kernel. With bisecting the 
kernel, I could track this issue down to this commit between 4.14.2 and 4.14.3:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0f478f25d50cb6464678284a13f514fefc16e271

I was tempted to undo this change in my kernel, however this change
works around a bug in the I219 adapter and I didn't want to end up with
an unstable system. Related to this bug I read about TCP segmentation
offload and changed tso and gso values with ethtool. Eventually "ethtool
-K enp0s31f6 tso" off did the trick for me and network performance is
back to normal. You might have to change the name of enp0s31f6 to the
name of your Ethernet adapter or play with on/off values for tso and
gso.

In order to persist this setting after a reboot, I created a udev rule
that calls ethtool, maybe this  option works for you as well.

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

Title:
  Slow send speed with Intel I219-V on Ubuntu 18.04.1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Testing with iperf3 send speed is only 750mbps while receive speed is
  normal - 940mbps.

  Ubuntu 18.04.1
  Msi b250m mortar
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  django 1016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-11-09 (6 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7A69
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic 
root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/29/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.60
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M MORTAR ARCTIC (MS-7A69)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A69
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802691/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2018-12-13 Thread Torsten Römer
I just would like to add that I have the same problem about once a day
on a DELL Latitude E5550, usually a relatively short while after
resuming from standby. It never happens when I boot into the older
4.15.0-39-generic kernel.

On a Lenovo L420 that I have updated at the same time, I never had the
problem so far.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  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/1798961/+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 1710390] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000

2018-09-11 Thread Torsten Krah
Hardware is:

[   16.257444] iwlwifi :3d:00.0: loaded firmware version 36.e91976c0.0 
op_mode iwlmvm
[   16.282258] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless AC 
8265, REV=0x230


** Changed in: linux (Ubuntu)
   Status: Invalid => 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/1710390

Title:
  iwlwifi: Microcode SW error detected. Restarting 0x200

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug was resolved (see 1588632)  On ubuntu 17.04 recent update
  from kernel 4.10.0-30-generic to 4.10.0-32-generic has resulted in a
  regression, reintroducing this bug.

  iwlwifi :03:00.0: Microcode SW error detected.  Restarting 0x200.
  [   12.294262]  iwl_pcie_irq_handle_error+0x39/0x160 [iwlwifi]
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  janice 1664 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=be1fb904-a9f5-4c1f-a154-349c0a6e63de
  InstallationDate: Installed on 2016-07-12 (396 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160712)
  MachineType: Dell Inc. Dell System XPS 15Z
  Package: linux (not installed)
  ProcFB:
   0 nouveaufb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=c280c3d0-6ec1-4080-9d10-74acc2399bad ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-30-generic N/A
   linux-backports-modules-4.10.0-30-generic  N/A
   linux-firmware 1.164.1
  Tags:  zesty
  Uname: Linux 4.10.0-30-generic x86_64
  UpgradeStatus: Upgraded to zesty on 2017-03-11 (153 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo www-data
  _MarkForUpload: True
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0XK6HV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn0XK6HV:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS 15Z
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710390/+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 1710390] Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000

2018-09-11 Thread Torsten Krah
I still have this:

[ 9438.934175] iwlwifi :3d:00.0: Error sending 
CMD_DTS_MEASUREMENT_TRIGGER_WIDE: time out after 2000ms.
[ 9438.934188] iwlwifi :3d:00.0: Current CMD queue read_ptr 218 write_ptr 
219
[ 9438.935409] iwlwifi :3d:00.0: HCMD_ACTIVE already clear for command 
CMD_DTS_MEASUREMENT_TRIGGER_WIDE
[ 9438.935446] iwlwifi :3d:00.0: Microcode SW error detected.  Restarting 
0x200.
[ 9438.935526] iwlwifi :3d:00.0: Start IWL Error Log Dump:
[ 9438.935536] iwlwifi :3d:00.0: Status: 0x0100, count: 6
[ 9438.935542] iwlwifi :3d:00.0: Loaded firmware version: 36.e91976c0.0
[ 9438.935549] iwlwifi :3d:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN   
[ 9438.935554] iwlwifi :3d:00.0: 0x02F0 | trm_hw_status0
[ 9438.935560] iwlwifi :3d:00.0: 0x | trm_hw_status1
[ 9438.935565] iwlwifi :3d:00.0: 0x000248DC | branchlink2
[ 9438.935570] iwlwifi :3d:00.0: 0x0003A7DA | interruptlink1
[ 9438.935575] iwlwifi :3d:00.0: 0x0003A7DA | interruptlink2
[ 9438.935581] iwlwifi :3d:00.0: 0x | data1
[ 9438.935586] iwlwifi :3d:00.0: 0x0080 | data2
[ 9438.935591] iwlwifi :3d:00.0: 0x0783 | data3
[ 9438.935596] iwlwifi :3d:00.0: 0x | beacon time
[ 9438.935602] iwlwifi :3d:00.0: 0x31919AD7 | tsf low
[ 9438.935607] iwlwifi :3d:00.0: 0x0002 | tsf hi
[ 9438.935612] iwlwifi :3d:00.0: 0x | time gp1
[ 9438.935617] iwlwifi :3d:00.0: 0x31919AD8 | time gp2
[ 9438.935623] iwlwifi :3d:00.0: 0x0001 | uCode revision type
[ 9438.935628] iwlwifi :3d:00.0: 0x0024 | uCode version major
[ 9438.935633] iwlwifi :3d:00.0: 0xE91976C0 | uCode version minor
[ 9438.935638] iwlwifi :3d:00.0: 0x0230 | hw version
[ 9438.935644] iwlwifi :3d:00.0: 0x00489000 | board version
[ 9438.935649] iwlwifi :3d:00.0: 0x00DA0400 | hcmd
[ 9438.935654] iwlwifi :3d:00.0: 0x00022000 | isr0
[ 9438.935659] iwlwifi :3d:00.0: 0x0080 | isr1
[ 9438.935665] iwlwifi :3d:00.0: 0x08001802 | isr2
[ 9438.935670] iwlwifi :3d:00.0: 0x00400080 | isr3
[ 9438.935675] iwlwifi :3d:00.0: 0x | isr4
[ 9438.935680] iwlwifi :3d:00.0: 0x00DA0400 | last cmd Id
[ 9438.935685] iwlwifi :3d:00.0: 0x | wait_event
[ 9438.935691] iwlwifi :3d:00.0: 0xD82D | l2p_control
[ 9438.935696] iwlwifi :3d:00.0: 0x | l2p_duration
[ 9438.935701] iwlwifi :3d:00.0: 0x | l2p_mhvalid
[ 9438.935706] iwlwifi :3d:00.0: 0x | l2p_addr_match
[ 9438.935711] iwlwifi :3d:00.0: 0x008F | lmpm_pmg_sel
[ 9438.935717] iwlwifi :3d:00.0: 0x28031619 | timestamp
[ 9438.935722] iwlwifi :3d:00.0: 0x00344860 | flow_handler
[ 9438.935921] iwlwifi :3d:00.0: 0x | ADVANCED_SYSASSERT
[ 9438.935927] iwlwifi :3d:00.0: 0x | umac branchlink1
[ 9438.935932] iwlwifi :3d:00.0: 0x | umac branchlink2
[ 9438.935937] iwlwifi :3d:00.0: 0x | umac interruptlink1
[ 9438.935942] iwlwifi :3d:00.0: 0x | umac interruptlink2
[ 9438.935947] iwlwifi :3d:00.0: 0x | umac data1
[ 9438.935952] iwlwifi :3d:00.0: 0x | umac data2
[ 9438.935957] iwlwifi :3d:00.0: 0x | umac data3
[ 9438.935962] iwlwifi :3d:00.0: 0x | umac major
[ 9438.935967] iwlwifi :3d:00.0: 0x | umac minor
[ 9438.935973] iwlwifi :3d:00.0: 0x | frame pointer
[ 9438.935978] iwlwifi :3d:00.0: 0x | stack pointer
[ 9438.935983] iwlwifi :3d:00.0: 0x | last host cmd
[ 9438.935988] iwlwifi :3d:00.0: 0x | isr status reg
[ 9438.935998] ieee80211 phy0: Hardware restart was requested
[ 9438.936013] iwlwifi :3d:00.0: Failed to get the temperature (err=-110)


And the workaround described is already in the NetworkManager.conf (was already 
in place). So still there's some problem here using 18.04 LTS.

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

Title:
  iwlwifi: Microcode SW error detected. Restarting 0x200

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug was resolved (see 1588632)  On ubuntu 17.04 recent update
  from kernel 4.10.0-30-generic to 4.10.0-32-generic has resulted in a
  regression, reintroducing this bug.

  iwlwifi :03:00.0: Microcode SW error detected.  Restarting 0x200.
  [   12.294262]  iwl_pcie_irq_handle_error+0x39/0x160 [iwlwifi]
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  janice 1664 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=be1fb904-a9f5-4c1f-a154-349c0a6e63de
  InstallationDate: Installed on 2016-07-12 (396 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160712)
  MachineType: Dell Inc. Dell System XPS 

[Kernel-packages] [Bug 1643657] Re: touchpad not work at a toshiba satellite L870-16G

2016-11-21 Thread Torsten Franz
** Summary changed:

- toutchpad not work
+ touchpad not work at a toshiba satellite L870-16G

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

Title:
  touchpad not work at a toshiba satellite L870-16G

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i have a computer toshiba satellite, After a power outage, my touchpad
  not work now.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-47-generic 4.4.0-47.68
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   mohammedamine   1863 F...m pulseaudio
   /dev/snd/controlC0:  mohammedamine   1863 F pulseaudio
   /dev/snd/controlC1:  mohammedamine   1863 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 21 17:57:19 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=d9295237-1313-43d4-8a44-8897d2d7750b
  InstallationDate: Installed on 2016-10-14 (37 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: TOSHIBA Satellite L870-16G
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed 
root=UUID=5c2ce860-3279-487d-bc05-b028a6380555 ro net.ifnames=0 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-47-generic N/A
   linux-backports-modules-4.4.0-47-generic  N/A
   linux-firmware1.157.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.20
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.20:bd10/24/2012:svnTOSHIBA:pnSatelliteL870-16G:pvrPSKFNE-00K00LFR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L870-16G
  dmi.product.version: PSKFNE-00K00LFR
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643657/+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 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

2016-10-20 Thread Torsten Casselt
Are you serious? You release a new kernel 4.4.0-45 without the fixes in
4.4.0-44 sitting in -proposed? What do you think -proposed is meant for?
Systems using -proposed to avoid this bug now happily boot the new
kernel facing this bug again.

Could you please get your stuff together and stop breaking
installations?! Why do you think people are using LTS releases?

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

Title:
  Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  SRU Justification

  Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds"
  causes a regression in the requester uid and gid passed to userspace
  during automount, as the current credentials during automount are
  those of root and not the user who requested the mount.

  Fix: Use current->real_cred instead of current->cred for getting the
  requester's uid and gid.

  Regression Potential: Minimal. current->cred and current->real_cred
  are the same except when credentials are overridden, thus
  current->real_cred contains the same credentials that autofs had been
  using prior to the change which overrides the credentials during
  automount.

  ---

  Hello,

  I have run into a bug relating autofs's parameter substitution (e.g.
  UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40.
  Kernel version 4.4.0-28 does things correctly but testing intermediate
  kernel versions is hard due to earlier bugs related with fs's.
  Incorrect parameter substitution makes CIFS mounting with variable
  credentials impossible.

  Wat was expected:
  $UID in autofs map are substituted by the uid of the user that starts the 
auto-mounting process.

  What actually happens:
  Root's uid (0) is substituted instead.

  This ill parameter substitution likely caused by recent fixes
  resolving permissions problems for nfs/cifs mounts and dfs referrals
  (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount
  with the filesystems creds' but that is a wild guess.

  Furthermore; playing with the force_standard_program_map_env settings
  in autofs.conf and prefixing variables with 'AUTOFS_' does not solve
  anything.

  Yours kindly,

  Chris

   Additional info 

    lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  run1   3015 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214
  InstallationDate: Installed on 2016-09-19 (10 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp0s8no wireless extensions.

   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 
ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-40-generic N/A
   linux-backports-modules-4.4.0-40-generic  N/A
   linux-firmware1.157.3
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1629204] Re: Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

2016-10-19 Thread Torsten Casselt
The kernel in -proposed is working.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Autofs parameter substitution broken in kernel 4.4.0-38 and 4.4.0-40

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  SRU Justification

  Impact: ca6fe3344554 "fs: Call d_automount with the filesystems creds"
  causes a regression in the requester uid and gid passed to userspace
  during automount, as the current credentials during automount are
  those of root and not the user who requested the mount.

  Fix: Use current->real_cred instead of current->cred for getting the
  requester's uid and gid.

  Regression Potential: Minimal. current->cred and current->real_cred
  are the same except when credentials are overridden, thus
  current->real_cred contains the same credentials that autofs had been
  using prior to the change which overrides the credentials during
  automount.

  ---

  Hello,

  I have run into a bug relating autofs's parameter substitution (e.g.
  UID, GID, etc) with kernel versions 4.4.0-38 and proposed 4.4.0-40.
  Kernel version 4.4.0-28 does things correctly but testing intermediate
  kernel versions is hard due to earlier bugs related with fs's.
  Incorrect parameter substitution makes CIFS mounting with variable
  credentials impossible.

  Wat was expected:
  $UID in autofs map are substituted by the uid of the user that starts the 
auto-mounting process.

  What actually happens:
  Root's uid (0) is substituted instead.

  This ill parameter substitution likely caused by recent fixes
  resolving permissions problems for nfs/cifs mounts and dfs referrals
  (#1626112 and #1612135). And possibly the fix 'fs: Call d_automount
  with the filesystems creds' but that is a wild guess.

  Furthermore; playing with the force_standard_program_map_env settings
  in autofs.conf and prefixing variables with 'AUTOFS_' does not solve
  anything.

  Yours kindly,

  Chris

   Additional info 

    lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  run1   3015 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=f2a2c5c4-2f41-482a-80b4-968a87131214
  InstallationDate: Installed on 2016-09-19 (10 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig:
   enp0s8no wireless extensions.

   enp0s3no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic root=/dev/sda1 
ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-40-generic N/A
   linux-backports-modules-4.4.0-40-generic  N/A
   linux-firmware1.157.3
  RfKill:

  Tags:  xenial
  Uname: Linux 4.4.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629204/+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 1604396] Re: Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

2016-10-06 Thread Torsten Harenberg
Sorry, the second half of my post was from the NFS server (running
16.04) where the file system is local.

This here is a a 14.04 NFS *CLIENT*

[10:26] harenber@whep-web:~ $ ls /common/home/
aquota.user  ernis  hamacher   lehmann  riegel   tepel
arwa errenstharenber   lenz roggel   thartmann
becksfaustenharenberg  link sahu tsang
bergenth Finanzen   hartbrich  lisa sandhoff ugrin
bocprod  fischerhirsch lost+found   sannyumesh
boerner  fleischm   ilcmaettig  schick   volkmer
christinaflick  israelimoeller  scholz   wagner
cmwagner fp jaekel mvogel   schuelerpweiss
dcs  fstrothjemneumann  schuhwensing
debusgetsimple  kathrinofir schulz   wwwhome
dreesggilleskerstenpartimag seemayarr
duda glitza kind   pataraia sekretariat  yildirim
duelsen  goetze kuechler   physik2  springer zeitnitz
elkhalii grollius   lang   pro_ttbar_s  sweber
elli haeusling  lapitckii  puellen  tcorneli
[10:26] harenber@whep-web:~ $ uname -a
Linux whep-web 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
[10:26] harenber@whep-web:~ $ klist
Ticket cache: FILE:/tmp/krb5cc_1548_UcLLWT
Default principal: haren...@pleiades.uni-wuppertal.de

Valid starting   Expires  Service principal
10/06/2016 10:26:31  10/07/2016 10:26:31  
krbtgt/pleiades.uni-wuppertal...@pleiades.uni-wuppertal.de
[10:26] harenber@whep-web:~ $ mount | grep nfs
whep-nfs.pleiades.uni-wuppertal.de:/home on /common/home type nfs4 
(rw,sec=krb5i,soft,addr=132.195.125.8,clientaddr=132.195.124.14)
[10:27] harenber@whep-web:~ $ 

So 14.04 client: works, 16.04 client does not work, neither with 4.4.0
nor with 4.4.23 kernel.

Best regards,

  Torsten

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

Title:
  Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Since apt-upgrading my Ubuntu 16.04 PC to kernel 4.4.0-31 I can't cd
  into NFS4 subvolumes any more:

  zierke@rzpc100$ uname -a
  Linux rzpc100 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  zierke@rzpc100$ kinit
  Password for zie...@informatik.uni-hamburg.de:
  zierke@rzpc100$ cd /informatik2
  zierke@rzpc100$ cd rz
  -bash: cd: /informatik2/rz: Operation not permitted

  When I reboot my PC with the previous kernel 4.4.0-28 this works fine.

  This problem has also been mentioned in
  
https://www.kubuntuforums.net/showthread.php?70499-Latest-16-04-bug-NFS-problem-no-access-unless-I-use-root-first-strange
  https://ubuntuforums.org/showthread.php?t=2331137

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604396/+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 1604396] Re: Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

2016-10-06 Thread Torsten Harenberg
Hi,

I cannot verify that the new upstream kernel fixes that.

Also suffering from not being able to log into an NFS4/Kerberoized
directory with 16.04 anymore while the same works fine on 14.04. idmapd
are configured identically.

Ubuntu 16.04 (with new upstream kernel)


Could not chdir to home directory /common/home/harenber: Permission denied
groups: cannot find name for group ID 50094
-bash: /common/home/harenber/.bash_profile: Permission denied
harenber@bene:/$ mount | grep nfs
whep-nfs.pleiades.uni-wuppertal.de:/home on /common/home type nfs4 
(rw,relatime,vers=4.0,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5i,clientaddr=132.195.104.97,local_lock=none,addr=132.195.125.8)
harenber@bene:/$ cd /common
harenber@bene:/common$ ls -l
total 4
drwxr-xr-x 88 root users 4096 Sep 30 13:08 home
harenber@bene:/common$ cd home
-bash: cd: home: Permission denied
harenber@bene:/common$ klist
Ticket cache: KEYRING:persistent:1548:krb_ccache_JGqN6o8
Default principal: haren...@pleiades.uni-wuppertal.de

Valid starting   Expires  Service principal
06.10.2016 10:08:11  07.10.2016 10:08:11  
krbtgt/pleiades.uni-wuppertal...@pleiades.uni-wuppertal.de
harenber@bene:/common$ kinit -f
Password for haren...@pleiades.uni-wuppertal.de: 
harenber@bene:/common$ klist
Ticket cache: KEYRING:persistent:1548:krb_ccache_JGqN6o8
Default principal: haren...@pleiades.uni-wuppertal.de

Valid starting   Expires  Service principal
06.10.2016 10:09:10  07.10.2016 10:09:07  
krbtgt/pleiades.uni-wuppertal...@pleiades.uni-wuppertal.de
harenber@bene:/common$ ls -l 
ls: cannot access 'home': Permission denied
total 0
d? ? ? ? ?? home
harenber@bene:/common$ uname -a
Linux bene.physik.uni-wuppertal.de 4.4.23-040423-generic #201609300709 SMP Fri 
Sep 30 11:11:23 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
harenber@bene:/common$ 

whereas on 14.04:

[10:10] harenber@whep-nfs:~ $ klist
Ticket cache: FILE:/tmp/krb5cc_1548_S3S8IP
Default principal: haren...@pleiades.uni-wuppertal.de

Valid starting   Expires  Service principal
10/06/2016 10:10:07  10/07/2016 10:10:07  
krbtgt/pleiades.uni-wuppertal...@pleiades.uni-wuppertal.de
[10:10] harenber@whep-nfs:~ $ cd /common
[10:10] harenber@whep-nfs:/common $ ls
home
[10:10] harenber@whep-nfs:/common $ cd home
[10:10] harenber@whep-nfs:/common/home $ uname -a
Linux whep-nfs 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
[10:10] harenber@whep-nfs:/common/home $ 

Best regards,

  Torsten

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

Title:
  Kernel 4.4.0-31 cd into NFS4 directory: Operation not permitted

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  Since apt-upgrading my Ubuntu 16.04 PC to kernel 4.4.0-31 I can't cd
  into NFS4 subvolumes any more:

  zierke@rzpc100$ uname -a
  Linux rzpc100 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  zierke@rzpc100$ kinit
  Password for zie...@informatik.uni-hamburg.de:
  zierke@rzpc100$ cd /informatik2
  zierke@rzpc100$ cd rz
  -bash: cd: /informatik2/rz: Operation not permitted

  When I reboot my PC with the previous kernel 4.4.0-28 this works fine.

  This problem has also been mentioned in
  
https://www.kubuntuforums.net/showthread.php?70499-Latest-16-04-bug-NFS-problem-no-access-unless-I-use-root-first-strange
  https://ubuntuforums.org/showthread.php?t=2331137

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604396/+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 1597573] Re: Network installer fails to detect network on AMD Overdrive (ARM64)

2016-07-28 Thread Torsten König
Not sure if my opinion on yakkety is sufficient, but the patch fixes the
problem on my end. Current build of mini.iso detects the network
interfaces just fine.

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

Title:
  Network installer fails to detect network on AMD Overdrive (ARM64)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  Kernel: 4.4.0-21.37 (xenial)

  Installer fails to detect the XGBE network interface on AMD Overdrive,
  making it impossible to proceed with the network installer.

  Checking the kernel udeb modules, we're missing amd-xgbe as part of
  nic-modules.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597573/+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 1557924] Re: Machine fails to resume from suspend

2016-05-03 Thread Torsten Bronger
How can one install Linux 4.4.5 on Xenial?  It is not on
  Or can I use
?

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

Title:
  Machine fails to resume from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My machine (HP zbook 14 G2, http://store.hp.com/us/en/pdp/business-
  solutions/hp-zbook-14-g2-mobile-workstation-%28energy-star%29) fails
  to resume from suspend since kernel version 4.4.0-12. Version 4.4.0-10
  still works fine (I don't know about *-11).

  Below are the last log messages before machine suspended:

  Mär 14 20:54:23 moebius wpa_supplicant[888]: p2p-dev-wlo1: 
CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
  Mär 14 20:54:23 moebius dbus[699]: [system] Rejected send message, 10 matched 
rules; type="method_return", sender=":1.92" (uid=0 pid=1533 
comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") i
  Mär 14 20:54:23 moebius NetworkManager[623]:  NetworkManager state is 
now ASLEEP
  Mär 14 20:54:23 moebius whoopsie[649]: [20:54:23] Cannot reach: 
https://daisy.ubuntu.com
  Mär 14 20:54:23 moebius wpa_supplicant[888]: nl80211: deinit 
ifname=p2p-dev-wlo1 disabled_11b_rates=0
  Mär 14 20:54:23 moebius NetworkManager[623]:  Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Mär 14 20:54:23 moebius dbus[699]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
  Mär 14 20:54:23 moebius systemd[1]: Reached target Sleep.
  Mär 14 20:54:23 moebius systemd[1]: Starting Suspend...
  Mär 14 20:54:23 moebius systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Mär 14 20:54:23 moebius dbus[699]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
  Mär 14 20:54:23 moebius systemd[1]: Started Network Manager Script Dispatcher 
Service.
  Mär 14 20:54:23 moebius nm-dispatcher[1910]: Dispatching action 'down' for 
wlo1
  Mär 14 20:54:23 moebius wpa_supplicant[888]: nl80211: deinit ifname=wlo1 
disabled_11b_rates=0
  Mär 14 20:54:25 moebius bluetoothd[655]: Endpoint unregistered: sender=:1.56 
path=/MediaEndpoint/A2DPSource
  Mär 14 20:54:25 moebius bluetoothd[655]: Endpoint unregistered: sender=:1.56 
path=/MediaEndpoint/A2DPSink
  Mär 14 20:54:27 moebius org.gnome.zeitgeist.Engine[1243]: ** 
(zeitgeist-datahub:1958): WARNING **: zeitgeist-datahub.vala:229: Unable to get 
name "org.gnome.zeitgeist.datahub" on the bus!
  Mär 14 20:54:27 moebius gnome-session[1359]: ** (zeitgeist-datahub:1936): 
WARNING **: kde-recent-document-provider.vala:174: Couldn't find actor for 
'okular'.
  Mär 14 20:54:33 moebius systemd-sleep[1908]: Selected interface 'wlo1'
  Mär 14 20:54:33 moebius systemd-sleep[1908]: 'SUSPEND' command timed out.
  Mär 14 20:54:33 moebius systemd-sleep[1912]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Mär 14 20:54:33 moebius systemd-sleep[1908]: Suspending system...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-12-generic 4.4.0-12.28
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johnny 1401 F pulseaudio
   /dev/snd/controlC1:  johnny 1401 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar 16 08:27:16 2016
  HibernationDevice: RESUME=UUID=d987a311-b37d-44cf-9888-57b93b40cf51
  InstallationDate: Installed on 2016-03-14 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Hewlett-Packard HP ZBook 14 G2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-12-generic.efi.signed 
root=UUID=2b4e0fd5-152d-4456-8fce-fa2e8b77cebb ro quiet splash net.ifnames=0 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-12-generic N/A
   linux-backports-modules-4.4.0-12-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.13
  dmi.board.name: 2216
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.58
  dmi.chassis.asset.tag: 5CG54335T5
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.13:bd01/18/2016:svnHewlett-Packard:pnHPZBook14G2:pvrA3008C510003:rvnHewlett-Packard:rn2216:rvrKBCVersion96.58:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 14 G2
  dmi.product.version: A3008C510003
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about 

[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21

2016-04-26 Thread Torsten Gilles
Pedro, thank you for the hint, I'll try if that works as a workaround for me 
:-). I though the module build would disable secure boot since a dialog for a 
password for disabling pops up.
But it remains the question to me what changed from kernel-4.4.0-18 to 4.4.0-21 
that somehow broke the wl module loading process. Maybe it's that disabling 
that does not work anymore and if you disable security boot in BIOS you come 
around this?

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - wifi works normally.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1572659/+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 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21

2016-04-26 Thread Torsten Gilles
The same issue exists when using the broadcom-sta-dkms package instead of 
bcmwl-kernel-source on kernel 4.4.0-21 (also as with bcmwl-kernel-source this 
packages works on kernel-4.4.0-18): 
The loading of the module fails with modprobe: ERROR: could not insert 'wl': 
Required key not available. The reason seems to be because of insufficient 
privileges for some underlying action.

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - wifi works normally.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1572659/+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 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21

2016-04-22 Thread Torsten Gilles
I tried the new 16.04 release ISO and the problem exists for me (DELL
XPS 13) also which makes it unusable for me for now. Choosing an older
daily build before 20.4 where the 4.4.0-18 kernel is still used works
fine.

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - wifi works normally.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1572659/+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 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21

2016-04-21 Thread Torsten Gilles
I notice exactly the same problems with kernel 4.4.0-21 and bcmwl.

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - wifi works normally.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1572659/+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 900384] Re: usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which are not available in any package

2016-03-24 Thread Torsten
found this on usbip.sourceforge.net:

Download

For Linux, the source code of usbip was merged into the staging tree,
and finally has been moved to the mainline since Linux-3.17. Development
is ongoing in the kernel community, not here. Linux distributions will
provide binary packages of usbip. Just for historical records, the
project page keeps old download files of the Linux version. Do not use
them.

However, in newest kernel it don't work (4.4.0-12 / lubuntu 16.04) even if i 
can find:
./lib/modules/4.4.0-12-generic/kernel/drivers/usb/usbip
./lib/modules/4.4.0-12-generic/kernel/drivers/usb/usbip/usbip-host.ko
./lib/modules/4.4.0-12-generic/kernel/drivers/usb/usbip/usbip-core.ko

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

Title:
  usbipd requires usbip_common_mod.ko and usbip.ko kernel modules, which
  are not available in any package

Status in linux package in Ubuntu:
  Fix Released
Status in usbip package in Ubuntu:
  Fix Released

Bug description:
  I'm on Kubuntu oneiric (11.10), using usbip 0.1.7-3 and kernel linux-
  image-3.0.0-13-generic.

  I'm trying to set up USB/IP to share a USB-only printer/scanner over
  the LAN. However, whenever I try to start the demon, it gives the
  error message that the usbip_common_mod.ko and usbip.ko kernel modules
  are required:

  root@curie:~# usbipd -D
  usbip err: stub_driver.c:  33 (open_sysfs_stub_driver) usbip_common_mod.ko 
and usbip.ko must be loaded
  ** ERROR **: driver open failed
  Trace/breakpoint trap

  The package description of usbip says:
  " USB/IP requires kernel support which is included in Linux
   kernels 2.6.28 or newer."

  Unfortunately, I can't find a package that provides those kernel
  module.

  I have also installed the usbip-source package, but
  (1) its /usr/src/modules/usbip/src/README file says:
  "For newer kernels ( >=2.6.28 ), try linux-staging code!"
  and (2) trying to build it with m-a also fails:

  # Build the module
  cd src && /usr/bin/make KSOURCE=/usr/src/linux 
HCD_HEADER=/usr/src/modules/usbip/src/headers/hcd.h KBUILD_VERBOSE=0
  make[2]: Entering directory `/usr/src/modules/usbip/src'
  make -C /usr/src/linux LANG=C KBUILD_VERBOSE=0  M=`pwd` modules
  make[3]: Entering directory `/usr/src/linux-headers-3.0.0-13-generic'
    CC [M]  /usr/src/modules/usbip/src/stub_dev.o
  /usr/src/modules/usbip/src/stub_dev.c: In function ‘stub_probe’:
  /usr/src/modules/usbip/src/stub_dev.c:392:42: error: ‘struct device’ has no 
member named ‘bus_id’
  make[4]: *** [/usr/src/modules/usbip/src/stub_dev.o] Error 1
  make[3]: *** [_module_/usr/src/modules/usbip/src] Error 2
  make[3]: Leaving directory `/usr/src/linux-headers-3.0.0-13-generic'
  make[2]: *** [default] Error 2
  make[2]: Leaving directory `/usr/src/modules/usbip/src'
  make[1]: *** [binary-modules] Error 2
  make[1]: Leaving directory `/usr/src/modules/usbip'
  make: *** [kdist_build] Error 2
  BUILD FAILED!
  See /var/cache/modass/usbip.buildlog.3.0.0-13-generic.1323105464 for details.
  Build failed. Press Return to continue...

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

2016-01-30 Thread Torsten Franz
** Changed in: linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  error

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

2016-01-30 Thread Torsten Franz
Please add more information to your bugreport. Thank you!

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

Title:
  error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1539979/+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 1492146] Re: igb Detected Tx Unit Hang

2015-09-08 Thread Torsten Gollnick
Same problem here with 
 Dell Inc. PowerEdge R730/0H21J3, BIOS 1.2.10 03/09/2015
and
Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)

Renders the machine useless.

Kernel 3.16.0-43 is OK

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

Title:
  igb Detected Tx Unit Hang

Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  Hello!

  Have a:

  >lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  Codename:   trusty

  with kenel 3.16.0-46-generic.

  Today i do dist-upgrade and kernel was upgraded to 3.16.0-48-generic
  version.

  After reboot i've got this:

  Sep  4 09:02:52 mail kernel: [  310.616324] igb :02:00.0 em1: Reset 
adapter Sep  4 09:02:52 mail kernel: [  310.831157] igb :02:00.1 em2: Reset 
adapter Sep  4 09:02:56 mail kernel: [  315.154686] igb :02:00.0 em1: igb: 
em1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX Sep  4 09:02:56 mail 
kernel: [  315.202651] igb :02:00.1 em2: igb: em2 NIC Link is Up 1000 Mbps 
Full Duplex, Flow Control: RX Sep  4 09:03:02 mail kernel: [  321.608099] igb 
:02:00.0: Detected Tx Unit Hang
  Sep  4 09:03:02 mail kernel: [  321.608099]   Tx Queue <6>
  Sep  4 09:03:02 mail kernel: [  321.608099]   TDH  <23>
  Sep  4 09:03:02 mail kernel: [  321.608099]   TDT  <23>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_use  <25>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_clean<23>
  Sep  4 09:03:02 mail kernel: [  321.608099] buffer_info[next_to_clean]
  Sep  4 09:03:02 mail kernel: [  321.608099]   time_stamp   <112af>
  Sep  4 09:03:02 mail kernel: [  321.608099]   next_to_watch

  Sep  4 09:03:02 mail kernel: [  321.608099]   jiffies  <11531>
  Sep  4 09:03:02 mail kernel: [  321.608099]   desc.status  <120200>
  Sep  4 09:03:04 mail kernel: [  323.607349] igb :02:00.0: Detected Tx 
Unit Hang
  Sep  4 09:03:04 mail kernel: [  323.607349]   Tx Queue <6>
  Sep  4 09:03:04 mail kernel: [  323.607349]   TDH  <23>
  Sep  4 09:03:04 mail kernel: [  323.607349]   TDT  <23>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_use  <25>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_clean<23>
  Sep  4 09:03:04 mail kernel: [  323.607349] buffer_info[next_to_clean]
  Sep  4 09:03:04 mail kernel: [  323.607349]   time_stamp   <112af>
  Sep  4 09:03:04 mail kernel: [  323.607349]   next_to_watch

  Sep  4 09:03:04 mail kernel: [  323.607349]   jiffies  <11725>
  Sep  4 09:03:04 mail kernel: [  323.607349]   desc.status  <120200>
  Sep  4 09:03:06 mail kernel: [  325.606602] igb :02:00.0: Detected Tx 
Unit Hang
  Sep  4 09:03:06 mail kernel: [  325.606602]   Tx Queue <6>
  Sep  4 09:03:06 mail kernel: [  325.606602]   TDH  <23>
  Sep  4 09:03:06 mail kernel: [  325.606602]   TDT  <23>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_use  <25>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_clean<23>
  Sep  4 09:03:06 mail kernel: [  325.606602] buffer_info[next_to_clean]
  Sep  4 09:03:06 mail kernel: [  325.606602]   time_stamp   <112af>
  Sep  4 09:03:06 mail kernel: [  325.606602]   next_to_watch

  Sep  4 09:03:06 mail kernel: [  325.606602]   jiffies  <11919>
  Sep  4 09:03:06 mail kernel: [  325.606602]   desc.status  <120200>

  All network connections droped after that. System still unusable.

  Only after boot with old linux-image-3.16.0-46-generic my production
  mail server can work.

  It's a critical bug for me, can anybody help me?

  ethtool -i em1
  driver: igb
  version: 5.2.13-k
  firmware-version: 1.61, 0x8cd5, 1.949.0
  bus-info: :02:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1492146/+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 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2015-09-08 Thread Torsten Römer
With the freezes I had it was not possible to "revive" from, all I could
do is long-press the power button.

So maybe the freezes you encounter are another issue, maybe this bug:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1384512

It is about KDE but sounds similar and might be related to the video
driver, so maybe Unity suffers from the same issue?

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

Title:
  Daily, random hard freeze/lock up during idle since 13.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since about the final version of 13.10 (using it since Beta 2), my
  Lenovo L420 which was running stable until then randomly hard
  freezes/locks up about once a day while idling.

  It never happens while I am using the PC, only when I am away. It
  sometimes runs through a whole night, and sometimes it freezes when I
  leave it idle for just an hour or so. Once it froze while the screen
  was not blank yet, same situation.

  I have tried to disable power management in KDE and run without
  external screen and external harddisks, just on battery with nothing
  connected, then it also happens.

  The screen is usually blank, there is no reaction to either mouse or
  keyboard, switching to a console not possible, connection through VNC
  or SSD not possible. I need to hard-shutdown by long-pressing the
  power button.

  There is nothing in dmesg or syslog, it just ends and continues with
  the restarts. No kernel panics or something like that.

  Any advice on how to trace down the issue or similar experience?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dode   2185 F pulseaudio
  Date: Wed Nov 27 14:06:00 2013
  HibernationDevice: RESUME=UUID=3f651677-4186-4f48-b0f8-c20b56dbb2e8
  InstallationDate: Installed on 2013-09-08 (80 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902.2)
  MachineType: LENOVO 78545HG
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5aa9fd7d-cb84-4ab2-90f3-514b79fa541d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   linux-backports-modules-3.11.0-13-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+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 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

2015-09-05 Thread Torsten Harenberg
Sorry for self-replying.. after another hour, I applied #15, deleted the
pairing, used blueman to re-pair and now it works :). Finally :) Thanks
everyone for the nice thread.

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

To manage notifications about this bug go to:
https://bugs.launchpad.net/blueman/+bug/1283003/+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 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

2015-09-05 Thread Torsten Harenberg
After reading a lot of bug reports and trying several solutions which
helped other people (for example #149), but I am still stuck getting
Ubuntu 14.04 to work with Bose Soundlink Headphones. Host is a Lenovo
Carbon X1 Carbon 3rd gen - having an Intel 7265 card.

I am able to pair, and also can set the A2DP profile for this device.
After a couple of seconds however, the device disconnects and kernel log
has a couple of

[   50.181581] Bluetooth: hci0 SCO packet for unknown connection handle
0

lines. Afterwards, the device rejects re-connection, only re-pairing
will bring it back to a connected state.

The device works fine with other hosts like several Android phones and
tablets, a MacBookAir running OS X, but I also got it running with the
same laptop (!) running Ubuntu 15.04. However, for my work I need to
stick with 14.04 to be compatible with colleagues.

Suspected a bug in the firmware, but I couldn't found newer firmware
than the one already used:

[  760.815953] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
[  760.895882] Bluetooth: hci0: Intel Bluetooth firmware patch completed and 
activated

Tried several kernel versions, no luck either.

Anyone with a idea how to fix the "SCO packet for unknown connection
handle" problem?

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

To manage notifications about this bug go to:
https://bugs.launchpad.net/blueman/+bug/1283003/+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 1480637] Re: touchpad not working. MODEL - Asus X550LC

2015-08-02 Thread Torsten Franz
*** This bug is a duplicate of bug 1314198 ***
https://bugs.launchpad.net/bugs/1314198

** This bug has been marked a duplicate of bug 1314198
   [Asus X550LC] Touchpad not Recognized in ubuntu 14.04

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

Title:
  touchpad not working. MODEL - Asus X550LC

Status in linux-lts-utopic package in Ubuntu:
  New

Bug description:
  hardware info $ dmidecode output  http://pastebin.com/UzQyczGe

  
  The touchpad is not working. I have used ubuntu 12.04 , 13.10, 14.10 , and 
many environments too. It never works. 
  I feel  there is some bios issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.16.0-45-generic 3.16.0-45.60~14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Aug  2 10:41:36 2015
  InstallationDate: Installed on 2015-07-11 (21 days ago)
  InstallationMedia: It
  SourcePackage: linux-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1480637/+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 1430696] Re: Bluetooth audio instability: Bluetooth: hci0 SCO packet for unknown connection handle

2015-05-30 Thread Torsten Harenberg
See the same under 15.04 running

Linux harenber-ThinkPad-X1-Carbon-3rd 3.19.0-18-generic #18-Ubuntu SMP
Tue May 19 18:31:35 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Bluetooth audio instability: Bluetooth: hci0 SCO packet for unknown
  connection handle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  (I'm creating a new bug as instructed at
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/898347/comments/29)

  I havea Nokia BH-216 bluetooth headset. Generally it works well, but
  randomly (after 5-15 minutes of use) it gets disconnected.

  The kernel log output looks like this:

  [ 3272.270382] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [ 3272.270383] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [ 3272.270384] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [ 3272.270384] Bluetooth: hci0 SCO packet for unknown connection handle 48
  [ 3272.270385] Bluetooth: hci0 SCO packet for unknown connection handle 0
  [ 3272.270386] Bluetooth: hci0 SCO packet for unknown connection handle 0

  With quick googling this seems to be happening to other people with
  other hardware and distributions so i suppose this is a BT audio bug
  in kernel. Bug #898347 is related.

  Tested on up to date Ubuntu 14.10 x86_64.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vranki 2421 F pulseaudio
   /dev/snd/controlC1:  vranki 2421 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Wed Mar 11 11:22:19 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=71d76087-3fdf-4f57-a0f4-0b128be4d386
  InstallationDate: Installed on 2015-02-12 (26 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: LENOVO 20C600LLMS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=e114ca99-f1c7-450f-a4a5-553075d92b7c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/14/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: J9ET96WW (2.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20C600LLMS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrJ9ET96WW(2.16):bd10/14/2014:svnLENOVO:pn20C600LLMS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C600LLMS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20C600LLMS
  dmi.product.version: ThinkPad Edge E540
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1430696/+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 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2014-12-09 Thread Torsten Römer
Following your experience, I have disabled CPU Power Management and
PCI Express Power Management in the BIOS of my Lenovo L420.

I did not have a single freeze in one month now (before about once a
week), so I suppose this solved my freezing issues as well. The fact
that the freezes occurred only during idle (power management kicking
in?) seems to confirm this.

BIOS or kernel bugs?

Glad I have a stable system again - Thanks for sharing!

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

Title:
  Daily, random hard freeze/lock up during idle since 13.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since about the final version of 13.10 (using it since Beta 2), my
  Lenovo L420 which was running stable until then randomly hard
  freezes/locks up about once a day while idling.

  It never happens while I am using the PC, only when I am away. It
  sometimes runs through a whole night, and sometimes it freezes when I
  leave it idle for just an hour or so. Once it froze while the screen
  was not blank yet, same situation.

  I have tried to disable power management in KDE and run without
  external screen and external harddisks, just on battery with nothing
  connected, then it also happens.

  The screen is usually blank, there is no reaction to either mouse or
  keyboard, switching to a console not possible, connection through VNC
  or SSD not possible. I need to hard-shutdown by long-pressing the
  power button.

  There is nothing in dmesg or syslog, it just ends and continues with
  the restarts. No kernel panics or something like that.

  Any advice on how to trace down the issue or similar experience?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dode   2185 F pulseaudio
  Date: Wed Nov 27 14:06:00 2013
  HibernationDevice: RESUME=UUID=3f651677-4186-4f48-b0f8-c20b56dbb2e8
  InstallationDate: Installed on 2013-09-08 (80 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.2)
  MachineType: LENOVO 78545HG
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5aa9fd7d-cb84-4ab2-90f3-514b79fa541d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   linux-backports-modules-3.11.0-13-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+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 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2014-09-21 Thread Torsten Römer
I am not aware of any workaround and I wonder if our freezes are related
or if we have individual hardware issues. But I am pretty sure I did not
have theses issues before 13.10 on the same hardware.

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

Title:
  Daily, random hard freeze/lock up during idle since 13.10

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Since about the final version of 13.10 (using it since Beta 2), my
  Lenovo L420 which was running stable until then randomly hard
  freezes/locks up about once a day while idling.

  It never happens while I am using the PC, only when I am away. It
  sometimes runs through a whole night, and sometimes it freezes when I
  leave it idle for just an hour or so. Once it froze while the screen
  was not blank yet, same situation.

  I have tried to disable power management in KDE and run without
  external screen and external harddisks, just on battery with nothing
  connected, then it also happens.

  The screen is usually blank, there is no reaction to either mouse or
  keyboard, switching to a console not possible, connection through VNC
  or SSD not possible. I need to hard-shutdown by long-pressing the
  power button.

  There is nothing in dmesg or syslog, it just ends and continues with
  the restarts. No kernel panics or something like that.

  Any advice on how to trace down the issue or similar experience?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dode   2185 F pulseaudio
  Date: Wed Nov 27 14:06:00 2013
  HibernationDevice: RESUME=UUID=3f651677-4186-4f48-b0f8-c20b56dbb2e8
  InstallationDate: Installed on 2013-09-08 (80 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.2)
  MachineType: LENOVO 78545HG
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5aa9fd7d-cb84-4ab2-90f3-514b79fa541d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   linux-backports-modules-3.11.0-13-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+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 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2014-07-20 Thread Torsten Römer
Unfortunately I still have this problem, by the time with kubuntu 14.04.
Often when the system is idling for some hours, it eventually freezes.

I again let Memtest86 running, it did 9 passes in more than 13 hours
without error, so it is probably not a memory issue.

There is usually an external screen connected via VGA, but I have seen
the freeze also when running on battery with no external devices
connected, that time while I was working. However, connecting an
external screen prevents the system from suspending - for a reasoning
that I can't follow - so this is why the system may idle for hours and
eventually freeze, while normally it would suspend after half an hour.

The syslog does not show anything besides a line of garbage at the point
where it crashed:

ul 20 18:40:01 linus CRON[5077]: (www-data) CMD ([ -x 
/usr/share/awstats/tools/update.sh ]  /usr/share/awstats/tools/update.sh)
Jul 20 18:40:01 linus CRON[5076]: (smmsp) CMD (test -x /etc/init.d/sendmail  
/usr/share/sendmail/sendmail cron-msp)
Jul 20 18:40:01 linus sm-msp-queue[5093]: My unqualified host name (linus) 
unknown; sleeping for retry
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Jul
 20 20:26:39 linus rsyslogd: [origin software=rsyslogd swVersion=7.4.4 
x-pid=969 x-info=http://www.rsyslog.com;] start
Jul 20 20:26:39 linus rsyslogd: rsyslogd's groupid changed to 103
Jul 20 20:26:39 linus rsyslogd: rsyslogd's userid changed to 101
Jul 20 20:26:39 linus kernel: [0.00] Initializing cgroup subsys cpuset
Jul 20 20:26:39 linus kernel: [0.00] Initializing cgroup subsys cpu
Jul 20 20:26:39 linus kernel: [0.00] Initializing cgroup subsys cpuacct
Jul 20 20:26:39 linus kernel: [0.00] Linux version 3.13.0-32-generic 
(buildd@kissel) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #57-Ubuntu SMP 
Tue Jul 15 03:51:08 UTC 2014 (Ubuntu 3.13.0-32.57-generic 3.13.11.4)

Any advice on what I could do to find out what the reason for the
freezes is?

Cheers,
Torsten

** Changed in: linux (Ubuntu)
   Status: Invalid = New

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

Title:
  Daily, random hard freeze/lock up during idle since 13.10

Status in “linux” package in Ubuntu:
  New

Bug description:
  Since about the final version of 13.10 (using it since Beta 2), my
  Lenovo L420 which was running stable until then randomly hard
  freezes/locks up about once a day while idling.

  It never happens while I am using the PC, only when I am away. It
  sometimes runs through a whole night, and sometimes it freezes when I
  leave it idle for just an hour or so. Once it froze while the screen
  was not blank yet, same situation.

  I have tried to disable power management in KDE and run without
  external screen and external harddisks, just on battery with nothing
  connected, then it also happens.

  The screen is usually blank, there is no reaction to either mouse or
  keyboard, switching to a console not possible, connection through VNC
  or SSD not possible. I need to hard-shutdown by long-pressing the
  power button.

  There is nothing in dmesg or syslog, it just ends and continues with
  the restarts. No kernel panics or something like that.

  Any advice on how to trace down the issue or similar experience?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dode   2185 F pulseaudio
  Date: Wed Nov 27 14:06:00 2013
  HibernationDevice: RESUME=UUID=3f651677-4186-4f48-b0f8-c20b56dbb2e8
  InstallationDate: Installed on 2013-09-08 (80 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.2)
  MachineType: LENOVO 78545HG
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5aa9fd7d-cb84-4ab2-90f3-514b79fa541d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   linux-backports-modules-3.11.0-13-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2013-12-08 Thread Torsten Römer
Thank you Joseph.

After running about one week without the bad memory module and another
week with a new 2nd 4GB module without any freeze I think we can assume
this bug is invalid :-)

Torsten

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

Title:
  Daily, random hard freeze/lock up during idle since 13.10

Status in “linux” package in Ubuntu:
  Invalid

Bug description:
  Since about the final version of 13.10 (using it since Beta 2), my
  Lenovo L420 which was running stable until then randomly hard
  freezes/locks up about once a day while idling.

  It never happens while I am using the PC, only when I am away. It
  sometimes runs through a whole night, and sometimes it freezes when I
  leave it idle for just an hour or so. Once it froze while the screen
  was not blank yet, same situation.

  I have tried to disable power management in KDE and run without
  external screen and external harddisks, just on battery with nothing
  connected, then it also happens.

  The screen is usually blank, there is no reaction to either mouse or
  keyboard, switching to a console not possible, connection through VNC
  or SSD not possible. I need to hard-shutdown by long-pressing the
  power button.

  There is nothing in dmesg or syslog, it just ends and continues with
  the restarts. No kernel panics or something like that.

  Any advice on how to trace down the issue or similar experience?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dode   2185 F pulseaudio
  Date: Wed Nov 27 14:06:00 2013
  HibernationDevice: RESUME=UUID=3f651677-4186-4f48-b0f8-c20b56dbb2e8
  InstallationDate: Installed on 2013-09-08 (80 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.2)
  MachineType: LENOVO 78545HG
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5aa9fd7d-cb84-4ab2-90f3-514b79fa541d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   linux-backports-modules-3.11.0-13-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+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 1255531] [NEW] Daily, random hard freeze/lock up during idle since 13.10

2013-11-27 Thread Torsten Römer
Public bug reported:

Since about the final version of 13.10 (using it since Beta 2), my
Lenovo L420 which was running stable until then randomly hard
freezes/locks up about once a day while idling.

It never happens while I am using the PC, only when I am away. It
sometimes runs through a whole night, and sometimes it freezes when I
leave it idle for just an hour or so. Once it froze while the screen was
not blank yet, same situation.

I have tried to disable power management in KDE and run without external
screen and external harddisks, just on battery with nothing connected,
then it also happens.

The screen is usually blank, there is no reaction to either mouse or
keyboard, switching to a console not possible, connection through VNC or
SSD not possible. I need to hard-shutdown by long-pressing the power
button.

There is nothing in dmesg or syslog, it just ends and continues with the
restarts. No kernel panics or something like that.

Any advice on how to trace down the issue or similar experience?

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-13-generic 3.11.0-13.20
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dode   2185 F pulseaudio
Date: Wed Nov 27 14:06:00 2013
HibernationDevice: RESUME=UUID=3f651677-4186-4f48-b0f8-c20b56dbb2e8
InstallationDate: Installed on 2013-09-08 (80 days ago)
InstallationMedia: Kubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.2)
MachineType: LENOVO 78545HG
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5aa9fd7d-cb84-4ab2-90f3-514b79fa541d ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-13-generic N/A
 linux-backports-modules-3.11.0-13-generic  N/A
 linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/12/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GET44WW (1.21 )
dmi.board.name: 78545HG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 78545HG
dmi.product.version: ThinkPad L420
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug saucy

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

Title:
  Daily, random hard freeze/lock up during idle since 13.10

Status in “linux” package in Ubuntu:
  New

Bug description:
  Since about the final version of 13.10 (using it since Beta 2), my
  Lenovo L420 which was running stable until then randomly hard
  freezes/locks up about once a day while idling.

  It never happens while I am using the PC, only when I am away. It
  sometimes runs through a whole night, and sometimes it freezes when I
  leave it idle for just an hour or so. Once it froze while the screen
  was not blank yet, same situation.

  I have tried to disable power management in KDE and run without
  external screen and external harddisks, just on battery with nothing
  connected, then it also happens.

  The screen is usually blank, there is no reaction to either mouse or
  keyboard, switching to a console not possible, connection through VNC
  or SSD not possible. I need to hard-shutdown by long-pressing the
  power button.

  There is nothing in dmesg or syslog, it just ends and continues with
  the restarts. No kernel panics or something like that.

  Any advice on how to trace down the issue or similar experience?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dode   2185 F pulseaudio
  Date: Wed Nov 27 14:06:00 2013
  HibernationDevice: RESUME=UUID=3f651677-4186-4f48-b0f8-c20b56dbb2e8
  InstallationDate: Installed on 2013-09-08 (80 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.2)
  MachineType: LENOVO 78545HG
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5aa9fd7d-cb84-4ab2-90f3-514b79fa541d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   linux-backports-modules-3.11.0-13-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10

2013-11-27 Thread Torsten Römer
I have done a memory test as suggested in
https://help.ubuntu.com/community/DebuggingSystemCrash - sorry for not
reading it earlier.

Errors were found at four addresses in the memory area of the second 4
GB module. After removing it and running with only the first 4 GB, no
more errors were found.

I will test for a week without the second module and report back if the
freeze is solved with that.

For anyone with a similar problem:
It seems really worth running the memory test! With 8 GB it took just about 50 
min for one complete pass.
Just press (right) shift on startup to get the GRUB boot menu, and start the 
memory test from there.

Cheers,
Torsten

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

Title:
  Daily, random hard freeze/lock up during idle since 13.10

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Since about the final version of 13.10 (using it since Beta 2), my
  Lenovo L420 which was running stable until then randomly hard
  freezes/locks up about once a day while idling.

  It never happens while I am using the PC, only when I am away. It
  sometimes runs through a whole night, and sometimes it freezes when I
  leave it idle for just an hour or so. Once it froze while the screen
  was not blank yet, same situation.

  I have tried to disable power management in KDE and run without
  external screen and external harddisks, just on battery with nothing
  connected, then it also happens.

  The screen is usually blank, there is no reaction to either mouse or
  keyboard, switching to a console not possible, connection through VNC
  or SSD not possible. I need to hard-shutdown by long-pressing the
  power button.

  There is nothing in dmesg or syslog, it just ends and continues with
  the restarts. No kernel panics or something like that.

  Any advice on how to trace down the issue or similar experience?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-13-generic 3.11.0-13.20
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dode   2185 F pulseaudio
  Date: Wed Nov 27 14:06:00 2013
  HibernationDevice: RESUME=UUID=3f651677-4186-4f48-b0f8-c20b56dbb2e8
  InstallationDate: Installed on 2013-09-08 (80 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.2)
  MachineType: LENOVO 78545HG
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic 
root=UUID=5aa9fd7d-cb84-4ab2-90f3-514b79fa541d ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-13-generic N/A
   linux-backports-modules-3.11.0-13-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GET44WW (1.21 )
  dmi.board.name: 78545HG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 78545HG
  dmi.product.version: ThinkPad L420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+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 1239339] [NEW] [SAMSUNG ELECTRONICS CO., LTD. R40/R41] suspend/resume failure

2013-10-13 Thread Torsten Knodt
Public bug reported:

I guess this happended due to a hardware fault, but I am not sure.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic i686
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Sun Oct 13 12:19:16 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=5bc6d9ef-412d-4f14-a3fa-abe21a7f6b51
InstallationDate: Installed on 2013-06-11 (124 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 
(20130213)
InterpreterPath: /usr/bin/python3.3
MachineType: SAMSUNG ELECTRONICS CO., LTD. R40/R41
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b72c50bf-027b-45bc-bb2d-d316766f33c1 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not 
responding.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic  N/A
 linux-firmware 1.116
SourcePackage: linux
StagingDrivers: zram
Title: [SAMSUNG ELECTRONICS CO., LTD. R40/R41] suspend/resume failure
UpgradeStatus: Upgraded to saucy on 2013-10-11 (2 days ago)
UserGroups:
 
dmi.bios.date: 10/02/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 06YA
dmi.board.name: R40/R41
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr06YA:bd10/02/2006:svnSAMSUNGELECTRONICSCO.,LTD.:pnR40/R41:pvr06YA:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR40/R41:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A:
dmi.product.name: R40/R41
dmi.product.version: 06YA
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: apport-kerneloops i386 resume saucy staging suspend

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

Title:
  [SAMSUNG ELECTRONICS CO., LTD. R40/R41] suspend/resume failure

Status in “linux” package in Ubuntu:
  New

Bug description:
  I guess this happended due to a hardware fault, but I am not sure.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  Date: Sun Oct 13 12:19:16 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=5bc6d9ef-412d-4f14-a3fa-abe21a7f6b51
  InstallationDate: Installed on 2013-06-11 (124 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 
(20130213)
  InterpreterPath: /usr/bin/python3.3
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R40/R41
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=b72c50bf-027b-45bc-bb2d-d316766f33c1 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-12-generic N/A
   linux-backports-modules-3.11.0-12-generic  N/A
   linux-firmware 1.116
  SourcePackage: linux
  StagingDrivers: zram
  Title: [SAMSUNG ELECTRONICS CO., LTD. R40/R41] suspend/resume failure
  UpgradeStatus: Upgraded to saucy on 2013-10-11 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 10/02/2006
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 06YA
  dmi.board.name: R40/R41
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr06YA:bd10/02/2006:svnSAMSUNGELECTRONICSCO.,LTD.:pnR40/R41:pvr06YA:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR40/R41:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A:
  dmi.product.name: R40/R41
  dmi.product.version: 06YA
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Kernel-packages] [Bug 1094066] Re: [Samsung NP350V5C-S07DE] Keyboard blocked after having used volume keys

2013-09-08 Thread Torsten Bronger
I'm sorry but I can't do that I'm afraid.  The level of suffering is not
high enough for me to perform this procedure.  Besides, it seems to work
only with Windows installed, which is not the case in my case.  Or does
it also work from inside a VirtualBox?

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

Title:
  [Samsung NP350V5C-S07DE] Keyboard blocked after having used volume
  keys

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  After having pressed Fn + Louder on my Samsung NP350V5C-S07, the
  volume is increased to max, and the keyboard is completely
  unresponsive from thereon.  The system works normal, only the keyboard
  is blocked.  I have to restart the machine.

  Support page?:
  http://www.samsung.com/uk/support/model/NP350V5C-S07DE-downloads

  ---
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bronger1392 F lxpanel
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=68fbe940-90cd-457f-b3dd-ada0921a5891
  InstallationDate: Installed on 2012-12-27 (0 days ago)
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic 
root=UUID=8b7bdae8-1a26-4fcb-97ad-602fabd4e95d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-21-generic N/A
   linux-backports-modules-3.5.0-21-generic  N/A
   linux-firmware1.95
  StagingDrivers: rts5139
  Tags:  quantal staging
  Uname: Linux 3.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 06/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04AAL
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP350V5C-S07DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04AAL:bd06/30/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04AAL.022.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S07DE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
  dmi.product.version: P04AAL.022.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094066/+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 1094066] Re: Keyboard blocked after having used volume keys

2013-08-10 Thread Torsten Bronger
The model name on the sticker is NP350V5C-907DE.


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

Title:
  Keyboard blocked after having used volume keys

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After having pressed Fn + Louder on my Samsung NP350V5C-S07, the volume is 
increased to max, and the keyboard is completely unresponsive from thereon.  
The system works normal, only the keyboard is blocked.  I have to restart the 
machine.
  --- 
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bronger1392 F lxpanel
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=68fbe940-90cd-457f-b3dd-ada0921a5891
  InstallationDate: Installed on 2012-12-27 (0 days ago)
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic 
root=UUID=8b7bdae8-1a26-4fcb-97ad-602fabd4e95d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-21-generic N/A
   linux-backports-modules-3.5.0-21-generic  N/A
   linux-firmware1.95
  StagingDrivers: rts5139
  Tags:  quantal staging
  Uname: Linux 3.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 06/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04AAL
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP350V5C-S07DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04AAL:bd06/30/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04AAL.022.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S07DE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
  dmi.product.version: P04AAL.022.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094066/+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 1094066] Re: [Samsung NP350V5C-907DE] Keyboard blocked after having used volume keys

2013-08-10 Thread Torsten Bronger
http://www.samsung.com/de/consumer/notebooks-displays/notebook-
computers/serie-3/NP350V5C-S07DE-gallery

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

Title:
  [Samsung NP350V5C-907DE] Keyboard blocked after having used volume
  keys

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After having pressed Fn + Louder on my Samsung NP350V5C-S07, the
  volume is increased to max, and the keyboard is completely
  unresponsive from thereon.  The system works normal, only the keyboard
  is blocked.  I have to restart the machine.

  Support page?:
  http://www.samsung.com/uk/support/model/NP350V5C-S07DE-downloads

  ---
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bronger1392 F lxpanel
  CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
  DistroRelease: Ubuntu 12.10
  HibernationDevice: RESUME=UUID=68fbe940-90cd-457f-b3dd-ada0921a5891
  InstallationDate: Installed on 2012-12-27 (0 days ago)
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release amd64 
(20121017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB:
   0 radeondrmfb
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic 
root=UUID=8b7bdae8-1a26-4fcb-97ad-602fabd4e95d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-21-generic N/A
   linux-backports-modules-3.5.0-21-generic  N/A
   linux-firmware1.95
  StagingDrivers: rts5139
  Tags:  quantal staging
  Uname: Linux 3.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 06/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04AAL
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP350V5C-S07DE
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04AAL:bd06/30/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX:pvrP04AAL.022.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S07DE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 
350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX
  dmi.product.version: P04AAL.022.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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