date:20191017

[Kernel-packages] [Bug 1848439] Re: generic/562 from ubuntu_xfstests_btrfs failed on D

2019-10-17 Thread Po-Hsu Lin

** Patch added: "btrfs-generic-562-output.diff"
   
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1848439/+attachment/5297778/+files/btrfs-generic-562-output.diff

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

Title:
  generic/562 from ubuntu_xfstests_btrfs failed on D

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  Issue found on node amd64 node "kili"

   generic/562_check_dmesg: something found in dmesg (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.dmesg)
   - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad)
   --- tests/generic/562.out  2019-10-16 10:51:13.164700997 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad
  2019-10-16 12:35:45.694630398 +
   @@ -1,5 +1,102404 @@
QA output created by 562
   +XFS_IOC_CLONE: No space left on device
File foo data after cloning and remount:
   -000 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 
   +000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
   +*
   +0004096 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/562.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad'
  to see the entire diff)

  Syslog with kernel traces:
   BTRFS info (device sdb2): checking UUID tree
   [ cut here ]
   BTRFS: Transaction aborted (error -28)
   WARNING: CPU: 52 PID: 53560 at fs/btrfs/ioctl.c:3350 
clone_finish_inode_update+0x102/0x130 [btrfs]
   Modules linked in: dm_thin_pool dm_persistent_data dm_bio_prison dm_snapshot 
dm_bufio btrfs zstd_compress dm_flakey dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm ioatdma irqbypass mei_me mei ipmi_si crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel joydev input_leds ipmi_devintf intel_cstate 
ipmi_msghandler intel_rapl_perf mac_hid acpi_pad acpi_power_meter sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid aesni_intel 
mgag200 aes_x86_64 crypto_simd i2c_algo_bit cryptd ttm glue_helper 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ixgbe ahci 
lpc_ich xfrm_algo i2c_i801 libahci dca mdio wmi [last unloaded: scsi_debug]
   CPU: 52 PID: 53560 Comm: xfs_io Tainted: G  I   5.0.0-31-generic 
#33-Ubuntu
   Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS 
SE5C610.86B.01.01.1008.031920151331 03/19/2015
   RIP: 0010:clone_finish_inode_update+0x102/0x130 [btrfs]
   Code: ff ff ff 49 8b 45 50 f0 48 0f ba a8 40 ce 00 00 02 72 19 83 fb fb 0f 
84 86 3a 05 00 89 de 48 c7 c7 48 08 ad c0 e8 90 18 03 e4 <0f> 0b 4c 89 ef 89 d9 
ba 16 0d 00 00 48 c7 c6 90 30 ac c0 e8 2e d9
   RSP: 0018:bcf6e4017b60 EFLAGS: 00010286
   RAX:  RBX: ffe4 RCX: 0006
   RDX: 0007 RSI: 0082 RDI: 9ec45fa16440
   RBP: bcf6e4017b90 R08: 0001 R09: 3827
   R10: 0004 R11:  R12: 9ec455442a60
   R13: 9ec4533992d8 R14: 0a40 R15: 9ec1cb06c800
   FS:  7f34c46f3800() GS:9ec45fa0() knlGS:
   CS:  0010 DS:  ES:  CR0: 80050033
   CR2: 7f34c46f1ef8 CR3: 000d124f6003 CR4: 001606e0
   Call Trace:
