date:20180912

This test can be run on Trusty / Xenial ARM64 now.
Thanks

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Fix Released

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Failed to build libhugetlbfs-2.20 from source on 4.4 / 3.13 Trusty
  ARM64

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  It will fail to build libhugetlbfs verison 2.20 for SRU regression-
  test on 3.13 ARM64

  It's ok on 4.10 / 4.4 ARM64, but not 4.4.0-88.111~14.04.1 and
  3.13.0-126.175 ARM64

  Looks like it's failing with:
  LD64 (hugelink_rw test) obj64/linkhuge_rw
  /usr/bin/ld: final link failed: File truncated

  This is not a regression. As this issue has been seen before.

  Complete make log:
  $ make
 VERSION
  version string: 2.20
 CC64 obj64/elflink.o
 AS64 obj64/sys-aarch64elf.o
 CC64 obj64/hugeutils.o
 CC64 obj64/version.o
 CC64 obj64/init.o
 CC64 obj64/morecore.o
 CC64 obj64/debug.o
 CC64 obj64/alloc.o
 CC64 obj64/shm.o
 CC64 obj64/kernel-features.o
 LD64 (shared) obj64/libhugetlbfs.so
 AR64 obj64/libhugetlbfs.a
 CC64 obj64/init_privutils.o
 LD64 (shared) obj64/libhugetlbfs_privutils.so
 CCHOST obj/init_privutils.o
 CCHOST obj/debug.o
 CCHOST obj/hugeutils.o
 CCHOST obj/kernel-features.o
 ARHOST obj/libhugetlbfs_privutils.a
 CC64 obj64/gethugepagesize.o
 CC64 obj64/testutils.o
 CC64 obj64/libtestutils.o
 LD64 (lib test) obj64/gethugepagesize
 CC64 obj64/test_root.o
 LD64 (lib test) obj64/test_root
 CC64 obj64/find_path.o
 LD64 (lib test) obj64/find_path
 CC64 obj64/unlinked_fd.o
 LD64 (lib test) obj64/unlinked_fd
 CC64 obj64/misalign.o
 LD64 (lib test) obj64/misalign
 CC64 obj64/readback.o
 LD64 (lib test) obj64/readback
 CC64 obj64/truncate.o
 LD64 (lib test) obj64/truncate
 CC64 obj64/shared.o
 LD64 (lib test) obj64/shared
 CC64 obj64/private.o
 LD64 (lib test) obj64/private
 CC64 obj64/fork-cow.o
 LD64 (lib test) obj64/fork-cow
 CC64 obj64/empty_mounts.o
 LD64 (lib test) obj64/empty_mounts
 CC64 obj64/large_mounts.o
 LD64 (lib test) obj64/large_mounts
 CC64 obj64/meminfo_nohuge.o
 LD64 (lib test) obj64/meminfo_nohuge
 CC64 obj64/ptrace-write-hugepage.o
 LD64 (lib test) obj64/ptrace-write-hugepage
 CC64 obj64/icache-hygiene.o
  icache-hygiene.c: In function ‘test_once’:
  icache-hygiene.c:158:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, 0);
 ^
  icache-hygiene.c:162:12: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
 ftruncate(fd, 0);
  ^
  icache-hygiene.c:171:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, hpage_size);
 ^
  icache-hygiene.c:177:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, 0);
 ^
 LD64 (lib test) obj64/icache-hygiene
 CC64 obj64/slbpacaflush.o
 LD64 (lib test) obj64/slbpacaflush
 CC64 obj64/chunk-overcommit.o
 LD64 (lib test) obj64/chunk-overcommit
 CC64 obj64/mprotect.o
 LD64 (lib test) obj64/mprotect
 CC64 obj64/alloc-instantiate-race.o
  alloc-instantiate-race.c: In function ‘thread_racer’:
  alloc-instantiate-race.c:114:6: warning: variable ‘rc’ set but not used 
[-Wunused-but-set-variable]
int rc;
^
 LD64 (lib test) obj64/alloc-instantiate-race
 CC64 obj64/mlock.o
 LD64 (lib test) obj64/mlock
 CC64 obj64/truncate_reserve_wraparound.o
 LD64 (lib test) obj64/truncate_reserve_wraparound
 CC64 obj64/truncate_sigbus_versus_oom.o
 LD64 (lib test) obj64/truncate_sigbus_versus_oom
 CC64 obj64/map_high_truncate_2.o
 LD64 (lib test) obj64/map_high_truncate_2
 CC64 obj64/truncate_above_4GB.o
 LD64 (lib test) obj64/truncate_above_4GB
 CC64 obj64/direct.o
 LD64 (lib test) obj64/direct
 CC64 obj64/misaligned_offset.o
 LD64 (lib test) obj64/misaligned_offset
 CC64 obj64/brk_near_huge.o
 LD64 (lib test) obj64/brk_near_huge
 CC64 obj64/task-size-overrun.o
 LD64 (lib test) obj64/task-size-overrun
 CC64 obj64/stack_grow_into_huge.o

[Kernel-packages] [Bug 1783140] Re: KVM live migration fails

2018-09-12 Thread  Christian Ehrhardt 

Prep complete:
- Regression tests from the PPA
- Tests of the bug being fixed on the PPA
- MP review
- SRU Template

Uploading for consideration by the SRU Team

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

Title:
  KVM live migration fails

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Triaged

Bug description:
  [Impact]

   * Backport fix from the 2.6.2 stable branch to the qemu 2.5 in Xenial

   * Newer guests might use virtio attributes that are clobbered on 
 migration with the old qemu code.

  [Test Case]

   * Setup two Xenial hosts on ppc64el

   * Create a guest that has a rather new kernel (>=4.14) I'd recommend 
 Bionic

   * Migrate that guest from Host1 to Host2

  [Regression Potential]

   * The modification could affect virtio handling in other cases in a non 
 expected way, but mostly related to migrations. So the expected 
 regression would be issues to migrate properly.
 I verified plenty of migrations in regression testing and we had
 this very code in the Yakkety release as we picked 2.6.1 stable release 
 back then. Due to that it is actually pretty well tested and should not 
 really regress anything out in the wild.

  [Other Info]
   
   * So far this only triggers on the confused endian marshalling on 
 ppc64el, but in theory a different case could trigger it on x86 just as 
 much.

  ---

  Environment:
  2 POWER8 with Ubuntu 16.04.4 LTS as KVM hypervisor.
  1 KVM guest with Ubuntu 18.04 LTS. Virtual disk for the guest is a qcow2 file 
on an NFS share, accessible from both hypervisors, so live migration is 
possible and works for all other guests (SLES, RHEL, Ubunutu 16.04),
  Live migratino of Ubuntu 18.04 guest fails on ppc, while the same test on an 
x86_64 environment suceeds.

  root@pkvm2:~# virsh migrate --persistent --live p8lnxtst4 
qemu+ssh://pkvm1/system
  error: internal error: early end of file from monitor, possible problem: 
2018-07-23T11:12:25.586385Z qemu-system-ppc64: VQ 0 size 0x100 Guest index 
0x38aa inconsistent with Host index 0xa980: delta 0x8f2a
  2018-07-23T11:12:25.586434Z qemu-system-ppc64: error while loading state for 
instance 0x0 of device 'pci@8002000:01.0/virtio-net'
  2018-07-23T11:12:25.587246Z qemu-system-ppc64: load of migration failed: 
Operation not permitted

  root@pkvm2:~# uname -a
  Linux pkvm2 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:51:21 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1783140/+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 1727290] Re: ubuntu_unionmount_overlayfs_suite failed on 4.15 Azure

This issue still exist
4.15.0-1023.24-azure
http://10.246.72.46/4.15.0-1023.24-azure/bionic-linux-azure-azure-4.15.0-Standard_A6-ubuntu_unionmount_overlayfs_suite/ubuntu_unionmount_overlayfs_suite/results/ubuntu_unionmount_overlayfs_suite.overlayfs/debug/ubuntu_unionmount_overlayfs_suite.overlayfs.DEBUG.html

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Confirmed

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

Title:
  ubuntu_unionmount_overlayfs_suite failed on 4.15 Azure

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 4.15.0-1022.23 azure
  This test has failed on all the azure instances this cycle, it looks like it 
has stopped at the "rename-empty-dir" test:

TEST rename-file.py:110: Rename file over a dir
./run --rename /mnt/a/foo108/ /mnt/a/empty108/ -E ENOTDIR
./run --rename /mnt/a/foo108/ /mnt/a/dir108/ -E ENOTDIR
./run --open-file /mnt/a/foo108/ -r -R :xxx:yyy:zzz -E ENOTDIR
TEST rename-file.py:121: Rename file over parent dir
./run --rename /mnt/a/foo109/ /mnt/a -E ENOTDIR
./run --open-file /mnt/a/foo109/ -r -R :xxx:yyy:zzz -E ENOTDIR
***
*** ./run --ov --ts=0 rename-empty-dir
***
TEST rename-empty-dir.py:10: Rename empty dir and rename back
./run --rename /mnt/a/empty100 /mnt/a/no_dir100 -E EXDEV
/mnt/a/empty100: Expected error (Invalid cross-device link) was not 
produced

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1727290/+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 1791806] Re: alsa does not detech headphone output on Clevo P651RS laptop

2018-09-12 Thread Lehel Gyuro

Hi

The behavior was always present, in 3.xx and 4.xx line.

Tested with 4.19.0-041900rc3-generic_4.19.0-041900rc3.201809120832,
result is the same, all outputs are correctly detected with the
exception of the headphone:

[   22.873713] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[   22.900370] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
[   22.900372] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
[   22.900373] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   22.900374] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   22.900375] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
[   22.900376] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   22.900377] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
[   22.900378] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12


** Tags removed: apport-collected bionic
** Tags added: kernel-bug-exists-upstream

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

