Seems like it need ipu3 driver, which gets included since v5.0-rc1 [1].
[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc1/
--
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/1812114
Po-Hsu, thanks for the report. I'm not sure the lock down kernel config
makes sense for ppc64el and s390x, and the qa-regression-testing script
should be updated to reflect that.
The linux-kvm case is possibly worth adjusting the config, I need to
discuss that more with the Security Team.
--
You
verified on LNG5-DVT1-C2 for bionic , it works as expected.
image: X36
BIOS:0.5.4
package: thermald 1.7.0-5ubuntu2
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** 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
** 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
For clarification, this happens on the target after it comes back from
the reboot and restores the iSCSI configuration.
--
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/1812086
Title:
kern
Public bug reported:
The psock_tpacket in the net test from ubuntu_kernel_selftests failed with B-KVM
$ sudo ./psock_tpacket
test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory
Look into the code, it seems that this file not found error is caused by
the attempt to access /proc/k
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) =>
Taihsi
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) =>
Taihsi
** Description changed:
+ [Impact]
+ On Thinkpad X1 Extreme with two SSDs, if NQN in the firmware are
+ identical, then only one drive can be seen. NQN is supposed to be unique
+ but some Intel drives do not follow that.
+
+ [Fix]
+ The device-supplied subnqn is ignored and one will be generated
** Description changed:
USB DAC stops playing sound after a second.
- I had problem with kernel 4.15.
- So, I tried upgrading to 4.19 but still issue persists.
+ I had problem with kernel 4.15.
+ So, I tried upgrading to 4.19 but still issue persists.
I think, we might need to add it to soun
** 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
Could you try this kernel?
If it works, I will upstream the patch.
** Attachment added: "linux-image-4.15.18+_4.15.18+-1_amd64.deb"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5229881/+files/linux-image-4.15.18+_4.15.18+-1_amd64.deb
--
You received this bug noti
To enable this kallsyms symbol, CONFIG_KALLSYMS must be enabled in the
kernel.
And this config is not enabled in:
X-KVM
B-KVM
C-KVM
** Summary changed:
- psock_tpacket from the net test in ubuntu_kernel_selftests fail on B-KVM
+ psock_tpacket from the net test in ubuntu_kernel_selftests fail
You have been subscribed to a public bug:
Problem description:
During our Linux distribution performance regression testing, we found
*significant* performance degradations on Ubuntu 16.04.5 LTS compared to
other major Linux distributions on s390x when running SPECint2017. Some
SPECint2017 micro-
Kernel in #82 should use smbus mode.
i2c-i801 should be loaded;
no kernel parameters needed;
Recognized input devices names:
touchpad:
"Synaptics TM3288-011"
Trackpoint:
"TPPS/2 Elan TrackPoint"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Public bug reported:
Problem description:
During our Linux distribution performance regression testing, we found
*significant* performance degradations on Ubuntu 16.04.5 LTS compared to
other major Linux distributions on s390x when running SPECint2017. Some
SPECint2017 micro-benchmarks show a per
the dmesg about disconnect is manual disconnection of usb DAC
[ 5937.978117] usb 1-1.4.2: USB disconnect, device number 16
After fresh boot, if I plug-in the DAC the dmesg shows
[ 155.552404] usb 1-1.4.1: new full-speed USB device number 10 using xhci_hcd
[ 155.941031] usb 1-1.4.1: New USB dev
Thanks for the heads up, sounds very interesting!
I know you said you are still analyzing, so I'll wait ... so many
questions in my mind already :-)
But one thing to check up front - which gcc version are you using on
this test on Ubuntu and which one on the systems you compare?
** Also affects:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin16045
--
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/1812182
Title:
Performance degradation with SPECint2017
** Changed in: ubuntu-power-systems
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
nvme multipath does not report path rela
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
I have built 5.0 rc2 with "do_dkms_nvidia = false"
--
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/1811721
Title:
Mainline Kernel Builds Failing for > v4.20 for amd64 on
kernel.ubuntu.c
** 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
Could this be a race condition with the device file creation and start
of the hv-kvp-daemon.service?
[from /var/log/syslog]
Jan 16 10:26:45 kvp-disco-test systemd[1]: Started Hyper-V KVP Protocol Daemon.
...
Jan 16 10:26:45 kvp-disco-test KVP: KVP starting; pid is:213
Jan 16 10:26:45 kvp-disco-tes
Public bug reported:
This test will attempt to insert the test_bpf module, but this module
does not exist in KVM kernels:
$ sudo modprobe test_bpf
modprobe: FATAL: Module test_bpf not found in directory
/lib/modules/4.15.0-1028-kvm
The script:
$ sudo ./test_bpf.sh
test_bpf: [FAIL]
$ cat test_
** 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
** 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
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** 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 associ
** 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
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** 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 associ
** 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
And the exact kernel version is also of high interest - I assume the HWE
kernel was used (4.15) and not the GA kernel (4.4)?!
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** 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
backports: bug 1811847
** 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
Public bug reported:
This test failed because of the unsuccessful attempt to add a dummy device with
ip link command:
# devdummy="test-dummy0"
# ip link add name "$devdummy" type dummy
RTNETLINK answers: Operation not supported
selftests: rtnetlink.sh
=
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** 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
Forgot to mention: Downgrading linux-firmware from 1.173.3 to 1.173.2
made a single port work again.
Still cannot use two ports.
--
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/181
Public bug reported:
This test will attempt to insert the test_user_copy module, but this
module does not exist in KVM kernels:
# modprobe test_user_copy
modprobe: FATAL: Module test_user_copy not found in directory
/lib/modules/4.15.0-1028-kvm
The script:
if /sbin/modprobe -q test_user_copy; t
In Cosmic, this test can be skipped by checking the module existence.
So maybe we should fix this in the kernel (testing tool).
--
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/1812198
T
** 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
** 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
** 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
** 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
--- Comment From harih...@in.ibm.com 2019-01-17 06:33 EDT---
On the standard kernel also I am seeing the same values.
root@ltc-test:~# cat /sys/module/vhost/parameters/max_mem_regions
64
root@ltc-test:~# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.10 (Cosmic Cuttlefish)"
ID=ubuntu
ID_LI
** 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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** Changed in: ubuntu-power-systems
Status: Incomplete => 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/1796839
Title:
Only 64 Memory regions or dimms supported for Hotpl
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
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/1811846
Title:
linux: 4.4.0-142.168 -pro
** 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
backports: bug 1811857
Performance on NVMe has increased a lot.
-update kernel
Run status group 0 (all jobs):
READ: bw=1358MiB/s (1424MB/s), 1358MiB/s-1358MiB/s (1424MB/s-1424MB/s),
io=133GiB (142GB), run=19-19msec
-proposed kernel
Run status group 0 (all jobs):
READ: bw=1406MiB/s (1475MB/s), 1406MiB/s-1
** 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
backports: bug 1811847
** 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
And here is a kernel snap for testing:
http://people.canonical.com/~ppisati/lp1810797/dragonboard-
kernel_4.15.0-43.46~lp1810797_arm64.snap
hcitool has a problem accessing hci0 on Ubuntu core (at least, in my
tests), use bluetoothctl instead:
p-pisati@localhost:~$ sudo bluetoothctl
[NEW] Controll
** 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
The -proposed kernel works fine. Thanks.
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
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/1811856
Title:
linux: 3.13.0-165.215 -pr
--- Comment From heinz-werner_se...@de.ibm.com 2019-01-17 07:55 EDT---
Fix verified upfront via upstream integration, as verification statement from
IBM
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
** 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
backports: bug 1811847
** Also affects: linux (Ubuntu Disco)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
adjusting tags according to #11
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
thanks for looking into this issue and trying to fix it. I've installed your
kernel, however, the issue is still there (at least for me). I've attach my
dmesg log. The first suspend/resume at ~122 causes that the touchpad is not
working anymore. There is also
"[ 122.097687] psmouse serio1: Fai
** 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
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.15.0-1032.34 -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-t
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** 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 up
** 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
backports: bug 1811857
Hi Thorsten:
Failing log of "XXX Failed to disable mouse XXX" doesn't matter.
Actually in line:
[ 123.824705] psmouse serio2: trackpoint: Elan TrackPoint firmware: 0x06,
buttons: 3/3
This means trackpoint works well, I assume touchpad works too.
Did you ever use the touchpad?
Please try to use
Hi, the trackpoint worked well but the touchpad did not after the first
suspend/resume (I really did try to use it). However, I will test it
again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
** Changed in: kernel-sru-workflow/verification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/certification-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
** 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
Ugh, i think i was wrong, it is working. But directly after a resume the
touchpad is not working and can it can take quite an amount to work
(more than 30s)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
--- Comment From marc.beye...@de.ibm.com 2019-01-17 09:26 EDT---
Hi there, here are the answers to your questions:
- Regarding gcc versions: We are using the standard gcc versions of the
distros. This is gcc 5.4.0 on Ubuntu 16.04.5 LTS and 4.8.5 on the other
distros.
- Regarding kernel ve
Verification done on Cosmic (no errors seen on dmesg).
Waiting for verification on Bionic by the reporter.
root@shuckle:~# uname -a
Linux shuckle 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
root@shuckle:~# fdisk /dev/nvme0n1 # create one partition
I now have performed 5 suspend/resumes and the first 4 times the
touchpad did work 5-40s after the resume. However, after the 5th resume
the touchpad didn’t wake up again (waited 8min).
I also noticed that I can use the touchpad to perform clicks even if the
cursor is not moving (not by using the
** 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
backports: bug 1811847
** Changed in: kernel-sru-workflow/snap-certification-testing
Status: Confirmed => In Progress
--
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/1811419
Title:
linux: 4.15.0-44.47 -p
Just to be sure, since Ubuntu's gcc has "--enable-default-pie" I wanted to
check.
Do "the others" set pie by default as well?
Just want to make sure that their execution without explicit pie is -no-pie
while ours would then be -pie.
For your kernel thoughts - even though the first idea was alrea
Verification done on Xenial.
- server:
root@shuckle:~# uname -a
Linux shuckle 4.4.0-142-generic #168-Ubuntu SMP Wed Jan 16 21:00:45 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
root@shuckle:~# iptables -F
root@shuckle:~# iptables -A INPUT -p tcp -m tcp --syn --dport -m connlimit
--connlimit-abo
Public bug reported:
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
** 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
Verification done on Cosmic for regression on an older adapter model,
I/O stress (iozone) finishes successfully, no errors seen in dmesg.
Waiting for verification on Bionic by the reporter.
root@dixie:~# fdisk /dev/sdb # create one partition
root@dixie:~# mkfs.ext4 /dev/sdb1
root@dixie:~# mount /
** 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
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
** 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 workfl
Hi Thorsten:
Your case is very special, I never reproduce it.
Please pass "rmi_core.debug_flags=0x7" to kernel parameter, then boot, test and
upload the dmesg.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.4.0-1075.85 -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-te
I added the kernel parameter and did a suspend/resume and attached the
dmesg log. Btw I never noticed that the trackpoint didn’t survived
suspend/resume (which occasional also happens with 4.19.x)
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+at
Hi Thorsten:
Your dmesg is flushed by input log.
please upload "journalctl -b 0 -k"
--
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
** 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
Hi, here is the journalctl log
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5230010/+files/journalctl.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
I'm guessing this must be caused by one of the new firmware files for
AMD gpus. Can you please attach the output of running 'lspci -vvnn' in a
terminal? Thanks!
** Changed in: linux-firmware (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
1 - 100 of 182 matches
Mail list logo