btrfs_clone+0xa18/0x1080 [btrfs]
btrfs_clone_files+0xfe/0x160 [btrfs]
btrfs_remap_file_range+0x321/0x410 [btrfs]
do_clone_file_range+0x12b/0x260
vfs_clone_file_range+0x3a/0xb0
ioctl_file_clone+0x93/0xc0
do_vfs_ioctl+0x495/0x640
? putname+0x47/0x50
ksys_ioctl+0x67/0x90
__x64_sys_ioctl+0x1a/0x20
do_syscall_64+0x5a/0x110
entry_SYSCALL_64_after_hwframe+0x44/0xa9
   RIP: 0033:0x7f34c4a5e417
   Code: 00 00 90 48 8b 05 79 0a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff 
ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 
01 c3 48 8b 0d 49 0a 0d 00 f7 d8 64 89 01 48
   RSP: 002b:7fff6c7b9e98 EFLAGS: 0246 ORIG_RAX: 0010
   RAX: ffda RBX: 0012 RCX: 7f34c4a5e417
   RDX: 0012 RSI: 40049409 RDI: 0008
   RBP:  R08: 7fff6c7de0a0 R0

[Kernel-packages] [Bug 1848439] Status changed to Confirmed

2019-10-17 Thread Ubuntu Kernel Bot

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Disco)
   Status: New => 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/1848439

Title:
  generic/562 from ubuntu_xfstests_btrfs failed on D

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  Issue found on node amd64 node "kili"

   generic/562_check_dmesg: something found in dmesg (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.dmesg)
   - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad)
   --- tests/generic/562.out  2019-10-16 10:51:13.164700997 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad
  2019-10-16 12:35:45.694630398 +
   @@ -1,5 +1,102404 @@
QA output created by 562
   +XFS_IOC_CLONE: No space left on device
File foo data after cloning and remount:
   -000 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 
   +000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
   +*
   +0004096 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/562.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad'
  to see the entire diff)

  Syslog with kernel traces:
   BTRFS info (device sdb2): checking UUID tree
   [ cut here ]
   BTRFS: Transaction aborted (error -28)
   WARNING: CPU: 52 PID: 53560 at fs/btrfs/ioctl.c:3350 
clone_finish_inode_update+0x102/0x130 [btrfs]
   Modules linked in: dm_thin_pool dm_persistent_data dm_bio_prison dm_snapshot 
dm_bufio btrfs zstd_compress dm_flakey dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm ioatdma irqbypass mei_me mei ipmi_si crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel joydev input_leds ipmi_devintf intel_cstate 
ipmi_msghandler intel_rapl_perf mac_hid acpi_pad acpi_power_meter sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid aesni_intel 
mgag200 aes_x86_64 crypto_simd i2c_algo_bit cryptd ttm glue_helper 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ixgbe ahci 
lpc_ich xfrm_algo i2c_i801 libahci dca mdio wmi [last unloaded: scsi_debug]
   CPU: 52 PID: 53560 Comm: xfs_io Tainted: G  I   5.0.0-31-generic 
#33-Ubuntu
   Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS 
SE5C610.86B.01.01.1008.031920151331 03/19/2015
   RIP: 0010:clone_finish_inode_update+0x102/0x130 [btrfs]
   Code: ff ff ff 49 8b 45 50 f0 48 0f ba a8 40 ce 00 00 02 72 19 83 fb fb 0f 
84 86 3a 05 00 89 de 48 c7 c7 48 08 ad c0 e8 90 18 03 e4 <0f> 0b 4c 89 ef 89 d9 
ba 16 0d 00 00 48 c7 c6 90 30 ac c0 e8 2e d9
   RSP: 0018:bcf6e4017b60 EFLAGS: 00010286
   RAX:  RBX: ffe4 RCX: 0006
   RDX: 0007 RSI: 0082 RDI: 9ec45fa16440
   RBP: bcf6e4017b90 R08: 0001 R09: 3827
   R10: 0004 R11:  R12: 9ec455442a60
   R13: 9ec4533992d8 R14: 0a40 R15: 9ec1cb06c800
   FS:  7f34c46f3800() GS:9ec45fa0() knlGS:
   CS:  0010 DS:  ES:  CR0: 80050033
   CR2: 7f34c46f1ef8 CR3: 000d124f6003 CR4: 001606e0
   Call Trace:
btrfs_clone+0xa18/0x1080 [btrfs]
btrfs_clone_files+0xfe/0x160 [btrfs]
btrfs_remap_file_range+0x321/0x410 [btrfs]
do_clone_file_range+0x12b/0x260
vfs_clone_file_range+0x3a/0xb0
ioctl_file_clone+0x93/0xc0
do_vfs_ioctl+0x495/0x640
? putname+0x47/0x50
ksys_ioctl+0x67/0x90
__x64_sys_ioctl+0x1a/0x20
do_syscall_64+0x5a/0x110
entry_SYSCALL_64_after_hwframe+0x44/0xa9
   RIP: 0033:0x7f34c4a5e417
   Code: 00 00 90 48 8b 05 79 0a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff 
ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 
01 c3 48 8b 0d 49 0a 0d 00 f7 d8 64 89 01 48
   RSP: 002b:7fff6c7b9e98 EFLAGS: 0246 ORIG_RAX: 0010
   RAX: ffda RBX: 0012 RCX: 7f34c4a5e417
   RDX: 0012 RSI: 40049409 RDI: 0008
   RBP:  R08: 7fff6c7de0a0 R09: 000

[Kernel-packages] [Bug 1848333] Re: wifi problem delays boot in live mode

2019-10-17 Thread sudodus

attached photo showing the waiting

** Attachment added: "lubuntu-waiting-90s.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333/+attachment/5297779/+files/lubuntu-waiting-90s.jpg

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

Title:
  wifi problem delays boot in live mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
  days ago (Oct 6).

  Now there is a delay of 1 min 30 sec during booting, and I think there
  is something wrong with the recognition of the wifi hardware or maybe
  matching of driver and hardware. It happens in 'this' computer, a
  middle-aged Toshiba laptop with a generation 3 Intel i5 cpu and also
  in a Dell Latitude E7240 with a generation 4 Intel i5 cpu and I guess
  another wifi chip.

  In both cases both ethernet and wifi works. I see available wifi
  routers and can connect (when I have the password).

  I tested also with the Xubuntu eoan iso file, and the same delay
  happened there.

  I think the drivers are OK, but something in the logic for recognition
  of them might be bad.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lubuntu2316 F pulseaudio
  CasperVersion: 1.426
  CurrentDesktop: LXQt
  Date: Wed Oct 16 11:36:22 2019
  LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191015)
  MachineType: TOSHIBA SATELLITE PRO C850-19W
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed persistent ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.10
  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.10:bd09/24/2012:svnTOSHIBA:pnSATELLITEPROC850-19W:pvrPSCBXE-00C00VN5:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-19W
  dmi.product.sku: PSCBXE
  dmi.product.version: PSCBXE-00C00VN5
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333/+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 1848439] Re: generic/562 from ubuntu_xfstests_btrfs failed on D

2019-10-17 Thread Po-Hsu Lin

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

Title:
  generic/562 from ubuntu_xfstests_btrfs failed on D

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

Bug description:
  Issue found on node amd64 node "kili"

   generic/562_check_dmesg: something found in dmesg (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.dmesg)
   - output mismatch (see 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad)
   --- tests/generic/562.out  2019-10-16 10:51:13.164700997 +
   +++ 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad
  2019-10-16 12:35:45.694630398 +
   @@ -1,5 +1,102404 @@
QA output created by 562
   +XFS_IOC_CLONE: No space left on device
File foo data after cloning and remount:
   -000 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 c7 
   +000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
   +*
   +0004096 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5 e5
   ...
   (Run 'diff -u 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/tests/generic/562.out
 
/home/ubuntu/autotest/client/tmp/ubuntu_xfstests_btrfs/src/xfstests-bld/xfstests-dev/results//generic/562.out.bad'
  to see the entire diff)

  Syslog with kernel traces:
   BTRFS info (device sdb2): checking UUID tree
   [ cut here ]
   BTRFS: Transaction aborted (error -28)
   WARNING: CPU: 52 PID: 53560 at fs/btrfs/ioctl.c:3350 