Title:
  alsa does not detech headphone output on Clevo P651RS laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Even though there is a duplex S/Pdif + Headphones out output the
  following line is observed:

  [   13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
  [   13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
  [   13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [   13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [   13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [   13.617782] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [   13.617783] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
  [   13.632784] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input19
  [   13.632851] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input20
  [   13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
  [   13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
  [   13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
  [   13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
  [   13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lehel  1673 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0
  InstallationDate: Installed on 2017-04-30 (499 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency 
root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! 
"acpi_osi=Windows 2009"
  ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-lowlatency N/A
   linux-backports-modules-4.15.0-34-lowlatency  N/A
   linux-firmware1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-34-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1726225] Re: Zesty s390x zKVM failed with selftest-setup and intercept test in kvm-unit-tests

The zKVM does not support KVM.

Checker had been implemented on it.
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=274781934fc8c58c41e962bac0731bbe087ffccb

TestError: Test skipped, this systems does not have KVM extension
support


** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Fix Released

** Changed in: qemu (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Zesty s390x zKVM failed with selftest-setup and intercept test in kvm-
  unit-tests

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  Steps:
  1. git clone https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  2. cd kvm-unit-tests
  3. ./configure; make
  4. sudo ./run_tests.sh -v

  And you will see the detailed command it use, run the one for selftest-setup 
as root:
  # TESTNAME=selftest-setup TIMEOUT=90s ACCEL= ./s390x/run s390x/selftest.elf 
-smp 1 -append 'test 123'
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/selftest.elf -smp 1 -append test 123 # 
-initrd /tmp/tmp.gj7cBJS2hH
  PASS: selftest: true
  PASS: selftest: argc == 3
  PASS: selftest: argv[0] == PROGNAME
  PASS: selftest: argv[1] == test
  PASS: selftest: argv[2] == 123
  PASS: selftest: 3.0/2.0 == 1.5
  PASS: selftest: Program interrupt: expected(1) == received(1)
  ABORT: selftest: Unexpected program interrupt: 5 at 0x12b94, ilen 6

  SUMMARY: 7 tests

  EXIT: STATUS=127

  Run the one for intercept as root:
  # TESTNAME=intercept TIMEOUT=90s ACCEL= ./s390x/run s390x/intercept.elf -smp 1
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults 
-nographic -machine s390-ccw-virtio,accel=tcg -chardev stdio,id=con0 -device 
sclpconsole,chardev=con0 -kernel s390x/intercept.elf -smp 1 # -initrd 
/tmp/tmp.4QCRdccGRJ
  PASS: intercept: stpx: store prefix
  FAIL: intercept: stpx: Program interrupt: expected(4) == received(0)
  FAIL: intercept: stpx: Program interrupt: expected(6) == received(0)
  ABORT: intercept: stpx: Unexpected program interrupt: 5 at 0x109dc, ilen 4

  SUMMARY: 3 tests, 2 unexpected failures

  EXIT: STATUS=127

  This is not a regression as we just add the test for s390x in this
  cycle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1726225/+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 1732620] Re: AMD Naples server failed with the tsc test in monotonic_time testsuite

This bug is still valid.
http://10.246.72.4/test-results/4.15.0-34.37-generic/lodygin__4.15.0-34.37__2018-08-29_07-34-00/monotonic_time-test-suite.html

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Confirmed

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

Title:
  AMD Naples server failed with the tsc test in monotonic_time testsuite

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This test failed on node lodygin (AMD Naples) constantly against every
  kernel. This issue can be found in older kernel as well.

  Steps:
   1. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
   2. make -C autotest-client-tests/monotonic_time/src
   3. sudo 

  $ sudo autotest-client-tests/monotonic_time/src/time_test --duration 300 tsc
  INFO: time_test: new tsc-warp maximum:  -931
  INFO: time_test: running tsc test on 128 cpus for 300 seconds
  INFO: time_test: new tsc-warp maximum: -9576
  INFO: time_test: new tsc-warp maximum:-10583
  INFO: time_test: new tsc-warp maximum:-10640
  INFO: time_test: new tsc-warp maximum:-10925
  FAIL: tsc-worst-warp=-10925

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: User Name 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 15 09:23 seq
   crw-rw 1 root audio 116, 33 Nov 15 09:23 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Nov 16 07:28:18 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: AMD Corporation Speedway
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: RSW1001E
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Speedway
  dmi.board.vendor: AMD Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: To be filled by O.E.M.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrRSW1001E:bd07/24/2017:svnAMDCorporation:pnSpeedway:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnSpeedway:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:
  dmi.product.family: Default string
  dmi.product.name: Speedway
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: AMD Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1732620/+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 1717897] Re: libhugetlbfs failed with "Heap did not shrink"

This test was blacklisted for Bionic and onward.

Marking this as Won't fix.

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  libhugetlbfs failed with "Heap did not shrink"

Status in ubuntu-kernel-tests:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix

Bug description:
  1. Test with Artful + 4.12 kernel deployed by MaaS, this one has passed.
  2. Install 4.13 kernel from -proposed, retest, this one will fail
  3. Reboot to 4.12 again, this will fail too.

  
  09:44:44 INFO | LD_PRELOAD=libheapshrink.so HUGETLB_MORECORE_SHRINK=yes 
HUGETLB_MORECORE=yes heapshrink (2M: 64): PASS (inconclusive)
  09:44:44 INFO | LD_PRELOAD=libhugetlbfs.so libheapshrink.so 
HUGETLB_MORECORE_SHRINK=yes HUGETLB_MORECORE=yes heapshrink (2M: 64): FAIL  
  Heap did not shrink
  09:44:44 INFO | HUGETLB_VERBOSE=1 HUGETLB_MORECORE=yes heap-overflow (2M: 
64):PASS

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: User Name 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 18 09:40 seq
   crw-rw 1 root audio 116, 33 Sep 18 09:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   
  Date: Mon Sep 18 09:44:55 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Intel Corporation S2600CWR
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=5170da90-e3b5-4db0-bea9-22859499daf4 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2016
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C610.86B.01.01.0018.072020161249
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600CWR
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H12884-261
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.0018.072020161249:bd07/20/2016:svnIntelCorporation:pnS2600CWR:pvr:rvnIntelCorporation:rnS2600CWR:rvrH12884-261:cvn..:ct17:cvr..:
  dmi.product.family: Family
  dmi.product.name: S2600CWR
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1717897/+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 1738962] Re: Failed to build upstream bpf test on Artful ARM64

Artful EOL.

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  Failed to build upstream bpf test on Artful ARM64

Status in ubuntu-kernel-tests:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Steps:
   1. git clone --depth=1 https://github.com/torvalds/linux.git
   2. sudo apt-get install clang llvm libcap-dev libelf-dev build-essential 
   3. Change the Makefile in linux/tools/testing/selftests/ to build bpf test 
only
   4. make

  Result:
   * It complains about missing headers, like the 'bits/libc-header-start.h', 
but it can be found in /usr/include/aarch64-linux-gnu/bits/
   
  $ find /usr -name libc-header-start.h
  /usr/include/aarch64-linux-gnu/bits/libc-header-start.h

  $ dpkg -S libc-header-start.h
  libc6-dev:arm64: /usr/include/aarch64-linux-gnu/bits/libc-header-start.h


  
  $ make
  make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/bpf'
  make -C ../../../lib/bpf 
OUTPUT=/home/ubuntu/linux/tools/testing/selftests/bpf/
  make[2]: Entering directory '/home/ubuntu/linux/tools/lib/bpf'
  make[2]: Leaving directory '/home/ubuntu/linux/tools/lib/bpf'
  make -C ../../../lib/bpf 
OUTPUT=/home/ubuntu/linux/tools/testing/selftests/bpf/
  make[2]: Entering directory '/home/ubuntu/linux/tools/lib/bpf'
  make[2]: Leaving directory '/home/ubuntu/linux/tools/lib/bpf'
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_verifier.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_verifier
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_tag.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_tag
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_maps.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_maps
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_lru_map.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_lru_map
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_lpm_map.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_lpm_map
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_progs.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_progs
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_align.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_align
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_verifier_log.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_verifier_log
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_dev_cgroup.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_dev_cgroup
  clang -I. -I./include/uapi -I../../../include/uapi \
 -Wno-compare-distinct-pointer-types  \
 -O2 -target bpf -emit-llvm -c 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_pkt_access.c -o - |  \
  llc -march=bpf -mcpu=generic -filetype=obj -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_pkt_access.o
  In file included from 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_pkt_access.c:8:
  /usr/include/string.h:26:10: fatal

[Kernel-packages] [Bug 1740017] Re: sprs test from kvm-unit-tests will hang on PowerPC

Still valid.
Can see on Cosmic w/ P9 as well.
http://10.246.72.4/test-results/4.17.0-9.10-generic/baltar__4.17.0-9.10__2018-08-25_01-29-00/ubuntu_kvm_unit_tests/results/ubuntu_kvm_unit_tests.all/debug/ubuntu_kvm_unit_tests.all.DEBUG.html

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Confirmed

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

Title:
  sprs test from kvm-unit-tests will hang on PowerPC

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have switched our kvm-unit-test test suite from archive tarball to 
upstream repo recently.
  And now the sprs test will hang on the ppc64le system.

  12/24 04:18:33 DEBUG| utils:0153| [stdout] MIGRATION=yes TESTNAME=sprs
  TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf -smp 1 -append '-w'

  It was failing with this test with the version of our archived tarball
  bug 1723904 (but still failing on Xenial, and 4.10 kernel on Xenail, 
therefore it has something to do with the qemu on Zesty.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1740017/+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 1791806] Re: alsa does not detech headphone output on Clevo P651RS laptop

2018-09-12 Thread Lehel Gyuro

Another person affected, the harware is an older issue of the same OEM
manufacturer:

https://ubuntuforums.org/showthread.php?t=2339157=a123aad1652866ab16dd9e5cc839f279

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

Title:
  alsa does not detech headphone output on Clevo P651RS laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Even though there is a duplex S/Pdif + Headphones out output the
  following line is observed:

  [   13.617774] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC898: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line
  [   13.617776] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=1 
(0x14/0x0/0x0/0x0/0x0)
  [   13.617778] snd_hda_codec_realtek hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [   13.617779] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [   13.617780] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [   13.617781] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [   13.617782] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [   13.617783] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
  [   13.632784] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input19
  [   13.632851] input: HDA Intel PCH Line Out as 
/devices/pci:00/:00:1f.3/sound/card0/input20
  [   13.632905] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1f.3/sound/card0/input21
  [   13.632953] input: HDA Intel PCH HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1f.3/sound/card0/input22
  [   13.632989] input: HDA Intel PCH HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1f.3/sound/card0/input23
  [   13.633108] input: HDA Intel PCH HDMI/DP,pcm=9 as 
/devices/pci:00/:00:1f.3/sound/card0/input24
  [   13.633291] input: HDA Intel PCH HDMI/DP,pcm=10 as 
/devices/pci:00/:00:1f.3/sound/card0/input25
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lehel  1673 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=14306ed9-327a-44fd-8c4d-2eba92aa55c0
  InstallationDate: Installed on 2017-04-30 (499 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-lowlatency 
root=/dev/mapper/xubuntu--vg-root ro noquiet nosplash i915.modeset=1 acpi_osi=! 
"acpi_osi=Windows 2009"
  ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-lowlatency N/A
   linux-backports-modules-4.15.0-34-lowlatency  N/A
   linux-firmware1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-34-lowlatency x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-23 (18 days ago)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04:bd09/14/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791806/+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 1747823] Re: noresv-preserve-resv-page test in libhugetlbfs failed on Trusty arm64

09/12 11:27:53 DEBUG| utils:0153| [stdout] noresv-preserve-resv-page
(2M: 64):  FAILSteal reserved page

Bug is still valid.
http://10.246.72.4/test-results/3.13.0-158.208-generic/ms10-35-mcdivittB0-kernel__3.13.0-158.208__2018-09-12_11-15-00/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Confirmed

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

Title:
  noresv-preserve-resv-page test in libhugetlbfs failed on Trusty arm64

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Deploy an ARM64 system with Trusty
  2. Install necessary packages
  3. git clone --depth=1 -b next 
https://github.com/libhugetlbfs/libhugetlbfs.git
  4. make BUILDTYPE=NATIVEONLY
  5. execute the run_test.py in tests directory

  Result:
  * The noresv-preserve-resv-page test case will fail

  Output with sudo ./run_test.py -v:
  noresv-preserve-resv-page (2M: 64):   Starting testcase 
"noresv-preserve-resv-page", pid 16071
  Reserve all hugepages 31935
  Write  to 0x2f97e0 to steal reserved page
  FAIL  Steal reserved page

  Output with sudo ./run_test.py -V
  noresv-preserve-resv-page (2M: 64): libhugetlbfs 
[ms10-34-mcdivittB0-kernel:19589]: INFO: Found pagesize 2048 kB
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Parsed kernel version: 
[3] . [13] . [0] 
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Feature 
private_reservations is present in this kernel
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Feature noreserve_safe 
is present in this kernel
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Feature map_hugetlb is 
present in this kernel
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Kernel has MAP_PRIVATE 
reservations.  Disabling heap prefaulting.
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: Kernel supports 
MAP_HUGETLB
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: HUGETLB_SHARE=0, 
sharing disabled
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: HUGETLB_NO_RESERVE=no, 
reservations enabled
  libhugetlbfs [ms10-34-mcdivittB0-kernel:19589]: INFO: No segments were 
appropriate for remapping
  FAILSteal reserved page


  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-141-generic 3.13.0-141.190
  ProcVersionSignature: User Name 3.13.0-141.190-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-141-generic aarch64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Wed Feb  7 03:11:38 2018
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-141-generic N/A
   linux-backports-modules-3.13.0-141-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1747823/+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 1792288] [NEW] package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package

2018-09-12 Thread sammy

Public bug reported:

trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-340 340.106-0ubuntu3
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libnvidia-compute-390_390.48-0ubuntu3_amd64.deb
 /var/cache/apt/archives/nvidia-utils-390_390.48-0ubuntu3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libnvidia-compute-390 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
AptOrdering:
 libcuda1-340:amd64: Remove
 nvidia-opencl-icd-340:amd64: Remove
 libnvidia-compute-390:amd64: Install
 nvidia-utils-390:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Sep 13 07:28:35 2018
DpkgTerminalLog:
 Preparing to unpack .../libnvidia-compute-390_390.48-0ubuntu3_amd64.deb ...
 Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu3) ...
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libnvidia-compute-390_390.48-0ubuntu3_amd64.deb 
(--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package nvidia-340 340.106-0ubuntu3
ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', 
which is also in package nvidia-340 340.106-0ubuntu3
InstallationDate: Installed on 2018-08-31 (12 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: nvidia-graphics-drivers-390
Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also 
in package nvidia-340 340.106-0ubuntu3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package libnvidia-compute-390 (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu
  /libnvidia-ml.so', which is also in package nvidia-340
  340.106-0ubuntu3

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

Bug description:
  trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-340 340.106-0ubuntu3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libnvidia-compute-390_390.48-0ubuntu3_amd64.deb
   /var/cache/apt/archives/nvidia-utils-390_390.48-0ubuntu3_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libnvidia-compute-390 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  AptOrdering:
   libcuda1-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   libnvidia-compute-390:amd64: Install
   nvidia-utils-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Sep 13 07:28:35 2018
  DpkgTerminalLog:
   Preparing to unpack .../libnvidia-compute-390_390.48-0ubuntu3_amd64.deb ...
   Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu3) ...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/libnvidia-compute-390_390.48-0ubuntu3_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package nvidia-340 340.106-0ubuntu3
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.106-0ubuntu3
  InstallationDate: Installed on 2018-08-31 (12 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-compute-390 (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.106-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1729510] Re: libhugetlbfs failed with "[Errno 95] Operation not supported" on s390x zVM

As 17.10 has reaches its EOL, and the test was blacklisted on Bionic and onward.
I will mark this task as Won't fix.

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  libhugetlbfs failed with "[Errno 95] Operation not supported" on s390x
  zVM

Status in ubuntu-kernel-tests:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Steps:
  1. sudo apt-get install git python-minimal -y
  2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
  3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
  4. rm -fr autotest/client/tests
  5. ln -sf ~/autotest-client-tests autotest/client/tests
  6. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/libhugetlbfs/control

  It will failed with the following python code piece when trying to
  access /proc/sys/vm/nr_hugepages:

  utils.write_one_line('/proc/sys/vm/nr_hugepages',
  str(pages_requested))

  With error message:
    [Errno 95] Operation not supported

  For Xenial, the error message is:
[Errno 524] Unknown error 524

  This issue is not a regression.

  Full error log:

  $ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client
  /autotest-local --verbose autotest/client/tests/libhugetlbfs/control

  07:20:37 INFO | Writing results to 
/home/ubuntu/autotest/client/results/default
  07:20:37 DEBUG| Initializing the state engine
  07:20:37 DEBUG| Persistent state client.steps now set to []
  07:20:37 DEBUG| Persistent option harness now set to None
  07:20:37 DEBUG| Persistent option harness_args now set to None
  07:20:37 DEBUG| Selected harness: standalone
  07:20:48 INFO | START timestamp=1509607248localtime=Nov 
02 07:20:48
  07:20:48 DEBUG| Persistent state client._record_indent now set to 1
  07:20:48 INFO |   START   libhugetlbfslibhugetlbfs
timestamp=1509607248localtime=Nov 02 07:20:48
  07:20:48 DEBUG| Persistent state client._record_indent now set to 2
  07:20:48 DEBUG| Persistent state client.unexpected_reboot now set to 
('libhugetlbfs', 'libhugetlbfs')
  07:20:49 DEBUG| Running 'apt-get install --yes --force-yes build-essential 
git gcc'
  07:20:50 DEBUG| [stdout] Reading package lists...
  07:20:50 DEBUG| [stdout] Building dependency tree...
  07:20:50 DEBUG| [stdout] Reading state information...
  07:20:50 DEBUG| [stdout] build-essential is already the newest version 
(12.4ubuntu1).
  07:20:50 DEBUG| [stdout] gcc is already the newest version (4:7.2.0-1ubuntu1).
  07:20:50 DEBUG| [stdout] git is already the newest version 
(1:2.14.1-1ubuntu4).
  07:20:50 DEBUG| [stdout] The following packages were automatically installed 
and are no longer required:
  07:20:50 DEBUG| [stdout]   containerd linux-headers-4.13.0-14 
linux-headers-4.13.0-14-generic
  07:20:50 DEBUG| [stdout]   linux-image-4.13.0-14-generic 
linux-image-extra-4.13.0-14-generic runc
  07:20:50 DEBUG| [stdout] Use 'sudo apt autoremove' to remove them.
  07:20:50 DEBUG| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not 
upgraded.
  07:20:50 ERROR| [stderr] W: --force-yes is deprecated, use one of the options 
starting with --allow instead.
  07:20:50 DEBUG| Running 'which gcc'
  07:20:50 DEBUG| [stdout] /usr/bin/gcc
  07:20:53 ERROR| Exception escaping from test:
  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 378, in _exec
  _cherry_pick_call(self.initialize, *args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 738, in 
_cherry_pick_call
  return func(*p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/tests/libhugetlbfs/libhugetlbfs.py", 
line 39, in initialize
  str(pages_requested))
    File "/home/ubuntu/autotest/client/shared/utils.py", line 408, in 
write_one_line
  open_write_close(filename, line.rstrip('\n') + '\n')
    File "/home/ubuntu/autotest/client/shared/utils.py", line 416, in 
open_write_close
  f.close()
  IOError: [Errno 95] Operation not supported

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic s390x
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not

[Kernel-packages] [Bug 1763323] Re: ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel

Still failing for the latest KVM kernel - 4.15.0-1021.21-kvm

http://10.246.72.4/test-results/4.15.0-1021.21-kvm/bionic-linux-kvm-
kvm-4.15.0-groucho-
ubuntu_quota_smoke_test/ubuntu_quota_smoke_test/results/ubuntu_quota_smoke_test
.quota-smoke-test/debug/ubuntu_quota_smoke_test.quota-smoke-
test.DEBUG.html

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Confirmed

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

Title:
  ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in linux-kvm source package in Xenial:
  New

Bug description:
  The "enable disable fan test" will fail with Xenial KVM kernel

  Error message:
RTNETLINK answers: Operation not supported
/usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev ens4 dstport 
0 local 10.246.72.56 fan-map 250.0.0.0/8:10.246.0.0/16
/usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation
RTNETLINK answers: Cannot assign requested address
iptables v1.6.0: Couldn't load target `fan-egress':No such file or directory

Try `iptables -h' or 'iptables --help' for more information.
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: Bad rule (does a matching rule exist in that chain?).
iptables: No chain/target/match by that name.
rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory
/usr/sbin/fanatic: unable to bring fan up, unable to configure

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26
  ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117
  Uname: Linux 4.4.0-1021-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 12 10:22:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1763323/+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 1747828] Re: chunk-overcommit test in libhugetlbfs test suite will fail on Trusty ARM64

09/12 11:27:57 DEBUG| utils:0153| [stdout] chunk-overcommit (2M: 64):
FAILKilled by signal "Bus error" due to overcommit

Bug still valid.
http://10.246.72.4/test-results/3.13.0-158.208-generic/ms10-35-mcdivittB0-kernel__3.13.0-158.208__2018-09-12_11-15-00/libhugetlbfs/results/libhugetlbfs/debug/libhugetlbfs.DEBUG.html

** Changed in: ubuntu-kernel-tests
   Status: Incomplete => Confirmed

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

Title:
  chunk-overcommit test in libhugetlbfs test suite will fail on Trusty
  ARM64

Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Deploy an ARM64 system with Trusty
  2. Install necessary packages
  3. git clone --depth=1 -b next 
https://github.com/libhugetlbfs/libhugetlbfs.git
  4. make BUILDTYPE=NATIVEONLY
  5. execute the run_test.py in tests directory

  Result:
  * The chunk-overcommit test case will fail

  chunk-overcommit (2M: 64):Starting testcase "chunk-overcommit", pid 17370
  overcommit: 31935 hugepages available: chunk1=15968 chunk2=15968
  Looks like we've overcommitted, testing...
  FAIL  Killed by signal "Bus error" due to overcommit

  Error message could be found in syslog:
  AutotestCrashHandler: Application chunk-overcommi, PID 2269 crashed
  AutotestCrashHandler: Writing core files to 
['/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.chunk-overcommi.2269']
  AutotestCrashHandler: Could not determine from which application core file 
/home/ubuntu/autotest/client/results/default/libhugetlbfs/debug/crash.chunk-overcommi.2269/core
 is from

  Please find the attachement for the core file.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-141-generic 3.13.0-141.190
  ProcVersionSignature: User Name 3.13.0-141.190-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-141-generic aarch64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Wed Feb  7 04:14:16 2018
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-141-generic N/A
   linux-backports-modules-3.13.0-141-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1747828/+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 1768452] Re: Unable to insert test_bpf module on Xenial s390x

This test has been blacklisted on Xenial:
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=243c0b88ee50cb5fffa04f55dd49f76cd365d778

** Changed in: ubuntu-kernel-tests
   Status: New => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => Invalid

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

Title:
  Unable to insert test_bpf module on Xenial s390x

Status in ubuntu-kernel-tests:
  Won't Fix
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  After the test_bpf insert issue for Xenial was fixed in bug 1765698

  But it looks like the s390x needs some extra work.
  $ sudo modprobe test_bpf
  modprobe: ERROR: could not insert 'test_bpf': Invalid argument

  4 tests failed here:
test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create 
err=-524 len=4096
test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create 
err=-524 len=4096
test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create 
err=-524 len=4096
test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime 
err=-524

  Complete test result:
  https://pastebin.ubuntu.com/p/zMDwVjwF7X/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-123-generic 4.4.0-123.147
  ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128
  Uname: Linux 4.4.0-123-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed May  2 03:45:22 2018
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-123-generic N/A
   linux-backports-modules-4.4.0-123-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1768452/+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 1773000] Re: [18.04] [regression testing] ubuntu_bpf tests failing on amd64

It looks like this issue has gone.

1466.   08/28 17:49:09 INFO |ubuntu_bpf:0077| Summary: 713 PASSED, 0 FAILED
1467.   08/28 17:49:09 INFO |ubuntu_bpf:0077| test_verifier: PASSED
1468.   08/28 17:49:09 INFO |ubuntu_bpf:0077|
1469.   08/28 17:49:09 INFO |ubuntu_bpf:0077| Running test_maps bpf test..
1470.   08/28 17:49:09 INFO |ubuntu_bpf:0077| test_maps: PASSED
1471.   08/28 17:49:09 INFO |ubuntu_bpf:0077|
1472.   08/28 17:49:09 INFO |ubuntu_bpf:0077| bpf tests PASSED
1473.   

http://10.246.72.4/test-
results/4.15.0-34.37-generic/ubuntu_bpf-4.15.0-34.37-amd64-index.html


** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [18.04] [regression testing] ubuntu_bpf tests failing on amd64

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  For example:  http://10.246.72.4/test-
  results/4.15.0-21.22-generic/ubuntu_bpf-4.15.0-21.22-amd64-index.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1773000/+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 1728244] Re: Touchpad stops working after reboot on Apollo Lake

2018-09-12 Thread Kai-Heng Feng

Sure.

Kernel with the patch included:
https://people.canonical.com/~khfeng/lp1728244-norpm/

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1728244/+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 1782723] Re: dnotify in ubuntu_stress_smoke_test failed on KVM kernels

dnotify test will now get skipped for KVM kernels.
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=f0dde6e357b4d87f7509c6a8105457fff9619a78

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

Title:
  dnotify in ubuntu_stress_smoke_test failed on KVM kernels

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Won't Fix

Bug description:
  == Justification ==
  In the Xenial 4.4 and Bionic 4.15 KVM kernel, the CONFIG_DNOTIFY was not set, 
which is causing failures in the stress-ng dnotify test.

   [stdout] dnotify FAILED
   [stdout] stress-ng: debug: [3043] 2 processors online, 2 processors 
configured
   [stdout] stress-ng: info:  [3043] dispatching hogs: 4 dnotify
   [stdout] stress-ng: debug: [3043] cache allocate: reducing cache level from 
L3 (too high) to L2
   [stdout] stress-ng: debug: [3043] cache allocate: default cache size: 4096K
   [stdout] stress-ng: debug: [3043] starting stressors
   [stdout] stress-ng: debug: [3044] stress-ng-dnotify: started [3044] 
(instance 0)
   [stdout] stress-ng: debug: [3043] 4 stressors spawned
   [stdout] stress-ng: fail:  [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: debug: [3046] stress-ng-dnotify: started [3046] 
(instance 2)
   [stdout] stress-ng: debug: [3047] stress-ng-dnotify: started [3047] 
(instance 3)
   [stdout] stress-ng: fail:  [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3046] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] info: 5 failures reached, aborting stress process
   [stdout] stress-ng: debug: [3046] stress-ng-dnotify: exited [3046] (instance 
2)
   [stdout] stress-ng: fail:  [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3047] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] info: 5 failures reached, aborting stress process
   [stdout] stress-ng: debug: [3047] stress-ng-dnotify: exited [3047] (instance 
3)
   [stdout] stress-ng: fail:  [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3044] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] info: 5 failures reached, aborting stress process
   [stdout] stress-ng: debug: [3044] stress-ng-dnotify: exited [3044] (instance 
0)
   [stdout] stress-ng: error: [3043] process 3044 (stress-ng-dnotify) 
terminated with an error, exit status=1 (stress-ng core failure)
   [stdout] stress-ng: debug: [3043] process [3044] terminated
   [stdout] stress-ng: debug: [3045] stress-ng-dnotify: started [3045] 
(instance 1)
   [stdout] stress-ng: fail:  [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] stress-ng: fail:  [3045] stress-ng-dnotify: fcntl F_NOTIFY failed, 
errno=22 (Invalid argument)
   [stdout] info: 5 failures reached, aborting stress process
   [stdout] stress-ng: debug: [3045] stress-ng-dnotify: exited [3045] (instance 
1)
   [stdout] stress-ng: error: [3043] process 3045 (stress-ng-dnotify) 
terminated with an error, exit status=1 (stress-ng core failure)
   [stdout] stress-ng: debug: [3043] process [3045] terminated
   [stdout] stress-ng: error: [3043] process 3046 (stress-ng-dnotify) 
terminated with an error, exit status=1 (stress-ng core failure)
   [stdout] stress-ng: debug: [3043] process [3046] terminated
   [stdout] stress-ng: error: [3043] process 3047 (stress-ng-dnotify) 
terminated with an

[Kernel-packages] [Bug 1791725] Re: linux-aws: 4.15.0-1022.22 -proposed tracker

2018-09-12 Thread Brad Figg

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

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

Title:
  linux-aws: 4.15.0-1022.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1791719
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791725/+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 1786729] Re: execveat03 in ubuntu_ltp_syscalls failed on X/B

Mark it as incomplete while waiting for verifications.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

Title:
  execveat03 in ubuntu_ltp_syscalls failed on X/B

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Fix Released
Status in linux-aws package in Ubuntu:
  New
Status in linux source package in Xenial:
  New
Status in linux-aws source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux-aws source package in Bionic:
  New

Bug description:
  This is a POTENTIAL REGRESSION.

  PASSED with 4.4.0-1063-aws
  FAILED with 4.4.0-1064-aws in proposed

  This is a new test case added 4 days ago.
  From the commit message it looks like this is a test case for commit 
8db6c34f1dbc:
  The regression is introduced from 8db6c34f1dbc ("Introduce v3 namespaced
  file capabilities"). Overlayfs and possibly other networking filesystems
  unhash the dentry on unlink, fail on this test with above change.

  However this commit has been applied in the Xenial AWS kernel
  (14985d791) with bug 1778286

  This might have something to do with the way how we backport it (the
  EINVAL return value is the clue)

  
  <<>>
  tag=execveat03 stime=1534135632
  cmdline="execveat03"
  contacts=""
  analysis=exit
  <<>>
  incrementing stop
  tst_test.c:1017: INFO: Timeout per run is 0h 05m 00s
  execveat03.c:70: FAIL: execveat() returned unexpected errno: EINVAL

  Summary:
  passed   0
  failed   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=0 termination_type=exited termination_id=1 corefile=no
  cutime=0 cstime=0
  <<>>

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1064-aws 4.4.0-1064.74
  ProcVersionSignature: User Name 4.4.0-1064.74-aws 4.4.140
  Uname: Linux 4.4.0-1064-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Aug 13 04:51:09 2018
  Ec2AMI: ami-529fb82a
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: x1e.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1786729/+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 1791725] Re: linux-aws: 4.15.0-1022.22 -proposed tracker

2018-09-12 Thread Khaled El Mously

** Summary changed:

- linux-aws:  -proposed tracker
+ linux-aws: 4.15.0-1022.22 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-aws: 4.15.0-1022.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1791719
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791725/+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 1791756] Re: linux-lts-trusty: 3.13.0-159.209~precise1 -proposed tracker

2018-09-12 Thread Khaled El Mously

** Summary changed:

- linux-lts-trusty:  -proposed tracker
+ linux-lts-trusty: 3.13.0-159.209~precise1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-lts-trusty: 3.13.0-159.209~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1791754
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791756/+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 1774359] Re: could not find module by name='off'

2018-09-12 Thread Zhou

Ubuntu 18.04 On Precision 5530 Quadro P1000
Confirm the issue with nvidai 396.

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

alias  off

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1774359/+subscriptions

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

[Kernel-packages] [Bug 1774366] Re: Fix MCE handling for user access of poisoned device-dax mapping

2018-09-12 Thread quanxian

sorry, there will be more commits available.

c7486104a5ce x86/mce: Fix set_mce_nospec() to avoid #GP fault

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

Title:
  Fix MCE handling for user access of poisoned device-dax mapping

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  Description:

  Customer reports:

  —

  We've tried the ndctl error injection. Now the error injection is
  successful. But we have a couple of questions related with the
  poisoned block.

  Here are some tests/steps that I did:

  1. I mmap the first 10GB of /dev/dax13.0 to virtual address space and
  inject an error at offset 1GB (block offset should be 1GB/512bytes =
  2097152) which seems fine:

  [root@scaqae09celadm13 wning]# ndctl inject-error --uninject --block=2097152 
--count=1 namespace13.0
  Warning: Un-injecting previously injected errors here will
  not cause the kernel to 'forget' its badblock entries. Those
  have to be cleared through the normal process of writing
  the affected blocks

  {
  "dev":"namespace13.0",
  "mode":"dax",
  "size":518967525376,
  "uuid":"0738c8bd-3b3f-4989-9d0e-0e9c6006c810",
  "chardev":"dax13.0",
  "numa_node":0,
  "badblock_count":1,
  "badblocks":[

  { "offset":2097152, "length":1, "dimms":[ "nmem1" ] }
  ]
  }

  2. In my test program, I just try to read every address of the first
  10GB. At the first time, when I read the offset 1GB, I got the SIGBUS
  error, but in the sinfo struct of signal handler, the failed address
  is NULL and signal code is 128 which seems incorrect. But then if we
  run again, the unit test gets stuck here:

  rt_sigaction(SIGBUS,

  {0x400dd2, [], SA_RESTORER|SA_SIGINFO, 0x7fb5cf839270}
  , NULL, 8) = 0

  And here is the output of log messages:

  Apr 3 14:39:23 scaqae09celadm13 kernel: mce: Uncorrected hardware memory 
error in user-access at 952b20
  Apr 3 14:51:11 scaqae09celadm13 kernel: mce: Uncorrected hardware memory 
error in user-access at 94eb30
  Apr 3 14:51:11 scaqae09celadm13 kernel: mce_notify_irq: 48 callbacks 
suppressed
  Apr 3 14:51:11 scaqae09celadm13 kernel: mce: [Hardware Error]: Machine check 
events logged
  Apr 3 14:51:11 scaqae09celadm13 kernel: Memory failure: 0x94eb300: reserved 
kernel page still referenced by 1 users
  Apr 3 14:51:11 scaqae09celadm13 kernel: Memory failure: 0x94eb300: recovery 
action for reserved kernel page: Failed
  Apr 3 14:51:11 scaqae09celadm13 kernel: mce: Memory error not recovered

  The program I use is (simple do memcpy and directly read from the
  target address):

  for (i = 0; i < DAX_MAPPING_SIZE; i++) // DAX_MAPPING_SIZE is 10G

  { total += peek(buf + i); }
  char peek(void *addr)

  { char temp[128]; memcpy(temp, addr, 1); return *(char *)addr; }
  May I ask do we missed steps in triggering the SIGBUS error?

  Target Kernel: 4.19
  Target Release: 18.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1774366/+subscriptions

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

Re: [Kernel-packages] [Bug 1791537] Re: 4.15 linux kernel - unable to access the internet

2018-09-12 Thread jason

Question - as I was trying to implement the .19 kernel, I ran into issues
that appeared to be linked to Virtual Box.  Per the instructions (
https://wiki.ubuntu.com/Kernel/MainlineBuilds?action=show=KernelMainlineBuilds)
Virtual box would need to be removed to get around the issue.  My question
is after the .19 is implemented could I then reinstall Virtualbox?

Also, could I just wait it out until the next Ubuntu update that had
another kernel update and would that fix the problem?

Thanks,
jason

On Wed, Sep 12, 2018 at 3:31 PM Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.19 kernel[0].
>
> If this bug is fixed in the mainline kernel, please add the following
> tag 'kernel-fixed-upstream'.
>
> If the mainline kernel does not fix this bug, please add the tag:
> 'kernel-bug-exists-upstream'.
>
> Once testing of the upstream kernel is complete, please mark this bug as
> "Confirmed".
>
>
> Thanks in advance.
>
> [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1791537
>
> Title:
>   4.15 linux kernel - unable to access the internet
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Budgie was running great until sometime this week, post minimal update
>   - per notification saying i needed to. Ever since then, say September
>   7th ish, i can not access any internet. Wifi, ethernet, usb wifi,
>   anything.
>
>   I tried to run the command ubuntu-bug linux as directed, but when I
>   tried to submit was given error, something about unable to translate.
>   Makes sense since I can’t connect to the internet.  I then reverted
>   back to the previous linux kernel version and was able to access the
>   internet.
>
>   The command did show that I am on 4.15 kernel. If this is the issue,
>   can someone tell me how to move up to 4.17, if that is the fix? If
>   that is not the fix - ideas?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.15.0-33-generic 4.15.0-33.36
>   ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
>   Uname: Linux 4.15.0-33-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  kop2872 F pulseaudio
>   CurrentDesktop: Budgie:GNOME
>   Date: Sun Sep  9 14:37:19 2018
>   HibernationDevice: RESUME=UUID=fc67782e-72fa-4d11-be6c-d91d09848f01
>   InstallationDate: Installed on 2018-07-21 (49 days ago)
>   InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release
> amd64 (20180426)
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 8087:0a2a Intel Corp.
>Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp.
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: HP HP Pavilion Notebook
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic
> root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-33-generic N/A
>linux-backports-modules-4.15.0-33-generic  N/A
>linux-firmware 1.173.1
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/26/2018
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.87
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 80A2
>   dmi.board.vendor: HP
>   dmi.board.version: 91.1E
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A2:rvr91.1E:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
>   dmi.product.name: HP Pavilion Notebook
>   dmi.product.version: Type1ProductConfigId
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791537/+subscriptions
>


-- 
Thanks,
Jason

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

Title:
  4.15 linux kernel - unable to access the internet

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Budgie was running great until sometime this week, post minimal update
  - per notification saying i needed to. Ever since then, say September
  7th ish, i can not access any internet. Wifi,

[Kernel-packages] [Bug 1791790] Re: Kernel hang on drive pull caused by incomplete backport for bug 1597908

2018-09-12 Thread Steven Haber

To clarify -- I ran the testing with all of your kernel packages
installed and live, except for cloud-tools, which we don't use on HP
hardware (haha).

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

Title:
Kernel hang on drive pull caused by incomplete backport for bug
1597908

Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress

Bug description:
A bug was introduced when backporting the fix for
http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu
16.04 LTS 4.4 kernels >= 4.4.0-36, and many other non-LTS kernels.

This patch changes the context in which timeout work is scheduled for
block devices in the kernel. Previously, timeout work was executed
directly from the timer callback that fired when a deadline was met.
After the patch, timeout work is scheduled using a background work
queue. This means that by the time the work executes, the device queue
which originally scheduled the work could be torn down. In order to
prevent this, the patch takes a reference on the device queue when
executing the timeout work.

The problem is that the last reference to this queue can be removed
before the timeout work can be executed. During teardown, the block
system executes a freeze followed by a drain. The freeze drops the
last reference on the queue. The drain tries to clean up any
outstanding work, including timeout work. After a freeze, the timeout
work in the background queue is unable to obtain a reference, and
exits early without completing work. The work is now permanently stuck
in the queue and it will never be completed. The drain in the device
teardown path spins indefinitely.

The bug manifests as a hang that looks like this:
[] schedule+0x35/0x80
[] hpsa_scan_start+0x109/0x140 [hpsa]
[] ? wake_atomic_t_function+0x60/0x60
[] hpsa_rescan_ctlr_worker+0x1d2/0x652 [hpsa]
[] process_one_work+0x165/0x480
[] worker_thread+0x4b/0x4c0
[] ? process_one_work+0x480/0x480
[] kthread+0xd8/0xf0
[] ? kthread_create_on_node+0x1e0/0x1e0
[] ret_from_fork+0x3f/0x70
[] ? kthread_create_on_node+0x1e0/0x1e0

The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's
most recent 4.4 kernel.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4e9b6f20828ac880dbc1fa2fdbafae779473d1af

We hit this bug nearly 100% of the time on some of our HP hardware.
The HPSA driver has a tendency to aggressively remove missing devices,
so it widens the race. As a result, we've been building our own kernel
with this patch applied. It would be really nice if we could get it
into mainline Ubuntu.

Let me know what additional information is needed. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791790/+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 1791790] Re: Kernel hang on drive pull caused by incomplete backport for bug 1597908

2018-09-12 Thread Steven Haber

Hey Joseph! I just ran one of our machines through our drive power
faulting test. It survived 5 hotplug events without crashing. Usually
it's 100% repro of the crash. Seems to work. Thanks much!

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

Title:
Kernel hang on drive pull caused by incomplete backport for bug
1597908

Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress

The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's
most recent 4.4 kernel.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4e9b6f20828ac880dbc1fa2fdbafae779473d1af

Let me know what additional information is needed. Thanks!

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

[Kernel-packages] [Bug 1792189] Re: linux-firmware does not depend on initramfs-tools

2018-09-12 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  linux-firmware does not depend on initramfs-tools

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  In bug #1646197 the linux-firmware.postinst was added to call update-
  initramfs (provided by initramfs-tools.  If the initramfs-tools
  package is not installed the installation of linux-firmware will fail.

  Recreate:
  sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs*
  sudo apt-get install --assume-yes linux-generic

  Result:
  Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ...
  Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ...
  Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ...
  Setting up initramfs-tools-bin (0.130ubuntu3.3) ...
  Setting up linux-firmware (1.173.1) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm
  /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf
  update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2.
  dpkg: error processing package linux-firmware (--configure):
   installed linux-firmware package post-installation script subprocess 
returned error exit status 2
  ...
  Errors were encountered while processing:
   linux-firmware
   linux-image-generic
   linux-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Impact:
  Builds of minimized images start with an image that has the linux-kvm kernel 
but lack initramfs-tools.  Derivative builds that require a different kernel, 
linux-generic for example, will purge the existing kernel and install the 
correct kernel which could pull in linux-firmware and initramfs-tools.  In that 
case the builds fail unless initramfs-tools is installed prior to kernel 
installation as a workaround for this missing package dependency.

  This has been recreated on cosmic and bionic, a fix is desired on
  each.  (I was unable to recreate on Xenial but that package lacks the
  dependency as well).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+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 1792141] Re: Screen problems two monitors, with all kernels over 4.13, so 4.14, 4.15 etc.

2018-09-12 Thread Martin Eisenstein

Hey Joseph Salisbury (jsalisbury) ;)

I tested the Kernel Version 4.19-rc3 and my PC is working normally
again.

The error is clearly in the kernel versions 4.13 - 4.17, because these
have also tested. I could not test the 4.18 kernel.

Currently I can only use Linux Mint with the kernel 4.4 stable. But this
is only limited because the network card and the sound card do not work
due to lack of kernel and driver support.

Is this a security risk if I want to use this kernel productively? With
security risk I mean, I could be hacked from the outside.

Thanks lot;);)

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

Title:
  Screen problems two monitors, with all kernels over 4.13, so 4.14,
  4.15 etc.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As of kernel 4.13, I have problems with my two screens. This affects all 
kernels over 4.13, that is 4.14, 4.15, and so on.
  Affected are computers with current AMD hardware.
  My computer system:
  Motherboard: MSI X470 GAMING M7 AC
  CPU: AMD Ryzen 7 2700
  Graphics card: MSI R9 380

  If you want to use both monitors on top of each other, the ad
  management crashes and only one monitor is activated. The other
  monitor is deactivated and can not be reactivated afterwards.

  For all kernels under 4.13, ad management works perfectly.

  Affected are all Ubuntu / Linux Mint / Arch versions. It does not
  matter if you use Xfce, Mate, Cinamon or Gnome. The above stated
  versions have all been tested and delivered, with my hardware, the
  same results.

  I have found other users who have the same bug:
  https://www.linuxmintusers.de/index.php?topic=49574.msg698322#msg698322

  Is this bug known and how can I fix it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792141/+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 1791323] Re: XFS fallocate implementation incorrectly reports ENOSPC

2018-09-12 Thread Charles Hathaway

Confirmed in the latest RC kernel:

charles@ubuntuvm:~/temp$ fallocate -l 1GB image.img
charles@ubuntuvm:~/temp$ sudo modprobe loop
[sudo] password for charles: 
charles@ubuntuvm:~/temp$ mkfs.xfs image.img 
meta-data=image.img  isize=512agcount=4, agsize=61035 blks
 =   sectsz=512   attr=2, projid32bit=1
 =   crc=1finobt=1, sparse=0, rmapbt=0, 
reflink=0
data =   bsize=4096   blocks=244140, imaxpct=25
 =   sunit=0  swidth=0 blks
naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
log  =internal log   bsize=4096   blocks=855, version=2
 =   sectsz=512   sunit=0 blks, lazy-count=1
realtime =none   extsz=4096   blocks=0, rtextents=0
charles@ubuntuvm:~/temp$ mkdir mnt
charles@ubuntuvm:~/temp$ mount -o loop ./image.img mnt
mount: only root can use "--options" option
charles@ubuntuvm:~/temp$ sudo mount -o loop ./image.img mnt
charles@ubuntuvm:~/temp$ cd mnt/
charles@ubuntuvm:~/temp/mnt$ sudo fallocate -o 0 -l 700mb image.img
charles@ubuntuvm:~/temp/mnt$ sudo fallocate -o 0 -l 700mb image.img
fallocate: fallocate failed: No space left on device
charles@ubuntuvm:~/temp/mnt$ uname -a
Linux ubuntuvm 4.19.0-041900rc3-generic #201809120832 SMP Wed Sep 12 12:35:08 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
charles@ubuntuvm:~/temp/mnt$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename:   bionic


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

** Tags added: kernel-bug-exists-upstream

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

Title:
  XFS fallocate implementation incorrectly reports ENOSPC

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When given an offset of 0 and a length, fallocate (man 2 fallocate)
  reports ENOSPC if the size of the file + the length to be allocated is
  greater than the available space.

  Example below using the fallocate command (man 1 fallocate) for
  simplicity; the issue is with the logic backing the system call.

  chathaway@bender:~/temp$ fallocate -l 1GB example.img
  chathaway@bender:~/temp$ mkfs.xfs example.img 
  meta-data=example.imgisize=512agcount=4, agsize=61035 blks
   =   sectsz=512   attr=2, projid32bit=1
   =   crc=1finobt=1, sparse=0, rmapbt=0, 
reflink=0
  data =   bsize=4096   blocks=244140, imaxpct=25
   =   sunit=0  swidth=0 blks
  naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
  log  =internal log   bsize=4096   blocks=855, version=2
   =   sectsz=512   sunit=0 blks, lazy-count=1
  realtime =none   extsz=4096   blocks=0, rtextents=0
  chathaway@bender:~/temp$ sudo modprobe loop
  chathaway@bender:~/temp$ mkdir mnt
  chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/
  chathaway@bender:~/temp$ cd mnt
  chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt
  chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt
  fallocate: fallocate failed: No space left on device
  chathaway@bender:~/temp/mnt$ df -h .
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/loop0  951M  766M  185M  81% /home/chathaway/temp/mnt

  Expected behaviour: because we allocate 768MB starting at offset 0,
  and have 951MB on the disk, we would expect that the allocation should
  be fine. Other filesystem behave this way (for example, ext4).

  Thanks!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chathaway   2608 F pulseaudio
   /dev/snd/controlC1:  chathaway   2608 F pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.04
  MachineType: ASUSTeK COMPUTER INC. UX303LN
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img 
root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 
systemd.show_status=false splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm docker sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LN.204
  dmi.board.asset.tag:

[Kernel-packages] [Bug 1792209] Re: net: hns: Avoid hang when link is changed while handling packets

2018-09-12 Thread dann frazier

** Changed in: linux (Ubuntu)
   Status: Incomplete => In Progress

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  net: hns: Avoid hang when link is changed while handling packets

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  If an admin uses ethtool to change the link speed or duplex setting while the 
hardware is still processing packets, a hardware hang may result.

  [Test Case]
  While traffic is in-progress, use ethtool to change link speed/duplex.

  [Fix]
  Fixes have been applied upstream:
  455c4401fe7a5 net: hns: add netif_carrier_off before change speed and duplex
  31fabbee8f5c6 net: hns: add the code for cleaning pkt in chip

  [Regression Risk]
  The only Ubuntu-supported system that uses this driver is the HiSilicon D05 
board, on which the fix was explicitly tested.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792209/+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 1792183] Re: Wakeup immediately after sleep

2018-09-12 Thread Nir Yeffet

Resolved in v4.19 rc3. (though the laptop wont wake up from other ACPI
wakeup event, such as LID0, even if enabled)

** Tags added: kernel-fixed-upstream

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

Title:
  Wakeup immediately after sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since the recent update (kernel included) the laptop will wakeup
  several seconds after sleep. The problem seems to be related to USB3.0
  since running `echo XHC1 > /proc/acpi/wakeup` solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nir1806 F pulseaudio
   /dev/snd/controlC1:  nir1806 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 09:18:34 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=e9e386b2-d064-4d74-8194-aef4a9d41bb8
  InstallationDate: Installed on 2018-03-23 (172 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 002: ID 05ac:8406 Apple, Inc. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=b7c8eea7-b64d-4137-bfba-6ae7016d0e31 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (138 days ago)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792183/+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 1792239] Re: linux-azure: 4.18.0-1001.1~18.04.1 -proposed tracker

2018-09-12 Thread Marcelo Cerri

** Changed in: kernel-sru-workflow
   Status: In Progress => Invalid

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Invalid

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/promote-to-updates
   Status: New => Invalid

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   Status: New => Invalid

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Invalid

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Invalid

** Changed in: kernel-sru-workflow/upload-to-ppa
   Status: New => Invalid

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Invalid

** Changed in: linux-azure (Ubuntu Bionic)
   Status: Confirmed => Invalid

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

Title:
  linux-azure: 4.18.0-1001.1~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  Invalid
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Invalid
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Invalid
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Invalid

Bug description:
  This bug is for tracking the 4.18.0-1001.1~18.04.1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 12. September 2018 21:32 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1792239/+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 1792239] Re: linux-azure: 4.18.0-1001.1~18.04.1 -proposed tracker

2018-09-12 Thread Brad Figg

** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

** Description changed:

  This bug is for tracking the 4.18.0-1001.1~18.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Wednesday, 12. September 2018 21:32 UTC

** Description changed:

  This bug is for tracking the 4.18.0-1001.1~18.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 12. September 2018 21:32 UTC
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux-azure: 4.18.0-1001.1~18.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.18.0-1001.1~18.04.1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  kernel-stable-phase:Packaging
  kernel-stable-phase-changed:Wednesday, 12. September 2018 21:32 UTC

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1792239/+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 1791545] Re: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838]

Thanks for the update.  I'll mark this bug as Fix Released.  Just move
it back to confirmed if the bug comes back.

** Changed in: linux (Ubuntu Cosmic)
   Status: Confirmed => Fix Released

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

Title:
  watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838]

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  FYI, getting this error message on my gemini-lake-based laptop when
  running the daily 18.10 build

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callen 1691 F pulseaudio
  Date: Sun Sep  9 13:13:25 2018
  Failure: oops
  InstallationDate: Installed on 2018-08-16 (23 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723)
  MachineType: Acer Swift SF114-32
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=6f91c64c-cc9a-40f5-9813-9d1c329cfaeb ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.name: Sapporo_GL_S
  dmi.board.vendor: GLK
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL_S:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.family: Swift 1
  dmi.product.name: Swift SF114-32
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791545/+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 1792141] Re: Screen problems two monitors, with all kernels over 4.13, so 4.14, 4.15 etc.

2018-09-12 Thread Martin Eisenstein

Hello everybody, thank you for your messages. This is my first bug
message. Therefore I ask for a little patience. Which logs are needed?
I'll upload it as soon as I know which logs it should be.

I have not yet tested the new kernel but will do it immediately, (I just
got home from work ...;))

The problems with the two monitors I did not have with my old system.
MSI 370 chipset motherboard and AMD 8350 processor and the Radeo R9 380
graphics card. There I could run the two superimposed and with the
kernels over 4.13. So I suspect a connection with the new Ryzen or the
X470 Chispatz.

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

Title:
  Screen problems two monitors, with all kernels over 4.13, so 4.14,
  4.15 etc.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As of kernel 4.13, I have problems with my two screens. This affects all 
kernels over 4.13, that is 4.14, 4.15, and so on.
  Affected are computers with current AMD hardware.
  My computer system:
  Motherboard: MSI X470 GAMING M7 AC
  CPU: AMD Ryzen 7 2700
  Graphics card: MSI R9 380

  If you want to use both monitors on top of each other, the ad
  management crashes and only one monitor is activated. The other
  monitor is deactivated and can not be reactivated afterwards.

  For all kernels under 4.13, ad management works perfectly.

  Affected are all Ubuntu / Linux Mint / Arch versions. It does not
  matter if you use Xfce, Mate, Cinamon or Gnome. The above stated
  versions have all been tested and delivered, with my hardware, the
  same results.

  I have found other users who have the same bug:
  https://www.linuxmintusers.de/index.php?topic=49574.msg698322#msg698322

  Is this bug known and how can I fix it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792141/+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 1792239] [NEW] linux-azure: 4.18.0-1001.1~18.04.1 -proposed tracker

2018-09-12 Thread Marcelo Cerri

Public bug reported:

This bug is for tracking the 4.18.0-1001.1~18.04.1 upload package. This
bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: Invalid

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-beta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-candidate
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-edge
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/snap-release-to-stable
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/stakeholder-signoff
 Importance: Medium
 Assignee: Joshua R. Poulson (jrp)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux-azure (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live

** Tags added: kernel-release-tracking-bug

** Tags added: kernel-release-tracking-bug-live

** Also affects: linux-azure (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Tags added: bionic

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

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-beta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-candidate
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-edge
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/snap-release-to-stable

[Kernel-packages] [Bug 1791746] Re: linux-aws: 4.4.0-1030.33 -proposed tracker

2018-09-12 Thread Brad Figg

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1791745
  phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1030.33 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1791745
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791746/+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 1741409] Re: stress smoke test hang with dev test on AWS Xenial kernel

2018-09-12 Thread Stefan Bader

It might be fixed if AWS runs a Xen hypervisor which has the following
patch included (this is from the development tree of upstream Xen, so
will be part of Xen-4.12).

commit be07023be115c94b7fbb51d2ef6f421ddd680de8
Author: Roger Pau Monné 
Date:   Tue Jul 24 15:54:18 2018 +0200

x86/vhpet: add support for level triggered interrupts

One can never say for sure what AWS runs, so whether its fixed or not
can only be found out by trial and error.

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

Title:
  stress smoke test hang with dev test on AWS Xenial kernel

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  The test will hang on dev STARTING, and get killed by the timeout
  setting.

  DEBUG| [stdout] dccp PASSED
  DEBUG| [stdout] dentry STARTING
  DEBUG| [stdout] dentry RETURNED 0
  DEBUG| [stdout] dentry PASSED
  DEBUG| [stdout] dev STARTING

  No interesting output in dmesg:
  [8.281861] random: nonblocking pool is initialized
  [8.338335] ppdev: user-space parallel port driver
  [   11.662848] cgroup: new mount options do not match the existing 
superblock, will be ignored
  [   12.272168] systemd[1]: Started ACPI event daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1045-aws 4.4.0-1045.54
  ProcVersionSignature: User Name 4.4.0-1045.54-aws 4.4.98
  Uname: Linux 4.4.0-1045-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  Date: Fri Jan  5 06:47:45 2018
  Ec2AMI: ami-a2e544da
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1741409/+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 1791545] Re: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838]

2018-09-12 Thread Chris Allen

It stopped since the last 4.17 kernel update via apt so I think it's
been resolved.

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

Title:
  watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838]

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  FYI, getting this error message on my gemini-lake-based laptop when
  running the daily 18.10 build

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  callen 1691 F pulseaudio
  Date: Sun Sep  9 13:13:25 2018
  Failure: oops
  InstallationDate: Installed on 2018-08-16 (23 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723)
  MachineType: Acer Swift SF114-32
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=6f91c64c-cc9a-40f5-9813-9d1c329cfaeb ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [gpg-agent:838]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.name: Sapporo_GL_S
  dmi.board.vendor: GLK
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd05/02/2018:svnAcer:pnSwiftSF114-32:pvrV1.03:rvnGLK:rnSapporo_GL_S:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.family: Swift 1
  dmi.product.name: Swift SF114-32
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

2018-09-12 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/1792215

Title:
  watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:271]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System will not load desktop graphical display after entering login
  details at the login screen. Only way to launch GUI is to drop to a
  terminal at the login screen and then run startx at which point the
  GUI does load up

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1567 F pulseaudio
ck429  2554 F pulseaudio
  Date: Wed Sep 12 20:23:02 2018
  Failure: oops
  InstallationDate: Installed on 2018-09-12 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  MachineType: HP HP ENVY Laptop 13-ah0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:271]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8482
  dmi.board.vendor: HP
  dmi.board.version: 69.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/07/2018:svnHP:pnHPENVYLaptop13-ah0xxx:pvrType1ProductConfigId:rvnHP:rn8482:rvr69.28:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 13-ah0xxx
  dmi.product.sku: 4EY21EA#ABU
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188119/+files/WifiSyslog.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16

[Kernel-packages] [Bug 1789949] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1789949/+attachment/5188118/+files/UdevDb.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16 days ago)

[Kernel-packages] [Bug 1789949] nmcli-con.txt

apport information

** Attachment added: "nmcli-con.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188120/+files/nmcli-con.txt

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

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface

[Kernel-packages] [Bug 1789949] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1789949/+attachment/5188104/+files/Lspci.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16 days ago)

[Kernel-packages] [Bug 1789949] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1789949/+attachment/5188117/+files/RfKill.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16 days ago)

[Kernel-packages] [Bug 1789949] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188116/+files/PulseList.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16 days

[Kernel-packages] [Bug 1789949] NetDevice.ra0.txt

apport information

** Attachment added: "NetDevice.ra0.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188108/+files/NetDevice.ra0.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26

[Kernel-packages] [Bug 1789949] NetDevice.wlp4s0.txt

apport information

** Attachment added: "NetDevice.wlp4s0.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188109/+files/NetDevice.wlp4s0.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on

[Kernel-packages] [Bug 1792215] [NEW] watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:271]

2018-09-12 Thread chris forrest

Public bug reported:

System will not load desktop graphical display after entering login
details at the login screen. Only way to launch GUI is to drop to a
terminal at the login screen and then run startx at which point the GUI
does load up

ProblemType: KernelOops
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-7-generic 4.18.0-7.8
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1567 F pulseaudio
  ck429  2554 F pulseaudio
Date: Wed Sep 12 20:23:02 2018
Failure: oops
InstallationDate: Installed on 2018-09-12 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
MachineType: HP HP ENVY Laptop 13-ah0xxx
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:271]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8482
dmi.board.vendor: HP
dmi.board.version: 69.28
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/07/2018:svnHP:pnHPENVYLaptop13-ah0xxx:pvrType1ProductConfigId:rvnHP:rn8482:rvr69.28:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY Laptop 13-ah0xxx
dmi.product.sku: 4EY21EA#ABU
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-kerneloops cosmic kernel-oops

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

Title:
  watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:271]

Status in linux package in Ubuntu:
  New

Bug description:
  System will not load desktop graphical display after entering login
  details at the login screen. Only way to launch GUI is to drop to a
  terminal at the login screen and then run startx at which point the
  GUI does load up

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1567 F pulseaudio
ck429  2554 F pulseaudio
  Date: Wed Sep 12 20:23:02 2018
  Failure: oops
  InstallationDate: Installed on 2018-09-12 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  MachineType: HP HP ENVY Laptop 13-ah0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:2:271]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8482
  dmi.board.vendor: HP
  dmi.board.version: 69.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/07/2018:svnHP:pnHPENVYLaptop13-ah0xxx:pvrType1ProductConfigId:rvnHP:rn8482:rvr69.28:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY Laptop 13-ah0xxx
  dmi.product.sku: 4EY21EA#ABU
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792215/+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 1792144] Re: missing patch for i915 in 4.15.0-33-generic => black screen on boot

2018-09-12 Thread sh-dvl

yes, unfortunately we still see this bug (else we haven't filed it
here).

so, when the given patch is already added in -23 and we're using -33, it
seems to be that that patch doesn't help for our problem, even the
behaviour is really similar.

so. should we file a bug at freedesktop?

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

Title:
  missing patch for i915 in 4.15.0-33-generic => black screen on boot

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

Bug description:
  we must use i915 with modesetting, because else the hdmi-audio isn't
  available.

  enabling modesetting, the monitor went black immediately after dmesg:

  fb: switching to inteldrmfb from EFI VGA
  Console: switching to colour dummy device 80x25
  [drm] Replacing VGA console driver

  for this bug at https://bugs.freedesktop.org/show_bug.cgi?id=105549
  there seems to be a patch available which doesn't seem to be
  integrated in last available xenial-kernel 4.15.0-33-generic.

  please integrate it in next kernel-update.

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

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188101/+files/Dependencies.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26

[Kernel-packages] [Bug 1789949] IpAddr.txt

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1789949/+attachment/5188102/+files/IpAddr.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16 days ago)

[Kernel-packages] [Bug 1789949] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188103/+files/IwConfig.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16 days

[Kernel-packages] [Bug 1789949] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188100/+files/CurrentDmesg.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26

[Kernel-packages] [Bug 1789949] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188113/+files/ProcEnviron.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16

[Kernel-packages] [Bug 1789949] PciNetwork.txt

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188111/+files/PciNetwork.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16

[Kernel-packages] [Bug 1789949] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188114/+files/ProcInterrupts.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on

[Kernel-packages] [Bug 1789949] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188112/+files/ProcCpuinfoMinimal.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on

[Kernel-packages] [Bug 1789949] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188115/+files/ProcModules.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16

[Kernel-packages] [Bug 1789949] NetworkManager.conf.txt

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188110/+files/NetworkManager.conf.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on

[Kernel-packages] [Bug 1789949] NetDevice.enp3s0.txt

apport information

** Attachment added: "NetDevice.enp3s0.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188106/+files/NetDevice.enp3s0.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on

[Kernel-packages] [Bug 1789949] NetDevice.lo.txt

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1789949/+attachment/5188107/+files/NetDevice.lo.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26

[Kernel-packages] [Bug 1789949] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1789949/+attachment/5188105/+files/Lsusb.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16 days ago)

[Kernel-packages] [Bug 1789949] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1789949/+attachment/5188099/+files/CRDA.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/1789949

Title:
  WiFi-Stick TP-Link T2UH not working

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.

  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.

  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 

  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  a  2175 F pulseaudio
   /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
   /dev/snd/controlC0:  a  2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (16 days ago)

[Kernel-packages] [Bug 1791790] Re: Kernel hang on drive pull caused by incomplete backport for bug 1597908

I built a test kernel with commit 4e9b6f20828ac880dbc1fa2fdbafae779473d1af.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1791790

Can you test this kernel and see if it resolves this bug?

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the
linux-modules, linux-modules-extra and linux-image-unsigned .deb packages.

Thanks in advance!

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

Title:
Kernel hang on drive pull caused by incomplete backport for bug
1597908

Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress

The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's
most recent 4.4 kernel.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4e9b6f20828ac880dbc1fa2fdbafae779473d1af

Let me know what additional information is needed. Thanks!

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

[Kernel-packages] [Bug 1789949] Re: WiFi-Stick TP-Link T2UH not working

apport information

** Tags added: apport-collected

** Description changed:

  TP-Link Archer T2UH, AC600, version 1
  After plugging in the WiFi-Stick, nothing happens on Ubuntu(while on Windows 
10 I was immediately able to connect).
  So searching on the web I found some kind of "solution", which it not really 
working well.
  on various Forums I found the links to the following drivers:
  https://github.com/chenhaiq/mt7610u_wifi_sta_v3002_dpo_20130916
  https://github.com/Anty0/mt7610u_wifi_sta_v3002_dpo_20130916/
  From which the first works well on Debian, but fail to compile on ubuntu.
  And the second one works on ubuntu, but makes the network manager laggin, and 
won't let me reconnect after some random disconnects, until I restart the 
NetworkManager.That happens quite often. Plugging it out and back in, also 
requires "sudo systemctl restart NetworkManager" to reconnect. To compile this, 
I had to manually copy-paste the git, cause the readme description seemed to be 
referring to another package.
  Also, I don't know how secure these drivers are.
  There is also a driver from TP-Link, which is too old and doesnt work with 
newer kernels.
  Mediatek also has driver, but i didnt know how to build them.
  
  Before launching "ubuntu-bug" i unplugged and replugged the WiFi-Stick
  (thus showing "no networks") and im connected to the internet through
  another (built-in) device.
  
  For the TP-Link T2UH the lsusb will show:
  Bus 003 Device 012: ID 148f:761a Ralink Technology, Corp. 
  
  while disconnected the "ip a" will show:
  9: ra0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
  
  lsb_release -rd shows:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  
  Not sure if this is a bug of the Network Manager, or just a missing feature. 
Maybe it would be good to have a driver for it from the repository. Or to 
somehow integrate the chip-support into the system.
  Thank you.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 30 17:51:16 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-08-26 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 10.66.0.1 dev wlp4s0 proto dhcp metric 600 
   10.66.0.0/18 dev wlp4s0 proto kernel scope link src 10.66.42.112 metric 600 
   169.254.0.0/16 dev wlp4s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0  wifi  connected/org/freedesktop/NetworkManager/Devices/4  
uni-ms 1dee93213-b593-434a-b2eb-5504f3b5bfc7  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   ra0 wifi  unmanaged/org/freedesktop/NetworkManager/Devices/5  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  a  2175 F pulseaudio
+  /dev/snd/pcmC0D0p:   a  2175 F...m pulseaudio
+  /dev/snd/controlC0:  a  2175 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ InstallationDate: Installed on 2018-08-26 (16 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ IpRoute:
+  default via 10.65.0.1 dev wlp4s0 proto dhcp metric 600 
+  default via 10.66.0.1 dev ra0 proto dhcp metric 601 
+  10.65.0.0/20 dev wlp4s0 proto kernel scope link src 10.65.3.214 metric 600 
+  10.66.0.0/18 dev ra0 proto kernel scope link src 10.66.33.131 metric 601 
+

[Kernel-packages] [Bug 1792174] Re: Xenial update to 4.4.148 stable release

2018-09-12 Thread Stefan Bader

Skipped:
* "x86/paravirt: Fix spectre-v2 mitigations for paravirt
  guests (CVE-2018-15594)
* "x86/speculation: Protect against userspace-userspace
  spectreRSB" (CVE-2018-15572)

Skipped patches from L1TF (CVE-2018-3620, CVE-2018-3646):
* "x86/speculation/l1tf: Increase 32bit PAE
  __PHYSICAL_PAGE_SHIFT"
* "x86/mm: Move swap offset/type up in PTE to work around
  erratum"
* "x86/mm: Fix swap entry comment and macro"
* "x86/speculation/l1tf: Change order of offset/type in
  swap entry"
* "x86/speculation/l1tf: Protect swap entries against L1TF"
* "x86/speculation/l1tf: Protect PROT_NONE PTEs against
  speculation"
* "x86/speculation/l1tf: Make sure the first page is
  always reserved"
* "x86/speculation/l1tf: Add sysfs reporting for l1tf"
* "x86/speculation/l1tf: Disallow non privileged high MMIO
  PROT_NONE mappings"
* "x86/speculation/l1tf: Limit swap file size to MAX_PA/2"
* "x86/bugs: Move the l1tf function and define pr_fmt
  properly"
* "x86/speculation/l1tf: Extend 64bit swap file size limit"
* "x86/cpufeatures: Add detection of L1D cache flush
  support."
* "x86/speculation/l1tf: Protect PAE swap entries against
  L1TF"
* "x86/speculation/l1tf: Fix up pte->pfn conversion for
  PAE"
* "x86/speculation/l1tf: Invert all not present mappings"
* "x86/speculation/l1tf: Make pmd/pud_mknotpresent()
  invert"
* "x86/mm/pat: Make set_memory_np() L1TF safe"
* "x86/speculation/l1tf: Fix up CPU feature flags"
* "x86/speculation/l1tf: Unbreak
  !__HAVE_ARCH_PFN_MODIFY_ALLOWED architectures"


Modified "mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1" to do the 
changes to arch/x86/include/asm/pgtable_types.h only (because changes to 
arch/x86/include/asm/pgtable_64.h were already present).


** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15572

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15594

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3620

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3646

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.148 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.148 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.148 stable release shall be
- applied:
+ The following patches from the 4.4.148 stable release shall be applied:
+ * ext4: fix check to prevent initializing reserved inodes
+ * tpm: fix race condition in tpm_common_write()
+ * ipv4+ipv6: Make INET*_ESP select CRYPTO_ECHAINIV
+ * fork: unconditionally clear stack on fork
+ * parisc: Enable CONFIG_MLONGCALLS by default
+ * parisc: Define mb() and add memory barriers to assembler unlock sequences
+ * xen/netfront: don't cache skb_shinfo()
+ * ACPI / LPSS: Add missing prv_offset setting for byt/cht PWM devices
+ * scsi: sr: Avoid that opening a CD-ROM hangs with runtime power management 
enabled
+ * root dentries need RCU-delayed freeing
+ * fix mntput/mntput race
+ * fix __legitimize_mnt()/mntput() race
+ * IB/core: Make testing MR flags for writability a static inline function
+ * IB/mlx4: Mark user MR as writable if actual virtual memory is writable
+ * IB/ocrdma: fix out of bounds access to local buffer
+ * ARM: dts: imx6sx: fix irq for pcie bridge
+ * kprobes/x86: Fix %p uses in error messages
+ * x86/irqflags: Provide a declaration for native_save_fl
+ * UBUNTU: SAUCE: Sync pgtable_64.h with upstream stable
+ * mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1
+ * UBUNTU: SAUCE: Sync pgtable-3level.h with upstream stable
+ * UBUNTU: SAUCE: Sync pgtable.h with upstream stable
+ * mm: Add vm_insert_pfn_prot()
+ * mm: fix cache mode tracking in vm_insert_mixed()
+ * x86/mm/kmmio: Make the tracer robust against L1TF
+ * x86/init: fix build with CONFIG_SWAP=n
+ * Linux 4.4.148

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

Title:
  Xenial update to 4.4.148 stable release

Status in linux package

[Kernel-packages] [Bug 1791323] Re: XFS fallocate implementation incorrectly reports ENOSPC

2018-09-12 Thread Charles Hathaway

Hi Joseph,

Give me a moment to try testing the upstream kernel; I haven't done that
before.

This issue was first reported by a customer sometime back, we worked
around it by changing the way we called fallocate. I believe I confirmed
it back in 16.04, but I haven't tested beyond that.

Charles

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

Title:
  XFS fallocate implementation incorrectly reports ENOSPC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When given an offset of 0 and a length, fallocate (man 2 fallocate)
  reports ENOSPC if the size of the file + the length to be allocated is
  greater than the available space.

  Example below using the fallocate command (man 1 fallocate) for
  simplicity; the issue is with the logic backing the system call.

  chathaway@bender:~/temp$ fallocate -l 1GB example.img
  chathaway@bender:~/temp$ mkfs.xfs example.img 
  meta-data=example.imgisize=512agcount=4, agsize=61035 blks
   =   sectsz=512   attr=2, projid32bit=1
   =   crc=1finobt=1, sparse=0, rmapbt=0, 
reflink=0
  data =   bsize=4096   blocks=244140, imaxpct=25
   =   sunit=0  swidth=0 blks
  naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
  log  =internal log   bsize=4096   blocks=855, version=2
   =   sectsz=512   sunit=0 blks, lazy-count=1
  realtime =none   extsz=4096   blocks=0, rtextents=0
  chathaway@bender:~/temp$ sudo modprobe loop
  chathaway@bender:~/temp$ mkdir mnt
  chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/
  chathaway@bender:~/temp$ cd mnt
  chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt
  chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt
  fallocate: fallocate failed: No space left on device
  chathaway@bender:~/temp/mnt$ df -h .
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/loop0  951M  766M  185M  81% /home/chathaway/temp/mnt

  Expected behaviour: because we allocate 768MB starting at offset 0,
  and have 951MB on the disk, we would expect that the allocation should
  be fine. Other filesystem behave this way (for example, ext4).

  Thanks!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chathaway   2608 F pulseaudio
   /dev/snd/controlC1:  chathaway   2608 F pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.04
  MachineType: ASUSTeK COMPUTER INC. UX303LN
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img 
root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 
systemd.show_status=false splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm docker sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LN.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791745] Re: linux: 4.4.0-136.162 -proposed tracker

2018-09-12 Thread Steve Beattie

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-136.162 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1791746 (linux-aws), bug 1791747 (linux-lts-xenial)
  derivatives: bug 1791749 (linux-aws), bug 1791750 (linux-euclid), bug 1791751 
(linux-kvm), bug 1791752 (linux-raspi2), bug 1791753 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1791745/+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 1707887] Re: Failed to build libhugetlbfs-2.20 from source on 4.4 / 3.13 Trusty ARM64

Sam, does this need to be chased down?

 very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

Title:
  Failed to build libhugetlbfs-2.20 from source on 4.4 / 3.13 Trusty
  ARM64

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It will fail to build libhugetlbfs verison 2.20 for SRU regression-
  test on 3.13 ARM64

  It's ok on 4.10 / 4.4 ARM64, but not 4.4.0-88.111~14.04.1 and
  3.13.0-126.175 ARM64

  Looks like it's failing with:
  LD64 (hugelink_rw test) obj64/linkhuge_rw
  /usr/bin/ld: final link failed: File truncated

  This is not a regression. As this issue has been seen before.

  Complete make log:
  $ make
 VERSION
  version string: 2.20
 CC64 obj64/elflink.o
 AS64 obj64/sys-aarch64elf.o
 CC64 obj64/hugeutils.o
 CC64 obj64/version.o
 CC64 obj64/init.o
 CC64 obj64/morecore.o
 CC64 obj64/debug.o
 CC64 obj64/alloc.o
 CC64 obj64/shm.o
 CC64 obj64/kernel-features.o
 LD64 (shared) obj64/libhugetlbfs.so
 AR64 obj64/libhugetlbfs.a
 CC64 obj64/init_privutils.o
 LD64 (shared) obj64/libhugetlbfs_privutils.so
 CCHOST obj/init_privutils.o
 CCHOST obj/debug.o
 CCHOST obj/hugeutils.o
 CCHOST obj/kernel-features.o
 ARHOST obj/libhugetlbfs_privutils.a
 CC64 obj64/gethugepagesize.o
 CC64 obj64/testutils.o
 CC64 obj64/libtestutils.o
 LD64 (lib test) obj64/gethugepagesize
 CC64 obj64/test_root.o
 LD64 (lib test) obj64/test_root
 CC64 obj64/find_path.o
 LD64 (lib test) obj64/find_path
 CC64 obj64/unlinked_fd.o
 LD64 (lib test) obj64/unlinked_fd
 CC64 obj64/misalign.o
 LD64 (lib test) obj64/misalign
 CC64 obj64/readback.o
 LD64 (lib test) obj64/readback
 CC64 obj64/truncate.o
 LD64 (lib test) obj64/truncate
 CC64 obj64/shared.o
 LD64 (lib test) obj64/shared
 CC64 obj64/private.o
 LD64 (lib test) obj64/private
 CC64 obj64/fork-cow.o
 LD64 (lib test) obj64/fork-cow
 CC64 obj64/empty_mounts.o
 LD64 (lib test) obj64/empty_mounts
 CC64 obj64/large_mounts.o
 LD64 (lib test) obj64/large_mounts
 CC64 obj64/meminfo_nohuge.o
 LD64 (lib test) obj64/meminfo_nohuge
 CC64 obj64/ptrace-write-hugepage.o
 LD64 (lib test) obj64/ptrace-write-hugepage
 CC64 obj64/icache-hygiene.o
  icache-hygiene.c: In function ‘test_once’:
  icache-hygiene.c:158:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, 0);
 ^
  icache-hygiene.c:162:12: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
 ftruncate(fd, 0);
  ^
  icache-hygiene.c:171:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, hpage_size);
 ^
  icache-hygiene.c:177:11: warning: ignoring return value of ‘ftruncate’, 
declared with attribute warn_unused_result [-Wunused-result]
ftruncate(fd, 0);
 ^
 LD64 (lib test) obj64/icache-hygiene
 CC64 obj64/slbpacaflush.o
 LD64 (lib test) obj64/slbpacaflush
 CC64 obj64/chunk-overcommit.o
 LD64 (lib test) obj64/chunk-overcommit
 CC64 obj64/mprotect.o
 LD64 (lib test) obj64/mprotect
 CC64 obj64/alloc-instantiate-race.o
  alloc-instantiate-race.c: In function ‘thread_racer’:
  alloc-instantiate-race.c:114:6: warning: variable ‘rc’ set but not used 
[-Wunused-but-set-variable]
int rc;
^
 LD64 (lib test) obj64/alloc-instantiate-race
 CC64 obj64/mlock.o
 LD64 (lib test) obj64/mlock
 CC64 obj64/truncate_reserve_wraparound.o
 LD64 (lib test) obj64/truncate_reserve_wraparound
 CC64 obj64/truncate_sigbus_versus_oom.o
 LD64 (lib test) obj64/truncate_sigbus_versus_oom
 CC64 obj64/map_high_truncate_2.o
 LD64 (lib test) obj64/map_high_truncate_2
 CC64 obj64/truncate_above_4GB.o
 LD64 (lib test) obj64/truncate_above_4GB
 CC64 obj64/direct.o
 LD64 (lib test) obj64/direct
 CC64 obj64/misaligned_offset.o
 LD64 (lib test) obj64/misaligned_offset
 CC64 obj64/brk_near_huge.o
 LD64 (lib test) obj64/brk_near_huge
 CC64 obj64/task-size-overrun.o
 LD64 (lib test)

[Kernel-packages] [Bug 1791979] ProcModules.txt

2018-09-12 Thread Tadeusz

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1791979/+attachment/5188083/+files/ProcModules.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/1791979

Title:
  USB enumeration problem / Wandboard Quad rev. b1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The USB devices are detected/enumerated correctly with system start, but when 
disconnected later and connected once again are not recognized / enumerated 
anymore.
  Also removal of ci_hdrc_imx module causes the system hard lock without any 
information printed in the console.
  Tried with 4.15.0-29 4.15.0-33 4.15.0-34

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic armv7l
  .etc.asound.conf:
   defaults.pcm.card 1
   defaults.ctl.card 1
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-34-generic.
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: armhf
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info:
   Card hw:0 'DWHDMI'/'DW-HDMI rev 0x0a, irq 19'
 Mixer name : ''
 Components : ''
 Controls  : 0
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  Card1.Amixer.info:
   Card hw:1 'imxspdif'/'imx-spdif'
 Mixer name : ''
 Components : ''
 Controls  : 7
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Date: Tue Sep 11 18:11:46 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb:
   Bus 001 Device 002: ID 03f0:4117 Hewlett-Packard LaserJet 1018
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttymxc0,115200 root=/dev/sda2
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  StagingDrivers: imx_media imx_media_csi imx_media_ic imx_media_vdic 
imx_media_capture imx_media_common
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  .etc.asound.conf:
   defaults.pcm.card 1
   defaults.ctl.card 1
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-34-generic.
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: armhf
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info:
   Card hw:0 'DWHDMI'/'DW-HDMI rev 0x0a, irq 19'
 Mixer name : ''
 Components : ''
 Controls  : 0
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  Card1.Amixer.info:
   Card hw:1 'imxspdif'/'imx-spdif'
 Mixer name : ''
 Components : ''
 Controls  : 7
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb:
   Bus 001 Device 002: ID 03f0:4117 Hewlett-Packard LaserJet 1018
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttymxc0,115200 root=/dev/sda2
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  StagingDrivers: imx_media_capture imx_media imx_media_vdic imx_media_ic 
imx_media_csi imx_media_common
  Tags:  bionic staging
  Uname: Linux 4.15.0-34-generic armv7l
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False

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

2018-09-12 Thread Tadeusz

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1791979/+attachment/5188079/+files/CurrentDmesg.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/1791979

Title:
  USB enumeration problem / Wandboard Quad rev. b1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The USB devices are detected/enumerated correctly with system start, but when 
disconnected later and connected once again are not recognized / enumerated 
anymore.
  Also removal of ci_hdrc_imx module causes the system hard lock without any 
information printed in the console.
  Tried with 4.15.0-29 4.15.0-33 4.15.0-34

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic armv7l
  .etc.asound.conf:
   defaults.pcm.card 1
   defaults.ctl.card 1
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-34-generic.
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: armhf
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info:
   Card hw:0 'DWHDMI'/'DW-HDMI rev 0x0a, irq 19'
 Mixer name : ''
 Components : ''
 Controls  : 0
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  Card1.Amixer.info:
   Card hw:1 'imxspdif'/'imx-spdif'
 Mixer name : ''
 Components : ''
 Controls  : 7
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Date: Tue Sep 11 18:11:46 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb:
   Bus 001 Device 002: ID 03f0:4117 Hewlett-Packard LaserJet 1018
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttymxc0,115200 root=/dev/sda2
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  StagingDrivers: imx_media imx_media_csi imx_media_ic imx_media_vdic 
imx_media_capture imx_media_common
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  .etc.asound.conf:
   defaults.pcm.card 1
   defaults.ctl.card 1
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-34-generic.
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: armhf
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info:
   Card hw:0 'DWHDMI'/'DW-HDMI rev 0x0a, irq 19'
 Mixer name : ''
 Components : ''
 Controls  : 0
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  Card1.Amixer.info:
   Card hw:1 'imxspdif'/'imx-spdif'
 Mixer name : ''
 Components : ''
 Controls  : 7
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb:
   Bus 001 Device 002: ID 03f0:4117 Hewlett-Packard LaserJet 1018
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttymxc0,115200 root=/dev/sda2
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  StagingDrivers: imx_media_capture imx_media imx_media_vdic imx_media_ic 
imx_media_csi imx_media_common
  Tags:  bionic staging
  Uname: Linux 4.15.0-34-generic armv7l
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791979/+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 1741437] Re: SRU testing node rumford tend to fail with directory-concurrent.sh.ext2 test in ubuntu_ecryptfs test suite

hi sam, Should we be looking at this in this current sru cycle?

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

Title:
  SRU testing node rumford tend to fail with directory-
  concurrent.sh.ext2 test in ubuntu_ecryptfs test suite

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Reproduce rate 5 out of 5.

  This issue failed frequently on this node, and can be seen on older 4.13 
kernel.
  And this test can pass on the other node. so that this should not be 
considered as a regression in this cycle.
   
  Steps:
  1. Deploy an Artful system
  2. bzr branch --use-existing-dir lp:ecryptfs
  3. sudo tests/run_one.sh -K -t directory-concurrent.sh -b 100 -D 
/mnt/image -l /mnt/lower -u /mnt/upper -f ext2
  directory-concurrent  failed to fork child
  failed to fork child
  ...
  failed to fork child
  failed to fork child
  failed to fork child
  failed to fork child
  failed to fork child
  FAIL

  Test Summary:
  0 passed
  1 failed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-22-generic 4.13.0-22.25
  ProcVersionSignature: User Name 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  5 08:24 seq
   crw-rw 1 root audio 116, 33 Jan  5 08:24 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDmesg:
   [ 5185.596138] EXT4-fs (loop0): mounting ext2 file system using the ext4 
subsystem
   [ 5185.639876] EXT4-fs (loop0): mounted filesystem without journal. Opts: 
user_xattr,acl
  Date: Fri Jan  5 09:51:42 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic.efi.signed 
root=UUID=051b34ce-dfed-4e36-aa78-851c5a284ee4 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-22-generic N/A
   linux-backports-modules-4.13.0-22-generic  N/A
   linux-firmware 1.169.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1741437/+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 1741409] Re: stress smoke test hang with dev test on AWS Xenial kernel

Been sorting through many of the ubuntu-kernel-tests bugs.

This is one of the few that actually is being worked.

Stefan, any update on this? Should this be/ Has it been fixed? I can
revisit once i finish cleaning up the list

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Sean Feole (sfeole)

** Changed in: ubuntu-kernel-tests
   Importance: Undecided => Medium

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

Title:
  stress smoke test hang with dev test on AWS Xenial kernel

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-aws package in Ubuntu:
  In Progress

Bug description:
  The test will hang on dev STARTING, and get killed by the timeout
  setting.

  DEBUG| [stdout] dccp PASSED
  DEBUG| [stdout] dentry STARTING
  DEBUG| [stdout] dentry RETURNED 0
  DEBUG| [stdout] dentry PASSED
  DEBUG| [stdout] dev STARTING

  No interesting output in dmesg:
  [8.281861] random: nonblocking pool is initialized
  [8.338335] ppdev: user-space parallel port driver
  [   11.662848] cgroup: new mount options do not match the existing 
superblock, will be ignored
  [   12.272168] systemd[1]: Started ACPI event daemon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1045-aws 4.4.0-1045.54
  ProcVersionSignature: User Name 4.4.0-1045.54-aws 4.4.98
  Uname: Linux 4.4.0-1045-aws x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  Date: Fri Jan  5 06:47:45 2018
  Ec2AMI: ami-a2e544da
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: t2.nano
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-aws
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1741409/+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 1729510] Re: libhugetlbfs failed with "[Errno 95] Operation not supported" on s390x zVM

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

Title:
  libhugetlbfs failed with "[Errno 95] Operation not supported" on s390x
  zVM

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps:
  1. sudo apt-get install git python-minimal -y
  2. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
  3. git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
  4. rm -fr autotest/client/tests
  5. ln -sf ~/autotest-client-tests autotest/client/tests
  6. AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/libhugetlbfs/control

  It will failed with the following python code piece when trying to
  access /proc/sys/vm/nr_hugepages:

  utils.write_one_line('/proc/sys/vm/nr_hugepages',
  str(pages_requested))

  With error message:
    [Errno 95] Operation not supported

  For Xenial, the error message is:
[Errno 524] Unknown error 524

  This issue is not a regression.

  Full error log:

  $ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client
  /autotest-local --verbose autotest/client/tests/libhugetlbfs/control

  07:20:37 INFO | Writing results to 
/home/ubuntu/autotest/client/results/default
  07:20:37 DEBUG| Initializing the state engine
  07:20:37 DEBUG| Persistent state client.steps now set to []
  07:20:37 DEBUG| Persistent option harness now set to None
  07:20:37 DEBUG| Persistent option harness_args now set to None
  07:20:37 DEBUG| Selected harness: standalone
  07:20:48 INFO | START timestamp=1509607248localtime=Nov 
02 07:20:48
  07:20:48 DEBUG| Persistent state client._record_indent now set to 1
  07:20:48 INFO |   START   libhugetlbfslibhugetlbfs
timestamp=1509607248localtime=Nov 02 07:20:48
  07:20:48 DEBUG| Persistent state client._record_indent now set to 2
  07:20:48 DEBUG| Persistent state client.unexpected_reboot now set to 
('libhugetlbfs', 'libhugetlbfs')
  07:20:49 DEBUG| Running 'apt-get install --yes --force-yes build-essential 
git gcc'
  07:20:50 DEBUG| [stdout] Reading package lists...
  07:20:50 DEBUG| [stdout] Building dependency tree...
  07:20:50 DEBUG| [stdout] Reading state information...
  07:20:50 DEBUG| [stdout] build-essential is already the newest version 
(12.4ubuntu1).
  07:20:50 DEBUG| [stdout] gcc is already the newest version (4:7.2.0-1ubuntu1).
  07:20:50 DEBUG| [stdout] git is already the newest version 
(1:2.14.1-1ubuntu4).
  07:20:50 DEBUG| [stdout] The following packages were automatically installed 
and are no longer required:
  07:20:50 DEBUG| [stdout]   containerd linux-headers-4.13.0-14 
linux-headers-4.13.0-14-generic
  07:20:50 DEBUG| [stdout]   linux-image-4.13.0-14-generic 
linux-image-extra-4.13.0-14-generic runc
  07:20:50 DEBUG| [stdout] Use 'sudo apt autoremove' to remove them.
  07:20:50 DEBUG| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not 
upgraded.
  07:20:50 ERROR| [stderr] W: --force-yes is deprecated, use one of the options 
starting with --allow instead.
  07:20:50 DEBUG| Running 'which gcc'
  07:20:50 DEBUG| [stdout] /usr/bin/gcc
  07:20:53 ERROR| Exception escaping from test:
  Traceback (most recent call last):
    File "/home/ubuntu/autotest/client/shared/test.py", line 378, in _exec
  _cherry_pick_call(self.initialize, *args, **dargs)
    File "/home/ubuntu/autotest/client/shared/test.py", line 738, in 
_cherry_pick_call
  return func(*p_args, **p_dargs)
    File "/home/ubuntu/autotest/client/tests/libhugetlbfs/libhugetlbfs.py", 
line 39, in initialize
  str(pages_requested))
    File "/home/ubuntu/autotest/client/shared/utils.py", line 408, in 
write_one_line
  open_write_close(filename, line.rstrip('\n') + '\n')
    File "/home/ubuntu/autotest/client/shared/utils.py", line 416, in 
open_write_close
  f.close()
  IOError: [Errno 95] Operation not supported

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic s390x
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Thu Nov

[Kernel-packages] [Bug 1792100] Re: Boot hangs at "loading initial ramdisk..."

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  Boot hangs at "loading initial ramdisk..."

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  I cannot load a kernel beyond 4.15.0-32-generic on my machine.
  Both 4.15.0-33-generic and 4.15.0-34-generic hang at "loading initial 
ramdisk...".

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kms2233 F pulseaudio
   /dev/snd/controlC1:  kms2233 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 10:52:00 2018
  HibernationDevice: RESUME=UUID=c3d34d19-9e9e-4967-ac45-f1d699cf5eef
  InstallationDate: Installed on 2018-01-05 (249 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Precision Tower 7810
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=90d43be7-a2f7-4500-8b88-9bd7a549d96d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (132 days ago)
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A27
  dmi.board.name: 0KJCC5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA27:bd06/25/2018:svnDellInc.:pnPrecisionTower7810:pvr:rvnDellInc.:rn0KJCC5:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792100/+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 1740017] Re: sprs test from kvm-unit-tests will hang on PowerPC

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

Title:
  sprs test from kvm-unit-tests will hang on PowerPC

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We have switched our kvm-unit-test test suite from archive tarball to 
upstream repo recently.
  And now the sprs test will hang on the ppc64le system.

  12/24 04:18:33 DEBUG| utils:0153| [stdout] MIGRATION=yes TESTNAME=sprs
  TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf -smp 1 -append '-w'

  It was failing with this test with the version of our archived tarball
  bug 1723904 (but still failing on Xenial, and 4.10 kernel on Xenail, 
therefore it has something to do with the qemu on Zesty.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1740017/+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 1720951] Re: seccomp test from upstream failed with "global.KILL_process"

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

Title:
  seccomp test from upstream failed with "global.KILL_process"

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps:
   1. git clone https://github.com/torvalds/linux.git
   2. make -C linux/tools/testing/selftests/seccomp all
   3. home/ubuntu/linux/tools/testing/selftests/seccomp/seccomp_bpf

  [ RUN  ] global.KILL_thread
  [   OK ] global.KILL_thread
  [ RUN  ] global.KILL_process
  seccomp_bpf.c:714:global.KILL_process:Expected 0 (0) != (((signed char) 
(((status) & 0x7f) + 1) >> 1) > 0) (0)
  global.KILL_process: Test terminated by assertion
  [ FAIL ] global.KILL_process

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: User Name 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct  3 04:55 seq
   crw-rw 1 root audio 116, 33 Oct  3 04:55 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Tue Oct  3 06:53:20 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Intel Corporation S2600CWR
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=5170da90-e3b5-4db0-bea9-22859499daf4 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2016
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C610.86B.01.01.0018.072020161249
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600CWR
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H12884-261
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.0018.072020161249:bd07/20/2016:svnIntelCorporation:pnS2600CWR:pvr:rvnIntelCorporation:rnS2600CWR:rvrH12884-261:cvn..:ct17:cvr..:
  dmi.product.family: Family
  dmi.product.name: S2600CWR
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1720951/+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 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3

** Changed in: linux (Ubuntu)
Importance: Undecided => Medium

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

Title:
Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in
Cosmic 18.10, works with 18.04.1 desktop installer live image

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

Bug description:
Repro:
1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully
updated

-> Keyboard backlight should come on or change but doesn't. The
gnome-shell pop-up icon for the keyboard backlight appears for both
keys, but the icon's "progress" bar is not visible.

Kernel version is linux-image-4.17.0-9-generic

This is the same in X and Wayland session. In case it matters, Nvidia
binary drivers are installed but Nvidia is switched off via Prime
setting in nvidia-settings. Running with Intel drivers

The keyboard backlight works perfectly when booting from the 18.04.1
desktop live image. When turning on light with 18.04.1, it is off
again after rebooting into 18.10. (However 18.04.1 seems to freeze
when shutting down from menu, I have to hard-shut it off).

Most other important Fn+Fx special keys on this laptop work (display
brightness, touchpad off, sound) except for the airplane mode key. However the
airplane mode key only fails in gnome-shell but works on the console (this is
filed as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367)
(Not working are a key that seems to mean "display off" and another of
unclear purpose that never worked on any laptop I ever saw, maybe "presentation
mode" as it seems to depict a flip chart or projection screen).

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.17.0-9-generic 4.17.0-9.10
ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
Uname: Linux 4.17.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: angela16196 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 7 22:08:12 2018
InstallationDate: Installed on 2018-09-05 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 13d3:5256 IMC Networks
Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX561UD
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.17.0-9-generic N/A
linux-backports-modules-4.17.0-9-generic N/A
linux-firmware1.174
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/06/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX561UD.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX561UD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: ZenBook Flip
dmi.product.name: UX561UD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

[Kernel-packages] [Bug 1791411] Re: screen definition

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  screen definition

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i can't specify screen 1600x1200

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-77-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Sep  8 10:39:44 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 3.16.0-77-generic, i686: installed
   nvidia-304, 304.135, 3.16.0-77-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:0229]
  InstallationDate: Installed on 2018-09-07 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: Dell Inc. Vostro 1700
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-77-generic 
root=UUID=83e07ade-7c87-484b-83e9-ef2d5681e758 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/14/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0HX767
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd06/14/2007:svnDellInc.:pnVostro1700:pvr:rvnDellInc.:rn0HX767:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Vostro 1700
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Sep  8 10:37:09 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791411/+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 1738152] Re: generic/308 for xfs in xfstests test suite will hang on i386 system

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

Title:
  generic/308 for xfs in xfstests test suite will hang on i386 system

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This test case (generic/308) will hang on i386 system and gets killed
  when our timeout setting kicks-in.

  Discussion could be found here:
  https://lkml.org/lkml/2015/9/26/466

  The patch in the mail thread was not applied.

  I think we need to update our repo first to see if this is something
  related to the xfstest test suite itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-103-generic (not installed)
  ProcVersionSignature: User Name 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic i686
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 33 Dec 14 08:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed 
with exit code 1:
  CRDA: N/A
  Date: Thu Dec 14 09:08:47 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=username/i386/ga-16.04/xenial/daily/boot-kernel 
nomodeset 
root=squash:http://10.246.72.3:5248/images/username/i386/ga-16.04/xenial/daily/squashfs
 ro ip=hostname:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc 
cloud-config-url=http://10.246.72.3:5240/MAAS/metadata/latest/by-id/k6mn4w/?op=get_preseed
 apparmor=0 log_host=10.246.72.3 log_port=514 BOOTIF=01-e0:07:1b:f5:e5:2c
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-103-generic N/A
   linux-backports-modules-4.4.0-103-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd12/27/2015:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1738152/+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 1791979] UdevDb.txt

2018-09-12 Thread Tadeusz

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1791979/+attachment/5188084/+files/UdevDb.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/1791979

Title:
  USB enumeration problem / Wandboard Quad rev. b1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The USB devices are detected/enumerated correctly with system start, but when 
disconnected later and connected once again are not recognized / enumerated 
anymore.
  Also removal of ci_hdrc_imx module causes the system hard lock without any 
information printed in the console.
  Tried with 4.15.0-29 4.15.0-33 4.15.0-34

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic armv7l
  .etc.asound.conf:
   defaults.pcm.card 1
   defaults.ctl.card 1
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-34-generic.
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: armhf
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info:
   Card hw:0 'DWHDMI'/'DW-HDMI rev 0x0a, irq 19'
 Mixer name : ''
 Components : ''
 Controls  : 0
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  Card1.Amixer.info:
   Card hw:1 'imxspdif'/'imx-spdif'
 Mixer name : ''
 Components : ''
 Controls  : 7
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  Date: Tue Sep 11 18:11:46 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb:
   Bus 001 Device 002: ID 03f0:4117 Hewlett-Packard LaserJet 1018
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttymxc0,115200 root=/dev/sda2
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  StagingDrivers: imx_media imx_media_csi imx_media_ic imx_media_vdic 
imx_media_capture imx_media_common
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  .etc.asound.conf:
   defaults.pcm.card 1
   defaults.ctl.card 1
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-34-generic.
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: armhf
  ArecordDevices:  List of CAPTURE Hardware Devices 
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info:
   Card hw:0 'DWHDMI'/'DW-HDMI rev 0x0a, irq 19'
 Mixer name : ''
 Components : ''
 Controls  : 0
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  Card1.Amixer.info:
   Card hw:1 'imxspdif'/'imx-spdif'
 Mixer name : ''
 Components : ''
 Controls  : 7
 Simple ctrls  : 0
  Card1.Amixer.values:
   
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb:
   Bus 001 Device 002: ID 03f0:4117 Hewlett-Packard LaserJet 1018
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttymxc0,115200 root=/dev/sda2
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  StagingDrivers: imx_media_capture imx_media imx_media_vdic imx_media_ic 
imx_media_csi imx_media_common
  Tags:  bionic staging
  Uname: Linux 4.15.0-34-generic armv7l
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791979/+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 1791537] Re: 4.15 linux kernel - unable to access the internet

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  4.15 linux kernel - unable to access the internet

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Budgie was running great until sometime this week, post minimal update
  - per notification saying i needed to. Ever since then, say September
  7th ish, i can not access any internet. Wifi, ethernet, usb wifi,
  anything.

  I tried to run the command ubuntu-bug linux as directed, but when I
  tried to submit was given error, something about unable to translate.
  Makes sense since I can’t connect to the internet.  I then reverted
  back to the previous linux kernel version and was able to access the
  internet.

  The command did show that I am on 4.15 kernel. If this is the issue,
  can someone tell me how to move up to 4.17, if that is the fix? If
  that is not the fix - ideas?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kop2872 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Sep  9 14:37:19 2018
  HibernationDevice: RESUME=UUID=fc67782e-72fa-4d11-be6c-d91d09848f01
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57c4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.87
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A2
  dmi.board.vendor: HP
  dmi.board.version: 91.1E
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A2:rvr91.1E:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791537/+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 1747661] Re: ecryptfs complains about "Error encrypting page" on 4.13 Artful

closing bug per last comment

** Changed in: ubuntu-kernel-tests
   Status: New => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  ecryptfs complains about "Error encrypting page" on 4.13 Artful

Status in ubuntu-kernel-tests:
  Won't Fix
Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Artful:
  Won't Fix

Bug description:
  This issue was spotted on my computer for work (CID 201408-15386),
  installed with disk encrypted

  The following error message could be found in syslog

  ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-4]
  ecryptfs_writepage: Error encrypting page (upper index [0x])

  Found this issue because the system is crashing frequently today, but
  I think this is not the cause of the crash, as the error can be found
  on last Thursday and Friday but the system is stable.

  Check through my archived syslog, this issue was first spotted on Jan.
  30 19:00, 4.13.0-32 was install earlier that day in the morning.

  For older log before Jan.30 (Jan.25 / 26) with 4.13.0-31, there is no
  such error message in the syslog.


  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sam1530 F pulseaudio
   /dev/snd/controlC0:  sam1530 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Feb  6 19:54:10 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=3a922472-e01e-42fa-a61d-7d7f645e3672
  InstallationDate: Installed on 2017-07-12 (209 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Latitude 7250
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-24 (13 days ago)
  dmi.bios.date: 12/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0N248W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd12/26/2016:svnDellInc.:pnLatitude7250:pvr:rvnDellInc.:rn0N248W:rvrX02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 7250
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1747661/+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 1791389] Re: usb 3-4: device descriptor read/64, error -110

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  usb 3-4: device descriptor read/64, error -110

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

Bug description:
  Hello,

  dmesg:
  [7.776138] usb 3-4: device descriptor read/64, error -110
  [8.048909] usb 3-4: New USB device found, idVendor=0cf3, idProduct=9271, 
bcdDevice= 1.08
  [8.048917] usb 3-4: New USB device strings: Mfr=16, Product=32, 
SerialNumber=48
  [8.048922] usb 3-4: Product: USB2.0 WLAN
  [8.048927] usb 3-4: Manufacturer: ATHEROS
  [8.048939] usb 3-4: SerialNumber: 12345

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2485 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2485 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 20:39:28 2018
  InstallationDate: Installed on 2017-10-13 (329 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-7-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  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:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.sku: System SKUNumber
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1791389/+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 1738178] Re: ubuntu_ecryptfs tests failed on Xenial s390x instances

Hi  Sam, looks like this bug was somewhat fixed , still an issue?

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   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/1738178

Title:
  ubuntu_ecryptfs tests failed on Xenial s390x instances

Status in ubuntu-kernel-tests:
  Incomplete
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  In the ubuntu_ecryptfs test suite, it constantly fail with 28 test
  cases on all s390x instances (zVM / zKVM / Ubuntu on LPAR) with Xenial
  kernel.

   miscdev-bad-count.sh.xfs 3 sec   Failed
    extend-file-random.sh.xfs   5 sec   Failed
    trunc-file.sh.xfs   3 sec   Failed
    directory-concurrent.sh.xfs 2 sec   Failed
    file-concurrent.sh.xfs  5 sec   Failed
    lp-994247.sh.xfs3 sec   Failed
    llseek.sh.xfs   4 sec   Failed
    lp-469664.sh.xfs5 sec   Failed
    lp-524919.sh.xfs5 sec   Failed
    lp-509180.sh.xfs6 sec   Failed
    lp-613873.sh.xfs11 sec  Failed
    lp-745836.sh.xfs10 sec  Failed
    lp-870326.sh.xfs6 sec   Failed
    lp-885744.sh.xfs9 sec   Failed
    lp-926292.sh.xfs9 sec   Failed
    inotify.sh.xfs  10 sec  Failed
    mmap-bmap.sh.xfs9 sec   Failed
    mmap-close.sh.xfs   10 sec  Failed
    mmap-dir.sh.xfs 9 sec   Failed
    read-dir.sh.xfs 6 sec   Failed
    setattr-flush-dirty.sh.xfs  5 sec   Failed
    inode-race-stat.sh.xfs  5 sec   Failed
    lp-911507.sh.xfs5 sec   Failed
    lp-561129.sh.xfs5 sec   Failed
    mknod.sh.xfs7 sec   Failed
    link.sh.xfs 3 sec   Failed
    xattr.sh.xfs5 sec   Failed
    namelen.sh.xfs  4 sec   Failed

  Tested with the upstream repo from lp:ecryptfs (revno 894)
  There is not much error message to see, these test cases just exit with 1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-104-generic 4.4.0-104.127
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [104616.551505] EXT4-fs (loop0): mounting ext3 file system using the ext4 
subsystem
   [104616.574291] EXT4-fs (loop0): mounted filesystem with ordered data mode. 
Opts: user_xattr,acl,commit=600,barrier=1,data=ordered
  Date: Thu Dec 14 05:33:55 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-104-generic N/A
   linux-backports-modules-4.4.0-104-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1738178/+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 1739560] Re: Trusty arm64 system will hang on libhugetlbfs shmoverride_linked test

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

Title:
  Trusty arm64 system will hang on libhugetlbfs shmoverride_linked test

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps:
  1. Deploy an ARM64 system with Trusty
  2. Install necessary packages
  3. git clone --depth=1 -b next 
https://github.com/libhugetlbfs/libhugetlbfs.git
  4. make  BUILDTYPE=NATIVEONLY
  5. execute the run_test.py in tests directory

  Results:
   * you will see it stuck at shmoverride_linked test, no output for this test 
in syslog

  truncate_reserve_wraparound (2M: 64): PASS
  truncate_sigbus_versus_oom (2M: 64):  PASS
  get_huge_pages (2M: 64):  PASS
  shmoverride_linked (2M: 64):

  This issue can be reproduced in 3.13.0-137 and 3.13.0-138 in proposed.
  As we didn't run any regression-test on this node between 3.13.0-135 ~ 
3.13.0-136 (this node was broken).

  This test cannot be built on ARM64 before (till 3.13.0-133, we have
  changed to use the upstream repo since then) therefore I think this
  can be considered as not a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-137-generic 3.13.0-137.186
  ProcVersionSignature: User Name 3.13.0-137.186-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-137-generic aarch64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg:

  Date: Thu Dec 21 07:49:12 2017
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   enp1s0d1  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-137-generic N/A
   linux-backports-modules-3.13.0-137-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1739560/+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 1738962] Re: Failed to build upstream bpf test on Artful ARM64

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

Title:
  Failed to build upstream bpf test on Artful ARM64

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps:
   1. git clone --depth=1 https://github.com/torvalds/linux.git
   2. sudo apt-get install clang llvm libcap-dev libelf-dev build-essential 
   3. Change the Makefile in linux/tools/testing/selftests/ to build bpf test 
only
   4. make

  Result:
   * It complains about missing headers, like the 'bits/libc-header-start.h', 
but it can be found in /usr/include/aarch64-linux-gnu/bits/
   
  $ find /usr -name libc-header-start.h
  /usr/include/aarch64-linux-gnu/bits/libc-header-start.h

  $ dpkg -S libc-header-start.h
  libc6-dev:arm64: /usr/include/aarch64-linux-gnu/bits/libc-header-start.h


  
  $ make
  make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/bpf'
  make -C ../../../lib/bpf 
OUTPUT=/home/ubuntu/linux/tools/testing/selftests/bpf/
  make[2]: Entering directory '/home/ubuntu/linux/tools/lib/bpf'
  make[2]: Leaving directory '/home/ubuntu/linux/tools/lib/bpf'
  make -C ../../../lib/bpf 
OUTPUT=/home/ubuntu/linux/tools/testing/selftests/bpf/
  make[2]: Entering directory '/home/ubuntu/linux/tools/lib/bpf'
  make[2]: Leaving directory '/home/ubuntu/linux/tools/lib/bpf'
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_verifier.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_verifier
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_tag.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_tag
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_maps.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_maps
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_lru_map.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_lru_map
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_lpm_map.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_lpm_map
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_progs.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_progs
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_align.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_align
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_verifier_log.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_verifier_log
  gcc -Wall -O2 -I../../../include/uapi -I../../../lib 
-I../../../../include/generated  -I../../../includetest_dev_cgroup.c 
/home/ubuntu/linux/tools/testing/selftests/bpf/libbpf.a 
/home/ubuntu/linux/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_dev_cgroup
  clang -I. -I./include/uapi -I../../../include/uapi \
 -Wno-compare-distinct-pointer-types  \
 -O2 -target bpf -emit-llvm -c 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_pkt_access.c -o - |  \
  llc -march=bpf -mcpu=generic -filetype=obj -o 
/home/ubuntu/linux/tools/testing/selftests/bpf/test_pkt_access.o
  In file included from

[Kernel-packages] [Bug 1791513] Re: system hang after resume from standby with i915 in bionic

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  system hang after resume from standby with i915 in bionic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've upgraded my i7-2600 system (cpu with integrated i915) from ubuntu
  16.04 x86_64 to 18.04.1 x86_64 using do-release-upgrade.

  It works fine except hanging after resume from standby. The system
  does to standby (suspend to ram) when idle automatically. When it text
  console, it resumes fine from pm-suspend, but after switching to
  graphics the system hangs (magic sysrq does not work either). The
  problem occurs with 4.15.0-33-generic and is also present with
  mainline 4.18.7.

  kern.log ends with: "kernel: PM: suspend entry (deep)". When resuming
  into text console first, I get

  kernel: [  117.272524] PM: suspend entry (deep)
  kernel: [  117.272526] PM: Syncing filesystems ... done.
  kernel: [  117.354945] Freezing user space processes ... (elapsed 0.001 
seconds) done.
  kernel: [  117.356708] OOM killer disabled.
  kernel: [  117.356709] Freezing remaining freezable tasks ... (elapsed 0.001 
seconds) done.
  kernel: [  117.357920] Suspending console(s) (use no_console_suspend to debug)
  kernel: [  117.359239] serial 00:05: disabled
  kernel: [  117.359734] parport_pc 00:02: disabled
  kernel: [  117.388004] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
  kernel: [  117.388119] sd 3:0:0:0: [sdb] Stopping disk
  kernel: [  117.395014] sd 2:0:0:0: [sda] Synchronizing SCSI cache
  kernel: [  117.395123] sd 2:0:0:0: [sda] Stopping disk
  kernel: [  118.008264] ACPI: Preparing to enter system sleep state S3
  kernel: [  118.009459] PM: Saving platform NVS memory
  kernel: [  118.009851] Disabling non-boot CPUs ...
  kernel: [  118.025074] smpboot: CPU 1 is now offline
  kernel: [  118.049113] smpboot: CPU 2 is now offline
  kernel: [  118.073695] smpboot: CPU 3 is now offline
  kernel: [  118.096142] IRQ 16: no longer affine to CPU4
  kernel: [  118.097170] smpboot: CPU 4 is now offline
  kernel: [  118.120153] IRQ 25: no longer affine to CPU5
  kernel: [  118.120163] IRQ 30: no longer affine to CPU5
  kernel: [  118.120168] IRQ 31: no longer affine to CPU5
  kernel: [  118.120174] IRQ 33: no longer affine to CPU5
  kernel: [  118.120182] IRQ 38: no longer affine to CPU5
  kernel: [  118.121192] smpboot: CPU 5 is now offline
  kernel: [  118.144160] IRQ 23: no longer affine to CPU6
  kernel: [  118.144165] IRQ 27: no longer affine to CPU6
  kernel: [  118.144173] IRQ 32: no longer affine to CPU6
  kernel: [  118.144186] IRQ 37: no longer affine to CPU6
  kernel: [  118.145194] smpboot: CPU 6 is now offline
  kernel: [  118.169244] smpboot: CPU 7 is now offline
  kernel: [  118.170914] ACPI: Low-level resume complete
  kernel: [  118.170954] PM: Restoring platform NVS memory
  kernel: [  118.172220] Enabling non-boot CPUs ...
  kernel: [  118.172262] x86: Booting SMP configuration:
  kernel: [  118.172262] smpboot: Booting Node 0 Processor 1 APIC 0x2
  kernel: [  118.175214]  cache: parent cpu1 should not be sleeping
  kernel: [  118.175439] CPU1 is up
  kernel: [  118.175481] smpboot: Booting Node 0 Processor 2 APIC 0x4
  kernel: [  118.178697]  cache: parent cpu2 should not be sleeping
  kernel: [  118.178941] CPU2 is up
  kernel: [  118.178988] smpboot: Booting Node 0 Processor 3 APIC 0x6
  kernel: [  118.182312]  cache: parent cpu3 should not be sleeping
  kernel: [  118.182576] CPU3 is up
  kernel: [  118.182623] smpboot: Booting Node 0 Processor 4 APIC 0x1
  kernel: [  118.185397]  cache: parent cpu4 should not be sleeping
  kernel: [  118.185713] CPU4 is up
  kernel: [  118.185762] smpboot: Booting Node 0 Processor 5 APIC 0x3
  kernel: [  118.188483]  cache: parent cpu5 should not be sleeping
  kernel: [  118.188788] CPU5 is up
  kernel: [  118.188823] smpboot: Booting Node 0 Processor 6 APIC 0x5
  kernel: [  118.191562]  cache: parent cpu6 should not be sleeping
  kernel: [  118.191888] CPU6 is up
  kernel: [  118.191926] smpboot: Booting Node 0 Processor 7 APIC 0x7
  kernel: [  118.194646]  cache: parent cpu7 should not be sleeping
  kernel: [  118.194994] CPU7 is up
  kernel: [  118.202014] ACPI: Waking up from system sleep state S3
  kernel: [  118.222689] usb usb3: root hub lost power or was reset

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

** Tags added: kernel-da-key

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information

[Kernel-packages] [Bug 1791323] Re: XFS fallocate implementation incorrectly reports ENOSPC

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc3

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  XFS fallocate implementation incorrectly reports ENOSPC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When given an offset of 0 and a length, fallocate (man 2 fallocate)
  reports ENOSPC if the size of the file + the length to be allocated is
  greater than the available space.

  Example below using the fallocate command (man 1 fallocate) for
  simplicity; the issue is with the logic backing the system call.

  chathaway@bender:~/temp$ fallocate -l 1GB example.img
  chathaway@bender:~/temp$ mkfs.xfs example.img 
  meta-data=example.imgisize=512agcount=4, agsize=61035 blks
   =   sectsz=512   attr=2, projid32bit=1
   =   crc=1finobt=1, sparse=0, rmapbt=0, 
reflink=0
  data =   bsize=4096   blocks=244140, imaxpct=25
   =   sunit=0  swidth=0 blks
  naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
  log  =internal log   bsize=4096   blocks=855, version=2
   =   sectsz=512   sunit=0 blks, lazy-count=1
  realtime =none   extsz=4096   blocks=0, rtextents=0
  chathaway@bender:~/temp$ sudo modprobe loop
  chathaway@bender:~/temp$ mkdir mnt
  chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/
  chathaway@bender:~/temp$ cd mnt
  chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt
  chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt
  fallocate: fallocate failed: No space left on device
  chathaway@bender:~/temp/mnt$ df -h .
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/loop0  951M  766M  185M  81% /home/chathaway/temp/mnt

  Expected behaviour: because we allocate 768MB starting at offset 0,
  and have 951MB on the disk, we would expect that the allocation should
  be fine. Other filesystem behave this way (for example, ext4).

  Thanks!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chathaway   2608 F pulseaudio
   /dev/snd/controlC1:  chathaway   2608 F pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.04
  MachineType: ASUSTeK COMPUTER INC. UX303LN
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img 
root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 
systemd.show_status=false splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm docker sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LN.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1791323] Re: XFS fallocate implementation incorrectly reports ENOSPC

Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced.   If this is a
regression, we can perform a kernel bisect to identify the commit that
introduced the problem.


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

Title:
  XFS fallocate implementation incorrectly reports ENOSPC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When given an offset of 0 and a length, fallocate (man 2 fallocate)
  reports ENOSPC if the size of the file + the length to be allocated is
  greater than the available space.

  Example below using the fallocate command (man 1 fallocate) for
  simplicity; the issue is with the logic backing the system call.

  chathaway@bender:~/temp$ fallocate -l 1GB example.img
  chathaway@bender:~/temp$ mkfs.xfs example.img 
  meta-data=example.imgisize=512agcount=4, agsize=61035 blks
   =   sectsz=512   attr=2, projid32bit=1
   =   crc=1finobt=1, sparse=0, rmapbt=0, 
reflink=0
  data =   bsize=4096   blocks=244140, imaxpct=25
   =   sunit=0  swidth=0 blks
  naming   =version 2  bsize=4096   ascii-ci=0 ftype=1
  log  =internal log   bsize=4096   blocks=855, version=2
   =   sectsz=512   sunit=0 blks, lazy-count=1
  realtime =none   extsz=4096   blocks=0, rtextents=0
  chathaway@bender:~/temp$ sudo modprobe loop
  chathaway@bender:~/temp$ mkdir mnt
  chathaway@bender:~/temp$ sudo mount -o loop ./example.img ./mnt/
  chathaway@bender:~/temp$ cd mnt
  chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt
  chathaway@bender:~/temp/mnt$ sudo fallocate -l 768MB -o 0 hello.txt
  fallocate: fallocate failed: No space left on device
  chathaway@bender:~/temp/mnt$ df -h .
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/loop0  951M  766M  185M  81% /home/chathaway/temp/mnt

  Expected behaviour: because we allocate 768MB starting at offset 0,
  and have 951MB on the disk, we would expect that the allocation should
  be fine. Other filesystem behave this way (for example, ext4).

  Thanks!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chathaway   2608 F pulseaudio
   /dev/snd/controlC1:  chathaway   2608 F pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.04
  MachineType: ASUSTeK COMPUTER INC. UX303LN
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 
initrd=\EFI\Pop_OS-c80adbe3-92ed-45ea-a314-7e7c694d0161\initrd.img 
root=UUID=c80adbe3-92ed-45ea-a314-7e7c694d0161 ro quiet loglevel=0 
systemd.show_status=false splash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm docker sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 09/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX303LN.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX303LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX303LN.204:bd09/01/2014:svnASUSTeKCOMPUTERINC.:pnUX303LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX303LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791323/+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 1729849] Re: mkfs.xfs complains about /dev/sdb2 is busy on Xenial

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

** Changed in: linux (Ubuntu Xenial)
   Status: Confirmed => 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/1729849

Title:
  mkfs.xfs complains about /dev/sdb2 is busy on Xenial

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete

Bug description:
  This issue is reproducible on two different nodes in our testpool,
  fozzie and rizzo, both with 4.4.0-98-generic amd64.

  On a clean install system with a scratch drive sdb available.
   
  Steps:
  1. sudo parted /dev/sdb mklabel -s gpt
  2. sudo parted /dev/sdb mkpart -s p1 xfs 1MiB 2MiB
  3. sudo parted /dev/sdb mkpart -s p2 xfs 20001MiB 4MiB
  4. sudo mkfs.xfs -f /dev/sdb1
  5. sudo mkfs.xfs -f /dev/sdb2

  Result:
  mkfs.xfs: cannot open /dev/sdb2: Device or resource busy

  
  In my test case, there are 5 partitions from sdb1 to sdb5, only sdb2 will 
fail with this. And this happens on both nodes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: User Name 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  3 12:07 seq
   crw-rw 1 root audio 116, 33 Nov  3 12:07 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Nov  3 12:37:59 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R310
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd09/06/2013:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA09:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1729849/+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 1791790] Re: Kernel hang on drive pull caused by incomplete backport for bug 1597908

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  Kernel hang on drive pull caused by incomplete backport for bug
  1597908

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  A bug was introduced when backporting the fix for
  http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu
  16.04 LTS 4.4 kernels >= 4.4.0-36, and many other non-LTS kernels.

  This patch changes the context in which timeout work is scheduled for
  block devices in the kernel. Previously, timeout work was executed
  directly from the timer callback that fired when a deadline was met.
  After the patch, timeout work is scheduled using a background work
  queue. This means that by the time the work executes, the device queue
  which originally scheduled the work could be torn down. In order to
  prevent this, the patch takes a reference on the device queue when
  executing the timeout work.

  The problem is that the last reference to this queue can be removed
  before the timeout work can be executed. During teardown, the block
  system executes a freeze followed by a drain. The freeze drops the
  last reference on the queue. The drain tries to clean up any
  outstanding work, including timeout work. After a freeze, the timeout
  work in the background queue is unable to obtain a reference, and
  exits early without completing work. The work is now permanently stuck
  in the queue and it will never be completed. The drain in the device
  teardown path spins indefinitely.

  The bug manifests as a hang that looks like this:
  [] schedule+0x35/0x80
  [] hpsa_scan_start+0x109/0x140 [hpsa]
  [] ? wake_atomic_t_function+0x60/0x60
  [] hpsa_rescan_ctlr_worker+0x1d2/0x652 [hpsa]
  [] process_one_work+0x165/0x480
  [] worker_thread+0x4b/0x4c0
  [] ? process_one_work+0x480/0x480
  [] kthread+0xd8/0xf0
  [] ? kthread_create_on_node+0x1e0/0x1e0
  [] ret_from_fork+0x3f/0x70
  [] ? kthread_create_on_node+0x1e0/0x1e0

  The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's 
most recent 4.4 kernel.
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4e9b6f20828ac880dbc1fa2fdbafae779473d1af

  We hit this bug nearly 100% of the time on some of our HP hardware.
  The HPSA driver has a tendency to aggressively remove missing devices,
  so it widens the race. As a result, we've been building our own kernel
  with this patch applied. It would be really nice if we could get it
  into mainline Ubuntu.

  Let me know what additional information is needed. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791790/+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 1747630] Re: Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

very old bug, with no action on it, marking bug as incomplete and will
close in 5 days if no update.

** Changed in: ubuntu-kernel-tests
   Status: New => Incomplete

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

Title:
  Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

Status in ubuntu-kernel-tests:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue can be reproduced in 3.2.0-133 in proposed and 3.2.0-131.
  So it should not be considered as a regression.

  We didn't spot this issue before, until I'm testing 3.2 kernel on one
  of the laptop (CID 201307-13930) in Cert lab instead of using our
  regular regression-testing test pool from kernel team this cycle.

    ==
    FAIL: test_022_aslr_hardy_vdso (__main__.KernelSecurityTest)
    ASLR of vdso
    --
    Traceback (most recent call last):
  File "./test-kernel-security.py", line 1863, in test_022_aslr_hardy_vdso
    self._test_aslr('vdso', expected)
  File "./test-kernel-security.py", line 1795, in _test_aslr
    self._test_aslr_all(area, expected, "unlimited stack %s" % area)
  File "./test-kernel-security.py", line 1772, in _test_aslr_all
    self._test_aslr_exec(area, expected, target, name)
  File "./test-kernel-security.py", line 1765, in _test_aslr_exec
    self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1134, in assertShellExitEquals
    self.assertEqual(expected, rc, msg + result + report)
    AssertionError: unlimited stack vdso native:
    Got exit code 1, expected 0
    Command: './aslr', 'vdso', '--verbose'
    Output:
    Checking ASLR of vdso:
     0x40022000
     0x40022000
     0x40022000
    FAIL: ASLR not functional (vdso always at 0x40022000)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1747630/+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 1731455] Re: generic/166 test for btrfs from xfstests will hang