[Kernel-packages] [Bug 1770643] Re: Logitech QuickCam 4000 Pro halts system
** 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/1770643 Title: Logitech QuickCam 4000 Pro halts system Status in libv4l package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After switching from Fedora to Ubuntu (17.10 and now 18.04), whenever I plug my Logitech QuickCam 4000 Pro USB webcam and I start vlc or any other camera capture program, the memory of the program increases to maximum, as a consequence the system halt and the only way out is to reboot the machine. [ 663.031843] Linux video capture interface: v2.00 [ 663.039656] pwc: Logitech QuickCam 4000 Pro USB webcam detected. [ 663.557858] pwc: Registered as video0. [ 663.557925] input: PWC snapshot button as /devices/pci:00/:00:14.0/usb3/3-6/3-6.3/input/input14 [ 663.558101] usbcore: registered new interface driver Philips webcam --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1778 F pulseaudio /dev/snd/pcmC0D0p: bnv1778 F...m pulseaudio /dev/snd/controlC0: bnv1778 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (194 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (15 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libv4l/+bug/1770643/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/345498
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
New
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
New
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
New
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in openvswitch package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Merge proposal unlinked:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/345498
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
New
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
New
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
New
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in openvswitch package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1770013] Re: linux-aws: 4.4.0-1020.20 -proposed tracker
4.4.0-1058.67 - aws Regression test CMPL, RTB. Issue to note in x86_64 (aws): libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 1, bad config 3, only spotted on t2.small, passed on the rest ubuntu_docker_smoke_test - test case issue ubuntu_kvm_unit_tests - test skipped due to no KVM support ubuntu_lxc - lxc-test-ubunut failed (Failed to start networking in ubuntu-cloud container), only spotted on t2.small, passed on the rest Skipped / blacklisted: * ubuntu_ltp * ubuntu_seccomp * ubuntu_sysdig_smoke_test * ubuntu_zram_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- 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/1770013 Title: linux-aws: 4.4.0-1020.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1770011 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/1770013/+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 1750513] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140209/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] Re: Screen brightness control doesn't work
apport information ** Tags added: apport-collected bionic ** Description changed: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.9-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: lchr 2877 F pulseaudio + /dev/snd/controlC1: lchr 2877 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-04-04 (41 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) + MachineType: LENOVO 20HJS1NW00 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pl_PL.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-20-generic N/A + linux-backports-modules-4.15.0-20-generic N/A + linux-firmware 1.173 + Tags: bionic + Uname: Linux 4.15.0-20-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/24/2017 + dmi.bios.vendor: LENOVO + dmi.bios.version: N1UET37W (1.11 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20HJS1NW00 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad P51 + dmi.product.name: 20HJS1NW00 + dmi.product.version: ThinkPad P51 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140207/+files/AlsaInfo.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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia:
[Kernel-packages] [Bug 1750513] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140213/+files/ProcCpuinfo.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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140211/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140208/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140212/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140219/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140214/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140220/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140210/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140218/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140217/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] Re: Screen brightness control doesn't work
I've added the apport logs, they are from Ubuntu 18.04 as since then I've tried installing 17.04 and then upgraded it to 18.04. The problem still persists. ** 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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140215/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1750513] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1750513/+attachment/5140216/+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/1750513 Title: Screen brightness control doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On 4.13 kernels I cannot change brightness of my display. Other users of the same laptop model also have the issue. Using kernel 4.10 the problem doesn't happen and brightness can be changed using hardware buttons(fn+f5, fn+f6). On 4.13 I cannot find any settings that would allow me to change brightness. On 4.13 linux always starts with really dimmed screen which makes the computer hard to use in any kind of daylight, even indoors. lsb_release -rd: Description: Ubuntu 16.04.3 LTS Release: 16.04 uname -a: Linux redacted-ThinkPad-P51 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux (also happens in any earlier version of 4.13, I need to revert up to 4.10 in order for it to work) Hardware: Lenovo ThinkPad P51 15.6" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 20 09:00:09 2018 InstallationDate: Installed on 2017-10-03 (139 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lchr 2877 F pulseaudio /dev/snd/controlC1: lchr 2877 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-04 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: LENOVO 20HJS1NW00 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=3afbbc52-6d66-4597-a1f2-6254d9f44643 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-11 (5 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/24/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET37W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HJS1NW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET37W(1.11):bd07/24/2017:svnLENOVO:pn20HJS1NW00:pvrThinkPadP51:rvnLENOVO:rn20HJS1NW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HJS1NW00 dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750513/+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 1770013] Re: linux-aws: 4.4.0-1020.20 -proposed tracker
** Tags added: regression-testing-passed -- 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/1770013 Title: linux-aws: 4.4.0-1020.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed 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: 1770011 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/1770013/+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 1752081] Re: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
Same issue on Cosmic. -- 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/1752081 Title: platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Hello, dmesg: [5.421791] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-11-generic 4.15.0-11.12 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1860 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Tue Feb 27 09:46:36 2018 InstallationDate: Installed on 2017-10-13 (136 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.15.0-11-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-11-generic N/A linux-backports-modules-4.15.0-11-generic N/A linux-firmware 1.171 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.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1752081/+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 1748853] Re: Intel 9462 A370:42A4 doesn't work
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1748853 Title: Intel 9462 A370:42A4 doesn't work Status in HWE Next: Fix Released Status in Linux: Incomplete Status in linux package in Ubuntu: New Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Invalid Bug description: [Impact] The PCI ID [A370:42A4] is not included in iwlwifi driver, so that Intel 9462 with that ID won't work. [Fix] According the 2 patches sent to 4.15 stable, which were not be included before 4.15 EOL, so we cherry pick the 2 patches to Ubuntu 4.15 kernel. https://www.spinics.net/lists/stable/msg235420.html [Regression Potential] Adding IDs, no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1748853/+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 1769077] Re: linux: 3.13.0-148.197 -proposed tracker
Hardware Certification was completed with linux 3.13.0-146.195 (bug 1766601). Setting certification-testing to 'Fix Released'. ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1769077 Title: linux: 3.13.0-148.197 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1769080 (linux-lts-trusty) derivatives: -- 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/1769077/+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 1755118] Re: Unable to create KVM with uvtool on A/X/X-hwe ppc64le system
** Summary changed: - Unable to create KVM with uvtool on A/X-hwe ppc64le system + Unable to create KVM with uvtool on A/X/X-hwe ppc64le system -- 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/1755118 Title: Unable to create KVM with uvtool on A/X/X-hwe ppc64le system Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: Triaged Bug description: When trying to create a KVM instance with uvtool on Artful ppc64le, it always report that the created instance was not running. Steps: sudo su apt-get install qemu-kvm uvtool -y ssh-keygen -t rsa -N '' uvt-simplestreams-libvirt sync release=artful arch=ppc64el uvt-kvm create kvm-test release=artful arch=ppc64el uvt-kvm wait kvm-test --insecure Result: uvt-kvm: error: libvirt domain 'kvm-test' is not running. This issue might be related to bug 1452016 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 12 08:03 seq crw-rw 1 root audio 116, 33 Mar 12 08:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: ppc64el 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: Mon Mar 12 08:40:22 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=36575f9a-a03d-4d21-874c-db9886a8ffbd ro console=hvc0 ProcLoadAvg: 9.65 5.79 4.46 1/1853 109388 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.13.0-37-generic (buildd@bos02-ppc64el-004) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #42-Ubuntu SMP Wed Mar 7 14:12:30 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.695 GHz (cpu 159) max: 3.695 GHz (cpu 1) avg: 3.695 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755118/+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 1771535] [NEW] synaptics trackpad not detected by libinput
Public bug reported: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic ** Attachment added: "dmesg output" https://bugs.launchpad.net/bugs/1771535/+attachment/5140256/+files/dmesg -- 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/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Confirmed Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux Upgra
[Kernel-packages] [Bug 1771537] [NEW] Kexec -p Seems load kernel failed, and doesn't reboot after a panic
Public bug reported: After install linux-crashdump, everything seems successfully. But when I trigger an panic over: echo c > /proc/sysrq-trigger , kernel panics and hungs, and doesn't reboot. even if i do the following: echo 10 > /proc/sys/kernel/panic And it is reproducible on my system. Here is my system information: rs@ubuntuDev$ uname -a Linux ubuntuDev 3.19.0-80-generic #88~14.04.1-Ubuntu SMP Fri Jan 13 14:54:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux And it is the lsb info: rs@ubuntuDev$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty rs@ubuntuDev$ Here is result of kdump-config show before i trigger an panic: rs@ubuntuDev$ kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2d00 current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic rs@ubuntuDev$ And I have successfully solved this problem by these steps after the above kdump-config show: 1: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic 2: echo c > /proc/sysrq-trigger And this time, system successfully rebooted into the secondary kernel whiout crashkernel param, and the vmcore is dumpped successfully. So, It seems we should strip out the BOOT_IMAGE string from result of `cat /proc/cmdline`. As a result, we need change kdump-config script from: # Assemble the --commmand-line: if [ -z "$KDUMP_CMDLINE" ] ; then KDUMP_CMDLINE=`cat /proc/cmdline | \ sed -r -e 's/(^| )crashkernel=[^ ]*//g' \ -e 's/(^| )hugepages=[^ ]*//g' \ -e 's/(^| )hugepagesz=[^ ]*//g' \ -e 's/(^| )abm=[^ ]*//g'` fi into: # Assemble the --commmand-line: if [ -z "$KDUMP_CMDLINE" ] ; then KDUMP_CMDLINE=`cat /proc/cmdline | \ sed -r -e 's/(^| )crashkernel=[^ ]*//g' \ -e 's/(^| )hugepages=[^ ]*//g' \ -e 's/(^| )hugepagesz=[^ ]*//g' \ -e 's/(^| )abm=[^ ]*//g'` \ -e 's/(^| )BOOT_IMAGE=[^ ]*//g' fi Could you guys re-check this bug? I can provide other information with pleasure, if needed. ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1771537 Title: Kexec -p Seems load kernel failed, and doesn't reboot after a panic Status in kexec-tools package in Ubuntu: New Bug description: After install linux-crashdump, everything seems successfully. But when I trigger an panic over: echo c > /proc/sysrq-trigger , kernel panics and hungs, and doesn't reboot. even if i do the following: echo 10 > /proc/sys/kernel/panic And it is reproducible on my system. Here is my system information: rs@ubuntuDev$ uname -a Linux ubuntuDev 3.19.0-80-generic #88~14.04.1-Ubuntu SMP Fri Jan 13 14:54:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux And it is the lsb info: rs@ubuntuDev$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.2 LTS Release: 14.04 Codename: trusty rs@ubuntuDev$ Here is result of kdump-config show before i trigger an panic: rs@ubuntuDev$ kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x2d00 current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-3.19.0-80-generic root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic rs@ubuntuDev$ And I have successfully solved this problem by these steps after the above kdump-config show: 1: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic 2: echo c > /proc/sysrq-trigger And this time, system successfully rebooted into the secondary kernel whiout crashkernel param, and the vmcore is dumpped successfully. So, It seems we should strip out the BOOT_IMAGE string from result
[Kernel-packages] [Bug 1771535] Re: synaptics trackpad not detected by libinput
** Attachment added: "lspci -vnvn" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+attachment/5140273/+files/lspci-vnvn.log -- 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/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Confirmed Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+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 1770011] Re: linux: 4.4.0-125.150 -proposed tracker
Mark this task as incomplete for the missing i386 tests. 4.4.0-125.150 - lowlatency Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kvm_unit_tests - 29 failed on amaura, 18 failed on groucho, 20 failed on michael, 28 failed on pepe ubuntu_lxc - lxc-test-ubuntu (Failed to start networking in ubuntu-cloud container) ubuntu_qrt_kernel_aslr_collisions - network issue, not a bug ubuntu_stress_smoke_test - efivar test failed, test has been disabled in the test suite 4.4.0-125.150 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kvm_unit_tests - 28 failed on amaura, 20 failed on michael, 28 failed on pepe ubuntu_stress_smoke_test - efivar test failed, test has been disabled in the test suite Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_docker_smoke_test - test case issue ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - pmu on ms10-34-mcdivittB0-kernel (bug 1751000) gicv2-ipi and gicv2-active on starmie ubuntu_stress_smoke_test - efivar test failed, test has been disabled in the test suite Issue to note in ppc64le: ubuntu_kvm_smoke_test - unable to create KVM with uvtool, bug 1755118 ubuntu_stress_smoke_test - failed on entei, network issue Issue to note in s390x (Ubuntu on LPAR): aio_dio_bugs - invalidate-failure failed (bug 1730895) subblock-eof-read failed (bug 1768430) extend-stat failed (bug 1768435) libhugetlbfs - failed 11 killed by signal 7 bad config 1 scrashme - Test failed to build (bug 1689240) ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in ubuntu-cloud container) Issue to note in s390x (zKVM): aio_dio_bugs - invalidate-failure failed (bug 1730895) subblock-eof-read failed (bug 1768430) extend-stat failed (bug 1768435) libhugetlbfs - failed 11 killed by signal 7 bad config 1 scrashme - Test failed to build (bug 1689240) ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - 11 failed (nested kvm is not supported) Issue to note in s390x (zVM): aio_dio_bugs - invalidate-failure failed (bug 1730895) subblock-eof-read failed (bug 1768430) extend-stat failed (bug 1768435) libhugetlbfs - failed 11 killed by signal 7 bad config 1 scrashme - Test failed to build (bug 1689240) ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452) ubuntu_ecryptfs - passed after re-test ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - skey failed MISSING i386 result in this cycle: curtin bug 1768709 ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- 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/1770011 Title: linux: 4.4.0-125.150 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Fix Released 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: Incomplete Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released 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 1770013 (linux-aws), bug 1770015 (linux-lts-xenial) derivatives: bug 1770016 (linux-aws), bug 1770018 (linux-euclid), bug 177
[Kernel-packages] [Bug 1771535] Status changed to Confirmed
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/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Confirmed Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+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 1771535] Re: synaptics trackpad not detected by libinput
** Attachment added: "/proc/bus/input/devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+attachment/5140272/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Confirmed Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+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 1771535] Re: synaptics trackpad not detected by libinput
On the other hand, it was working perfectly during installation from the live CD menu. -- 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/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Confirmed Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+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 1769077] Re: linux: 3.13.0-148.197 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing 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/1769077 Title: linux: 3.13.0-148.197 -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: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1769080 (linux-lts-trusty) derivatives: -- 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/1769077/+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 1759723] Re: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation.
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1759723 Title: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation. Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Problem Description: === Performed HOTPLUG cpu attach operation for the guest and guest console becomes unresponsive. Steps to re-create: == 1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels 2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes root@boslcp3:/home# uname -a Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.15.0-12-generic root@boslcp3g3:/kte/tools/setup.d# uname -a Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g3:/kte/tools/setup.d# uname -r 4.15.0-12-generic 3. Started HTX & stress-ng for on guest for 10-15 min 4. Cleaned up the tests to perform hot-plug and ensure enough memory and cpu was there (killed all Process using kill) 5. Performed cpu hot-plug and guest went into hung state Before Hotplug: root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu 64 root@boslcp3:~# 6. After this operation, guest becomes unrepsonsive as below root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3626.146375] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3626.146699] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 seconds. [ 3626.147016] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 seconds. [ 3626.147361] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds. [ 3626.147686] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds. [ 3626.147937] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds. [ 3626.148173] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds. [ 3626.148406] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. root@boslcp3g3:~# root@boslcp3g3:~# ps -ef | grep stress-ng [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3746.978221] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3746.978534] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4446.361899] systemd[1]: Failed to start Journal Service. [ 4897.632142] systemd[1]: Failed to star
[Kernel-packages] [Bug 1771542] [NEW] Suspend to idle: Open lid didn't resume
Public bug reported: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: originate-from-1769555 timbuktu ** Description changed: [Impact] - Some platforms is set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. + Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened -- 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/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: New Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+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 1737423] Re: With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video memory misdetected as 512 Mb : result was kernel panic in worst case and memory crash in
Hello
Not tested under AMD64
My problem is to have a graphic processor on a (old pentium) computer
without agp port to be able to edit video.
I made the choice to have in this secondary house an old (at very low
cost) desktop computer with a comfortable 24' screen and to travel with
an usb key (lighter than a portable computer)
And my (Main use at home) is an AMD64 with graphic processor on video
card
I looked at my notes about this computer
with nvidia proprietary driver, had problem
with nouveau, worked with screen connected with VGA cable, but not
correctly centered (something like colomn 1 outside the screen)
with nouveau, connected with DVI cable, had problem
file (copied month ago) /var/log/Xorg.0.log
contained (key elements i noted)
18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
[ 18.806] (==) Matched nvidia as autoconfigured driver 1
[ 18.806] (==) Matched nouveau as autoconfigured driver 2
[ 18.810] (II) LoadModule: "nvidia"
[ 18.814] (WW) Warning, couldn't open module nvidia
[ 18.814] (II) UnloadModule: "nvidia"
[ 18.815] (II) Unloading nvidia
[ 18.815] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 18.815] (II) LoadModule: "nouveau"
[ 18.819] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 18.825] (II) Module nouveau: vendor="X.Org Foundation"
[ 18.825] compiled for 1.15.0, module version = 1.0.10
[ 18.826] Module class: X.Org Video Driver
[ 18.826] ABI class: X.Org Video Driver, version 15.0
So, wrong detection at 18.759 before loading nividia and nouveau
0xc000/536870912 adresse correct , but size 536870912 = 512Mo
incorrect
searched in the source i was able to find, arrived at
nouveau_device_get_param(struct nouveau_device *dev,
uint64_t param, uint64_t *value)
{
struct nouveau_device_priv *nvdev = nouveau_device(dev);
struct drm_nouveau_getparam g;
int ret;
if (!nvdev || !value)
return -EINVAL;
g.param = param;
ret = drmCommandWriteRead(nvdev->fd, DRM_NOUVEAU_GETPARAM,
&g, sizeof(g));
if (ret)
return ret;
*value = g.value;
return 0;
}
attempted to limit use of memory, using, VideoRam 262144 but not
succeeded
For me, the goog thing to do is to be able to recover the information
obtained at hardware level
done lspci
jean@jean-Soisy:~$ lspci -v -s 03:09.0
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev
a1) (prog-if 00 [VGA controller])
Flags: bus master, 66MHz, medium devsel, latency 40, IRQ 21
Memory at 9400 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (32-bit, prefetchable) [size=512M]
Memory at 9200 (32-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at e000 [disabled] [size=128K]
Capabilities:
Kernel driver in use: nouveau
done lspci in verbose mode
jean@jean-Soisy:~$ sudo lspci -v -k -x -s 03:09.0
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev
a1) (prog-if 00 [VGA controller])
Flags: bus master, 66MHz, medium devsel, latency 40, IRQ 21
Memory at 9400 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (32-bit, prefetchable) [size=512M]
Memory at 9200 (32-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at e000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Kernel driver in use: nouveau
00: de 10 21 02 06 01 b0 02 a1 00 00 03 00 28 00 00
10: 00 00 00 94 08 00 00 c0 00 00 00 92 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 60 00 00 00 00 00 00 00 09 01 05 01
noted 10: 00 00 00 94 = 0x9400 (in little endian)
done lspi once more
jean@jean-Soisy:~$ sudo lspci -vv -k - -s 03:09.0
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev
a1) (prog-if 00 [VGA controller])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR-
Latency: 40 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 21
Region 0: Memory at 9400 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at c000 (32-bit, prefetchable) [size=512M]
Region 2: Memory at 9200 (32-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at e000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: nouveau
00: de 10 21 02 06 01 b0 02 a1 00 00 03 00 28 00 00
10: 00 00 00 94 08 00 00 c0 00 00 00 92 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 60 00 00 00 00 00 00 00 09
[Kernel-packages] [Bug 1766825] Re: Bluetooth issues with Dell XPS 13 (9370)
It seems there is no update since 2015 to qca subdir of linux-firmware, so those newer blobs will need to be submitted by Qualcomm, maybe ytkim specifically who did that 3 years ago if he's still at Qualcomm: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/log/qca -- 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/1766825 Title: Bluetooth issues with Dell XPS 13 (9370) Status in Dell Sputnik: Triaged Status in linux package in Ubuntu: Confirmed Bug description: I have the following problem with my Bluetooth module on my new Dell XPS 13 (9370) with Ubuntu preinstalled. The bluetooth module gets disabled for some reason. The bluetooth devices (keyboard and mouse) just stop working in the middle of the work, the Bluetooth indicator goes away and the module is also gone in the rfkill list. To get it back working I need to reboot the machine, start the BIOS, disable the Bluetooth module and re-enable it or I have to turn the machine completely off and on again. After that, the bluetooth module is available again. That's pretty annoying. My syslog when this happens: Apr 11 12:25:45 visyu-albatross kernel: [ 2513.913725] usb 1-7: USB disconnect, device number 3 Apr 11 12:25:45 visyu-albatross acpid: input device has been disconnected, fd 22 Apr 11 12:25:46 visyu-albatross systemd[1]: Starting Load/Save RF Kill Switch Status... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Load/Save RF Kill Switch Status. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c9 of user root. Apr 11 12:25:46 visyu-albatross acpid: input device has been disconnected, fd 21 Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Startup finished in 15ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSource Apr 11 12:25:46 visyu-albatross bluetoothd[1062]: Endpoint unregistered: sender=:1.80 path=/MediaEndpoint/A2DPSink Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12109]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12109]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[1]: Started Session c10 of user root. Apr 11 12:25:46 visyu-albatross systemd[12109]: Received SIGRTMIN+24 from PID 12120 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Starting User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Startup finished in 14ms. Apr 11 12:25:46 visyu-albatross systemd[1]: Started User Manager for UID 0. Apr 11 12:25:46 visyu-albatross systemd[1]: Stopping User Manager for UID 0... Apr 11 12:25:46 visyu-albatross systemd[12123]: Reached target Shutdown. Apr 11 12:25:46 visyu-albatross systemd[12123]: Starting Exit the Session... Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Default. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Basic System. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Timers. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Paths. Apr 11 12:25:46 visyu-albatross systemd[12123]: Stopped target Sockets. Apr 11 12:25:46 visyu-albatross systemd[12123]: Received SIGRTMIN+24 from PID 12133 (kill). Apr 11 12:25:46 visyu-albatross systemd[1]: Created slice User Slice of root. Apr 11 12:25:46 visyu-albatross systemd[1]: Start
[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume
** Description changed: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] - According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.15 kernel. + According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened -- 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/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+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 159356] Re: System freeze on high memory usage
still happens with Fedora 28 -- 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/159356 Title: System freeze on high memory usage Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Status in Fedora: Confirmed Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 1771546] [NEW] WARNING: setup_local_APIC+0x27f/0x340
Public bug reported: when load kernel with kexec: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic and then, triggers a panic: echo c > /proc/sysrq-trigger and now we got reboot into secondary kernel, but at this process, we will got this call trace with 100% reproducible: [14257.863168] Initializing cgroup subsys net_prio [14257.864506] Initializing cgroup subsys hugetlb [14257.865898] CPU: Physical Processor ID: 0 [14257.867035] CPU: Processor Core ID: 0 [14257.869296] mce: CPU supports 0 MCE banks [14257.870495] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 [14257.870495] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 [14257.901734] ftrace: allocating 30063 entries in 118 pages [14258.976524] [ cut here ] [14258.983143] WARNING: CPU: 0 PID: 1 at /build/linux-lts-vivid-PmeBs4/linux-lts-vivid-3.19.0/arch/x86/kernel/apic/apic.c:1400 setup_local_APIC+0x27f/0x340() [14259.005863] Modules linked in: [14259.009221] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-80-generic #88~14.04.1-Ubuntu [14259.015315] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [14259.021134] 88003191fe18 817b63c3 [14259.036605] 81a8b9d0 88003191fe58 81075d6a 88003191fdfc [14259.055284] 0001 00f0 [14259.061414] Call Trace: [14259.063414] [] dump_stack+0x63/0x81 [14259.067742] [] warn_slowpath_common+0x8a/0xc0 [14259.076934] [] warn_slowpath_null+0x1a/0x20 [14259.085878] [] setup_local_APIC+0x27f/0x340 [14259.101292] [] native_smp_prepare_cpus+0x2f2/0x3af [14259.111873] [] kernel_init_freeable+0xaf/0x1f9 [14259.114495] [] ? rest_init+0x80/0x80 [14259.116783] [] kernel_init+0xe/0xf0 [14259.118990] [] ret_from_fork+0x58/0x90 [14259.121292] [] ? rest_init+0x80/0x80 [14259.123341] ---[ end trace 7384fc8d5897e3f0 ]--- [14259.130738] Spurious LAPIC timer interrupt on cpu 0 [14259.153429] do_IRQ: 0.145 No irq handler for vector (irq -1) [14259.157634] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [14259.161002] smpboot: CPU0: Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz (fam: 06, model: 4e, stepping: 03) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771546 Title: WARNING: setup_local_APIC+0x27f/0x340 Status in linux package in Ubuntu: New Bug description: when load kernel with kexec: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic and then, triggers a panic: echo c > /proc/sysrq-trigger and now we got reboot into secondary kernel, but at this process, we will got this call trace with 100% reproducible: [14257.863168] Initializing cgroup subsys net_prio [14257.864506] Initializing cgroup subsys hugetlb [14257.865898] CPU: Physical Processor ID: 0 [14257.867035] CPU: Processor Core ID: 0 [14257.869296] mce: CPU supports 0 MCE banks [14257.870495] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 [14257.870495] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 [14257.901734] ftrace: allocating 30063 entries in 118 pages [14258.976524] [ cut here ] [14258.983143] WARNING: CPU: 0 PID: 1 at /build/linux-lts-vivid-PmeBs4/linux-lts-vivid-3.19.0/arch/x86/kernel/apic/apic.c:1400 setup_local_APIC+0x27f/0x340() [14259.005863] Modules linked in: [14259.009221] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-80-generic #88~14.04.1-Ubuntu [14259.015315] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [14259.021134] 88003191fe18 817b63c3 [14259.036605] 81a8b9d0 88003191fe58 81075d6a 88003191fdfc [14259.055284] 0001 00f0 [14259.061414] Call Trace: [14259.063414] [] dump_stack+0x63/0x81 [14259.067742] [] warn_slowpath_common+0x8a/0xc0 [14259.076934] [] warn_slowpath_null+0x1a/0x20 [14259.085878] [] setup_local_APIC+0x27f/0x340 [14259.101292] [] native_smp_prepare_cpus+0x2f2/0x3af [14259.111873] [] kernel_init_freeable+0xaf/0x1f9 [14259.114495] [] ? rest_init+0x80/0x80 [14259.116783] [] kernel_init+0xe/0xf0 [14259.118990] [] ret_from_fork+0x58/0x90 [14259.121292] [] ? rest_init+0x80/0x80 [14259.123341] ---[ end trace 7384fc8d5897e3f0 ]--- [14259.130738] Spurious LAPIC timer interrupt on cpu 0 [14259.153429] do_IRQ: 0.145 No irq handler for
[Kernel-packages] [Bug 1771542] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1771542 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+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 1759723] Re: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation.
** Changed in: ubuntu-power-systems Status: Fix Released => 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/1759723 Title: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation. Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Problem Description: === Performed HOTPLUG cpu attach operation for the guest and guest console becomes unresponsive. Steps to re-create: == 1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels 2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes root@boslcp3:/home# uname -a Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.15.0-12-generic root@boslcp3g3:/kte/tools/setup.d# uname -a Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g3:/kte/tools/setup.d# uname -r 4.15.0-12-generic 3. Started HTX & stress-ng for on guest for 10-15 min 4. Cleaned up the tests to perform hot-plug and ensure enough memory and cpu was there (killed all Process using kill) 5. Performed cpu hot-plug and guest went into hung state Before Hotplug: root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu 64 root@boslcp3:~# 6. After this operation, guest becomes unrepsonsive as below root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3626.146375] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3626.146699] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 seconds. [ 3626.147016] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 seconds. [ 3626.147361] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds. [ 3626.147686] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds. [ 3626.147937] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds. [ 3626.148173] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds. [ 3626.148406] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. root@boslcp3g3:~# root@boslcp3g3:~# ps -ef | grep stress-ng [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3746.978221] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3746.978534] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4446.361899] systemd[1]: Failed to start Journal Service. [ 4897.632142] systemd[1]: Failed to start Journal Service. ^Z ^X ^C ^Z ^X ^C 7. ping to boslcp3g
[Kernel-packages] [Bug 1771546] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1771546 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: vivid -- 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/1771546 Title: WARNING: setup_local_APIC+0x27f/0x340 Status in linux package in Ubuntu: Incomplete Bug description: when load kernel with kexec: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic and then, triggers a panic: echo c > /proc/sysrq-trigger and now we got reboot into secondary kernel, but at this process, we will got this call trace with 100% reproducible: [14257.863168] Initializing cgroup subsys net_prio [14257.864506] Initializing cgroup subsys hugetlb [14257.865898] CPU: Physical Processor ID: 0 [14257.867035] CPU: Processor Core ID: 0 [14257.869296] mce: CPU supports 0 MCE banks [14257.870495] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 [14257.870495] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 [14257.901734] ftrace: allocating 30063 entries in 118 pages [14258.976524] [ cut here ] [14258.983143] WARNING: CPU: 0 PID: 1 at /build/linux-lts-vivid-PmeBs4/linux-lts-vivid-3.19.0/arch/x86/kernel/apic/apic.c:1400 setup_local_APIC+0x27f/0x340() [14259.005863] Modules linked in: [14259.009221] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-80-generic #88~14.04.1-Ubuntu [14259.015315] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [14259.021134] 88003191fe18 817b63c3 [14259.036605] 81a8b9d0 88003191fe58 81075d6a 88003191fdfc [14259.055284] 0001 00f0 [14259.061414] Call Trace: [14259.063414] [] dump_stack+0x63/0x81 [14259.067742] [] warn_slowpath_common+0x8a/0xc0 [14259.076934] [] warn_slowpath_null+0x1a/0x20 [14259.085878] [] setup_local_APIC+0x27f/0x340 [14259.101292] [] native_smp_prepare_cpus+0x2f2/0x3af [14259.111873] [] kernel_init_freeable+0xaf/0x1f9 [14259.114495] [] ? rest_init+0x80/0x80 [14259.116783] [] kernel_init+0xe/0xf0 [14259.118990] [] ret_from_fork+0x58/0x90 [14259.121292] [] ? rest_init+0x80/0x80 [14259.123341] ---[ end trace 7384fc8d5897e3f0 ]--- [14259.130738] Spurious LAPIC timer interrupt on cpu 0 [14259.153429] do_IRQ: 0.145 No irq handler for vector (irq -1) [14259.157634] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [14259.161002] smpboot: CPU0: Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz (fam: 06, model: 4e, stepping: 03) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771546/+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 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X
I tested with 4.17 rc4 and the problem persists -- 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/1747463 Title: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu. There are lots of AMD-Vi logged events and I get irq crashes or acpi hangups with a 'normal' boot. I got it to boot by disabling IOMMU in the BIOS and adding "iommu=soft" to the kernel booting options in grub. linux can then detect everything properly (all cores) and I've had zero crashes. The only issue is that it's using software IOMMU which could have a performance penalty because it has to copy all the data of some PCI devices to sub 4G regions. Alternatively it boots with the kernel option "acpi=off" but only detects a single core/thread. I attached a kernel log. I believe(d) this might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085 --- ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fixme 1487 F pulseaudio /dev/snd/controlC0: fixme 1487 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece InstallationDate: Installed on 2018-01-31 (4 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group B350GT5 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 RfKill: Tags: bionic Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.asset.tag: None dmi.board.name: B350GT5 dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: None dmi.product.name: B350GT5 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1747463/+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 1771557] [NEW] NVMe boot drives not supported - failing in generating initramfs
Public bug reported: [Impact] The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing and not building the initram disk. Upstream solution is composed for at least 2 patches (it's a series, but the 2 below are really the needed ones): commit 3cb744c9 Author: Ben Hutchings hook-functions: Rewrite block device sysfs lookup to be generic commit 8ac52dc0 Author: Ben Hutchings hook-functions: Include modules for all components of a multi-disk device Instead of doing the backport, which is huge, we added another sed substitution: currently the script has substitutions for sdX and hdX, in order to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY. It's less intrusive than the full backport, since this is a SRU to Trusty only. [Test Case] To be added. [Regression Potential] If the sed expression was somewhat broken, we could have an issue generating initiramfs for generic block devices, like regular HDDs. [Other Info] This issue is based on Debian bug #785147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147 ** Affects: initramfs-tools Importance: Unknown Status: Fix Released ** Affects: initramfs-tools (Ubuntu) Importance: High Assignee: Guilherme G. Piccoli (gpiccoli) Status: In Progress ** Affects: initramfs-tools (Ubuntu Trusty) Importance: High Assignee: Guilherme G. Piccoli (gpiccoli) Status: In Progress ** Affects: initramfs-tools (Ubuntu Xenial) Importance: Medium Status: Fix Released ** Tags: sts trusty ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Milestone: None => trusty-updates ** Bug watch added: Debian Bug tracker #785147 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147 ** Also affects: linux via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147 Importance: Unknown Status: Unknown -- 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/1771557 Title: NVMe boot drives not supported - failing in generating initramfs Status in initramfs-tools: Fix Released Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Trusty: In Progress Status in initramfs-tools source package in Xenial: Fix Released Bug description: [Impact] The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing and not building the initram disk. Upstream solution is composed for at least 2 patches (it's a series, but the 2 below are really the needed ones): commit 3cb744c9 Author: Ben Hutchings hook-functions: Rewrite block device sysfs lookup to be generic commit 8ac52dc0 Author: Ben Hutchings hook-functions: Include modules for all components of a multi-disk device Instead of doing the backport, which is huge, we added another sed substitution: currently the script has substitutions for sdX and hdX, in order to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY. It's less intrusive than the full backport, since this is a SRU to Trusty only. [Test Case] To be added. [Regression Potential] If the sed expression was somewhat broken, we could have an issue generating initiramfs for generic block devices, like regular HDDs. [Other Info] This issue is based on Debian bug #785147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147 To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+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 1771557] Re: NVMe boot drives not supported - failing in generating initramfs
** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771557 Title: NVMe boot drives not supported - failing in generating initramfs Status in initramfs-tools: Fix Released Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Trusty: In Progress Status in initramfs-tools source package in Xenial: Fix Released Bug description: [Impact] The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing and not building the initram disk. Upstream solution is composed for at least 2 patches (it's a series, but the 2 below are really the needed ones): commit 3cb744c9 Author: Ben Hutchings hook-functions: Rewrite block device sysfs lookup to be generic commit 8ac52dc0 Author: Ben Hutchings hook-functions: Include modules for all components of a multi-disk device Instead of doing the backport, which is huge, we added another sed substitution: currently the script has substitutions for sdX and hdX, in order to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY. It's less intrusive than the full backport, since this is a SRU to Trusty only. [Test Case] To be added. [Regression Potential] If the sed expression was somewhat broken, we could have an issue generating initiramfs for generic block devices, like regular HDDs. [Other Info] This issue is based on Debian bug #785147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147 To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+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 1771557] Re: NVMe boot drives not supported - failing in generating initramfs
Fixed in Debian ** Project changed: linux => initramfs-tools ** Changed in: initramfs-tools Status: Unknown => 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/1771557 Title: NVMe boot drives not supported - failing in generating initramfs Status in initramfs-tools: Fix Released Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Trusty: In Progress Status in initramfs-tools source package in Xenial: Fix Released Bug description: [Impact] The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing and not building the initram disk. Upstream solution is composed for at least 2 patches (it's a series, but the 2 below are really the needed ones): commit 3cb744c9 Author: Ben Hutchings hook-functions: Rewrite block device sysfs lookup to be generic commit 8ac52dc0 Author: Ben Hutchings hook-functions: Include modules for all components of a multi-disk device Instead of doing the backport, which is huge, we added another sed substitution: currently the script has substitutions for sdX and hdX, in order to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY. It's less intrusive than the full backport, since this is a SRU to Trusty only. [Test Case] To be added. [Regression Potential] If the sed expression was somewhat broken, we could have an issue generating initiramfs for generic block devices, like regular HDDs. [Other Info] This issue is based on Debian bug #785147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147 To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+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 1771557] Re: NVMe boot drives not supported - failing in generating initramfs
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu) ** Changed in: initramfs-tools (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu Xenial) Status: New => Fix Released ** Changed in: initramfs-tools (Ubuntu Trusty) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu Trusty) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu Trusty) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: initramfs-tools (Ubuntu Trusty) Milestone: None => trusty-updates -- 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/1771557 Title: NVMe boot drives not supported - failing in generating initramfs Status in initramfs-tools: Fix Released Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools source package in Trusty: In Progress Status in initramfs-tools source package in Xenial: Fix Released Bug description: [Impact] The initramfs-tools hook-functions script cannot translate nvmeXnYpZ to nvmeXnY block device, so it's failing and not building the initram disk. Upstream solution is composed for at least 2 patches (it's a series, but the 2 below are really the needed ones): commit 3cb744c9 Author: Ben Hutchings hook-functions: Rewrite block device sysfs lookup to be generic commit 8ac52dc0 Author: Ben Hutchings hook-functions: Include modules for all components of a multi-disk device Instead of doing the backport, which is huge, we added another sed substitution: currently the script has substitutions for sdX and hdX, in order to convert sda1 to sda, for example. The new substitution converts nvmeXnYpZ to nvmeXnY. It's less intrusive than the full backport, since this is a SRU to Trusty only. [Test Case] To be added. [Regression Potential] If the sed expression was somewhat broken, we could have an issue generating initiramfs for generic block devices, like regular HDDs. [Other Info] This issue is based on Debian bug #785147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785147 To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1771557/+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 1761751] Re: Black screen on 18.04 + AMD RX460
Problem still exists in 4.16.9 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.9/ (#uname -r output is 4.16.9-041609-generic ) -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: * linux-image-4.15.0-041500-generic (mainline kernel), * linux-image-4.16.0-041600-generic (mainline kernel), * linux-image-4.15.0-13-generic (Ubuntu kernel), * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1770770] Re: Switch Build-Depends: transfig to fig2dev
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1770770 Title: Switch Build-Depends: transfig to fig2dev Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: We are still depending on a transitional package for transfig. Switch to the real package fig2dev. This is contributing to NBS in cosmic but is also valid in bionic. We need to bear in mind it is _not_ valid in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1770770/+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 1771575] [NEW] [Comm] IBM JDK 8.0.5.15 integration into Ubuntu
You have been subscribed to a public bug: Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.15 foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp15_20180502_01_ocdc.tar.gz local: 80sr5fp15_20180502_01_ocdc.tar.gz remote: 80sr5fp15_20180502_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp15_20180502_01_ocdc.tar.gz 226 Transfer successful. 651526537 bytes sent in 413.46 secs (1538.9 kB/s) ftp> quit 221 Goodbye. foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list 226 Transfer successful. ftp> quit 221 Goodbye. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-167902 severity-high targetmilestone-inin--- -- [Comm] IBM JDK 8.0.5.15 integration into Ubuntu https://bugs.launchpad.net/bugs/1771575 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1771575] [NEW] [Comm] IBM JDK 8.0.5.15 integration into Ubuntu
Public bug reported: Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.15 foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp15_20180502_01_ocdc.tar.gz local: 80sr5fp15_20180502_01_ocdc.tar.gz remote: 80sr5fp15_20180502_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp15_20180502_01_ocdc.tar.gz 226 Transfer successful. 651526537 bytes sent in 413.46 secs (1538.9 kB/s) ftp> quit 221 Goodbye. foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list 226 Transfer successful. ftp> quit 221 Goodbye. ** Affects: ibm-java71 (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-167902 severity-high targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-167902 severity-high targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771575 Title: [Comm] IBM JDK 8.0.5.15 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.15 foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp15_20180502_01_ocdc.tar.gz local: 80sr5fp15_20180502_01_ocdc.tar.gz remote: 80sr5fp15_20180502_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp15_20180502_01_ocdc.tar.gz 226 Transfer successful. 651526537 bytes sent in 413.46 secs (1538.9 kB/s) ftp> quit 221 Goodbye. foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list 226 Transfer successful. ftp> quit 221 Goodbye. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1771575/+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 1771575] Re: [Comm] IBM JDK 8.0.5.15 integration into Ubuntu
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771575 Title: [Comm] IBM JDK 8.0.5.15 integration into Ubuntu Status in ibm-java71 package in Ubuntu: New Bug description: Uploaded the Debian packages onto the Canonical FTP Server for 8.0.5.15 foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> prompt off Interactive mode off. ftp> put 80sr5fp15_20180502_01_ocdc.tar.gz local: 80sr5fp15_20180502_01_ocdc.tar.gz remote: 80sr5fp15_20180502_01_ocdc.tar.gz 200 PORT command successful. 150 Opening Binary connection for /80sr5fp15_20180502_01_ocdc.tar.gz 226 Transfer successful. 651526537 bytes sent in 413.46 secs (1538.9 kB/s) ftp> quit 221 Goodbye. foreman@cit7r02:~/sandbox/binary$ ftp archive.admin.canonical.com Connected to archive.admin.canonical.com. 220 youngberry.canonical.com FTP server (Poppy Upload Server) ready. Name (archive.admin.canonical.com:foreman): anonymous 331 Password required Password: 230 Login Successful. Remote system type is UNIX. Using binary mode to transfer files. ftp> bin 200 Type set to Binary. ftp> ls 200 PORT command successful. 150 Opening ASCII mode data connection for file list 226 Transfer successful. ftp> quit 221 Goodbye. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibm-java71/+bug/1771575/+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 1769696] Re: [SRU][Bionic/Artful] fix false positives in W+X checking
** Changed in: linux (Ubuntu Xenial) Status: New => 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/1769696 Title: [SRU][Bionic/Artful] fix false positives in W+X checking Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Status in linux source package in Artful: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] on ARM64 servers we observe call trace "arm64/mm: Found insecure W+X mapping at address 00a99000/0xa99000" while booting. These messages are a false positive and triggered at random. [Test] There is no reliable way to reproduce these warnings, they are triggered at random. But these messages can appear on any ARM64 server Cavium, Qualcomm etc. A test kernel is available in ppa:manjo/lp1769696 and the kernel was boot tested on a QDF2400 system and Cavium Thunderx. ubuntu@awrep2:~$ uname -a Linux awrep2 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ uname -a Linux boomer 4.15.0-21-generic #22~lp1769696+build.1-Ubuntu SMP Mon May 7 16:04:39 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux ubuntu@boomer:~$ [Fix] Upstream fix is available in linux-next 65d313ee1a7d init: fix false positives in W+X checking [Regression Potential] potential for any regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769696/+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 1770003] Comment bridged from LTC Bugzilla
--- Comment From gwal...@br.ibm.com 2018-05-16 10:04 EDT---
(In reply to comment #56)
> Created attachment 127215 [details]
> [PATCH][SRU][Bionic 1/9] scsi: qla2xxx: Fix session cleanup for N2N
sorry folks,
After the submission I have noted the wrong authority in the set by me,
and so I updated the patch 1/9 fixing the author to Quinn Tran instead.
--
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/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
IBM is requesting these nine patches to be SRU'd to Bionic. IBM found
that the current Bionic kernel contains a problem related to qla2xxx
driver which causes the following:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
== Regression Potential ==
Medium. There are nine patches in this pull request. They are not specific
to a
paticular arch, but they are specific to qla2xxx.
== Test Case ==
A test kernel was built with these patches and tested by IBM.
IBM states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+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 1768526] Re: Include nfp driver in linux-modules
Hi, I'm wondering if there is anything Netronome can do to assist with regards to this bug. Its very important to us. -- 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/1768526 Title: Include nfp driver in linux-modules Status in linux package in Ubuntu: Triaged Bug description: SRU Justification: -- [Impact] * Currently the driver for Netronome Agilio SmartNICs, nfp.ko, is included in linux-moudles-extra. An implication of this is that on minimal installs, where the linux-modules but not linux-modules-extra packages are available, the nfp.ko module cannot be installed. In particular this means the driver for any VFs of Netronome Agilio SmartNICs which have been made available to guests using PCI pass-through cannot be used by those guests if they have installed using Canonical cloud images, a likely scenario. In contrast the driver for the i40e is provided in the linux-modules package and thus guests can access their VFs in the scenario described above. Thus we do not believe it is unreasonable to request that nfp.ko be included in linux-modules rather than linux-modules-extras. And we believe that this warrants SRU inclusion as it is the difference between users-of guests being able to use Netronome Agilio SmartNICs and not be able to use them. This is a packaging update request and included no request to change the kernel source code, thus no backports are requred. [Test Case] * Install system using Canonical cloud images * Observer that /lib/modules/*/kernel/drivers/net/ethernet/netronome/nfp/nfp.ko is missing; * If an Netronome Agilio SmartNIC device is present, via PCI pass-through or otherwise, that the nfp driver is not loaded and no netdevs are present for the Netronome Agilio SmartNIC. [Regression Potential] * Any bugs present in the nfp.ko will now be exposted to guests. However as the same nfp.ko driver binary is already included in and available on installs that have access to linux-modules-extra, this does not seem an unreasonable burden. [Other Info] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768526/+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 1770003] [PATCH][SRU][Bionic 1/9] scsi: qla2xxx: Fix session cleanup for N2N
--- Comment (attachment only) From gwal...@br.ibm.com 2018-05-16 10:00
EDT---
** Attachment added: "[PATCH][SRU][Bionic 1/9] scsi: qla2xxx: Fix session
cleanup for N2N"
https://bugs.launchpad.net/bugs/1770003/+attachment/5140353/+files/0001-scsi-qla2xxx-Fix-session-cleanup-for-N2N.patch
--
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/1770003
Title:
qla2xxx: Fix page fault at kmem_cache_alloc_node()
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
IBM is requesting these nine patches to be SRU'd to Bionic. IBM found
that the current Bionic kernel contains a problem related to qla2xxx
driver which causes the following:
[ 66.295233] Unable to handle kernel paging request for data at address
0x8882f6ed90e9151a
[ 66.295297] Faulting instruction address: 0xc038a110
cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
sp: c692f8d0
msr: 90009033
dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000 softe: 0irq_happened: 0x01
pid = 1762, comm = systemd-journal
Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu
4.15.0-20.21-generic 4.15.20)
enter ? for help
[c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350
(unreliable)
[c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
[c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
[c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
[c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
[c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
[c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
[c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
[c692fe30] c000b184 system_call+0x58/0x6c
--- Exception: c00 (System Call) at 74826f6fa9c4
SP (75dc5510) is in userspace
We were able to get rid of this problem cherry picking some of the
upstream patches. Do you think they might fit in the SRU criteria?
The commit ids are below and they were easily cherry picked.
eaf75d1815dad230dac2f1e8f1dc0349b2d50071: scsi: qla2xxx: Fix double free bug
after firmware timeout
6d67492764b39ad6efb6822816ad73dc141752f4: scsi: qla2xxx: Prevent relogin
trigger from sending too many commands
7ac0c332f96bb9688560726f5e80c097ed8de59a: scsi: qla2xxx: Fix warning in
qla2x00_async_iocb_timeout()
045d6ea200af794ba15515984cff63787a7fc3c0: scsi: qla2xxx: Don't call
dma_free_coherent with IRQ disabled.
1ae634eb28533b82f9777a47c1ade44cb8c0182b: scsi: qla2xxx: Serialize session
free in qlt_free_session_done
d8630bb95f46ea118dede63bd75533faa64f9612: scsi: qla2xxx: Serialize session
deletion by using work_lock
Requries: 1c6cacf4ea6c04a58a0e3057f5ed60c24a4ffeff ('scsi: qla2xxx:
Fixup locking for session deletion')
94cff6e114df56d0df74cdabe3481df38d9b0c1e: scsi: qla2xxx: Remove unused
argument from qlt_schedule_sess_for_dele?
9cd883f07a54e5301d51e259acd250bb035996be: scsi: qla2xxx: Fix session cleanup
for N2N
== Regression Potential ==
Medium. There are nine patches in this pull request. They are not specific
to a
paticular arch, but they are specific to qla2xxx.
== Test Case ==
A test kernel was built with these patches and tested by IBM.
IBM states the test kernel resolved the bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770003/+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 1759723] Re: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation.
Please always attach patches to the LP bug - this is the central tool for bug activity and would allow everybody involved to find everything at one place. -- 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/1759723 Title: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation. Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Problem Description: === Performed HOTPLUG cpu attach operation for the guest and guest console becomes unresponsive. Steps to re-create: == 1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels 2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes root@boslcp3:/home# uname -a Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.15.0-12-generic root@boslcp3g3:/kte/tools/setup.d# uname -a Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g3:/kte/tools/setup.d# uname -r 4.15.0-12-generic 3. Started HTX & stress-ng for on guest for 10-15 min 4. Cleaned up the tests to perform hot-plug and ensure enough memory and cpu was there (killed all Process using kill) 5. Performed cpu hot-plug and guest went into hung state Before Hotplug: root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu 64 root@boslcp3:~# 6. After this operation, guest becomes unrepsonsive as below root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3626.146375] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3626.146699] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 seconds. [ 3626.147016] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 seconds. [ 3626.147361] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds. [ 3626.147686] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds. [ 3626.147937] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds. [ 3626.148173] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds. [ 3626.148406] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. root@boslcp3g3:~# root@boslcp3g3:~# ps -ef | grep stress-ng [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3746.978221] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3746.978534] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4446.361899] systemd[1]: Failed to start Journal Service. [ 4897.632142] systemd[1]: Failed to sta
[Kernel-packages] [Bug 1759723] Comment bridged from LTC Bugzilla
--- Comment From lagar...@br.ibm.com 2018-05-16 10:11 EDT--- Patch set was resent to Canonical mailing list by Ziviani. -- 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/1759723 Title: ISST-LTE:KVM:Ubuntu18.04:BostonLC:boslcp3:boslcp3g3:Guest conosle hangs after hotplug CPU add operation. Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Problem Description: === Performed HOTPLUG cpu attach operation for the guest and guest console becomes unresponsive. Steps to re-create: == 1. updated boslcp3 host BMC :116 & PNOR: 20180302 levels 2. Installed Ubuntu1804 on boslcp3 host & guests with trap issue fixes root@boslcp3:/home# uname -a Linux boslcp3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:/home# uname -r 4.15.0-12-generic root@boslcp3g3:/kte/tools/setup.d# uname -a Linux boslcp3g3 4.15.0-12-generic #13+leo20180320 SMP Tue Mar 20 13:10:42 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3g3:/kte/tools/setup.d# uname -r 4.15.0-12-generic 3. Started HTX & stress-ng for on guest for 10-15 min 4. Cleaned up the tests to perform hot-plug and ensure enough memory and cpu was there (killed all Process using kill) 5. Performed cpu hot-plug and guest went into hung state Before Hotplug: root@boslcp3:~# virsh dumpxml boslcp3g3 | grep vcpu 64 root@boslcp3:~# 6. After this operation, guest becomes unrepsonsive as below root@boslcp3g3:~# [ 3626.140773] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3626.146375] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146457] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146624] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3626.146699] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.146768] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.146939] INFO: task rs:main Q:Reg:1995 blocked for more than 120 seconds. [ 3626.147016] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147088] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147285] INFO: task kworker/u128:2:57691 blocked for more than 120 seconds. [ 3626.147361] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147434] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147622] INFO: task smbd:1449 blocked for more than 120 seconds. [ 3626.147686] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.147760] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.147875] INFO: task smbd:1452 blocked for more than 120 seconds. [ 3626.147937] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148010] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148110] INFO: task smbd:1454 blocked for more than 120 seconds. [ 3626.148173] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.148344] INFO: task cron:1461 blocked for more than 120 seconds. [ 3626.148406] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3626.148488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. root@boslcp3g3:~# root@boslcp3g3:~# ps -ef | grep stress-ng [ 3746.978098] INFO: task jbd2/vda2-8:584 blocked for more than 120 seconds. [ 3746.978221] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978301] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3746.978447] INFO: task systemd-journal:665 blocked for more than 120 seconds. [ 3746.978534] Tainted: GW4.15.0-12-generic #13+leo20180320 [ 3746.978607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4446.361899] systemd[1]: Failed to start Journal Service. [ 4897.632142] systemd[1]: Failed to start Journal Service. ^Z
[Kernel-packages] [Bug 1771308] Re: Adding the user to a new group doesn't take effect on logout and back in
Daniel, what do you mean by "running process"? The steps involve login out and back in, so starting a new session, group changes should be active on a new login no? ** Package changed: linux (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1771308 Title: Adding the user to a new group doesn't take effect on logout and back in Status in gdm3 package in Ubuntu: New Bug description: Steps to reproduce: Log in to a GNOME session Use adduser to add yourself to an existing group Log out and back in Open a terminal, run "groups" and notice that your user isn't in the new group. Reboot and log in, and you user is now in the group. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1771308/+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 1771238] Re: Not able to passthrough > 32 PCIe devices to a KVM Guest
** 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/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
Status in linux package in Ubuntu:
Confirmed
Status in qemu package in Ubuntu:
New
Bug description:
Using an Ubuntu Server 16.04-based host with KVM hypervisor installed,
we are unable to launch a vanilla Ubuntu Server 16.04.4 guest with >=
32 PCIe devices. It is 100% reproducible. Using fewer PCIe devices
works fine. We are using the vanilla kvm and qemu packages from the
Canonical repos.
The ultimate goal is to create a KVM Guest wherein I can passthrough
44 PCI devices.
When a KVM Guest launches, it also has some internal PCIe devices
including host bridge, USB, IDE (for virtual disk), and virtual nic
etc.
Script used to launch all devices looks like this:
#!/bin/bash
NAME=16gpuvm
sudo qemu-img create -f qcow2 /home/lab/kvm/images/${NAME}.img 40G &&
sudo virt-install \
--name ${NAME} \
--ram 716800 \
--vcpus 88 \
--disk path=/home/lab/kvm/images/${NAME}.img,format=qcow2 \
--network bridge=virbr0 \
--graphics none \
--host-device 34:00.0 \
--host-device 36:00.0 \
--host-device 39:00.0 \
--host-device 3b:00.0 \
--host-device 57:00.0 \
--host-device 59:00.0 \
--host-device 5c:00.0 \
--host-device 5e:00.0 \
--host-device 61:00.0 \
--host-device 62:00.0 \
--host-device 63:00.0 \
--host-device 65:00.0 \
--host-device 66:00.0 \
--host-device 67:00.0 \
--host-device 35:00.0 \
--host-device 3a:00.0 \
--host-device 58:00.0 \
--host-device 5d:00.0 \
--host-device 2e:00.0 \
--host-device 2f:00.0 \
--host-device 51:00.0 \
--host-device 52:00.0 \
--host-device b7:00.0 \
--host-device b9:00.0 \
--host-device bc:00.0 \
--host-device be:00.0 \
--host-device e0:00.0 \
--host-device e2:00.0 \
--host-device e5:00.0 \
--host-device e7:00.0 \
--host-device c1:00.0 \
--host-device c2:00.0 \
--host-device c3:00.0 \
--host-device c5:00.0 \
--host-device c6:00.0 \
--host-device c7:00.0 \
--host-device b8:00.0 \
--host-device bd:00.0 \
--host-device e1:00.0 \
--host-device e6:00.0 \
--host-device b1:00.0 \
--host-device b2:00.0 \
--host-device da:00.0 \
--host-device db:00.0 \
--console pty,target_type=serial \
--location http://ftp.ubuntu.com/ubuntu/dists/xenial/main/installer-amd64 \
--initrd-inject=/home/lab/kvm/images/preseed.cfg \
--extra-args="
console=ttyS0,115200
locale=en_US
console-keymaps-at/keymap=us
console-setup/ask_detect=false
console-setup/layoutcode=us
keyboard-configuration/layout=USA
keyboard-configuration/variant=USA
hostname=${NAME}
file=file:/preseed.cfg
"
Passing > 32 device causes this issue: 32nd device hits a DPC error
and the host/HV crashes:
Apr 25 22:34:35 xpl-evt-16 kernel: [18125.977496] dpc :5b:10.0:pcie210:
DPC containment event, status:0x0009 source:0x
Apr 25 22:34:35 xpl-evt-16 kernel: [18125.977500] dpc :5b:10.0:pcie210:
DPC unmasked uncorrectable error detected, remove downstream devices
Apr 25 22:34:35 xpl-evt-16 kernel: [18125.994326] vfio-pci :5e:00.0:
Refused to change power state, currently in D3
Apr 25 22:34:35 xpl-evt-16 kernel: [18125.994427] iommu: Removing device
:5e:00.0 from group 92
From syslog (attached)
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194358] dpc :bb:04.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194387] dpc :bb:10.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194413] dpc :d9:00.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194439] dpc :d9:01.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194472] dpc :d9:02.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194499] dpc :d9:03.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194526] dpc :d9:04.0:pcie210:
DPC error containment capabilities: Int Msg #3, RPExt- PoisonedTLP+ SwTrigger+
RP PIO Log 0, DL_ActiveErr+
Apr 25 22:37:13 xpl-evt-16 kernel: [2.194553] dpc :d9:0c.0:pcie210:
DPC error containment capabilities: Int
[Kernel-packages] [Bug 1771542] Re: Suspend to idle: Open lid didn't resume
** 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/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+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 1770095] Comment bridged from LTC Bugzilla
--- Comment From dougm...@us.ibm.com 2018-05-16 11:05 EDT--- (In reply to comment #8) > Would you like me to build another test kernel with a version, so it won't > collide? I haven't heard back from Naveed, who was going to test last night. I hate to ask for a new kernel if he was able to test. But, this brings up a question I had. I am not familiar with the Ubuntu build procedures, so I'm just comparing to RedHat and Linux Makefile. In those build methods, there is a way to append an arbitrary string to the version (EXTRAVERSION) and it allows the kernel to avoid conflicts. Does such a mechanism exist for Ubuntu builds? Up to now, it seems that only numeric strings are being appended (e.g. "-21", "-90"). -- 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/1770095 Title: Need fix to aacraid driver to prevent panic Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Douglas Miller - 2018-05-08 15:45:13 == +++ This bug was initially created as a clone of Bug #167565 +++ A recent commit to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a bug whereby a panic may happen under certain recovery situations. The following commit fixes that: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?h=fixes&id=7d3af7d96af7b9f51e1ef67b6f4725f545737da2 We need this commit backported to Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770095/+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 1737423] Re: With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video memory misdetected as 512 Mb : result was kernel panic in worst case and memory crash in best
Found some document about size determination in pci devices
had run lspi
jean@jean-Soisy:~$ sudo lspci -vv -k - -s 03:09.0
03:09.0 VGA compatible controller: NVIDIA Corporation NV44A [GeForce 6200] (rev
a1) (prog-if 00 [VGA controller])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR- https://wiki.osdev.org/PCI
https://stackoverflow.com/questions/19006632/how-is-a-pci-pcie-bar-size-determined/39618552#39618552
To determine the amount of address space needed by a PCI device, you must save
the original value of the BAR,
write a value of all 1's to the register, then read it back.
The amount of memory can then be determined by masking the information bits,
performing a bitwise NOT ('~' in C), and incrementing the value by 1. The
original value of the BAR should then be restored.
on my computer : using sudo bless
parameter are located at /sys/bus/pci/devices/:03:09.0/config
replaced 08 00 00 c0 by ff ff ff ff then, computer blocked, but was able to
read 08 00 00 e0
that means
dropping 4 bits LSB -> 00 00 00 e0
inverting bitwise ff ff ff 10
adding one 00 00 00 20 means 512 M
BUT https://www.xilinx.com/Attachment/PCI_SPEV_V3_0.pdf
6.2.5.1. Address Maps
Devices are free to consume more address space than required
after explanation of a computation method, precision is given
The resultant 32-bit value is the memory/I/O range size decoded by the
register.
I Think that the problem is here = adress space decoded, but not
populated
Regards
Jean COLIN
--
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/1737423
Title:
With a (cheap) video card in PCI Geforce 6200 (NV44A) with 256Mb video
memory misdetected as 512 Mb : result was kernel panic in worst case
and memory crash in best case
Status in linux package in Ubuntu:
Confirmed
Bug description:
Under XP
card detected as
PCI\VEN_10DE&DEV_0221&SUBSYS_&REV_A1\4&3A321F38&0&48F0
PCI\VEN_10DE&DEV_0221&SUBSYS_&REV_A1\4&3A321F38&0&48F0
PCI\VEN_10DE&DEV_0221&SUBSYS_&REV_A1
PCI\VEN_10DE&DEV_0221&CC_03
memory range 9400 94FF
memory range C000 DFFF
memory range 9200 92FF
IRQ 09
IO range 03B0 03BB
IO range 03C0 03DF
memory range 000A 000B
Processeur graphique :GeForce 6200
Version du pilote : 307.83
Prise en charge DirectX : 9.0c
Horloge principale : 300 MHz
Débit de données mémoire :1064 MHz
Interface de mémoire :64 bits
Mémoire : 256 Mo
Type de mémoire : DDR2
Version BIOS vidéo : 5.44.A2.10.26
IRQ : 9
Bus : PCI
correctly detected as 256Mb and working
Under linux
file /var/log/Xorg.0.log
contains 18.759] (--) PCI: (0:3:9:0) 10de:0221:: rev 161, Mem @
0x9400/16777216, 0xc000/536870912, 0x9200/16777216, BIOS @
0x/131072
card bad detection ... 0xc000/536870912 correct adress, wrong size
536870912 soit 512Mo
output of:
sudo lshw -C display; lsb_release -a; uname -a
is
jean@jean-Soisy:~$ sudo lshw -C display; lsb_release -a; uname -a
[sudo] password for jean:
*-display
description: Display controller
produit: 82865G Integrated Graphics Controller
fabriquant: Intel Corporation
identifiant matériel: 2
information bus: pci@:00:02.0
version: 02
bits: 32 bits
horloge: 33MHz
fonctionnalités: pm bus_master cap_list rom
configuration: driver=i915 latency=0
ressources: irq:16 mémoire:a000-a7ff mémoire:9000-9007
portE/S:1800(taille=8)
*-display
description: VGA compatible controller
produit: NV44A [GeForce 6200]
fabriquant: NVIDIA Corporation
identifiant matériel: 9
information bus: pci@:03:09.0
version: a1
bits: 32 bits
horloge: 66MHz
fonctionnalités: pm vga_controller bus_master cap_list rom
configuration: driver=nouveau latency=40 maxlatency=1 mingnt=5
ressources: irq:21 mémoire:9400-94ff mémoire:c000-dfff
mémoire:9200-92ff mémoire:e000-e001
No LSB modules are available.
Distributor ID:Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename:trusty
Linux jean-Soisy 3.13.0-135-generic #184-Ubuntu SMP Wed Oct 18 11:56:31 UTC
2017 i686 i686 i686 GNU/Linux
Attempted to find where the memory size detection lies in the code,
but was too far in the labyrinth for me.
Regards
Jean COLIN
---
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jean 2206 F pulseaudio
[Kernel-packages] [Bug 1771555] [NEW] dmesg Error seen on system booting from Ubuntu18.04
You have been subscribed to a public bug: Problem Description === dmesg Error seen on system booting from Ubuntu18.04 Is this an issue? [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) user1@yob45wos:~$ sudo dmesg --level=alert user1@yob45wos:~$ sudo dmesg --level=crit user1@yob45wos:~$ sudo dmesg --level=err [3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.531263] vio vio: uevent: failed to send synthetic uevent [4.521383] nouveau 0004:04:00.0: unknown chipset (14a1) [4.521889] nouveau 0035:03:00.0: unknown chipset (14a1) [4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not supported by firmware: 0 0 [4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not supported by firmware: 0 0 [5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [ 22.109545] vio vio: uevent: failed to send synthetic uevent user1@yob45wos:~$ > > Problem Description > === > dmesg Error seen on system booting from Ubuntu18.04 > Is this an issue? These messages are seen on every IPL. Is there an issue? > [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) > [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) These messages should be marked as Warnings instead of Errors as they it supposedly a warning and not an error. This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg --level=err' again in 18.04. * In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) (LP: #1656908) - SAUCE: ima: Downgrade error to warning Mirroring this bug to distro to fix this in the latest kernel. Thank you. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: architecture-ppc64le bot-comment bugnameltc-166612 severity-high targetmilestone-inin--- -- dmesg Error seen on system booting from Ubuntu18.04 https://bugs.launchpad.net/bugs/1771555 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04
Can you run uname -a to confirm the correct kernel is booted? You should see this string in the output: "lp1768103". -- 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/1768103 Title: Lancer A0 Asic HBA's won't boot with 18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't boot with the lpfc driver in Ubuntu 18.04. After further review and discussion, this has been deemed a low risk issue since early A0 HBA's were only ever shipped to OEMs for test purposes. These cards were never shipped to end customers. We have been working to replace those cards whenever we discover them. We'll leave it up to Canonical to decide whether they want to pull this in this single patch to an 18.04 subsequent update. Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 but can see LPe16002B-M6 Resolution: new lpfc driver patch update. scsi: lpfc: Fix WQ/CQ creation for older asic's. https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue&id=83fae8ca4ae09403bfb99542f1aaa292c06cb111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768103/+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 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Just to confirm, 4.15-rc1 does not have the issue, but 4.15 final does?
If that is the case, we can try to narrow it down further. Could you
test v4.15-rc9:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/
--
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/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09/13/2016
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.board.name: ProLiant DL360
[Kernel-packages] [Bug 1770095] Re: Need fix to aacraid driver to prevent panic
Yes, you can add EXTRAVERSION info to the kernel name. This is done in the file: ~/debian.master/changelog. The top line would be changed like the following: linux (4.15.0-20.21) bionic; urgency=medium TO linux (4.15.0-20.21~lp1770095) bionic; urgency=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/1770095 Title: Need fix to aacraid driver to prevent panic Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Douglas Miller - 2018-05-08 15:45:13 == +++ This bug was initially created as a clone of Bug #167565 +++ A recent commit to aacraid (b60710ec7d7ab1ca277b458338563ac21b393906) introduced a bug whereby a panic may happen under certain recovery situations. The following commit fixes that: https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?h=fixes&id=7d3af7d96af7b9f51e1ef67b6f4725f545737da2 We need this commit backported to Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770095/+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 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: bionic -- 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/1771555 Title: dmesg Error seen on system booting from Ubuntu18.04 Status in linux package in Ubuntu: New Bug description: Problem Description === dmesg Error seen on system booting from Ubuntu18.04 Is this an issue? [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) user1@yob45wos:~$ sudo dmesg --level=alert user1@yob45wos:~$ sudo dmesg --level=crit user1@yob45wos:~$ sudo dmesg --level=err [3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.531263] vio vio: uevent: failed to send synthetic uevent [4.521383] nouveau 0004:04:00.0: unknown chipset (14a1) [4.521889] nouveau 0035:03:00.0: unknown chipset (14a1) [4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not supported by firmware: 0 0 [4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not supported by firmware: 0 0 [5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [ 22.109545] vio vio: uevent: failed to send synthetic uevent user1@yob45wos:~$ > > Problem Description > === > dmesg Error seen on system booting from Ubuntu18.04 > Is this an issue? These messages are seen on every IPL. Is there an issue? > [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) > [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) These messages should be marked as Warnings instead of Errors as they it supposedly a warning and not an error. This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg --level=err' again in 18.04. * In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) (LP: #1656908) - SAUCE: ima: Downgrade error to warning Mirroring this bug to distro to fix this in the latest kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771555/+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 1771480] Re: WARNING: CPU: 28 PID: 34085 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90()
The dev_disable_lro warning is happening due to some logic issues in the features code. The LRO on the VLAN (bond0.200, e.g.) that's being warned about does end up being disabled by a NETDEV_FEAT_CHANGE callback when the underlying bond0's features are updated, so the warning is spurious. Tracing the dev_disable_lro -> netdev_update_features for the bond0.2004 VLAN, I see: name="bond0" feat=219db89 hw_feat=20219cbe9 want_feat=20219cbe9 vlan_feat=198069 NETIF_F_LRO = 0x8000 dev_disable_lro wanted_features &= ~NETIF_F_LRO bond0.2004 wanted_features = 0x200194869# no LRO __netdev_update_features features = netdev_get_wanted_features return (dev->features & ~dev->hw_features) | dev->wanted_features; (0x19d809 & ~0x23839487b) | 0x200194869 ^LRO ^no LRO^no LRO 0x9000 | 0x200194869 $2 = 0x20019d869 ^ LRO vlan_dev_fix_features(dev, 0x20019d869) # has LRO struct net_device *real_dev = vlan_dev_priv(dev)->real_dev; netdev_features_t old_features = features; features &= real_dev->vlan_features;# 0x198069 has LRO features |= NETIF_F_RXCSUM; # 0x100198069 has LRO features &= real_dev->features; # 0x198009 has LRO features |= old_features & NETIF_F_SOFT_FEATURES; # save GSO / GRO features |= NETIF_F_LLTX; return features; # will have LRO So, basically, LRO is set in the underlying bond0's features, so it ends up being kept in the VLAN device's features even though it wasn't in wanted_features. Later, dev_disable_lro will call dev_disable_lro on all the lower devices (the bond0 in this case), and the update of features for the bond0 will issue a NETDEV_FEAT_CHANGE callback to the bond0.2004 VLAN, which will then set the features correctly. The Ubuntu 3.13 __netdev_update_features (called by dev_disable_lro via netdev_update_features) lacks additional logic found in later kernels to sync the features to lower devices. That presumably triggers the NETDEV_FEAT_CHANGE within the call to __netdev_update_features so that the bond0.2004 VLAN is updated before we return back to dev_disable_lro (but I haven't verified this). I suspect the fix to eliminate the warning is to apply the "sync_lower:" block from a later kernel __netdev_update_features to 3.13, along with the netdev_sync_lower_features function it uses. -- 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/1771480 Title: WARNING: CPU: 28 PID: 34085 at /build/linux- 90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() Status in linux package in Ubuntu: Incomplete Bug description: I have multiple instances of this dev_disable_lro error in kern.log. Also seeing this: systemd-udevd[1452]: timeout: killing 'bridge-network-interface' [2765] <4>May 1 22:56:42 xxx kernel: [ 404.520990] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:56:44 xxx kernel: [ 406.926429] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:56:45 xxx kernel: [ 407.569020] [ cut here ] <4>May 1 22:56:45 xxx kernel: [ 407.569029] WARNING: CPU: 28 PID: 34085 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() <4>May 1 22:56:45 xxx kernel: [ 407.569032] netdevice: bond0.2004 <4>May 1 22:56:45 xxx kernel: [ 407.569032] failed to disable LRO! <4>May 1 22:56:45 xxx kernel: [ 407.569035] Modules linked in: 8021q garp mrp bridge stp llc bonding iptable_filter ip_tables x_tables nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipmi_devintf mxm_wmi dcdbas x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd lpc_ich mei_me mei ipmi_si shpchp wmi acpi_power_meter mac_hid xfs libcrc32c raid10 usb_storage raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 igb ixgbe i2c_algo_bit multipath ahci dca ptp libahci pps_core linear megaraid_sas mdio dm_multipath scsi_dh <4>May 1 22:56:45 xxx kernel: [ 407.569112] CPU: 28 PID: 34085 Comm: brctl Not tainted 3.13.0-142-generic #191-Ubuntu <4>May 1 22:56:45 xxx kernel: [ 407.569115] Hardware name: Dell Inc. PowerEdge R730xd/072T6D, BIOS 2.7.1 001/22/2018 <4>May 1 22:56:45 xxx kernel: [ 407.569118] 881fcc753c70 8172e7fc 881fcc753cb8 <4>May 1 22:56:45 xxx kernel: [ 407.569129] 0009 881fcc753ca8 8106afad 883fcc6f8000 <4>May 1 22:56:45 xxx kernel: [ 407.569139] 883fcc696880 883fcc6f8000 881fce82dd40 <4>May 1 22:56:45 xxx
[Kernel-packages] [Bug 1771620] [NEW] Hang on network interface removal in Xen virtual machine
Public bug reported: On a hosting platform running Xen hypervisor, in a virtual machine with Ubuntu 18.04 system and the default kernel from Ubuntu, I try to detach a virtual network interface. On the Xen side, the virtual interface is removed from the VM but the kernel still has the interface. Then a couple of minutes afterwards, the kernel log show this kernel trace: INFO: task xenwatch:108 blocked for more than 120 seconds. Tainted: GW4.15.0-20-generic #21-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. xenwatchD0 108 2 0x8000 Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 xennet_remove+0xda/0x1c0 ? wait_woken+0x80/0x80 xenbus_dev_remove+0x54/0xa0 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 ? xenbus_otherend_changed+0x110/0x110 device_del+0x13d/0x360 ? xenbus_otherend_changed+0x110/0x110 ? xenbus_otherend_changed+0x110/0x110 device_unregister+0x1a/0x60 xenbus_dev_changed+0xa3/0x1e0 ? xenwatch_thread+0xcc/0x160 frontend_changed+0x21/0x50 xenwatch_thread+0xc4/0x160 ? wait_woken+0x80/0x80 kthread+0x121/0x140 ? find_watch+0x40/0x40 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 In the git repository of Linux, the commit c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 (xen-netfront: Fix hang on device removal) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 seems to be related to this situation. I rebuilded the Ubuntu kernel from the package source and applied this patch. Once the VM has booted with the new kernel, I was able to remove network interface without hangs from the kernel. I also booted the VM with the Ubuntu kernel 4.13.0-42-generic and was able to remove the network interface with success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 16 16:36:06 2018 ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1771620 Title: Hang on network interface removal in Xen virtual machine Status in linux-signed package in Ubuntu: New Bug description: On a hosting platform running Xen hypervisor, in a virtual machine with Ubuntu 18.04 system and the default kernel from Ubuntu, I try to detach a virtual network interface. On the Xen side, the virtual interface is removed from the VM but the kernel still has the interface. Then a couple of minutes afterwards, the kernel log show this kernel trace: INFO: task xenwatch:108 blocked for more than 120 seconds. Tainted: GW4.15.0-20-generic #21-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. xenwatchD0 108 2 0x8000 Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 xennet_remove+0xda/0x1c0 ? wait_woken+0x80/0x80 xenbus_dev_remove+0x54/0xa0 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 ? xenbus_otherend_changed+0x110/0x110 device_del+0x13d/0x360 ? xenbus_otherend_changed+0x110/0x110 ? xenbus_otherend_changed+0x110/0x110 device_unregister+0x1a/0x60 xenbus_dev_changed+0xa3/0x1e0 ? xenwatch_thread+0xcc/0x160 frontend_changed+0x21/0x50 xenwatch_thread+0xc4/0x160 ? wait_woken+0x80/0x80 kthread+0x121/0x140 ? find_watch+0x40/0x40 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 In the git repository of Linux, the commit c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 (xen-netfront: Fix hang on device removal) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 seems to be related to this situation. I rebuilded the Ubuntu kernel from the package source and applied this patch. Once the VM has booted with the new kernel, I was able to remove network interface without hangs from the kernel. I also booted the VM with the Ubuntu kernel 4.13.0-42-generic and was able to remove the network interface with success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 16 16:36:06 2
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Hi everyone, I also have an Asus ROG G752-VS with the same dead Elantech touchpad you have. But I got it to work, briefly: The Anaconda setup of Fedora 28 Atomic Workstation (https://torrent.fedoraproject.org/torrents/Fedora-AtomicWorkstation-ostree-x86_64-28.torrent) fully activates the touchpad, even with multitouch and tap-to-click. Unfortunately, after installation and ensuing re-boot the touchpad is dead again. For some reason that same installer doesn‘t work in all the other Fedora versions. Just wanted to share that, maybe it helps... -- 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/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0
[Kernel-packages] [Bug 1744173] Re: rfi-flush: Switch to new linear fallback flush
Hi Juerg, > When updating to 4.4.117 we reverted a bunch of SAUCE rfi-flush patches and > replaced them with the > upstream versions. Is there a possibility that your patches are no longer > required with those updates? None of these patches seems to be integrated int 4.4.0-124. So, we will need to backport them again. I will be working to get this done. What about artful (kernel 4.13). Are the patches still applying? -- 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/1744173 Title: rfi-flush: Switch to new linear fallback flush Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Bug description: [Impact] Change flush from congruence-first with dependencies to linear with no dependencies, which increases flush performance by 8x on P8, and 3x on P9 (as measured with null syscall loop, which will have the flush area in the L2). The flush also becomes simpler and more adaptable to different cache geometries. [Test Case] TBD. [Regression Potential] The risk is deemed low since the changes are confined to POWER only and the provided test kernels have been tested by IBM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1744173/+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 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X
@Peridot, Request from Upstream: For the original 4.13 kernel, I don't see any attachments that have the AMD-Vi messages in question. Were they completion timeouts (like in the later mainline kernel test, which I'll get to in a bit) or I/O page fault messages? Without that information it is hard to determine what the issue really is. (Just as an FYI, if the IOMMU is disabled in BIOS, then iommu=soft is not necessary on the kernel command line). For the upstream kernel test, since this is a Ryzen system, it's possible that the BIOS does not have a requisite fix for SME and IOMMU (see [1]). On the upstream kernel, if memory encryption is active by default without this BIOS fix, then the result is AMD-Vi completion-wait timeout messages. Try booting with mem_encrypt=off on the kernel command line or build a kernel with CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=n and see if that allows the kernel to boot. Thanks, Tom [1] https://bugzilla.kernel.org/show_bug.cgi?id=199513 ** Bug watch added: Linux Kernel Bug Tracker #199513 https://bugzilla.kernel.org/show_bug.cgi?id=199513 -- 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/1747463 Title: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu. There are lots of AMD-Vi logged events and I get irq crashes or acpi hangups with a 'normal' boot. I got it to boot by disabling IOMMU in the BIOS and adding "iommu=soft" to the kernel booting options in grub. linux can then detect everything properly (all cores) and I've had zero crashes. The only issue is that it's using software IOMMU which could have a performance penalty because it has to copy all the data of some PCI devices to sub 4G regions. Alternatively it boots with the kernel option "acpi=off" but only detects a single core/thread. I attached a kernel log. I believe(d) this might be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085 --- ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fixme 1487 F pulseaudio /dev/snd/controlC0: fixme 1487 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece InstallationDate: Installed on 2018-01-31 (4 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group B350GT5 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.170 RfKill: Tags: bionic Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.13 dmi.board.asset.tag: None dmi.board.name: B350GT5 dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: None dmi.product.name: B350GT5 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1747463/+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 1771480] Re: WARNING: CPU: 28 PID: 34085 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90()
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) 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/1771480 Title: WARNING: CPU: 28 PID: 34085 at /build/linux- 90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() Status in linux package in Ubuntu: Triaged Bug description: I have multiple instances of this dev_disable_lro error in kern.log. Also seeing this: systemd-udevd[1452]: timeout: killing 'bridge-network-interface' [2765] <4>May 1 22:56:42 xxx kernel: [ 404.520990] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:56:44 xxx kernel: [ 406.926429] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:56:45 xxx kernel: [ 407.569020] [ cut here ] <4>May 1 22:56:45 xxx kernel: [ 407.569029] WARNING: CPU: 28 PID: 34085 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() <4>May 1 22:56:45 xxx kernel: [ 407.569032] netdevice: bond0.2004 <4>May 1 22:56:45 xxx kernel: [ 407.569032] failed to disable LRO! <4>May 1 22:56:45 xxx kernel: [ 407.569035] Modules linked in: 8021q garp mrp bridge stp llc bonding iptable_filter ip_tables x_tables nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipmi_devintf mxm_wmi dcdbas x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd lpc_ich mei_me mei ipmi_si shpchp wmi acpi_power_meter mac_hid xfs libcrc32c raid10 usb_storage raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 igb ixgbe i2c_algo_bit multipath ahci dca ptp libahci pps_core linear megaraid_sas mdio dm_multipath scsi_dh <4>May 1 22:56:45 xxx kernel: [ 407.569112] CPU: 28 PID: 34085 Comm: brctl Not tainted 3.13.0-142-generic #191-Ubuntu <4>May 1 22:56:45 xxx kernel: [ 407.569115] Hardware name: Dell Inc. PowerEdge R730xd/072T6D, BIOS 2.7.1 001/22/2018 <4>May 1 22:56:45 xxx kernel: [ 407.569118] 881fcc753c70 8172e7fc 881fcc753cb8 <4>May 1 22:56:45 xxx kernel: [ 407.569129] 0009 881fcc753ca8 8106afad 883fcc6f8000 <4>May 1 22:56:45 xxx kernel: [ 407.569139] 883fcc696880 883fcc6f8000 881fce82dd40 <4>May 1 22:56:45 xxx kernel: [ 407.569150] Call Trace: <4>May 1 22:56:45 xxx kernel: [ 407.569160] [] dump_stack+0x64/0x82 <4>May 1 22:56:45 xxx kernel: [ 407.569168] [] warn_slowpath_common+0x7d/0xa0 <4>May 1 22:56:45 xxx kernel: [ 407.569175] [] warn_slowpath_fmt+0x4c/0x50 <4>May 1 22:56:45 xxx kernel: [ 407.569183] [] dev_disable_lro+0x87/0x90 <4>May 1 22:56:45 xxx kernel: [ 407.569195] [] br_add_if+0x1f3/0x430 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569205] [] add_del_if+0x5d/0x90 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569215] [] br_dev_ioctl+0x5b/0x90 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569223] [] dev_ifsioc+0x313/0x360 <4>May 1 22:56:45 xxx kernel: [ 407.569230] [] ? dev_get_by_name_rcu+0x69/0x90 <4>May 1 22:56:45 xxx kernel: [ 407.569237] [] dev_ioctl+0xe9/0x590 <4>May 1 22:56:45 xxx kernel: [ 407.569245] [] sock_do_ioctl+0x45/0x50 <4>May 1 22:56:45 xxx kernel: [ 407.569252] [] sock_ioctl+0x1f0/0x2c0 <4>May 1 22:56:45 xxx kernel: [ 407.569260] [] do_vfs_ioctl+0x2e0/0x4c0 <4>May 1 22:56:45 xxx kernel: [ 407.569267] [] ? fput+0xe/0x10 <4>May 1 22:56:45 xxx kernel: [ 407.569273] [] SyS_ioctl+0x81/0xa0 <4>May 1 22:56:45 xxx kernel: [ 407.569283] [] system_call_fastpath+0x2f/0x34 <4>May 1 22:56:45 xxx kernel: [ 407.569287] ---[ end trace df5aa31d75a7e2b1 ]--- <4>May 1 22:56:54 xxx kernel: [ 416.320138] bonding: bond1: Warning: the permanent HWaddr of enp131s0f0 - a0:36:9f:c1:25:d0 - is still in use by bond1. Set the HWaddr of enp131s0f0 to a different address to avoid conflicts. <4>May 1 22:57:00 xxx kernel: [ 422.362677] bonding: bond1: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:57:07 xxx kernel: [ 429.522843] [ cut here ] And here: <4>May 1 22:57:07 xxx kernel: [ 429.522843] [ cut here ] <4>May 1 22:57:07 xxx kernel: [ 429.522853] WARNING: CPU: 0 PID: 34191 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() <4>May 1 22:57:07 xxx kernel: [ 429.522857] netdevice: bond1.2001 <4>May 1 22:57:07 xxx kernel: [ 429.522857] failed to disable LRO! <4>May 1 22:57:07 xxx kernel: [ 429.522861] Modules linked in: 8021q garp mrp bridge stp llc bonding iptable_f
[Kernel-packages] [Bug 1771467] Re: Reboot/shutdown kernel panic on HP DL360 Gen9 w/ bionic 4.15.0
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.17 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.17-rc5
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
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/1771467
Title:
Reboot/shutdown kernel panic on HP DL360 Gen9 w/ bionic 4.15.0
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Bionic:
Incomplete
Bug description:
Verified on multiple DL360 Gen9 servers with up to date firmware.
Just before reboot or shutdown, there is the following panic:
[ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 289.093085] {1}[Hardware Error]: event severity: fatal
[ 289.093087] {1}[Hardware Error]: Error 0, type: fatal
[ 289.093088] {1}[Hardware Error]: section_type: PCIe error
[ 289.093090] {1}[Hardware Error]: port_type: 4, root port
[ 289.093091] {1}[Hardware Error]: version: 1.16
[ 289.093093] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093094] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093095] {1}[Hardware Error]: slot: 0
[ 289.093096] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093097] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093098] {1}[Hardware Error]: class_code: 040600
[ 289.093378] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093380] {1}[Hardware Error]: Error 1, type: fatal
[ 289.093381] {1}[Hardware Error]: section_type: PCIe error
[ 289.093382] {1}[Hardware Error]: port_type: 4, root port
[ 289.093383] {1}[Hardware Error]: version: 1.16
[ 289.093384] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 289.093386] {1}[Hardware Error]: device_id: :00:01.0
[ 289.093386] {1}[Hardware Error]: slot: 0
[ 289.093387] {1}[Hardware Error]: secondary_bus: 0x03
[ 289.093388] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x2f02
[ 289.093674] {1}[Hardware Error]: class_code: 040600
[ 289.093676] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 289.093678] Kernel panic - not syncing: Fatal hardware error!
[ 289.093745] Kernel Offset: 0x1cc0 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 289.105835] ERST: [Firmware Warn]: Firmware does not respond in time.
It does eventually restart after this. Then during the subsequent
POST, the following warning appears:
Embedded RAID 1 : Smart Array P440ar Controller - (2048 MB, V6.30) 7 Logical
Drive(s) - Operation Failed
- 1719-Slot 0 Drive Array - A controller failure event occurred prior
to this power-up. (Previous lock up code = 0x13) Action: Install the
latest controller firmware. If the problem persists, replace the
controller.
The latter's symptoms are described in
https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
but the running storage controller firmware is much newer than the
doc's resolution.
Neither of these problems occur during shutdown/reboot on the xenial
kernel.
FWIW, when running on old P89 (1.50 (07/20/2015) vs 2.56
(01/22/2018)), the shutdown failure mode was a loop like so:
[529151.035267] NMI: IOCK error (debug interrupt?) for reason 75 on CPU 0.
[529153.222883] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.222884] Do you have a strange power saving mode enabled?
[529153.222884] Dazed and confused, but trying to continue
[529153.554447] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554448] Do you have a strange power saving mode enabled?
[529153.554449] Dazed and confused, but trying to continue
[529153.554450] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554451] Do you have a strange power saving mode enabled?
[529153.554452] Dazed and confused, but trying to continue
[529153.554452] Uhhuh. NMI received for unknown reason 25 on CPU 0.
[529153.554453] Do you have a strange power saving mode enabled?
[529153.554454] Dazed and confused, but trying to continue
[
[Kernel-packages] [Bug 1771446] Re: package linux-headers-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1771446 Title: package linux-headers-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in linux package in Ubuntu: Incomplete Bug description: Computer starts up slower. Blank screen lasts too long. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.4.0-96-generic 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carol 1942 F pulseaudio /dev/snd/controlC0: carol 1942 F pulseaudio Date: Mon May 14 16:29:34 2018 DuplicateSignature: package:linux-headers-4.4.0-96-generic:4.4.0-96.119 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.12) ... dpkg: error processing package linux-headers-4.4.0-96-generic (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration HibernationDevice: RESUME=UUID=4a76a624-f2db-4b58-be3e-90c8580d30be InstallationDate: Installed on 2016-12-06 (524 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Hewlett-Packard HP Compaq dc7700 Ultra-slim Desktop ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=85ae04ce-a8ef-48b6-8795-9343c4a79d69 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.17 RfKill: SourcePackage: linux Title: package linux-headers-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.10 dmi.board.name: 0A5Ch dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 1222 dmi.chassis.type: 15 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.10:bd04/13/2007:svnHewlett-Packard:pnHPCompaqdc7700Ultra-slimDesktop:pvr:rvnHewlett-Packard:rn0A5Ch:rvr:cvnHewlett-Packard:ct15:cvr: dmi.product.name: HP Compaq dc7700 Ultra-slim Desktop dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771446/+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 1771364] Re: wireless headset not detecting 16.04
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc5 ** 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/1771364 Title: wireless headset not detecting 16.04 Status in linux package in Ubuntu: Incomplete Bug description: sennheiser headset I tried to connect via bluetooth but not detecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771364/+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 1771431] Re: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer)
** 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/1771431 Title: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer) Status in linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux package in Fedora: Confirmed Bug description: Hi I got an issue on Ubuntu 18.04 with latest packages. uname -a: Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lshw: *-usb:0 description: Keyboard product: Lenovo USB Receiver vendor: Lenovo physical id: 3 bus info: usb@1:3 version: 1.05 capabilities: usb-2.00 configuration: driver=usbhid maxpower=100mA speed=12Mbit/s My wireless keyboard is not working, Ubuntu only recognize some special keys (Super, Ctrl, Shift, Alt) This is a Mouse+Keyboard combo using a wireless receiver by usb: lsusb: Bus 001 Device 005: ID 17ef:609b Lenovo Mouse works fine, and in Windows 10 it works with no issues. I found multiple reported problems with this keyboard in other distros (and from Asus too, as the real manufacturer is Primax Electronics). https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486 https://ubuntuforums.org/showthread.php?t=2378862 https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu https://forums.linuxmint.com/viewtopic.php?f=49&t=260093&sid=20a073d5dd8abb1b7f23be608d7fdfd7 https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/ There is a workaround (I still didn't tried) but it needs to compile an specific driver. https://github.com/y-trudeau/linux_lenovo_ultraslim_plus There is already a kernel report about this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: julian 1342 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue May 15 15:53:41 2018 InstallationDate: Installed on 2018-05-14 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20FJS0NT07 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=818481db-36cb-4dba-8da5-8ecf15750b3b ro noapic acpi=off vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET38W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FJS0NT07 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET38W(1.25):bd03/27/2018:svnLENOVO:pn20FJS0NT07:pvrThinkPadT560:rvnLENOVO:rn20FJS0NT07:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FJS0NT07 dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1771431/+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 1771344] Re: Fix enabling bridge MMIO windows
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1771344 Title: Fix enabling bridge MMIO windows Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Breno Leitao On boot we save the configuration space of PCIe bridges. We do this so when we get an EEH event and everything gets reset that we can restore them. Unfortunately we save this state before we've enabled the MMIO space on the bridges. Hence if we have to reset the bridge when we come back MMIO is not enabled and we end up taking an PE freeze when the driver starts accessing again. This patch forces the memory/MMIO and bus mastering on when restoring bridges on EEH. Ideally we'd do this correctly by saving the configuration space writes later, but that will have to come later in a larger EEH rewrite. For now we have this simple fix. The original bug can be triggered on a boston machine by doing: echo 0x8000 > /sys/kernel/debug/powerpc/PCI0001/err_injct_outbound On boston, this PHB has a PCIe switch on it. Without this patch, you'll see two EEH events, 1 expected and 1 the failure we are fixing here. The second EEH event causes the anything under the PHB to disappear (i.e. the i40e eth). With this patch, only 1 EEH event occurs and devices properly recover. This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should be part of Ubuntu 18.04 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+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 1771309] Re: linux-libc-dev: linux/errno.h referrs to non-existing asm/errno.h
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1771309 Title: linux-libc-dev: linux/errno.h referrs to non-existing asm/errno.h Status in linux package in Ubuntu: Triaged Bug description: /usr/include/asm does not exist on my machine - only /usr/include/asm-generic. This seems to be a common problem: (https://stackoverflow.com/questions/14795608/asm-errno-h-no-such-file-or-directory ) These are the relevant packages I have installed: dpkg -l | egrep "linux-(headers|libc)" ii linux-headers-4.4.0-124 4.4.0-124.148 all Header files related to Linux kernel version 4.4.0 ii linux-headers-4.4.0-124-generic 4.4.0-124.148 amd64Linux kernel headers for version 4.4.0 on 64 bit x86 SMP ii linux-headers-generic 4.4.0.124.130 amd64Generic Linux kernel headers ii linux-libc-dev:amd644.4.0-124.148 amd64Linux Kernel Headers for development ii linux-libc-dev-armhf-cross 4.4.0-18.34cross1 all Linux Kernel Headers for development (for cross-compiling) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771309/+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 1771301] Re: Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for VXLAN tunnels
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => 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/1771301 Title: Setting ipv6.disable=1 prevents both IPv4 and IPv6 socket opening for VXLAN tunnels Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When booting with ipv6.disable=1, vxlan tunnels will fail to initialize with the error "vxlan: Cannot bind port 4789, err=-97" which is EAFNOSUPPORT. Expected result is that vxlan tunnels work when ipv6 is disabled. Description: Ubuntu 16.04.4 LTS Release: 16.04 linux-image-4.4.0-124-generic bug is fixed in RHEL in https://bugzilla.redhat.com/show_bug.cgi?id=1445054 Steps to reproduce: Deploy two identical 14.04 nodes with the following configuration: Add the following to /etc/default/grub then run 'sudo update-grub' GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1" Reboot both nodes sudo reboot Set up a tunnel using the following commands on each node modifying remote_ip to be the ip of the other node. modify veth0 ip to be subnet using the tunnel 10.10.10.x/24 ovs-vsctl del-port br-int vx1 ovs-vsctl del-port br-int veth1 ip link del veth0 ovs-vsctl add-port br-int vx1 -- set interface vx1 type=vxlan options:remote_ip=192.168.122.161 # remote_ip should be the ip of the other node ip link add type veth ip link set veth0 up ip link set veth1 up ovs-vsctl add-port br-int veth1 ip addr add 10.10.10.2/24 dev veth0 # on the second node use 10.10.10.3/24 Expected result is once the tunnel is configured on each side, you should be able to ping the ip of veth0 on the remote side while ipv6 is disabled. ping 10.10.10.2 or 10.10.10.3, whichever is the remote side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771301/+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 1765105] Re: HP Smart Array driver fails to load, kernel panics boot process
*** This bug is a duplicate of bug 1765232 *** https://bugs.launchpad.net/bugs/1765232 I have same problem on HP Proliant ML350 G5 on P400 smart array board, it's a kernel issue, last working kernel from ubuntu ppa or kernel.org is 4.13.16 >From kernel 4.14.1, no boot Tested also other live distrobutions with kernel 4.15 or 4.14 same issue, I opened a bug on bugzilla.kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1765105 Title: HP Smart Array driver fails to load, kernel panics boot process Status in linux package in Ubuntu: Confirmed Bug description: Hi I have an HP ProLiant G6 with a Smart Array controller on Bionic, Kernel 4.15.0-15, that fails to load the hpsa driver for the Smart Array, (occasionally) drops to the initramfs shell, as it cannot find a root device in a reasonable amount of time, and then finally kernel panics with the stack trace leading to the hpsa driver. Occasionally it will complain about resetting the logical volume scsi bus. Downgrading to the previous kernel 4.15.0-13 works just fine. Attached is a screenshot showing the kernel panic, and below is a link to a YouTube video of the whole boot process, a video recording from ILO. To save you the time of watching the whole thing, 39 seconds is the bus reset error, then it hangs around waiting for a root device, and the kernel panics at 4:16. The relevant information are separate below Video: https://youtu.be/45ka2Btgiqk lsb_release: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765105/+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 1771222] Re: Using sysctl to permanently disable IPv6 doesn't have any effect
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc5 ** 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/1771222 Title: Using sysctl to permanently disable IPv6 doesn't have any effect Status in linux package in Ubuntu: Incomplete Bug description: Shows up in version 18.04 of Ubuntu. I added the following 2 lines in /etc/sysctl.d/99-sysctl.conf and /etc/sysctl.d/01-disable-ipv6.conf: ``` net.ipv6.conf.all.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1 ``` Rebooting my machine sets those parameters for "all" and "default" but not for the sysctl options of my network interface: ``` net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.ens160.disable_ipv6 = 0 ``` I use disable_ipv6 above as an example. I've also verified this with the promote_secondaries option of ipv4. I can always restart systemd-sysctl.service at every boot and this will set net.ipv6.conf.ens160.disable_ipv6 to 1. Unfortunately though this won't work for devices that are hot-plugged. Other info: - version signature: Ubuntu 4.15.0-20.21-generic 4.15.17 - lspci is attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771222/+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 1771344] Re: Fix enabling bridge MMIO windows
I built a test kernel with commit 13a83eac373c49c0a081cbcd137e79210fe78acd. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771344 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-image-unsigned, linux-modules and linux-modules-extra .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/1771344 Title: Fix enabling bridge MMIO windows Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: == Comment: #0 - Breno Leitao On boot we save the configuration space of PCIe bridges. We do this so when we get an EEH event and everything gets reset that we can restore them. Unfortunately we save this state before we've enabled the MMIO space on the bridges. Hence if we have to reset the bridge when we come back MMIO is not enabled and we end up taking an PE freeze when the driver starts accessing again. This patch forces the memory/MMIO and bus mastering on when restoring bridges on EEH. Ideally we'd do this correctly by saving the configuration space writes later, but that will have to come later in a larger EEH rewrite. For now we have this simple fix. The original bug can be triggered on a boston machine by doing: echo 0x8000 > /sys/kernel/debug/powerpc/PCI0001/err_injct_outbound On boston, this PHB has a PCIe switch on it. Without this patch, you'll see two EEH events, 1 expected and 1 the failure we are fixing here. The second EEH event causes the anything under the PHB to disappear (i.e. the i40e eth). With this patch, only 1 EEH event occurs and devices properly recover. This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should be part of Ubuntu 18.04 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+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 1771276] Re: linux 4.15 currupts ipsec packets over non ethernet devices
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Tags added: kernel-da-key ** Tags added: bionic -- 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/1771276 Title: linux 4.15 currupts ipsec packets over non ethernet devices Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Linux 4.15 has a bug that currupts ipsec packets if they are received over a non ethernet interface. This is a serve showstopper bug for me since it breaks my VPN setup and locks me out of my server. see https://wiki.strongswan.org/issues/2571 and https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=87cdf3148b11 since 4.15 is already EOL, the only possibility is backporting the linked patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771276/+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 1770784] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest crashes in apparmor_file_alloc_security()
** Tags removed: bugnameltc-167748 severity-medium triage-g
--
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/1770784
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest
crashes in apparmor_file_alloc_security()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New
Bug description:
Test was running an Ubuntu 16.04 guest with a Ubuntu 18.04 host when
the guest dumped a vmcore.
According to the dump, the crash is actually a BUG_ON() raised from
apparmor_file_alloc_security() having called aa_begin_current_label()
which calls aa_current_raw_label() that in turn calls
aa_cred_raw_label() where the BUG_ON() resides:
static inline struct aa_label *aa_cred_raw_label(const struct cred *cred)
{
struct aa_task_ctx *ctx = cred_ctx(cred);
BUG_ON(!ctx || !ctx->label);
return ctx->label;
}
Now, the warnings we previously had seen raised from aa_file_perm()
may have been related since rcu_dereference() as fctx->label is NULL.
fctx = file_ctx(file);
rcu_read_lock();
flabel = rcu_dereference(fctx->label);
AA_BUG(!flabel);
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-124-generic
DUMPFILE: dump.201805110830 [PARTIAL DUMP]
CPUS: 32
DATE: Fri May 11 06:30:35 2018
UPTIME: 03:40:43
LOAD AVERAGE: 102.77, 103.38, 100.54
TASKS: 862
NODENAME: boslcp4g4
RELEASE: 4.4.0-124-generic
VERSION: #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018
MACHINE: ppc64le (2134 Mhz)
MEMORY: 16 GB
PANIC: "kernel BUG at
/build/linux-VRGJAN/linux-4.4.0/security/apparmor/include/context.h:69!"
PID: 18397
COMMAND: "chgrp"
TASK: c0035be322c0 [THREAD_INFO: c0035b5c]
CPU: 10
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 18397 TASK: c0035be322c0 CPU: 10 COMMAND: "chgrp"
#0 [c0035b5c3430] crash_kexec at c0176274
#1 [c0035b5c35d0] die at c0020ef8
#2 [c0035b5c3660] _exception at c0021244
#3 [c0035b5c37f0] program_check_common at c0006208
Program Check [700] exception frame:
R0: c04923e4R1: c0035b5c3ae0R2: c15fa700
R3: c000fcd01a00R4: 0001R5: ffc0
R6: c000fcd01b00R7: 0003fe8dR8: c163a700
R9: 0001R10: R11:
R12: c04fd880R13: c7b06400R14:
R15: R16: 0013R17:
R18: 3fffb7501468R19: R20: 3fffb74ff7e0
R21: R22: R23: 3fffdf3cbd40
R24: 9001R25: 0041R26: f000
R27: c0035b5c3dd0R28: c16342f8R29: c000fcd01a00
R30: c000fcd01a00R31:
NIP: c04fd8c8MSR: 80029033OR3: c04923e0
CTR: c04fd880LR: c04923e4XER:
CCR: 24004248MQ: 0001DAR: c00328004288
DSISR: c0035b5c39e0 Syscall Result:
#4 [c0035b5c3ae0] apparmor_file_alloc_security at c04fd8c8
[Link Register] [c0035b5c3ae0] security_file_alloc at c04923e4
#5 [c0035b5c3b50] security_file_alloc at c04923e4 (unreliable)
#6 [c0035b5c3b90] get_empty_filp at c02e7010
#7 [c0035b5c3c10] path_openat at c02faa2c
#8 [c0035b5c3c90] do_filp_open at c02fc9bc
#9 [c0035b5c3db0] do_sys_open at c02e3150
#10 [c0035b5c3e30] system_call at c0009484
System Call [c01] exception frame:
R0: 0005R1: 3fffdf3cb8c0R2: 3fffb7507e00
R3: 0100270514b0R4: 0008R5: 3fffb7501ef8
R6: 0008R7: 9001R8: 3fffdf3cbd40
R9: R10: R11:
R12: R13: 3fffb750a190
NIP: 3fffb74dbdacMSR: 8280f033OR3: 0100270514b0
CTR: LR: 3fffb74b7034XER:
CCR: 44004442MQ: 0001DAR: 3fffb748
DSISR: 4000 Syscall Result: fffe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770784/+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 1770784] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest crashes in apparmor_file_alloc_security()
** Tags added: triage-g
--
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/1770784
Title:
ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp4g4:ubuntu1604:P8 compat: guest
crashes in apparmor_file_alloc_security()
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
New
Bug description:
Test was running an Ubuntu 16.04 guest with a Ubuntu 18.04 host when
the guest dumped a vmcore.
According to the dump, the crash is actually a BUG_ON() raised from
apparmor_file_alloc_security() having called aa_begin_current_label()
which calls aa_current_raw_label() that in turn calls
aa_cred_raw_label() where the BUG_ON() resides:
static inline struct aa_label *aa_cred_raw_label(const struct cred *cred)
{
struct aa_task_ctx *ctx = cred_ctx(cred);
BUG_ON(!ctx || !ctx->label);
return ctx->label;
}
Now, the warnings we previously had seen raised from aa_file_perm()
may have been related since rcu_dereference() as fctx->label is NULL.
fctx = file_ctx(file);
rcu_read_lock();
flabel = rcu_dereference(fctx->label);
AA_BUG(!flabel);
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-124-generic
DUMPFILE: dump.201805110830 [PARTIAL DUMP]
CPUS: 32
DATE: Fri May 11 06:30:35 2018
UPTIME: 03:40:43
LOAD AVERAGE: 102.77, 103.38, 100.54
TASKS: 862
NODENAME: boslcp4g4
RELEASE: 4.4.0-124-generic
VERSION: #148-Ubuntu SMP Wed May 2 13:02:22 UTC 2018
MACHINE: ppc64le (2134 Mhz)
MEMORY: 16 GB
PANIC: "kernel BUG at
/build/linux-VRGJAN/linux-4.4.0/security/apparmor/include/context.h:69!"
PID: 18397
COMMAND: "chgrp"
TASK: c0035be322c0 [THREAD_INFO: c0035b5c]
CPU: 10
STATE: TASK_RUNNING (PANIC)
crash> bt
PID: 18397 TASK: c0035be322c0 CPU: 10 COMMAND: "chgrp"
#0 [c0035b5c3430] crash_kexec at c0176274
#1 [c0035b5c35d0] die at c0020ef8
#2 [c0035b5c3660] _exception at c0021244
#3 [c0035b5c37f0] program_check_common at c0006208
Program Check [700] exception frame:
R0: c04923e4R1: c0035b5c3ae0R2: c15fa700
R3: c000fcd01a00R4: 0001R5: ffc0
R6: c000fcd01b00R7: 0003fe8dR8: c163a700
R9: 0001R10: R11:
R12: c04fd880R13: c7b06400R14:
R15: R16: 0013R17:
R18: 3fffb7501468R19: R20: 3fffb74ff7e0
R21: R22: R23: 3fffdf3cbd40
R24: 9001R25: 0041R26: f000
R27: c0035b5c3dd0R28: c16342f8R29: c000fcd01a00
R30: c000fcd01a00R31:
NIP: c04fd8c8MSR: 80029033OR3: c04923e0
CTR: c04fd880LR: c04923e4XER:
CCR: 24004248MQ: 0001DAR: c00328004288
DSISR: c0035b5c39e0 Syscall Result:
#4 [c0035b5c3ae0] apparmor_file_alloc_security at c04fd8c8
[Link Register] [c0035b5c3ae0] security_file_alloc at c04923e4
#5 [c0035b5c3b50] security_file_alloc at c04923e4 (unreliable)
#6 [c0035b5c3b90] get_empty_filp at c02e7010
#7 [c0035b5c3c10] path_openat at c02faa2c
#8 [c0035b5c3c90] do_filp_open at c02fc9bc
#9 [c0035b5c3db0] do_sys_open at c02e3150
#10 [c0035b5c3e30] system_call at c0009484
System Call [c01] exception frame:
R0: 0005R1: 3fffdf3cb8c0R2: 3fffb7507e00
R3: 0100270514b0R4: 0008R5: 3fffb7501ef8
R6: 0008R7: 9001R8: 3fffdf3cbd40
R9: R10: R11:
R12: R13: 3fffb750a190
NIP: 3fffb74dbdacMSR: 8280f033OR3: 0100270514b0
CTR: LR: 3fffb74b7034XER:
CCR: 44004442MQ: 0001DAR: 3fffb748
DSISR: 4000 Syscall Result: fffe
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1770784/+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 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1771555 Title: dmesg Error seen on system booting from Ubuntu18.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Problem Description === dmesg Error seen on system booting from Ubuntu18.04 Is this an issue? [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) user1@yob45wos:~$ sudo dmesg --level=alert user1@yob45wos:~$ sudo dmesg --level=crit user1@yob45wos:~$ sudo dmesg --level=err [3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.531263] vio vio: uevent: failed to send synthetic uevent [4.521383] nouveau 0004:04:00.0: unknown chipset (14a1) [4.521889] nouveau 0035:03:00.0: unknown chipset (14a1) [4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not supported by firmware: 0 0 [4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not supported by firmware: 0 0 [5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [ 22.109545] vio vio: uevent: failed to send synthetic uevent user1@yob45wos:~$ > > Problem Description > === > dmesg Error seen on system booting from Ubuntu18.04 > Is this an issue? These messages are seen on every IPL. Is there an issue? > [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) > [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) These messages should be marked as Warnings instead of Errors as they it supposedly a warning and not an error. This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg --level=err' again in 18.04. * In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) (LP: #1656908) - SAUCE: ima: Downgrade error to warning Mirroring this bug to distro to fix this in the latest kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771555/+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 1771542] Re: Suspend to idle: Open lid didn't resume
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) 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/1771542 Title: Suspend to idle: Open lid didn't resume Status in linux package in Ubuntu: Triaged Status in linux source package in Artful: Triaged Status in linux source package in Bionic: Triaged Bug description: [Impact] Some platforms are set suspend-to-idle (s2idle) as default suspend mode, and then they can't resume the system from opening the lid. [Fix] According a patch sent to 4.17-rc1, which was not be included before 4.15 EOL, so we cherry pick the patch to Ubuntu 4.13 / 4.15 kernel. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=147a7d9d25ca2551aab15071cb1f048ecd9b7953 [Regression Potential] no regression could be happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771542/+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 1771546] Re: WARNING: setup_local_APIC+0x27f/0x340
Vivid is now EOL. Can you see if this bug still exists on a supported release, such as Artful or Bionic? ** 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/1771546 Title: WARNING: setup_local_APIC+0x27f/0x340 Status in linux package in Ubuntu: Incomplete Bug description: when load kernel with kexec: /sbin/kexec -p --command-line="root=UUID=5f248d51-af51-4178-bd4d-763d4a6648b3 ro console=ttyS0 console=tty0 irqpoll maxcpus=1 nousb" --initrd=/boot/initrd.img-3.19.0-80-generic /boot/vmlinuz-3.19.0-80-generic and then, triggers a panic: echo c > /proc/sysrq-trigger and now we got reboot into secondary kernel, but at this process, we will got this call trace with 100% reproducible: [14257.863168] Initializing cgroup subsys net_prio [14257.864506] Initializing cgroup subsys hugetlb [14257.865898] CPU: Physical Processor ID: 0 [14257.867035] CPU: Processor Core ID: 0 [14257.869296] mce: CPU supports 0 MCE banks [14257.870495] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 [14257.870495] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 [14257.901734] ftrace: allocating 30063 entries in 118 pages [14258.976524] [ cut here ] [14258.983143] WARNING: CPU: 0 PID: 1 at /build/linux-lts-vivid-PmeBs4/linux-lts-vivid-3.19.0/arch/x86/kernel/apic/apic.c:1400 setup_local_APIC+0x27f/0x340() [14259.005863] Modules linked in: [14259.009221] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-80-generic #88~14.04.1-Ubuntu [14259.015315] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [14259.021134] 88003191fe18 817b63c3 [14259.036605] 81a8b9d0 88003191fe58 81075d6a 88003191fdfc [14259.055284] 0001 00f0 [14259.061414] Call Trace: [14259.063414] [] dump_stack+0x63/0x81 [14259.067742] [] warn_slowpath_common+0x8a/0xc0 [14259.076934] [] warn_slowpath_null+0x1a/0x20 [14259.085878] [] setup_local_APIC+0x27f/0x340 [14259.101292] [] native_smp_prepare_cpus+0x2f2/0x3af [14259.111873] [] kernel_init_freeable+0xaf/0x1f9 [14259.114495] [] ? rest_init+0x80/0x80 [14259.116783] [] kernel_init+0xe/0xf0 [14259.118990] [] ret_from_fork+0x58/0x90 [14259.121292] [] ? rest_init+0x80/0x80 [14259.123341] ---[ end trace 7384fc8d5897e3f0 ]--- [14259.130738] Spurious LAPIC timer interrupt on cpu 0 [14259.153429] do_IRQ: 0.145 No irq handler for vector (irq -1) [14259.157634] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [14259.161002] smpboot: CPU0: Intel(R) Core(TM) i5-6360U CPU @ 2.00GHz (fam: 06, model: 4e, stepping: 03) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771546/+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 1771499] Re: package linux-image-extra-4.4.0-122-generic 4.4.0-122.146 failed to install/upgrade: subprocess installed post-removal script was killed by signal (Terminated)
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** 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/1771499 Title: package linux-image-extra-4.4.0-122-generic 4.4.0-122.146 failed to install/upgrade: subprocess installed post-removal script was killed by signal (Terminated) Status in linux package in Ubuntu: Incomplete Bug description: I was running bleachbit, it hung and crashed while I was using it to clear out apt. I couldn't finish in the terminal so i did "sudo reboot now". After rebooting I got this error popup requesting I send a bug report. I still couldn't run apt-get autoremove or autoclean so I was prompted with: E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. I did that an everything went back to normal (that I'm aware of). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-122-generic 4.4.0-122.146 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: catherine 2155 F pulseaudio /dev/snd/controlC0: catherine 2155 F pulseaudio Date: Tue May 15 22:17:02 2018 DuplicateSignature: package:linux-image-extra-4.4.0-122-generic:4.4.0-122.146 Removing linux-image-extra-4.4.0-122-generic (4.4.0-122.146) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-122-generic /boot/vmlinuz-4.4.0-122-generic dpkg: error processing package linux-image-extra-4.4.0-122-generic (--remove): subprocess installed post-removal script was killed by signal (Terminated) ErrorMessage: subprocess installed post-removal script was killed by signal (Terminated) HibernationDevice: RESUME=UUID=d0e88aed-0bea-4ee7-987b-57da2ead80b9 InstallationDate: Installed on 2017-04-12 (398 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed root=UUID=c199f55c-69ae-45a1-b45a-16652728bf57 ro text PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-extra-4.4.0-122-generic 4.4.0-122.146 failed to install/upgrade: subprocess installed post-removal script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.10 dmi.board.name: Z170 Gaming-ITX/ac dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.10:bd09/30/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771499/+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 1771620] Re: Hang on network interface removal in Xen virtual machine
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => 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/1771620 Title: Hang on network interface removal in Xen virtual machine Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: On a hosting platform running Xen hypervisor, in a virtual machine with Ubuntu 18.04 system and the default kernel from Ubuntu, I try to detach a virtual network interface. On the Xen side, the virtual interface is removed from the VM but the kernel still has the interface. Then a couple of minutes afterwards, the kernel log show this kernel trace: INFO: task xenwatch:108 blocked for more than 120 seconds. Tainted: GW4.15.0-20-generic #21-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. xenwatchD0 108 2 0x8000 Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 xennet_remove+0xda/0x1c0 ? wait_woken+0x80/0x80 xenbus_dev_remove+0x54/0xa0 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 ? xenbus_otherend_changed+0x110/0x110 device_del+0x13d/0x360 ? xenbus_otherend_changed+0x110/0x110 ? xenbus_otherend_changed+0x110/0x110 device_unregister+0x1a/0x60 xenbus_dev_changed+0xa3/0x1e0 ? xenwatch_thread+0xcc/0x160 frontend_changed+0x21/0x50 xenwatch_thread+0xc4/0x160 ? wait_woken+0x80/0x80 kthread+0x121/0x140 ? find_watch+0x40/0x40 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 In the git repository of Linux, the commit c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 (xen-netfront: Fix hang on device removal) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 seems to be related to this situation. I rebuilded the Ubuntu kernel from the package source and applied this patch. Once the VM has booted with the new kernel, I was able to remove network interface without hangs from the kernel. I also booted the VM with the Ubuntu kernel 4.13.0-42-generic and was able to remove the network interface with success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 16 16:36:06 2018 ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771620/+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 1771535] Re: synaptics trackpad not detected by libinput
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 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.17-rc5 ** 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/1771535 Title: synaptics trackpad not detected by libinput Status in linux package in Ubuntu: Incomplete Bug description: Laptop msi gp62 7rd leopard http://www.linlap.com/msi_gp62_leopard_pro After installing ubuntu 18.04, trackpad does not work at all. External usb mouse does work, though. $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PixArt HP USB Optical Mouse id=6[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=7[slave keyboard (3)] $ cat /proc/version_signature Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic 4.15.0.20.23 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roberto1513 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed May 16 10:17:30 2018 InstallationDate: Installed on 2018-05-15 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Micro-Star International Co., Ltd. GP62 7RD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=fb3ba161-3d9b-4fc3-844d-e45adb61a7f1 ro acpi=off quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16J9IMS.307 dmi.board.asset.tag: Default string dmi.board.name: MS-16J9 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J9IMS.307:bd11/07/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP627RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J9:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP62 7RD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771535/+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 1769331] Re: broken upgrade/ full install bionic from ubuntu-budgie 17.10
As the new installation keeps crashing at the login I can't run the command in the terminal window. ** 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/1769331 Title: broken upgrade/ full install bionic from ubuntu-budgie 17.10 Status in linux package in Ubuntu: Confirmed Bug description: I tried to upgrade von ubuntu-budgie 17.10 to 18.04 directly. extremly slow installation, on reboot it took minutes to start up, login led to a black screen and a few minutes later took me back to the login screen. after this i tried a full clean install first formatting my root- partiton only (same experience as before) and then also erasing my home-partiton. still the same problems. I tried two different iso's, I tried to boot from two different usb-sticks, I even tried the 32 bit instead of the 64. Always painfully slow installation (virtually taking 2 to 3 hours) and impossible to work with. Last guess was, that my computer war broken; but the reinstalled ubuntu-budgie 17.10 - working like charm. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: Budgie:GNOME Date: Sat May 5 10:13:41 2018 LiveMediaBuild: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769331/+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 1771620] Re: Hang on network interface removal in Xen virtual machine
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => 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/1771620 Title: Hang on network interface removal in Xen virtual machine Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: On a hosting platform running Xen hypervisor, in a virtual machine with Ubuntu 18.04 system and the default kernel from Ubuntu, I try to detach a virtual network interface. On the Xen side, the virtual interface is removed from the VM but the kernel still has the interface. Then a couple of minutes afterwards, the kernel log show this kernel trace: INFO: task xenwatch:108 blocked for more than 120 seconds. Tainted: GW4.15.0-20-generic #21-Ubuntu "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. xenwatchD0 108 2 0x8000 Call Trace: __schedule+0x297/0x8b0 schedule+0x2c/0x80 xennet_remove+0xda/0x1c0 ? wait_woken+0x80/0x80 xenbus_dev_remove+0x54/0xa0 device_release_driver_internal+0x15b/0x220 device_release_driver+0x12/0x20 bus_remove_device+0xec/0x160 ? xenbus_otherend_changed+0x110/0x110 device_del+0x13d/0x360 ? xenbus_otherend_changed+0x110/0x110 ? xenbus_otherend_changed+0x110/0x110 device_unregister+0x1a/0x60 xenbus_dev_changed+0xa3/0x1e0 ? xenwatch_thread+0xcc/0x160 frontend_changed+0x21/0x50 xenwatch_thread+0xc4/0x160 ? wait_woken+0x80/0x80 kthread+0x121/0x140 ? find_watch+0x40/0x40 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 In the git repository of Linux, the commit c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 (xen-netfront: Fix hang on device removal) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c2d2e6738a209f0f9dffa2dc8e7292fc45360d61 seems to be related to this situation. I rebuilded the Ubuntu kernel from the package source and applied this patch. Once the VM has booted with the new kernel, I was able to remove network interface without hangs from the kernel. I also booted the VM with the Ubuntu kernel 4.13.0-42-generic and was able to remove the network interface with success. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 16 16:36:06 2018 ProcEnviron: TERM=rxvt-unicode PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771620/+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 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) 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/1771555 Title: dmesg Error seen on system booting from Ubuntu18.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: Problem Description === dmesg Error seen on system booting from Ubuntu18.04 Is this an issue? [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) user1@yob45wos:~$ sudo dmesg --level=alert user1@yob45wos:~$ sudo dmesg --level=crit user1@yob45wos:~$ sudo dmesg --level=err [3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.531263] vio vio: uevent: failed to send synthetic uevent [4.521383] nouveau 0004:04:00.0: unknown chipset (14a1) [4.521889] nouveau 0035:03:00.0: unknown chipset (14a1) [4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not supported by firmware: 0 0 [4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not supported by firmware: 0 0 [5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [ 22.109545] vio vio: uevent: failed to send synthetic uevent user1@yob45wos:~$ > > Problem Description > === > dmesg Error seen on system booting from Ubuntu18.04 > Is this an issue? These messages are seen on every IPL. Is there an issue? > [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) > [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) These messages should be marked as Warnings instead of Errors as they it supposedly a warning and not an error. This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg --level=err' again in 18.04. * In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) (LP: #1656908) - SAUCE: ima: Downgrade error to warning Mirroring this bug to distro to fix this in the latest kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771555/+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 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
So I've tested all the way from rc2 -> rc7, and confirm that rc7 is the
issue. In two different machines:
machine1: running kernel was rc3
machine2: running kernel was rc4
In both cases, after install of rc7, and reboot, I see the issue. Logs
for the latest:
https://pastebin.ubuntu.com/p/yVTWBRqXSC/
--
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/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Bug description:
From an ephemeral environment in an HPGen9, the machine fails to
reboot when the ephemeral environment is Bionic (it does not fail in
Xenial).
Full log from the moment the 'sudo reboot' was executed:
https://pastebin.ubuntu.com/p/hyD6VY7CbW/
The actual failure is:
[ OK ] Stopped Remount Root and Kernel File Systems.
[ OK ] Reached target Shutdown.
[ OK ] Reached target Final Step.
Starting Reboot...
[ OK ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress
polling.
Stopping LVM2 metadata daemon...
[ OK ] Stopped LVM2 metadata daemon.
[ 257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 257.160530] {1}[Hardware Error]: event severity: fatal
[ 257.160533] {1}[Hardware Error]: Error 0, type: fatal
[ 257.160534] {1}[Hardware Error]: section_type: PCIe error
[ 257.160536] {1}[Hardware Error]: port_type: 4, root port
[ 257.160541] {1}[Hardware Error]: version: 1.16
[ 257.160544] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160546] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160547] {1}[Hardware Error]: slot: 0
[ 257.160548] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160550] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160552] {1}[Hardware Error]: class_code: 040600
[ 257.160554] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160556] {1}[Hardware Error]: Error 1, type: fatal
[ 257.160557] {1}[Hardware Error]: section_type: PCIe error
[ 257.160559] {1}[Hardware Error]: port_type: 4, root port
[ 257.160560] {1}[Hardware Error]: version: 1.16
[ 257.160562] {1}[Hardware Error]: command: 0x6010, status: 0x0143
[ 257.160564] {1}[Hardware Error]: device_id: :00:01.0
[ 257.160565] {1}[Hardware Error]: slot: 0
[ 257.160566] {1}[Hardware Error]: secondary_bus: 0x03
[ 257.160567] {1}[Hardware Error]: vendor_id: 0x8086, device_id: 0x6f02
[ 257.160568] {1}[Hardware Error]: class_code: 040600
[ 257.160569] {1}[Hardware Error]: bridge: secondary_status: 0x2000,
control: 0x0003
[ 257.160570] Kernel panic - not syncing: Fatal hardware error!
[ 257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 33 Apr 6 17:40 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed
with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 18.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: HP ProLiant DL360 Gen9
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine:
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled
cc:{datasource_list: [MAAS]}end_cc
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8
BOOTIF=01-94:18:82:7a:82:c8
ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
dmi.bios.date: 09
[Kernel-packages] [Bug 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => 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/1771439
Title:
[LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode
16.04.04 guest
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
This test fails in the same way on a P8 host, so it is nothing to do
with P9.
There have been many TM bugs fixed upstream since 4.4. I would suggest
starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state
in signal handler", 2017-08-22) and see if that helps.
The bad thing exception is being raised when executing the following
line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-transactional
state" and the MSR is set to be transactional (suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why we are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
I think we need the following commit to have this fixed:
commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
Author: Cyril Bur
Date: Tue Aug 23 10:46:17 2016 +1000
powerpc: signals: Discard transaction state from signal frames
Userspace can begin and suspend a transaction within the signal
handler which means they might enter sys_rt_sigreturn() with the
processor in suspended state.
sys_rt_sigreturn() wants to restore process context (which may have
been in a transaction before signal delivery). To do this it must
restore TM SPRS. To achieve this, any transaction initiated within the
signal frame must be discarded in order to be able to restore TM SPRs
as TM SPRs can only be manipulated non-transactionally..
>From the PowerPC ISA:
TM Bad Thing Exception [Category: Transactional Memory]
An attempt is made to execute a mtspr targeting a TM register in
other than Non-transactional state.
Not doing so results in a TM Bad Thing:
[12045.221359] Kernel BUG at c0050a40 [verbose debug info
unavailable]
[12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr
0x201033)
[12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
[12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
[12045.221634] Modules linked in: xt_CHECKSUM iptable_mangle
ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables
kvm_hv kvm
uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses
enclosure
scsi_transport_sas bnx2x ipr mdio libcrc32c
[12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0
#34
[12045.24] task: c000fce38600 ti: c000fceb4000 task.ti:
c000fceb4000
[12045.93] NIP: c0050a40 LR: c00163bc CTR:
[12045.222361] REGS: c000fceb7ac0 TRAP: 0700 Not tainted (4.7.0)
[12045.222418] MSR: 900300201033 CR:
28444280 XER: 2000
[12045.222625] CFAR: c00163b8 SOFTE: 0 PACATMSCRATCH:
90014280f033
GPR00: 0110b801 c000fceb7d40 c139c100 c000fce390d0
GPR04: 90034280f033
GPR08: b0001033 0001
GPR12: c2926400
GPR16:
GPR20:
GPR24: 398cadd0 398cb470
GPR28: 90034280f033 c000fceb7ea0 0001 c000fce390d0
[12045.223535] NIP [c0050a40] tm_restore_sprs+0xc/0x1c
[12045.223584] LR [c00163bc] tm_recheckpoint+0x5c/0xa0
[12045.223630] Call Trace:
[12045.223655] [c000fceb7d80] [c0026e74]
sys_rt_sigreturn+0x494/0x6c0
[12045.223738] [c000fceb7e30] [c00092e0]
system_call+0x38/0x108
[12045.223806] Instruction dump:
[12045.223841] 7c800164 4e800020 7c0022a6 f80304a8 7c0222a6 f80304b0
7c0122a6 f80304b8
[12045.223955] 4e800020 e80304a8 7c0023a6 e80304b0 <7c0223a6> e80304b8
7c0123a6 4e800020
[12045.224074] ---[ end trace cb8002ee240
[Kernel-packages] [Bug 1771555] Re: dmesg Error seen on system booting from Ubuntu18.04
I built a Bionic test kernel. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1771555 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-image-unsigned, linux-modules and linux-modules-extra .deb packages. Thanks in advance! ** Changed in: linux (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => 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/1771555 Title: dmesg Error seen on system booting from Ubuntu18.04 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Problem Description === dmesg Error seen on system booting from Ubuntu18.04 Is this an issue? [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) user1@yob45wos:~$ sudo dmesg --level=alert user1@yob45wos:~$ sudo dmesg --level=crit user1@yob45wos:~$ sudo dmesg --level=err [3.382733] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [3.382738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.531263] vio vio: uevent: failed to send synthetic uevent [4.521383] nouveau 0004:04:00.0: unknown chipset (14a1) [4.521889] nouveau 0035:03:00.0: unknown chipset (14a1) [4.634336] lpfc 0030:01:00.0: 0:6101 Disabling NVME support: Not supported by firmware: 0 0 [4.634416] lpfc 0030:01:00.0: 0:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [5.646354] lpfc 0030:01:00.1: 1:6101 Disabling NVME support: Not supported by firmware: 0 0 [5.646420] lpfc 0030:01:00.1: 1:2574 IO channels: irqs 4 fcp 4 nvme 0 MRQ: 16 [6.944481] lpfc 0030:01:00.1: 1:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [6.944634] lpfc 0030:01:00.0: 0:1303 Link Up Event x1 received Data: x1 x0 x80 x0 x0 x0 0 [ 22.109545] vio vio: uevent: failed to send synthetic uevent user1@yob45wos:~$ > > Problem Description > === > dmesg Error seen on system booting from Ubuntu18.04 > Is this an issue? These messages are seen on every IPL. Is there an issue? > [2.601750] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) > [2.601754] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) These messages should be marked as Warnings instead of Errors as they it supposedly a warning and not an error. This was fixed in LP #1656908 / Bug 150596, but seeing it with 'dmesg --level=err' again in 18.04. * In Ubuntu 17.04 : after reboot getting message in console like Unable to open file: /etc/keys/x509_ima.der (-2) (LP: #1656908) - SAUCE: ima: Downgrade error to warning Mirroring this bug to distro to fix this in the latest kernel. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771555/+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 1771439] Re: [LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode 16.04.04 guest
I built a test kernel with commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1771439
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-image-unsigned, linux-modules and linux-modules-extra .deb packages.
Thanks in advance!
** Changed in: linux (Ubuntu)
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) =>
Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Triaged => 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 => Medium
** 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/1771439
Title:
[LTC Test] Ubuntu 18.04: tm_sigreturn failed on P8 compat mode
16.04.04 guest
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Bug description:
This test fails in the same way on a P8 host, so it is nothing to do
with P9.
There have been many TM bugs fixed upstream since 4.4. I would suggest
starting with commit 044215d145a7 ("powerpc/tm: Fix illegal TM state
in signal handler", 2017-08-22) and see if that helps.
The bad thing exception is being raised when executing the following
line:
c004fcfc: b0 04 03 e8 ld r0,1200(r3)
-> c004fd00: a6 23 02 7c mtspr 130,r0
Which is basically restoring TEXASR in the thread.
ISA says "These registers can be written only when in Non-transactional
state" and the MSR is set to be transactional (suspended):
MSR: 800300201033 [ME][RI][IR][DR][LE][SF][HTM][TSU]
That explains why we are getting the "bad thing exception". A mtspr is
being called with a transaction suspended.
I think we need the following commit to have this fixed:
commit 78a3e8889b4b6b99775ed954696ff3e017f5d19b
Author: Cyril Bur
Date: Tue Aug 23 10:46:17 2016 +1000
powerpc: signals: Discard transaction state from signal frames
Userspace can begin and suspend a transaction within the signal
handler which means they might enter sys_rt_sigreturn() with the
processor in suspended state.
sys_rt_sigreturn() wants to restore process context (which may have
been in a transaction before signal delivery). To do this it must
restore TM SPRS. To achieve this, any transaction initiated within the
signal frame must be discarded in order to be able to restore TM SPRs
as TM SPRs can only be manipulated non-transactionally..
>From the PowerPC ISA:
TM Bad Thing Exception [Category: Transactional Memory]
An attempt is made to execute a mtspr targeting a TM register in
other than Non-transactional state.
Not doing so results in a TM Bad Thing:
[12045.221359] Kernel BUG at c0050a40 [verbose debug info
unavailable]
[12045.221470] Unexpected TM Bad Thing exception at c0050a40 (msr
0x201033)
[12045.221540] Oops: Unrecoverable exception, sig: 6 [#1]
[12045.221586] SMP NR_CPUS=2048 NUMA PowerNV
[12045.221634] Modules linked in: xt_CHECKSUM iptable_mangle
ipt_MASQUERADE
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp
llc ebtable_filter
ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables
kvm_hv kvm
uio_pdrv_genirq ipmi_powernv uio powernv_rng ipmi_msghandler autofs4 ses
enclosure
scsi_transport_sas bnx2x ipr mdio libcrc32c
[12045.222167] CPU: 68 PID: 6178 Comm: sigreturnpanic Not tainted 4.7.0
#34
[12045.24] task: c000fce38600 ti: c000fceb4000 task.ti:
c000fceb4000
[12045.93] NIP: c0050a40 LR: c00163bc CTR:
[12045.222361] REGS: c000fceb7ac0 TRAP: 0700 Not tainted (4.7.0)
[12045.222418] MSR: 900300201033 CR:
28444280 XER: 2000
[12045.222625] CFAR: c00163b8 SOFTE: 0 PACATMSCRATCH:
90014280f033
GPR00: 0110b801 c000fceb7d40 c139c100 c000fce390d0
GPR04: 90034280f033
GPR08: b0001033 0001