clone_finish_inode_update+0x102/0x130 [btrfs]
   Modules linked in: dm_thin_pool dm_persistent_data dm_bio_prison dm_snapshot 
dm_bufio btrfs zstd_compress dm_flakey dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm ioatdma irqbypass mei_me mei ipmi_si crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel joydev input_leds ipmi_devintf intel_cstate 
ipmi_msghandler intel_rapl_perf mac_hid acpi_pad acpi_power_meter sch_fq_codel 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid aesni_intel 
mgag200 aes_x86_64 crypto_simd i2c_algo_bit cryptd ttm glue_helper 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm ixgbe ahci 
lpc_ich xfrm_algo i2c_i801 libahci dca mdio wmi [last unloaded: scsi_debug]
   CPU: 52 PID: 53560 Comm: xfs_io Tainted: G  I   5.0.0-31-generic 
#33-Ubuntu
   Hardware name: Intel Corporation S2600WTT/S2600WTT, BIOS 
SE5C610.86B.01.01.1008.031920151331 03/19/2015
   RIP: 0010:clone_finish_inode_update+0x102/0x130 [btrfs]
   Code: ff ff ff 49 8b 45 50 f0 48 0f ba a8 40 ce 00 00 02 72 19 83 fb fb 0f 
84 86 3a 05 00 89 de 48 c7 c7 48 08 ad c0 e8 90 18 03 e4 <0f> 0b 4c 89 ef 89 d9 
ba 16 0d 00 00 48 c7 c6 90 30 ac c0 e8 2e d9
   RSP: 0018:bcf6e4017b60 EFLAGS: 00010286
   RAX:  RBX: ffe4 RCX: 0006
   RDX: 0007 RSI: 0082 RDI: 9ec45fa16440
   RBP: bcf6e4017b90 R08: 0001 R09: 3827
   R10: 0004 R11:  R12: 9ec455442a60
   R13: 9ec4533992d8 R14: 0a40 R15: 9ec1cb06c800
   FS:  7f34c46f3800() GS:9ec45fa0() knlGS:
   CS:  0010 DS:  ES:  CR0: 80050033
   CR2: 7f34c46f1ef8 CR3: 000d124f6003 CR4: 001606e0
   Call Trace:
btrfs_clone+0xa18/0x1080 [btrfs]
btrfs_clone_files+0xfe/0x160 [btrfs]
btrfs_remap_file_range+0x321/0x410 [btrfs]
do_clone_file_range+0x12b/0x260
vfs_clone_file_range+0x3a/0xb0
ioctl_file_clone+0x93/0xc0
do_vfs_ioctl+0x495/0x640
? putname+0x47/0x50
ksys_ioctl+0x67/0x90
__x64_sys_ioctl+0x1a/0x20
do_syscall_64+0x5a/0x110
entry_SYSCALL_64_after_hwframe+0x44/0xa9
   RIP: 0033:0x7f34c4a5e417
   Code: 00 00 90 48 8b 05 79 0a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff 
ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 
01 c3 48 8b 0d 49 0a 0d 00 f7 d8 64 89 01 48
   RSP: 002b:7fff6c7b9e98 EFLAGS: 0246 ORIG_RAX: 0010
   RAX: ffda RBX: 0012 RCX: 7f34c4a5e417
   RDX: 0012 RSI: 40049409 RDI: 0008
   RBP:  R08: 7fff6c7de0a0 R09: 7fff6c7de080
   R10: 002cb364 R11: 0246 R12: 
   R13:  R14:  R15: 5592f0c19328
   ---[ end

[Kernel-packages] [Bug 1848445] [NEW] Kernel needs a special workaround argument to boot

2019-10-17 Thread Ilgaz

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Description: Ubuntu 19.10
Release: 19.10

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

3) What you expected to happen

Boot

4) What happened instead

Freezes (see below for workaround), no visible sign of interaction
possible. Caps lock "led" doesn't work indicating keyboard isn't
working. Just a white cursor (non blinking) on screen, CPU doesn't seem
to do anything since fan stops after a while.

This is more likely a Linux "bug". Unless you pass acpi_osi= argument to
Linux kernel, it won't boot, appear and behave frozen with a (non
blinking) cursor on top left. There is no further information given to
user further complicating things.

Previously on 4.x kernels, system would boot using acpi=off argument
creating more problems on this particular laptop model (HP Pavilion X360
13 inch).

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
 /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
 /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 10:02:44 2019
HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
InstallationDate: Installed on 2019-10-13 (3 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-18-generic N/A
 linux-backports-modules-5.3.0-18-generic  N/A
 linux-firmware1.183
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
dmi.bios.date: 06/21/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.41
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2341
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 07.0A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion 13 x360 PC
dmi.product.sku: L0B89EA#AB8
dmi.product.version: 097712405F0410180
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug eoan

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

Title:
  Kernel needs a special workaround argument to boot

Status in linux package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description: Ubuntu 19.10
  Release: 19.10

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  3) What you expected to happen

  Boot

  4) What happened instead

  Freezes (see below for workaround), no visible sign of interaction
  possible. Caps lock "led" doesn't work indicating keyboard isn't
  working. Just a white cursor (non blinking) on screen, CPU doesn't
  seem to do anything since fan stops after a while.

  This is more likely a Linux "bug". Unless you pass acpi_osi= argument
  to Linux kernel, it won't boot, appear and behave frozen with a (non
  blinking) cursor on top left. There is no further information given to
  user further complicating things.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems on this particular laptop model (HP Pavilion
  X360 13 inch).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.

[Kernel-packages] [Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work

2019-10-17 Thread Kai-Heng Feng

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the 
regression.

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

Title:
  Lightdm is just a black screen when booting kernel 5.3 on an i5-6500,
  but kernels 5.0/5.2 work

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xorg freeze at boot on Intel Corporation HD Graphics 530 with 
linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan 
Ermine (development branch).
  If i boot with linux-image-5.0.0-31-generic the Xorg works well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Oct 14 11:15:23 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring
   Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G2 SFF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro 
resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.42
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.36
  dmi.chassis.asset.tag: CZC64082W1
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: X3J10ET#ABZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring
   Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP EliteDesk 800 G2 SFF
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic 
root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro nomodeset 
resume=U

[Kernel-packages] [Bug 1847892] Re: large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

2019-10-17 Thread Kai-Heng Feng

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the 
regression.

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

Title:
  large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Probably relevant:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795116

  Card is an RTL8723BE.

  On 16.04 with the HWE stack, after 1795116 was fixed performance was a
  stable 75-80Mb/s.

  Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
  Fri 26-Jul-19 12:28
  sent 459,277,171 bytes  received 35 bytes  9,278,327.39 bytes/sec

  Linux 4.15.0-55-generic #60~16.04.2-Ubuntu SMP Thu Jul 4 09:03:09 UTC 2019 
x86_64
  Sat 27-Jul-19 01:23
  sent 459,277,171 bytes  received 35 bytes  10,320,836.09 bytes/sec

  On 18.04, performance was still a stable 75-80Mb/s.

  After updating to 19.10, performance is typically ~50Mb/s, or about a
  37% regression.

  $ iwconfig wlan0
  wlan0 IEEE 802.11  ESSID:"**"  
Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB  
 
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=59/70  Signal level=-51 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:315   Missed beacon:0

  $ ./wifibench.sh 
  Linux 5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
  Sat 12-Oct-19 20:30
  sent 459,277,171 bytes  received 35 bytes  5,566,996.44 bytes/sec

  $ iwconfig wlan0 
  wlan0 IEEE 802.11  ESSID:"**"  
Mode:Managed  Frequency:2.442 GHz  Access Point: 4C:60:DE:FB:A8:AB  
 
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=68/70  Signal level=-42 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:315   Missed beacon:0

  So no corrupted packets or etc during that transfer.

  $ ifconfig wlan0
  wlan0: flags=4163  mtu 1500
  inet 192.168.1.33  netmask 255.255.255.0  broadcast 192.168.1.255
  ether dc:85:de:e4:17:a3  txqueuelen 1000  (Ethernet)
  RX packets 56608204  bytes 79066485957 (79.0 GB)
  RX errors 0  dropped 0  overruns 0  frame 0
  TX packets 21634510  bytes 8726094217 (8.7 GB)
  TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

  No issues of any kind in the week that it's been up. Just terrible
  performance.

  I'm painfully aware of all the module's parameters etc, and have tried
  them all, with no change in the results outside of typical wifi
  variance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847892/+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 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo

2019-10-17 Thread Kai-Heng Feng

Would it be possible for you to do a kernel bisection?

First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/

Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you found)
$ git bisect bad $(the bad version found)
$ make localmodconfig
$ make -j`nproc` deb-pkg
Install the newly built kernel, then reboot with it.
If the issue still happens,
$ git bisect bad
Otherwise,
$ git bisect good
Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the 
regression.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, when I turn off the computer, it hangs on the logo. I can
  not turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem
  with kernel 5.0, 5.3.

  There is no such problem with the 4.15 kernel. It happens that after
  90 seconds it turns off. And with a new core, he writes that he will
  turn off after 90 seconds, but he will not turn off.

  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC

  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  CurrentDesktop: XFCE
  Дата: Четверг 5 09:44:35 2019 Дата
  установки: установлено в 2019-08 -09 (26 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 
(20190210)
  ProcEnviron:
   LANGUAGE = ru_UA: ru
   PATH = (пользовательский, нет пользователя)
   XDG_RUNTIME_ DIR = 
   LANG = ru_UA.UTF -8
   SHELL = / bin / bash
  SourcePackage: gvfs
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка)
  ---
  Тип проблемы: ошибка
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  AudioDevicesInUse:
   КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID
   / dev / snd / controlC0: макс. 1055 F  pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Установлен 2019-08-09 (37 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 
(20190210)
  IwConfig:
   enp0s25 без беспроводных расширений.

   enp7s4 нет беспроводных расширений.

   нет никаких беспроводных расширений.
  Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower
  Пакет: Linux (не установлен)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень 
= UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1
  ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18
  RelatedPackageV ersions:
   linux- restricted- modules- 4.15.0- 62-родовое N / A
   linux- backports- modules- 4.15.0 - 62-типовой N / A
   linux-прошивка 1.173.9
  RfKill:

  Теги: bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: нет журнала обновления (возможно, новая установка)
  Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 26.10.2015
  dmi. bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board. asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis. asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: 
svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: 
rn2820h: rvr: cvnHewlett- Packard: ct6: cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dvtwelet dv00 от компании HP
  :

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842865/+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 1848445] Status changed to Confirmed

2019-10-17 Thread Ubuntu Kernel Bot

This change was made by a bot.

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

Title:
  Kernel needs a special workaround argument to boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description: Ubuntu 19.10
  Release: 19.10

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  3) What you expected to happen

  Boot

  4) What happened instead

  Freezes (see below for workaround), no visible sign of interaction
  possible. Caps lock "led" doesn't work indicating keyboard isn't
  working. Just a white cursor (non blinking) on screen, CPU doesn't
  seem to do anything since fan stops after a while.

  This is more likely a Linux "bug". Unless you pass acpi_osi= argument
  to Linux kernel, it won't boot, appear and behave frozen with a (non
  blinking) cursor on top left. There is no further information given to
  user further complicating things.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems on this particular laptop model (HP Pavilion
  X360 13 inch).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/+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 1848445] Re: Kernel needs a special workaround argument to boot

2019-10-17 Thread Kai-Heng Feng

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc3/

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

Title:
  Kernel needs a special workaround argument to boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description: Ubuntu 19.10
  Release: 19.10

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  3) What you expected to happen

  Boot

  4) What happened instead

  Freezes (see below for workaround), no visible sign of interaction
  possible. Caps lock "led" doesn't work indicating keyboard isn't
  working. Just a white cursor (non blinking) on screen, CPU doesn't
  seem to do anything since fan stops after a while.

  This is more likely a Linux "bug". Unless you pass acpi_osi= argument
  to Linux kernel, it won't boot, appear and behave frozen with a (non
  blinking) cursor on top left. There is no further information given to
  user further complicating things.

  Previously on 4.x kernels, system would boot using acpi=off argument
  creating more problems on this particular laptop model (HP Pavilion
  X360 13 inch).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ilgaz 21270 F pulseaudio
   /dev/snd/controlC1:  ilgaz 21270 F pulseaudio
   /dev/snd/pcmC1D0p:   ilgaz 21270 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 10:02:44 2019
  HibernationDevice: RESUME=UUID=f34af719-8757-473b-848b-7db85d6fefae
  InstallationDate: Installed on 2019-10-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Hewlett-Packard HP Pavilion 13 x360 PC
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=f6787f82-d072-410e-8058-2b7f14d012b9 ro verbose pci=biosirq acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (0 days ago)
  dmi.bios.date: 06/21/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.41
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2341
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.0A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.41:bd06/21/2018:svnHewlett-Packard:pnHPPavilion13x360PC:pvr097712405F0410180:rvnHewlett-Packard:rn2341:rvr07.0A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 13 x360 PC
  dmi.product.sku: L0B89EA#AB8
  dmi.product.version: 097712405F0410180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848445/+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 1847838] Re: [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

2019-10-17 Thread quanxian

47f50d610765 xhci: Fix USB 3.1 capability detection on early xHCI 1.1
spec based hosts

here is the fix in 5.4-rc3, please backport it into 19.04 if possible.

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

Title:
  [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  PLY02:~ # for i in `lspci | grep -i usb | awk '{print $1}'`;do lspci -s $i 
-v;done;
  00:14.0 USB controller: Intel Corporation C620 Series Chipset Family USB 3.0 
xHCI Controller (rev 03) (prog-if 30 [XHCI])
  Subsystem: Intel Corporation C620 Series Chipset Family USB 3.0 xHCI 
Controller
  Flags: bus master, medium devsel, latency 0, IRQ 34, NUMA node 0
  Memory at 3830 (64-bit, non-prefetchable) [size=64K]
  Capabilities: [70] Power Management version 2
  Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
  Kernel driver in use: xhci_hcd

  PLY02:~ # lsusb -t'
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M --- 
1M
  |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M  
-- 1M and should use driver uas instead of usb-storage.
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
  |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
  |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
  |__ Port 5: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M

  
  Target Kernel: TBD
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1847838/+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 1847838] Re: [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

2019-10-17 Thread quanxian

sorry it is 19.10. :)

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

Title:
  [Ubuntu 19.10-regression] USB3.1 test failed on CFL-1S8

Status in intel:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:

  PLY02:~ # for i in `lspci | grep -i usb | awk '{print $1}'`;do lspci -s $i 
-v;done;
  00:14.0 USB controller: Intel Corporation C620 Series Chipset Family USB 3.0 
xHCI Controller (rev 03) (prog-if 30 [XHCI])
  Subsystem: Intel Corporation C620 Series Chipset Family USB 3.0 xHCI 
Controller
  Flags: bus master, medium devsel, latency 0, IRQ 34, NUMA node 0
  Memory at 3830 (64-bit, non-prefetchable) [size=64K]
  Capabilities: [70] Power Management version 2
  Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
  Kernel driver in use: xhci_hcd

  PLY02:~ # lsusb -t'
  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M --- 
1M
  |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M  
-- 1M and should use driver uas instead of usb-storage.
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
  |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/5p, 480M
  |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
  |__ Port 5: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M

  
  Target Kernel: TBD
  Target Release: 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1847838/+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 1847948] Re: Improve NVMe guest performance on Bionic QEMU

2019-10-17 Thread Christian Ehrhardt 

Thanks Murilo, I need no test with the basic kernel yet.
But later when we really SRU this it will be good to do both a old and a HWE
kernel check.
Let me add that to the verification steps ...

** Description changed:

[Impact]

- * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO.
-But there can be platforms (like ppc64 spapr) that can and want to do
-exactly that.
+ * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO.
+ But there can be platforms (like ppc64 spapr) that can and want to do
+ exactly that.

- * Backport two patches from upstream (in since qemu 2.12 / Disco).
+ * Backport two patches from upstream (in since qemu 2.12 / Disco).

- * Due to that there is a tremendous speedup, especially useful with page
-size bigger than 4k. This avoids that being split into chunks and makes
-direct MMIO access possible for the guest.
+ * Due to that there is a tremendous speedup, especially useful with page
+ size bigger than 4k. This avoids that being split into chunks and makes
+ direct MMIO access possible for the guest.

[Test Case]

- * On ppc64 pass through an NVME device to the guest and run I/O
-benchmarks, see below for Details how to set that up.
-Note this needs the HWE kernel or another kernel fixup for [1].
+ * On ppc64 pass through an NVME device to the guest and run I/O
+ benchmarks, see below for Details how to set that up.
+ Note: this needs the HWE kernel or another kernel fixup for [1].
+Note: the test should also be done with the non-HWE kernel, the
+expectation there is that it would not show the perf benefits, but
+still work fine

[Regression Potential]

- * Changes:
-a) if the host driver allows mapping of MSI-X data the entire BAR is
- mapped. This is only done if the kernel reports that capability [1].
- This ensures that only on kernels able to do so qemu does expose the
- new behavior (safe against regression in that regard)
-b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local
- to just this HW and will not affect other HW.
+ * Changes:
+ a) if the host driver allows mapping of MSI-X data the entire BAR is
+ mapped. This is only done if the kernel reports that capability [1].
+ This ensures that only on kernels able to do so qemu does expose the
+ new behavior (safe against regression in that regard)
+ b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local
+ to just this HW and will not affect other HW.

-Generally the regressions that come to mind are slight changes in
-behavior (real HW vs the former emulation) that on some weird/old
-guests could cause trouble. But then it is limited to only PPC where
-only a small set of certified HW is really allowed.
+ Generally the regressions that come to mind are slight changes in
+ behavior (real HW vs the former emulation) that on some weird/old
+ guests could cause trouble. But then it is limited to only PPC where
+ only a small set of certified HW is really allowed.

-The mapping that might be added even on other platforms should not
-consume too much extra memory as long as it isn't used. Further since
-it depends on the kernel capability it isn't randomly issues on kernels
-where we expect it to fail.
+ The mapping that might be added even on other platforms should not
+ consume too much extra memory as long as it isn't used. Further since
+ it depends on the kernel capability it isn't randomly issues on kernels
+ where we expect it to fail.

-So while it is quite a change, it seems safe to me.
+ So while it is quite a change, it seems safe to me.

[Other Info]
-
- * I know, one could as well call that a "feature", but it really is a
-performance bug fix more than anything else. Also the SRU policy allows
-exploitation/toleration of new HW especially for LTS releases.
-Therefore I think this is fine as SRU.
+
+ * I know, one could as well call that a "feature", but it really is a
+ performance bug fix more than anything else. Also the SRU policy allows
+ exploitation/toleration of new HW especially for LTS releases.
+ Therefore I think this is fine as SRU.

1 2 >

1 - 100 of 183 matches

Mail list logo