[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
Today with 4.18.0-16-generic and s2idle activated, the consumption is lesser than in the past. 100 % at 0h00 : I leave my laptop without suspend it. KDE suspend my laptop after 15 min. 95% at 7h40 I've powertop enabled. -- 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep Status in linux package in Ubuntu: Incomplete Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+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 1802283] Re: system freezes
So seems like we can close this bug? -- 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/1802283 Title: system freezes Status in linux package in Ubuntu: Incomplete Bug description: My system freezes once every second day or so. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jnns 2519 F pulseaudio /dev/snd/controlC0: jnns 2519 F pulseaudio CurrentDesktop: GNOME Date: Thu Nov 8 12:07:32 2018 HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327 InstallationDate: Installed on 2018-08-05 (95 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KGS5DU00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago) dmi.bios.date: 09/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS5DU00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS5DU00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+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 1810619] Re: Sleep mode doesn't work
Today, with freshly installed 4.18.0-16-generic, it seems to be a better behavior. With s2idle : 100% battery at 0h00 95% at 7:40 $ sudo cat /sys/power/mem_sleep [s2idle] deep Moving mouse (connected via bluetooth) resumes the laptop. -- 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/1810619 Title: Sleep mode doesn't work Status in linux package in Ubuntu: Confirmed Bug description: On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with linux-image-4.18.0-13. The screen goes off correctly but any touch resume the laptop. This is the log : Jan 5 11:15:25 skeleton systemd[1]: Reached target Sleep. Jan 5 11:15:25 skeleton systemd[1]: Starting Suspend... Jan 5 11:15:25 skeleton systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 5 11:15:25 skeleton systemd-sleep[6229]: Suspending system... Jan 5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle) an 5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 5 11:15:25 skeleton systemd[1]: Started Network Manager Script Dispatcher Service. Jan 5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 scripts) Jan 5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running ordered scripts... [...] Resume : Jan 5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... done. Jan 5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes ... (elapsed 0.088 seconds) done. Jan 5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled. Jan 5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Jan 5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use no_console_suspend to debug) Jan 5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled. Jan 5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done. Jan 5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 enxe4b97acfa7e9: carrier on Jan 5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 4.18.0-12). Thanks, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810619/+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 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
The patch in #7 is already in latest Cosmic kernel. Does it solve the issue? If not, I'll build a test kernel with commit in #11. -- 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/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 Status in linux package in Ubuntu: Confirmed Bug description: Dear developer(s), I used a vdr-installation on Debian testing, before. Switched over to Ubuntu since the release of cosmic because of problems with GPU/steam under Debian. Now, I have problems to configure vdr because my TV stick doesn't seem to work with kernel 4.18. This is what I did: Installed Ubuntu, upgraded via aptitude to the latest packages, got the firmware "dvb-demod-si2168-b40-01.fw" and "dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* openelec.org and the modinfo output of si2168 and si2157), tried w_scan and failed (w_scan *can* find some signals but failes in getting the channels). That looks like this, f.e.: […} Scanning DVB-T2... 474000: (time: 01:38.796) 482000: (time: 01:43.155) 49: (time: 01:45.163) signal ok: QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0) Info: no data from PAT after 2 seconds deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 (0:0:0)) […] Now, I tried an older kernel - 4.15, because it's still in the cosmics' repository and tried w_scan again: Success, although the TV- Stick doesn't find all the channels I found with Debian Testing. So, maybe there's a regression in the latest kernel regarding the TV- Stick-driver or there is another firmware which will work better with 4.18…? Would be glad if someone could help to work that out… Greets! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jarosch1516 F pulseaudio /dev/snd/controlC0: jarosch1516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 23:32:50 2018 InstallationDate: Installed on 2018-10-24 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: BIOSTAR Group Hi-Fi A88S3+ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: Hi-Fi A88S3+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: None dmi.product.name: Hi-Fi A88S3+ dmi.product.sku: None dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+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 1800859] Re: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04)
The next step is to bisect between v4.13 and v4.15... -- 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/1800859 Title: Fail to suspend properly in Ubuntu 18.10 (Also occurred in 18.04) Status in linux package in Ubuntu: Expired Bug description: This has all the hallmarks of Bug #1774950 excepting that no amount of kernel reversion seems to solve the problem. System sporadically works fine, but mostly fails to suspend properly according to /var/log/kern.log ... $ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 $ cat /proc/version_signature Ubuntu 4.18.0-10.11-generic 4.18.12 $ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 2 Core(s) per socket: 2 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 101 Model name: AMD A12-9700P RADEON R7, 10 COMPUTE CORES 4C+6G Stepping:1 CPU MHz: 1582.715 CPU max MHz: 2500. CPU min MHz: 1300. BogoMIPS:4990.76 Virtualisation: AMD-V L1d cache: 32K L1i cache: 96K L2 cache:1024K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good acc_power nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc mwaitx cpb hw_pstate ssbd vmmcall fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576] Subsystem: Hewlett-Packard Company Family 15h (Models 60h-6fh) Processor Root Complex [103c:81f9] Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+ Address: fee08004 Data: 4021 Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+ 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:81f9] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [270 v1] #19 Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable+ Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: 0020 Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 10 PASIDCtl: Enable+ Exec- Priv-
[Kernel-packages] [Bug 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
Does this still happen on an up-to-date 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/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796582/+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 1800278] Re: kernel linux 4.18 crashes on xiaomi notebook pro
Does this still happen on an up-to-date 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/1800278 Title: kernel linux 4.18 crashes on xiaomi notebook pro Status in linux package in Ubuntu: Confirmed Bug description: hello here´s my hardware profile ; 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) 00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation Device 1d12 (rev a1) 02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 03:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a808 as xiaomi notebook pro late 2018 when i tried to use ubuntu 18.10(cosmic cuttlefish) with kernel 4.18 the system freeze and cause high processor activity (100%), high temperature, loud processor activity and the system crashes in one word all the system is static and i have to sutdown the system manually because there is no process respond to anything i can do... i tried every variant of this os and the bug repeat instantly after installation. i have to downgrade to ubuntu 18.04 to solve the probleme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800278/+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 1795292] Re: ELAN469D touch pad not working
Is parameter "ivrs_ioapic=" still needed? -- 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/1795292 Title: ELAN469D touch pad not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+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 1818407] Re: Cant access emmc, error -84
Yes, through e-mail. -- 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/1818407 Title: Cant access emmc, error -84 Status in linux package in Ubuntu: Confirmed Bug description: Greetings! I just got my new convertible(Asus TP202NAS, brand new) and wanted to install kubuntu 18.10 onto the internal storage, only to find that it cant see it. In dmesg i only got these two error: mc0: mmc_select_hs400 failed, error -84 mc0: error -84 whilst initializing mmc card Tried to google around for a solution but i didnt found any solution to this, also tried the kubuntu IRC channel but didnt got any luck there too /EDIT Submitted from a live session. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-release-upgrader-core 1:18.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CrashDB: ubuntu Date: Sun Mar 3 13:59:13 2019 LiveMediaBuild: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3661 F pulseaudio CasperVersion: 1.394 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 LiveMediaBuild: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 003: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:3501 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. TP202NAS Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP202NAS.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP202NAS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP202NAS.209:bd07/19/2018:svnASUSTeKCOMPUTERINC.:pnTP202NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP202NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: TP202NAS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+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 1818407] Re: Cant access emmc, error -84
How exactly i do that, just send them an e-mail? Just as a side note after a long trial and error i got into a different advenced section and i found some settings under Chipset\South Cluster Configuration\SCC Configuration: SCC Card Support (D27:F0) Disable SCC eMMC support (D28:F0) Enable eMMC Max Speed HS400 SCC UFS Support (D29:F0) Disable SCC SDIO Support (D30:F0) Disable This is pretty much all there is that i can relate to the storage. Dont want to disclose how to get in. Even i had to take this baby apart to reset the BIOS -- 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/1818407 Title: Cant access emmc, error -84 Status in linux package in Ubuntu: Confirmed Bug description: Greetings! I just got my new convertible(Asus TP202NAS, brand new) and wanted to install kubuntu 18.10 onto the internal storage, only to find that it cant see it. In dmesg i only got these two error: mc0: mmc_select_hs400 failed, error -84 mc0: error -84 whilst initializing mmc card Tried to google around for a solution but i didnt found any solution to this, also tried the kubuntu IRC channel but didnt got any luck there too /EDIT Submitted from a live session. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-release-upgrader-core 1:18.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CrashDB: ubuntu Date: Sun Mar 3 13:59:13 2019 LiveMediaBuild: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3661 F pulseaudio CasperVersion: 1.394 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 LiveMediaBuild: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 003: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:3501 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. TP202NAS Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP202NAS.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP202NAS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP202NAS.209:bd07/19/2018:svnASUSTeKCOMPUTERINC.:pnTP202NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP202NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: TP202NAS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+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 1752437] Re: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work
Does this still happen on an up-to-date 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/1752437 Title: [HP ENVY x360 - 15-bq102ng] Touchscreen does not work Status in linux package in Ubuntu: Incomplete Bug description: The touch screen on my HP ENVY x360 15-bq102ng does not work with stock kernel or with mainline kernel 4.16-rc3. marc@snapbug:~$ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=13 [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)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ HP Wireless hotkeys id=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=15 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP I id=11 [slave keyboard (3)] ↳ HP Wide Vision FHD Camera: HP W id=10 [slave keyboard (3)] WORKAROUND: Use the patch labeled "possible fix for touchscreen" with 4.17-rc3: https://bugzilla.kernel.org/attachment.cgi?id=275381 from upstream report: https://bugzilla.kernel.org/show_bug.cgi?id=198715 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.16.0-041600rc2-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: No key available with this passphrase. /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:34:50 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:83c6] InstallationDate: Installed on 2018-01-16 (42 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: HP HP ENVY x360 Convertible 15-bq1xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/26/2018 dmi.bios.vendor: AMI dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83C6 dmi.board.vendor: HP dmi.board.version: 63.18 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 15-bq1xx dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-4~a~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752437/+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 1774817] Re: Temperature sensors on x470 not reporting correctly
Does this affect "real" usage? AFAICT thermald doesn't work on AMD platforms (yet). -- 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/1774817 Title: Temperature sensors on x470 not reporting correctly Status in linux package in Ubuntu: Triaged Bug description: x470-I ROG strix motherboard and Ryzen 2700 After sudo sensors-detect and answering yes to all the probes the net result is: "Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported." sensors output lists: asus-isa- Adapter: ISA adapter cpu_fan:0 RPM nouveau-pci-0900 Adapter: PCI adapter fan1: 0 RPM temp1:+65.0°C (high = +95.0°C, hyst = +3.0°C) (crit = +105.0°C, hyst = +5.0°C) (emerg = +135.0°C, hyst = +5.0°C) k10temp-pci-00c3 Adapter: PCI adapter temp1:+94.2°C (high = +70.0°C) Where the cpu fan is patently wrong and the k10temp likewise. The nouveau-pci-0900 appears to be the actual CPU temperature. May be related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736 Other info: Description: Ubuntu 18.04 LTS Release: 18.04 version log: Ubuntu 4.15.0-22.24-generic 4.15.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774817/+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 1747273] Re: Can not control brightness on Thinkpad P51
Does this still happen on an up-to-date 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/1747273 Title: Can not control brightness on Thinkpad P51 Status in linux package in Ubuntu: Confirmed Bug description: I can not modify the screen brightness in Ubuntu 17.10. Controls aside, the classes in `proc` are either not available or non- functional depending on what arguments I provide in GRUB_CMDLINE_LINUX_DEFAULT. On a parallel installation (Ubuntu 16.04.3), brightness control works flawlessly. System Information -- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31) 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Device a171 (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M1200 Mobile] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) 02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 # with GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=Linux thinkpad-acpi.brightness_enable=1": $ grep . -R /sys/class/backlight/thinkpad_screen/* /sys/class/backlight/thinkpad_screen/actual_brightness:0 /sys/class/backlight/thinkpad_screen/bl_power:0 /sys/class/backlight/thinkpad_screen/brightness:11 /sys/class/backlight/thinkpad_screen/max_brightness:15 /sys/class/backlight/thinkpad_screen/power/runtime_active_kids:0 /sys/class/backlight/thinkpad_screen/power/runtime_suspended_time:0 grep: /sys/class/backlight/thinkpad_screen/power/autosuspend_delay_ms: Input/output error /sys/class/backlight/thinkpad_screen/power/runtime_enabled:disabled /sys/class/backlight/thinkpad_screen/power/runtime_active_time:0 /sys/class/backlight/thinkpad_screen/power/control:auto /sys/class/backlight/thinkpad_screen/power/async:disabled /sys/class/backlight/thinkpad_screen/power/runtime_usage:0 /sys/class/backlight/thinkpad_screen/power/runtime_status:unsupported grep: warning: /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/subsystem: recursive directory loop /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_kids:0 /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_suspended_time:0 grep: /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/autosuspend_delay_ms: Input/output error /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_enabled:disabled /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_active_time:0 /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/control:auto /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/async:disabled /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_usage:0 /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/power/runtime_status:unsupported /sys/class/backlight/thinkpad_screen/subsystem/thinkpad_screen/max_brightness:15
[Kernel-packages] [Bug 1779173] Re: Dell D6000 dock lacks multicast Ethernet functionality
Seems like these patches are not in upstream yet. -- 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/1779173 Title: Dell D6000 dock lacks multicast Ethernet functionality Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: Dell D6000 exposes a CDC_NCM device for Ethernet traffic. However, multicast Ethernet traffic is not processed making IPv6 not functional. Other services, like mDNS used for LAN service discovery are also hindered. The actual reason is that CDC_NCM driver was not processing requests to filter (admit) multicast traffic. I provide two patches to the linux kernel that admit all Ethernet multicast traffic whenever a multicast group is being joined. The solution is not optimal, as it makes the system receive more traffic than that strictly needed, but otherwise this only happens when the computer is connected to a dock and thus is running on AC power. I believe it is not worth the hassle to join only the requested groups. This is the same that is done in the CDN_ETHER driver. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1779173/+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 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
If it's the same one as LP: #1771467, then it's fixed. -- 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/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+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 1816947] Re: [Dell XPS L321X] Touchpad not working after last apt-get upgrade
Please attach dmesg when it works and when it doesn't work. -- 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/1816947 Title: [Dell XPS L321X] Touchpad not working after last apt-get upgrade Status in libinput package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: The touchpad doesn't work unless the cursor is moved slowly. WORKAROUND: Execute at a terminal: sudo modprobe -r psmouse sudo modprobe psmouse proto=imps ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.402 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 02:56:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:052e] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) MachineType: Dell Inc. Dell System XPS L321X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L321X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.394 CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:052e] LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Dell System XPS L321X Package: libinput (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/27/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L321X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel:
[Kernel-packages] [Bug 1818407] Re: Cant access emmc, error -84
Ok, please raise the issue to sdhci-pci maintainers: $ scripts/get_maintainer.pl -f drivers/mmc/host/sdhci-pci-core.c Adrian Hunter (maintainer:SECURE DIGITAL HOST CONTROLLER INTERFACE (SDHCI...) Ulf Hansson (maintainer:MULTIMEDIA CARD (MMC), SECURE DIGITAL (SD) AND...) linux-...@vger.kernel.org (open list:SECURE DIGITAL HOST CONTROLLER INTERFACE (SDHCI...) linux-ker...@vger.kernel.org (open list) -- 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/1818407 Title: Cant access emmc, error -84 Status in linux package in Ubuntu: Confirmed Bug description: Greetings! I just got my new convertible(Asus TP202NAS, brand new) and wanted to install kubuntu 18.10 onto the internal storage, only to find that it cant see it. In dmesg i only got these two error: mc0: mmc_select_hs400 failed, error -84 mc0: error -84 whilst initializing mmc card Tried to google around for a solution but i didnt found any solution to this, also tried the kubuntu IRC channel but didnt got any luck there too /EDIT Submitted from a live session. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-release-upgrader-core 1:18.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CrashDB: ubuntu Date: Sun Mar 3 13:59:13 2019 LiveMediaBuild: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3661 F pulseaudio CasperVersion: 1.394 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 LiveMediaBuild: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 003: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:3501 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. TP202NAS Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP202NAS.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP202NAS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP202NAS.209:bd07/19/2018:svnASUSTeKCOMPUTERINC.:pnTP202NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP202NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: TP202NAS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+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 1817091] Re: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1817091 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-42fYy1/46-libnvidia-compute-390_390.77-0ubuntu0.18.04.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Feb 21 21:29:40 2019 DuplicateSignature: package:libnvidia-compute-390:(not installed) Unpacking libnvidia-compute-390:amd64 (390.77-0ubuntu0.18.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-42fYy1/46-libnvidia-compute-390_390.77-0ubuntu0.18.04.2_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2018-12-03 (79 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 UpgradeStatus: Upgraded to bionic on 2018-12-04 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1817091/+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 1719545] Comment bridged from LTC Bugzilla
--- Comment From pavsu...@in.ibm.com 2019-03-06 23:35 EDT--- The kernel does not fix the original issue and the issue is still occurring. -- 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/1719545 Title: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2017-06-29 02:30:22 == ---Problem Description--- cpupower monitor shows multiple stop Idle_Stats ---uname output--- Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS. Then execute the cpupower monitor command to fetch all the Idle_Stats values. root@zz376p1:~# cpupower monitor |Idle_Stats PKG |CORE|CPU | snoo | stop | stop 0| 8| 0| 0.00| 0.00| 2.79 0| 8| 1| 0.00| 0.00| 70.68 0| 8| 2| 0.00| 0.00| 99.87 0| 8| 3| 0.00| 0.00| 67.28 0| 12| 4| 0.00| 0.00| 5.17 0| 12| 5| 0.00| 0.00| 12.50 0| 12| 6| 0.00| 0.00| 99.74 0| 12| 7| 0.00| 0.00| 0.00 8|2048| 8| 0.00| 0.00| 22.14 8|2048| 9| 0.00| 0.00| 102.3 8|2048| 10| 0.00| 0.00| 0.00 8|2048| 11| 0.00| 0.00| 99.97 8|2052| 12| 0.00| 0.00| 99.70 8|2052| 13| 0.00| 0.00| 23.86 8|2052| 14| 0.00| 0.00| 113.1 8|2052| 15| 0.00| 0.00| 0.00 As can be seen it shows 2 columns for stop. root@zz376p1:~# uname -a Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@zz376p1:~# cat /etc/os-release NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial root@zz376p1:~# cat /proc/cpuinfo | tail processor : 15 cpu : POWER9 (raw), altivec supported clock : 2600.00MHz revision: 1.0 (pvr 004e 0100) timebase: 51200 platform: PowerNV model : 8375-42A machine : PowerNV 8375-42A firmware: OPAL Userspace tool common name: /usr/bin/cpupower The userspace tool has the following bit modes: 64-bit Userspace rpm: linux-tools-common Userspace tool obtained from project website: na *Additional Instructions for pavsu...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. . There are 3 idle_stats (3 states) in this system. root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s snoo [T] -> snooze stop [T] -> stop0_lite stop [T] -> stop1_lite root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 3 Available idle states: snooze stop0_lite stop1_lite snooze: Flags/Description: snooze Latency: 0 Usage: 224 Duration: 423 stop0_lite: Flags/Description: stop0_lite Latency: 0 Usage: 1685 Duration: 530522 stop1_lite: Flags/Description: stop1_lite Latency: 4 Usage: 12693 Duration: 5405898106 root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s snoo [T] -> snooze stop [T] -> stop0_lite stop [T] -> stop1_lite root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 3 Available idle states: snooze stop0_lite stop1_lite snooze: Flags/Description: snooze Latency: 0 Usage: 272 Duration: 905 stop0_lite: Flags/Description: stop0_lite Latency: 0 Usage: 2141 Duration: 536399 stop1_lite: Flags/Description: stop1_lite Latency: 4 Usage: 15396 Duration: 6625668881 cpu monitor will print the results of all the 3 available idle_stats . The first stop -> stop0_lite stats and The second stop -> stop1_lite stats. cpupower monitor header prints the header list by getting the name of the idle stats. name (name description) snoo [T] -> snooze stop [T] -> stop0_lite stop
[Kernel-packages] [Bug 1812153] Re: CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel
** Also affects: linux-kvm (Ubuntu Disco)
Importance: Undecided
Assignee: Po-Hsu Lin (cypressyew)
Status: In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812153
Title:
CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel
Status in ubuntu-kernel-tests:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-kvm source package in Bionic:
Fix Released
Status in linux-kvm source package in Cosmic:
In Progress
Status in linux-kvm source package in Disco:
In Progress
Bug description:
The test_081_config_security_selinux_disable test failed on the Bionic
KVM kernel
FAIL: test_081_config_security_selinux_disable
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2152, in
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 209, in assertKernelConfig
self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
'%s option was expected to be unset in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be
unset in the kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 04:31:59 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812153/+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 1818899] Re: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login
There are two nouveau commits which landed in v4.18-rc6 get backport to Ubuntu's kernel. Can you test mainline kernel v4.18-rc6 and see if the issue also happens there? -- 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/1818899 Title: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I can boot to login, but if I input correct information it freezes. If I boot in recovery mode and choose to resume boot, I can login. But my external display doesn't register. If I choose the failsafeX version there is an error text related to xorg. I have not had any problems before on this terminal. It came when I let the system update and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 20:26:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:119b] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1197] InstallationDate: Installed on 2018-11-26 (100 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 004: ID 04f3:0c03 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A715-71G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=06e8310e-d1a9-42d8-a804-841358355e74 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmeleon_KLS dmi.board.vendor: KBL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd08/22/2017:svnAcer:pnAspireA715-71G:pvrV1.10:rvnKBL:rnCharmeleon_KLS:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-71G dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Mar 6 20:16:01 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 --- ProblemType: Bug .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:119b] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile]
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
Does reverting the simple commit help? If it helps then we should simply revert it. The other route is to back port the functional changes this commit depends on, ranges from v4.15 to v4.17. -- 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/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+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 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
The instruction uses deb because it's easier to remove. We can skip building the deb though. Use "make -j`nproc` && make -j`nproc` modules && sudo make modules_install && sudo make install` instead. When the bisection is done, the "artifacts" are in /boot/, /lib/modules/ and /var/lib/initramfs-tools/. Remove files in those places. -- 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/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 Status in linux package in Ubuntu: Confirmed Bug description: Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+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 1813783] Re: Unable to toggle Touchpad by keyboard shortcut
For this case, the key will be "KEYBOARD_KEY_f8=f21". -- 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/1813783 Title: Unable to toggle Touchpad by keyboard shortcut Status in linux package in Ubuntu: Confirmed Bug description: Pressing Fn+F5 button should toggle the onboard touchpad. This seems not to work and might be related to the following bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931 After pressing Fn+F5 shows the following: $ dmesg ... [ 248.412826] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0). [ 248.412833] atkbd serio0: Use 'setkeycodes e078 ' to make it known. [ 250.261108] atkbd serio0: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0). [ 250.261110] atkbd serio0: Use 'setkeycodes e078 ' to make it known. I've added the mentioned kernel parameters as described in https://wiki.ubuntu.com/DebuggingACPI (adding acpi=off) and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931/comments/21 (i8042.nomux=1) but the problem still exists. Touchpad also has a little dot in the upper left side which I assume also is for toggling on/off the touchpad. This is also unresponsive. How reproducible: Always Steps to Reproduce: Press Fn+F5 Actual results: Touchpad is not working Expected results: Touchpad should toggle on/off, making it able to use the touchpad. Extra info: Bios is up to date. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ inxi -F System:Host: CarogaLaptopLinux Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Machine: Device: laptop System: Standard product: Standard v: Standard serial: N/A Mobo: Standard model: Standard v: Standard serial: N/A UEFI: American Megatrends v: N.0.05 date: 04/14/2018 BatteryBAT0: charge: 42.2 Wh 90.2% condition: 46.7/46.7 Wh (100%) CPU: 6 core Intel Core i7-8750H (-MT-MCP-) cache: 9216 KB clock speeds: max: 4100 MHz 1: 1541 MHz 2: 2043 MHz 3: 2069 MHz 4: 2345 MHz 5: 2241 MHz 6: 2111 MHz 7: 2080 MHz 8: 2047 MHz 9: 2035 MHz 10: 2388 MHz 11: 1879 MHz 12: 2175 MHz Graphics: Card-1: Intel Device 3e9b Card-2: NVIDIA GP106M [GeForce GTX 1060 Mobile] Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@144.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics (Coffeelake 3x8 GT2) version: 4.5 Mesa 18.0.5 Audio: Card Intel Device a348 driver: snd_hda_intel Sound: ALSA v: k4.15.0-43-generic Network: Card-1: Intel Device a370 driver: iwlwifi IF: wlo1 state: up speed: N/A duplex: N/A mac: 94:b8:6d:fc:16:24 Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 IF: enp4s0 state: down mac: b0:25:aa:29:17:57 Drives:HDD Total Size: 500.1GB (25.6% used) ID-1: /dev/nvme0n1 model: WDS500G2X0C size: 500.1GB ID-2: /dev/nvme1n1 model: WDS500G2X0C size: 500.1GB Partition: ID-1: / size: 398G used: 61G (17%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: swap-1 size: 65.53GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p1 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 55.0C mobo: 54.0C Fan Speeds (in rpm): cpu: N/A Info: Processes: 387 Uptime: 16 min Memory: 3855.5/32027.2MB Client: Shell (zsh) inxi: 2.3.56 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caroga 3523 F...m pulseaudio /dev/snd/controlC0: caroga 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 16:04:41 2019 HibernationDevice: RESUME=UUID=8cafe715-f523-4099-8dd8-7f80c5de58d4 InstallationDate: Installed on 2018-08-17 (164 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Standard Standard ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=e177b84e-a10b-4a4e-8d1c-8eeafbb021ba ro quiet splash i8042.nomux=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2018 dmi.bios.vendor: American Megatrends
[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
Log in #20 is really useful. Please file an upstream bug at https://bugs.freedesktop.org/ Product: DRI Component: DRM/AMDgpu And attach the log in #20. Thanks! -- 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/1818580 Title: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Status in linux package in Ubuntu: Incomplete Bug description: I cannot boot PC normally, i must use recovery mode. WORKAROUND: Use kernel parameter: nomodeset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 5 00:59:48 2019 DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:353e] InstallationDate: Installed on 2012-02-27 (2562 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M vt.handoff=1 SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago) dmi.bios.date: 01/15/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+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 1521173] Re: AER: Corrected error received: id=00e0
I get the pcie errors on all X,L,K Ubuntu's disco 19.04 [ 3056.549121] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [ 3056.549136] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [ 3056.549147] pcieport :00:1c.0: device [8086:a33d] error status/mask=1000/2000 [ 3056.549154] pcieport :00:1c.0:[12] Timeout 00:1c.0 0604: 8086:a33d (rev f0) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 122 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 3000-3fff Memory behind bridge: a210-a21f Prefetchable memory behind bridge: a000-a00f Capabilities: Kernel driver in use: pcieport = lspci -s 000:00:1c.0 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port (rev f0) = $ lspci -vt -[:00]-+-00.0 Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers +-02.0 Intel Corporation UHD Graphics 630 (Desktop) +-08.0 Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model +-12.0 Intel Corporation Cannon Lake PCH Thermal Controller +-14.0 Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller +-14.2 Intel Corporation Cannon Lake PCH Shared SRAM +-14.3 Intel Corporation Wireless-AC 9560 [Jefferson Peak] +-16.0 Intel Corporation Cannon Lake PCH HECI Controller +-17.0 Intel Corporation SATA Controller [RAID mode] +-1c.0-[01]00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller +-1f.0 Intel Corporation Device a308 +-1f.3 Intel Corporation Cannon Lake PCH cAVS +-1f.4 Intel Corporation Cannon Lake PCH SMBus Controller \-1f.5 Intel Corporation Cannon Lake PCH SPI Controller -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed
[Kernel-packages] [Bug 1812153] Re: CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel
** Also affects: linux-kvm (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu Cosmic)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-kvm (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812153
Title:
CONFIG_SECURITY_SELINUX_DISABLE should be disabled on KVM kernel
Status in ubuntu-kernel-tests:
In Progress
Status in linux-kvm package in Ubuntu:
In Progress
Status in linux-kvm source package in Bionic:
Fix Released
Status in linux-kvm source package in Cosmic:
In Progress
Bug description:
The test_081_config_security_selinux_disable test failed on the Bionic
KVM kernel
FAIL: test_081_config_security_selinux_disable
(__main__.KernelSecurityConfigTest)
Ensure CONFIG_SECURITY_SELINUX_DISABLE is disabled (LP: #1680315)
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2152, in
test_081_config_security_selinux_disable
self.assertKernelConfig('SECURITY_SELINUX_DISABLE', expected)
File "./test-kernel-security.py", line 209, in assertKernelConfig
self.assertKernelConfigUnset(name)
File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
'%s option was expected to be unset in the kernel config' % name)
AssertionError: SECURITY_SELINUX_DISABLE option was expected to be
unset in the kernel config
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 04:31:59 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812153/+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 1818530] Re: bluetooth always starts at startup
*** This bug is a duplicate of bug 1574311 *** https://bugs.launchpad.net/bugs/1574311 ** This bug is no longer a duplicate of bug 1809783 When TLP is installed, Bluetooth always on when power on my laptop regardless of its previous state ** This bug has been marked a duplicate of bug 1574311 TLP by default breaks wifi/bluetooth status restore on startup. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1818530 Title: bluetooth always starts at startup Status in bluez package in Ubuntu: Incomplete Bug description: after every startup, I have to manually turn off bluetooth which is enabled at startup ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Mar 4 20:24:42 2019 InstallationDate: Installed on 2018-10-16 (139 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5d5 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-br0xx ProcEnviron: LC_CTYPE=en_IN TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=0bb24ccc-6f8f-43ca-8a73-ccd2f46a3633 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHPLaptop15g-br0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-br0xx dmi.product.sku: 2JR17PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:AF:BD:F0:13:69 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:1787 acl:0 sco:0 events:224 errors:0 TX bytes:43852 acl:0 sco:0 commands:224 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1818530/+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 1812189] Re: test_bpf in net from ubuntu_kernel_selftests failed on KVM / Cosmic kernels
Could be fixed by commit https://kernel.ubuntu.com/git/ubuntu/autotest- client-tests.git/commit/?id=fd2e1daffb3c66241aa8898c015eefe9ba0bf429 -- 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/1812189 Title: test_bpf in net from ubuntu_kernel_selftests failed on KVM / Cosmic kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-kvm source package in Xenial: New Status in linux source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-kvm source package in Cosmic: New Bug description: This test will attempt to insert the test_bpf module, but this module does not exist in KVM kernels: $ sudo modprobe test_bpf modprobe: FATAL: Module test_bpf not found in directory /lib/modules/4.15.0-1028-kvm The script: $ sudo ./test_bpf.sh test_bpf: [FAIL] $ cat test_bpf.sh #!/bin/sh # SPDX-License-Identifier: GPL-2.0 # Runs bpf test using test_bpf kernel module if /sbin/modprobe -q test_bpf ; then /sbin/modprobe -q -r test_bpf; echo "test_bpf: ok"; else echo "test_bpf: [FAIL]"; exit 1; fi This test_bpf module will need the CONFIG_TEST_BPF to be enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 08:29:29 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812189/+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 1818899] 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/1818899 Title: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I can boot to login, but if I input correct information it freezes. If I boot in recovery mode and choose to resume boot, I can login. But my external display doesn't register. If I choose the failsafeX version there is an error text related to xorg. I have not had any problems before on this terminal. It came when I let the system update and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 20:26:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:119b] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1197] InstallationDate: Installed on 2018-11-26 (100 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 004: ID 04f3:0c03 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A715-71G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=06e8310e-d1a9-42d8-a804-841358355e74 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmeleon_KLS dmi.board.vendor: KBL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd08/22/2017:svnAcer:pnAspireA715-71G:pvrV1.10:rvnKBL:rnCharmeleon_KLS:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-71G dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Mar 6 20:16:01 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 --- ProblemType: Bug .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:119b] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1197] InstallationDate: Installed on 2018-11-26 (100 days ago)
[Kernel-packages] [Bug 1818813] Re: Xenial update: 4.4.175 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: New => 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/1818813 Title: Xenial update: 4.4.175 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.175 upstream stable release from git://git.kernel.org/ Linux 4.4.175 uapi/if_ether.h: move __UAPI_DEF_ETHHDR libc define pinctrl: msm: fix gpio-hog related boot issues usb: dwc2: Remove unnecessary kfree kaweth: use skb_cow_head() to deal with cloned skbs ch9200: use skb_cow_head() to deal with cloned skbs smsc95xx: Use skb_cow_head to deal with cloned skbs dm thin: fix bug where bio that overwrites thin block ignores FUA x86/a.out: Clear the dump structure initially signal: Restore the stop PTRACE_EVENT_EXIT x86/platform/UV: Use efi_runtime_lock to serialise BIOS calls tracing/uprobes: Fix output for multiple string arguments alpha: Fix Eiger NR_IRQS to 128 alpha: fix page fault handling for r16-r18 targets Input: elantech - enable 3rd button support on Fujitsu CELSIUS H780 Input: bma150 - register input device after setting private data ALSA: usb-audio: Fix implicit fb endpoint setup by quirk ALSA: hda - Add quirk for HP EliteBook 840 G5 perf/core: Fix impossible ring-buffer sizes warning Input: elan_i2c - add ACPI ID for touchpad in Lenovo V330-15ISK Revert "Input: elan_i2c - add ACPI ID for touchpad in ASUS Aspire F5-573G" Documentation/network: reword kernel version reference cifs: Limit memory used by lock request calls to a page gpio: pl061: handle failed allocations ARM: dts: kirkwood: Fix polarity of GPIO fan lines ARM: dts: da850-evm: Correct the sound card name uapi/if_ether.h: prevent redefinition of struct ethhdr Revert "exec: load_script: don't blindly truncate shebang string" batman-adv: Force mac header to start of data on xmit batman-adv: Avoid WARN on net_device without parent in netns xfrm: refine validation of template and selector families libceph: avoid KEEPALIVE_PENDING races in ceph_con_keepalive() Revert "cifs: In Kconfig CONFIG_CIFS_POSIX needs depends on legacy (insecure cifs)" NFC: nxp-nci: Include unaligned.h instead of access_ok.h HID: debug: fix the ring buffer implementation drm/vmwgfx: Return error code from vmw_execbuf_copy_fence_user drm/vmwgfx: Fix setting of dma masks drm/modes: Prevent division by zero htotal mac80211: ensure that mgmt tx skbs have tailroom for encryption ARM: iop32x/n2100: fix PCI IRQ mapping MIPS: VDSO: Include $(ccflags-vdso) in o32,n32 .lds builds MIPS: OCTEON: don't set octeon_dma_bar_type if PCI is disabled mips: cm: reprime error cause debugfs: fix debugfs_rename parameter checking misc: vexpress: Off by one in vexpress_syscfg_exec() signal: Better detection of synchronous signals signal: Always notice exiting tasks mtd: rawnand: gpmi: fix MX28 bus master lockup problem perf tests evsel-tp-sched: Fix bitwise operator perf/core: Don't WARN() for impossible ring-buffer sizes x86/MCE: Initialize mce.bank in the case of a fatal error in mce_no_way_out() perf/x86/intel/uncore: Add Node ID mask KVM: nVMX: unconditionally cancel preemption timer in free_nested (CVE-2019-7221) KVM: x86: work around leak of uninitialized stack contents (CVE-2019-7222) usb: gadget: udc: net2272: Fix bitwise and boolean operations usb: phy: am335x: fix race condition in _probe dmaengine: imx-dma: fix wrong callback invoke fuse: handle zero sized retrieve correctly fuse: decrement NR_WRITEBACK_TEMP on the right page fuse: call pipe_buf_release() under pipe lock ALSA: hda - Serialize codec registrations ALSA: compress: Fix stop handling on compressed capture streams net: dsa: slave: Don't propagate flag changes on down slave interfaces net: systemport: Fix WoL with password after deep sleep skge: potential memory corruption in skge_get_regs() net: dp83640: expire old TX-skb enic: fix checksum validation for IPv6 dccp: fool proof ccid_hc_[rt]x_parse_options() string: drop __must_check from strscpy() and restore strscpy() usages in cgroup tipc: use destination length for copy string test_hexdump: use memcpy instead of strncpy thermal: hwmon: inline helpers when CONFIG_THERMAL_HWMON is not set exec: load_script: don't
[Kernel-packages] [Bug 1818815] Re: Xenial update: 4.4.176 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: New => 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/1818815 Title: Xenial update: 4.4.176 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.176 upstream stable release from git://git.kernel.org/ Linux 4.4.176 KVM: VMX: Fix x2apic check in vmx_msr_bitmap_mode() ax25: fix possible use-after-free mISDN: fix a race in dev_expire_timer() net/x25: do not hold the cpu too long in x25_new_lci() mfd: as3722: Mark PM functions as __maybe_unused mfd: as3722: Handle interrupts on suspend kvm: fix kvm_ioctl_create_device() reference counting (CVE-2019-6974) x86: livepatch: Treat R_X86_64_PLT32 as R_X86_64_PC32 net: ipv4: use a dedicated counter for icmp_v4 redirect packets net: stmmac: Fix a race in EEE enable callback vxlan: test dev->flags & IFF_UP before calling netif_rx() tcp: clear icsk_backoff in tcp_write_queue_purge() net: Do not allocate page fragments that are not skb aligned tcp: tcp_v4_err() should be more careful net: Add header for usage of fls64() sky2: Increase D3 delay again net: Fix for_each_netdev_feature on Big endian hwmon: (lm80) Fix missing unlock on error in set_fan_div() vsock: cope with memory allocation failure at socket creation time net: fix IPv6 prefix route residue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818815/+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 1818803] Re: Xenial update: 4.4.173 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: New => 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/1818803 Title: Xenial update: 4.4.173 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.173 upstream stable release from git://git.kernel.org/ Linux 4.4.173 fs: don't scan the inode cache before SB_BORN is set mm: migrate: don't rely on __PageMovable() of newpage after unlocking it drivers: core: Remove glue dirs from sysfs earlier cifs: Always resolve hostname before reconnecting mm, oom: fix use-after-free in oom_kill_process kernel/exit.c: release ptraced tasks before zap_pid_ns_processes mmc: sdhci-iproc: handle mmc_of_parse() errors during probe platform/x86: asus-nb-wmi: Drop mapping of 0x33 and 0x34 scan codes platform/x86: asus-nb-wmi: Map 0x35 to KEY_SCREENLOCK gfs2: Revert "Fix loop in gfs2_rbm_find" arm64: hyp-stub: Forbid kprobing of the hyp-stub ARM: cns3xxx: Fix writing to wrong PCI config registers after alignment fs/dcache: Fix incorrect nr_dentry_unused accounting in shrink_dcache_sb() CIFS: Do not count -ENODATA as failure for query directory l2tp: fix reading optional fields of L2TPv3 l2tp: remove l2specific_len dependency in l2tp_core ucc_geth: Reset BQL queue when stopping device net/rose: fix NULL ax25_cb kernel panic netrom: switch to sock timer API net/mlx4_core: Add masking for a few queries on HCA caps l2tp: copy 4 more bytes to linear part if necessary ipv6: Consider sk_bound_dev_if when binding a socket to an address fs: add the fsnotify call to vfs_iter_write s390/smp: Fix calling smp_call_ipl_cpu() from ipl CPU Revert "loop: Fold __loop_release into loop_release" Revert "loop: Get rid of loop_index_mutex" Revert "loop: Fix double mutex_unlock(_ctl_mutex) in loop_control_ioctl()" f2fs: read page index before freeing arm64: mm: remove page_mapping check in __sync_icache_dcache irqchip/gic-v3-its: Align PCI Multi-MSI allocation on their size perf unwind: Take pgoff into account when reporting elf to libdwfl perf unwind: Unwind with libdw doesn't take symfs into account vt: invoke notifier on screen size change can: bcm: check timer values before ktime conversion can: dev: __can_get_echo_skb(): fix bogous check for non-existing skb by removing it x86/kaslr: Fix incorrect i8254 outb() parameters KVM: x86: Fix single-step debugging Input: xpad - add support for SteelSeries Stratus Duo CIFS: Fix possible hang during async MTU reads and writes tty/n_hdlc: fix __might_sleep warning tty: Handle problem if line discipline does not have receive_buf staging: rtl8188eu: Add device code for D-Link DWA-121 rev B1 char/mwave: fix potential Spectre v1 vulnerability s390/smp: fix CPU hotplug deadlock with CPU rescan s390/early: improve machine detection ARC: perf: map generic branches to correct hardware condition ASoC: atom: fix a missing check of snd_pcm_lib_malloc_pages USB: serial: pl2303: add new PID to support PL2303TB USB: serial: simple: add Motorola Tetra TPG2200 device id net: bridge: Fix ethernet header pointer before check skb forwardable net_sched: refetch skb protocol for each filter net: ipv4: Fix memory leak in network namespace dismantle openvswitch: Avoid OOB read when parsing flow nlattrs net: Fix usage of pskb_trim_rcsum To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818803/+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 1818797] Re: Xenial update: 4.4.172 upstream stable release
** Changed in: linux (Ubuntu Xenial)
Status: New => 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/1818797
Title:
Xenial update: 4.4.172 upstream stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.172 upstream stable release
from git://git.kernel.org/
Linux 4.4.172
ipmi:ssif: Fix handling of multi-part return messages
net: speed up skb_rbtree_purge()
mm, proc: be more verbose about unstable VMA flags in /proc//smaps
mm/page-writeback.c: don't break integrity writeback on ->writepage() error
ocfs2: fix panic due to unrecovered local alloc
scsi: megaraid: fix out-of-bound array accesses
sysfs: Disable lockdep for driver bind/unbind files
ALSA: bebob: fix model-id of unit for Apogee Ensemble
dm snapshot: Fix excessive memory usage and workqueue stalls
dm kcopyd: Fix bug causing workqueue stalls
perf parse-events: Fix unchecked usage of strncpy()
perf svghelper: Fix unchecked usage of strncpy()
perf intel-pt: Fix error with config term "pt=0"
mmc: atmel-mci: do not assume idle after atmci_request_end
kconfig: fix memory leak when EOF is encountered in quotation
kconfig: fix file name and line number of warn_ignored_character()
clk: imx6q: reset exclusive gates on init
scsi: target: use consistent left-aligned ASCII INQUIRY data
net: call sk_dst_reset when set SO_DONTROUTE
media: firewire: Fix app_info parameter type in avc_ca{,_app}_info
powerpc/pseries/cpuidle: Fix preempt warning
pstore/ram: Do not treat empty buffers as valid
jffs2: Fix use of uninitialized delayed_work, lockdep breakage
arm64: perf: set suppress_bind_attrs flag to true
MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur
writeback: don't decrement wb->refcnt if !wb->bdi
e1000e: allow non-monotonic SYSTIM readings
platform/x86: asus-wmi: Tell the EC the OS will handle the display off hotkey
xfs: don't fail when converting shortform attr to long form during
ATTR_REPLACE
ipv6: Take rcu_read_lock in __inet6_bind for mapped addresses
ipv6: Consider sk_bound_dev_if when binding a socket to a v4 mapped address
r8169: Add support for new Realtek Ethernet
media: vb2: be sure to unlock mutex on errors
drm/fb-helper: Ignore the value of fb_var_screeninfo.pixclock
loop: Fix double mutex_unlock(_ctl_mutex) in loop_control_ioctl()
loop: Get rid of loop_index_mutex
loop: Fold __loop_release into loop_release
block/loop: Use global lock for ioctl() operation.
tipc: fix uninit-value in tipc_nl_compat_doit
tipc: fix uninit-value in tipc_nl_compat_name_table_dump
tipc: fix uninit-value in tipc_nl_compat_link_set
tipc: fix uninit-value in tipc_nl_compat_bearer_enable
tipc: fix uninit-value in tipc_nl_compat_link_reset_stats
sctp: allocate sctp_sockaddr_entry with kzalloc
selinux: fix GPF on invalid policy
sunrpc: handle ENOMEM in rpcb_getport_async
media: vb2: vb2_mmap: move lock up
LSM: Check for NULL cred-security on free
media: vivid: set min width/height to a value > 0
media: vivid: fix error handling of kthread_run
omap2fb: Fix stack memory disclosure
Disable MSI also when pcie-octeon.pcie_disable on
mfd: tps6586x: Handle interrupts on suspend
mips: fix n32 compat_ipc_parse_version
scsi: sd: Fix cache_type_store()
Yama: Check for pid death before checking ancestry
btrfs: wait on ordered extents on abort cleanup
crypto: authenc - fix parsing key with misaligned rta_len
crypto: authencesn - Avoid twice completion call in decrypt path
ip: on queued skb use skb_header_pointer instead of pskb_may_pull
packet: Do not leak dev refcounts on error exit
net: bridge: fix a bug on using a neighbour cache entry without checking its
state
ipv6: fix kernel-infoleak in ipv6_local_error()
arm64: Don't trap host pointer auth use to EL2
arm64/kvm: consistently handle host HCR_EL2 flags
proc: Remove empty line in /proc/self/status
media: em28xx: Fix misplaced reset of dev->v4l::field_count
f2fs: fix validation of the block count in sanity_check_raw_super
f2fs: fix missing up_read
f2fs: fix invalid memory access
f2fs: fix to do sanity check with cp_pack_start_sum
f2fs: fix to do sanity check with block address in main area v2
f2fs: fix to do sanity check with block address in main area
f2fs: fix to do
[Kernel-packages] [Bug 1818806] Re: Xenial update: 4.4.174 upstream stable release
** Changed in: linux (Ubuntu Xenial) Status: New => 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/1818806 Title: Xenial update: 4.4.174 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.174 upstream stable release from git://git.kernel.org/ Linux 4.4.174 rcu: Force boolean subscript for expedited stall warnings net: ipv4: do not handle duplicate fragments as overlapping net: fix pskb_trim_rcsum_slow() with odd trim offset inet: frags: better deal with smp races ipv4: frags: precedence bug in ip_expire() ip: frags: fix crash in ip_do_fragment() ip: process in-order fragments efficiently ip: add helpers to process in-order fragments faster. ip: use rb trees for IP frag queue. net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends ipv6: defrag: drop non-last frags smaller than min mtu net: modify skb_rbtree_purge to return the truesize of all purged skbs. ip: discard IPv4 datagrams with overlapping segments. inet: frags: fix ip6frag_low_thresh boundary inet: frags: get rid of ipfrag_skb_cb/FRAG_CB inet: frags: reorganize struct netns_frags rhashtable: reorganize struct rhashtable layout ipv6: frags: rewrite ip6_expire_frag_queue() inet: frags: do not clone skb in ip_expire() inet: frags: break the 2GB limit for frags storage inet: frags: remove inet_frag_maybe_warn_overflow() inet: frags: get rif of inet_frag_evicting() inet: frags: remove some helpers ipfrag: really prevent allocation on netns exit net: ieee802154: 6lowpan: fix frag reassembly inet: frags: use rhashtables for reassembly units rhashtable: add schedule points rhashtable: Add rhashtable_lookup() rhashtable: add rhashtable_lookup_get_insert_key() inet: frags: refactor lowpan_net_frag_init() inet: frags: refactor ipv6_frag_init() inet: frags: refactor ipfrag_init() inet: frags: add a pointer to struct netns_frags inet: frags: change inet_frags_init_net() return value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818806/+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 1818899] Re: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login
Judging by linux-image-4.15.0-46-generic.259292.crash, it appears a kernel crash in the nouveau driver is the problem here. If you are able and willing to disable the Nvidia GPU in your system BIOS then you might find that also works around the problem. A different solution would likely to be to install the proprietary Nvidia driver instead: sudo apt install nvidia-driver-390 ** Summary changed: - After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login + [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: nouveau ** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu) ** Also 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/1818899 Title: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login Status in linux package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I can boot to login, but if I input correct information it freezes. If I boot in recovery mode and choose to resume boot, I can login. But my external display doesn't register. If I choose the failsafeX version there is an error text related to xorg. I have not had any problems before on this terminal. It came when I let the system update and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 20:26:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:119b] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1197] InstallationDate: Installed on 2018-11-26 (100 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 004: ID 04f3:0c03 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A715-71G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=06e8310e-d1a9-42d8-a804-841358355e74 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Charmeleon_KLS dmi.board.vendor: KBL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd08/22/2017:svnAcer:pnAspireA715-71G:pvrV1.10:rvnKBL:rnCharmeleon_KLS:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-71G dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Mar 6 20:16:01 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 --- ProblemType: Bug .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5
[Kernel-packages] [Bug 1818879] Re: pull cirrus.ko into main kernel package
Are you suggesting anything in Xorg needs fixing, or is the Xorg task just an FYI because it's related? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (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/1818879 Title: pull cirrus.ko into main kernel package Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: In disco, xorg stopped shipping a cirrus module/driver, instead relying on the kernel one. But the kernel one is in the linux-modules- extra--generic package, which is not installed by default in vms. That breaks some assumptions: uvtool, for example, doesn't specify a video device when creating a vm, and the default in libvirt in such cases is to use cirrus. As a conseguence, disco VMs created by tools that do not specify a default video device won't have the cirrus.ko module, and X won't start there. It's a bit more complicated, however, because X just tries other fallbacks, but they also don't work. In particular, vesa doesn't work: [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted value (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/) We can change uvtool and specify a video device instead of leaving it blank (see bug #1818877), but there might be other tools out there spawning guests without telling them which video device to use, and they would also fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818879/+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 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
elhoir: 1) >"yes, its a copy paste of crash part of dmesg, not entire output." Then attach a full dmesg as previously advised. 2) >"GPU (RX 470) is quite new. I tested Ubuntu Cosmic and Ubuntu Dingo." To confirm, using only the RX470, it worked fine in Cosmic and Dingo. However, while using Dingo after a kernel update, Dingo stopped booting without a WORKAROUND? If so, which kernel update specifically? -- 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/1818580 Title: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Status in linux package in Ubuntu: Incomplete Bug description: I cannot boot PC normally, i must use recovery mode. WORKAROUND: Use kernel parameter: nomodeset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 5 00:59:48 2019 DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:353e] InstallationDate: Installed on 2012-02-27 (2562 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M vt.handoff=1 SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago) dmi.bios.date: 01/15/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+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 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
1) yes, its a copy paste of crash part of dmesg, not entire output. 2) well i cant test it, as its the 1st time im using amdgpu module, asi said. Previously i only used radeinsi and nouveau modules, my GPU (RX 470) is quite new. I tested Ubuntu Cosmic and Ubuntu Dingo. And no, none did require any workaround. -- 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/1818580 Title: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Status in linux package in Ubuntu: Incomplete Bug description: I cannot boot PC normally, i must use recovery mode. WORKAROUND: Use kernel parameter: nomodeset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 5 00:59:48 2019 DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:353e] InstallationDate: Installed on 2012-02-27 (2562 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M vt.handoff=1 SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago) dmi.bios.date: 01/15/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+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 1777586] Re: Ubuntu Server 18.04 LTS aacraid error
i can try. someone above found the issue was in a 4.13 kernel, i can move forward from 4.9.x and hopefully we can find where something changed. -- 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/1777586 Title: Ubuntu Server 18.04 LTS aacraid error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and am now running into these raid adapter driver errors. The server ran fine in older version. My apologies as I lost the exact version, but it never had any errors like this version. Now when ever I try to copy files to the RAID 5 drive, or untar a file, I get these errors now after a few MB's of written data. Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux batboat:/var/log$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 I have tried the IRQ debugging tips to no avail. I loaded in Debian9.4.0 and it only briefly showed this error once. But appears to be much more resilient and appears to work fine. Jun 19 00:02:21 batboat kernel: [ 498.770839] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.139167] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.795083] aacraid :03:09.0: Adapter health - 199 Jun 19 00:02:37 batboat kernel: [ 514.800376] aacraid :03:09.0: outstanding cmd: midlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800378] aacraid :03:09.0: outstanding cmd: lowlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800381] aacraid :03:09.0: outstanding cmd: error handler-0 Jun 19 00:02:37 batboat kernel: [ 514.800383] aacraid :03:09.0: outstanding cmd: firmware-5 Jun 19 00:02:37 batboat kernel: [ 514.800385] aacraid :03:09.0: outstanding cmd: kernel-0 Jun 19 00:02:37 batboat kernel: [ 514.800391] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800394] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800396] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800399] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800401] sd 4:0:0:0: Device offlined - not ready after error recovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+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 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
elhoir: 1) Regarding the dmesg posted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/comments/20 did you cut/snip it? Please ensure all logs are attached in their entirety (no cuts, snips, etc.). 2) To confirm a regression, regarding only the current AMD graphics card installed, what prior Ubuntu releases and prior kernel versions have you tested specifically, and did they require any WORKAROUNDs? ** Tags removed: regression ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-5.0 -- 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/1818580 Title: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Status in linux package in Ubuntu: Incomplete Bug description: I cannot boot PC normally, i must use recovery mode. WORKAROUND: Use kernel parameter: nomodeset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 5 00:59:48 2019 DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:353e] InstallationDate: Installed on 2012-02-27 (2562 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M vt.handoff=1 SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago) dmi.bios.date: 01/15/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+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 1818881] Re: ath10k_pci crashing
** 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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Confirmed Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias: pci:v168Cd0040sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
yes, system is totally messed up locally, still usable via SSH through -- 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/1818580 Title: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Status in linux package in Ubuntu: Incomplete Bug description: I cannot boot PC normally, i must use recovery mode. WORKAROUND: Use kernel parameter: nomodeset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 5 00:59:48 2019 DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:353e] InstallationDate: Installed on 2012-02-27 (2562 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M vt.handoff=1 SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago) dmi.bios.date: 01/15/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+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 1811815] Re: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked
TL;DR: I was wrong, sorry for the noise. After a bit more testing it seems that while the button does indeed seem to toggle the hard-block, it also triggers the flight mode toggle from userland (GNOME). These do not have to be in sync (pressing the button can at the same time disable the hard-block, but enable the soft-block). Adding the model to no_hw_rfkill does not disable GNOMEs flight mode when the button is pressed. So even though the flight mode button can be used as a workaround on affected models, they should still be added to the no_hw_rfkill list. I will prepare a patch for my S130. -- 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/1811815 Title: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked Status in linux package in Ubuntu: Confirmed Bug description: The issue here is that the drivers/platform/x86/ideapad_laptop.c module assumes the Lenovo Ideapad 330-15ICH has a hardware RF-kill switch, reads the I/O port for its state, gets a zero, and therefore reports to the kernel that RFkill is hard-blocked. The current workaround is to blacklist the module to stop it being loaded. I've attached a simple patch for the module that teaches it that this model does not have a hardware RF kill switch. Original Report - Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165 card, specifically on a Lenovo ideapad 330 laptop. A current workaround: - Blacklist the "ideapad-laptop" module. - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or something similar (if it does not already exist), and append "blacklist ideapad-laptop" to the file. Save and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dustin 1948 F pulseaudio /dev/snd/pcmC0D0p: dustin 1948 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 04:08:20 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 3938:1047 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 2012" quiet splash nouveau.modeset=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811815/+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 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
iḿ getting this logs in dmesg, maybe after trying to load amgpu with "sudo modprobe amdgpu"? ** Attachment added: "amdgpu-at-dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+attachment/5244194/+files/amdgpu-at-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/1818580 Title: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Status in linux package in Ubuntu: Incomplete Bug description: I cannot boot PC normally, i must use recovery mode. WORKAROUND: Use kernel parameter: nomodeset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 5 00:59:48 2019 DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:353e] InstallationDate: Installed on 2012-02-27 (2562 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M vt.handoff=1 SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago) dmi.bios.date: 01/15/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+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 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
** Attachment added: "video of (bad) booting" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+attachment/5244193/+files/VID_20190306_232129.3gp -- 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/1818580 Title: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Status in linux package in Ubuntu: Incomplete Bug description: I cannot boot PC normally, i must use recovery mode. WORKAROUND: Use kernel parameter: nomodeset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 5 00:59:48 2019 DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [174b:353e] InstallationDate: Installed on 2012-02-27 (2562 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=512M-:192M vt.handoff=1 SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago) dmi.bios.date: 01/15/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.10F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+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 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.
okay, the "modprobe.blacklist=amdgpu" parameter did work. Now at SSH: elhoir@elhoir-desktop:~$ sudo modprobe amdgpu [sudo] contraseña para elhoir: elhoir@elhoir-desktop:~$ No errors. elhoir@elhoir-desktop:~$ lsmod Module Size Used by amdgpu 3567616 2 chash 16384 1 amdgpu amd_iommu_v2 20480 1 amdgpu gpu_sched 32768 1 amdgpu ttm 102400 1 amdgpu drm_kms_helper180224 1 amdgpu drm 475136 6 gpu_sched,drm_kms_helper,amdgpu,ttm i2c_algo_bit 16384 1 amdgpu fb_sys_fops16384 1 drm_kms_helper syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper pci_stub 16384 1 vboxpci24576 0 vboxnetadp 28672 0 vboxnetflt 28672 0 vboxdrv 450560 3 vboxpci,vboxnetadp,vboxnetflt r8188eu 434176 0 lib80211 16384 1 r8188eu cfg80211 679936 1 r8188eu joydev 24576 0 snd_hda_codec_hdmi 53248 1 snd_hda_intel 45056 2 snd_hda_codec 126976 2 snd_hda_codec_hdmi,snd_hda_intel snd_ctxfi 114688 2 snd_hda_core 81920 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec snd_hwdep 20480 1 snd_hda_codec snd_pcm 102400 5 snd_ctxfi,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core snd_seq_midi 20480 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_rawmidi36864 1 snd_seq_midi snd_seq69632 2 snd_seq_midi,snd_seq_midi_event snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi snd_timer 36864 2 snd_seq,snd_pcm snd81920 18 snd_ctxfi,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_timer,snd_pcm,snd_rawmidi soundcore 16384 1 snd input_leds 16384 0 mac_hid16384 0 serio_raw 20480 0 intel_powerclamp 20480 0 intel_cstate 20480 0 kvm_intel 245760 0 kvm 634880 1 kvm_intel irqbypass 16384 1 kvm ip6t_REJECT16384 3 nf_reject_ipv6 20480 1 ip6t_REJECT nf_log_ipv616384 5 xt_hl 16384 22 ip6t_rt20480 3 binfmt_misc24576 1 sch_fq_codel 20480 5 ipt_REJECT 16384 3 nf_reject_ipv4 16384 1 ipt_REJECT nf_log_ipv416384 5 nf_log_common 16384 2 nf_log_ipv4,nf_log_ipv6 xt_LOG 20480 10 xt_limit 16384 13 xt_tcpudp 20480 29 xt_addrtype16384 4 xt_conntrack 16384 16 ip6table_filter16384 1 ip6_tables 32768 53 ip6table_filter nf_conntrack_netbios_ns16384 0 nf_conntrack_broadcast16384 1 nf_conntrack_netbios_ns nf_nat_ftp 20480 0 nf_nat 36864 1 nf_nat_ftp nf_conntrack_ftp 24576 1 nf_nat_ftp nf_conntrack 135168 6 xt_conntrack,nf_nat,nf_nat_ftp,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ftp nf_defrag_ipv6 24576 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack libcrc32c 16384 2 nf_conntrack,nf_nat f71882fg 40960 0 coretemp 20480 0 iptable_filter 16384 1 bpfilter 32768 0 parport_pc 40960 0 ppdev 24576 0 lp 20480 0 parport53248 3 parport_pc,lp,ppdev ip_tables 28672 9 iptable_filter x_tables 40960 13 ip6table_filter,xt_conntrack,iptable_filter,xt_LOG,xt_tcpudp,xt_addrtype,ip6t_rt,ip6_tables,ipt_REJECT,ip_tables,xt_limit,xt_hl,ip6t_REJECT autofs445056 2 hid_generic16384 0 usbhid 53248 0 hid 135168 2 usbhid,hid_generic gpio_ich 16384 0 ahci 40960 1 libahci32768 1 ahci lpc_ich24576 0 elhoir@elhoir-desktop:~$ -- 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/1818580 Title: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Status in linux package in Ubuntu: Incomplete Bug description: I cannot boot PC normally, i must use recovery mode. WORKAROUND: Use kernel parameter: nomodeset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0 Uname: Linux 5.0.0-7-lowlatency x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CompizPlugins: No value set for
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
Looks like it's 4 hours per build, so I'll give it a shot in the morning. Thanks for your help with the bisect - after v5.0-rc1 mainline failed to boot, I was worried about doing the bisect via 5.0 release candidate mainline builds -- 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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
I'm using this same version of ubuntu. Before crash I've opened new terminal window Ctrl + Alt + F1 and then I 'saw NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [plymouthd:305]'. In my case this do the trick: https://askubuntu.com/questions/875173/nmi-watchdog-bug-soft-lockup-cpu2-stuck-for-23s-plymouthd305 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux source package in Disco: Triaged Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
On Wed, Mar 6, 2019 at 1:10 PM directhex wrote: > > dmesg - the only difference from a "good" boot is the absence of "hns- > nic HISI00C2:02 enahisic2i2: link up" OK, thanks. Unfortunately, there's no smoking gun there, so I've started a bisect and uploaded another test kernel to https://launchpad.net/~dannf/+archive/ubuntu/xr320/+packages. Can you give that a try once it finishes building? -dann -- 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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1804533] Re: xen hibernation support for linux-aws (bionic+)
** Changed in: linux-aws (Ubuntu Cosmic) Status: In Progress => Fix Committed -- 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/1804533 Title: xen hibernation support for linux-aws (bionic+) Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Bionic: Fix Released Status in linux-aws source package in Cosmic: Fix Committed Status in linux-aws source package in Disco: In Progress Status in linux-aws source package in EE-Series: New Status in linux-aws source package in FF-Series: New Bug description: AWS-specific xen hibernation support (as is already supported in linux-aws Xenial and Trusty) has been ported to linux-aws Bionic by the Amazon team. Patches to be applied to linux-aws-bionic: UBUNTU: SAUCE [aws] x86/xen: Introduce new function to map HYPERVISOR_shared_info on UBUNTU: SAUCE [aws] x86/xen: add system core suspend and resume callbacks UBUNTU: SAUCE [aws] xen-netfront: add callbacks for PM suspend and hibernation support UBUNTU: SAUCE [aws] xen-time-introduce-xen_-save-restore-_steal_clock UBUNTU: SAUCE [aws] x86/xen: save and restore steal clock UBUNTU: SAUCE [aws] xen/events: add xen_shutdown_pirqs helper function UBUNTU: SAUCE [aws] x86/xen: close event channels for PIRQs in system core suspend UBUNTU: SAUCE [aws] PM / hibernate: update the resume offset on SNAPSHOT_SET_SWAP_AREA This patch set passes simple hibernation smoke-testing on an instance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1804533/+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 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
dmesg - the only difference from a "good" boot is the absence of "hns- nic HISI00C2:02 enahisic2i2: link up" ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+attachment/5244169/+files/dmesg.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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
Nope, never mind, the docs on the Ubuntu wiki are wrong and it's now impossible to attach an apport report offline (apport-collect is now mandatory for existing bugs, and does not allow passing an apport file as a parameter) I'll get & attach 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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore
@cascardo, the issue was reported in Xenial, now that the fix is released in Disco does it make it a good candidate for a backport to Xenial and Bionic? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1655280 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in makedumpfile source package in Xenial: New Status in linux source package in Bionic: Invalid Status in makedumpfile source package in Bionic: New Status in linux source package in Cosmic: Invalid Status in makedumpfile source package in Cosmic: In Progress Status in linux source package in Disco: Invalid Status in makedumpfile source package in Disco: Fix Released Bug description: == Comment: #0 - Ping Tian Han - 2017-01-09 02:51:00 == ---Problem Description--- Vmcore cannot be saved when triggering bug 150353 on roselp4: Copying data : [ 2.0 %] \/usr/sbin/kdump-config: line 591: 5502 Bus error makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [ 512.833872] kdump-tools[5450]: * kdump-tools: makedumpfile failed, falling back to 'cp' [ 573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad address [ 573.605717] kdump-tools[5450]: * kdump-tools: failed to save vmcore in /var/crash/201701090223 [ 573.765417] kdump-tools[5450]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/201701090223/dmesg.201701090223 [ 574.285506] kdump-tools[5450]: The kernel version is not supported. [ 574.285672] kdump-tools[5450]: The makedumpfile operation may be incomplete. [ 574.285767] kdump-tools[5450]: The dmesg log is saved to /var/crash/201701090223/dmesg.201701090223. [ 574.305422] kdump-tools[5450]: makedumpfile Completed. [ 574.315363] kdump-tools[5450]: * kdump-tools: saved dmesg content in /var/crash/201701090223 [ 574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600 [ 574.705384] kdump-tools[5450]: Rebooting. Stopping ifup for ib0... [ OK ] Stopped ifup for ib0. [ 1008.579897] reboot: Restarting system Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com ---uname output--- Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = lpar ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. config kdump on roselp4 2. try to trigger bug 150353 *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie Mitsuyoshi/carri...@us.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. == Comment: #3 - Brahadambal Srinivasan - 2017-01-10 02:42:25 == root@roselp4:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet crashkernel=384M-:512M root@roselp4:~# dmesg | grep Reser [0.00] Reserving 512MB of memory at 128MB for crashkernel (System RAM: 21760MB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+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 1719545] Re: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats
pavsu...@in.ibm.com, thanks for posting your test results to the bug. Your report is missing any confirmation that the bug is in fact fixed by the test kernel. Could you please provide some additional comments here stating if this kernel fixes the issue for you or not ? -- 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/1719545 Title: [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats Status in The Ubuntu-power-systems project: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: == Comment: #0 - PAVAMAN SUBRAMANIYAM - 2017-06-29 02:30:22 == ---Problem Description--- cpupower monitor shows multiple stop Idle_Stats ---uname output--- Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = P9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P9 8375-42A Hardware with Ubuntu 16.04.3 OS. Then execute the cpupower monitor command to fetch all the Idle_Stats values. root@zz376p1:~# cpupower monitor |Idle_Stats PKG |CORE|CPU | snoo | stop | stop 0| 8| 0| 0.00| 0.00| 2.79 0| 8| 1| 0.00| 0.00| 70.68 0| 8| 2| 0.00| 0.00| 99.87 0| 8| 3| 0.00| 0.00| 67.28 0| 12| 4| 0.00| 0.00| 5.17 0| 12| 5| 0.00| 0.00| 12.50 0| 12| 6| 0.00| 0.00| 99.74 0| 12| 7| 0.00| 0.00| 0.00 8|2048| 8| 0.00| 0.00| 22.14 8|2048| 9| 0.00| 0.00| 102.3 8|2048| 10| 0.00| 0.00| 0.00 8|2048| 11| 0.00| 0.00| 99.97 8|2052| 12| 0.00| 0.00| 99.70 8|2052| 13| 0.00| 0.00| 23.86 8|2052| 14| 0.00| 0.00| 113.1 8|2052| 15| 0.00| 0.00| 0.00 As can be seen it shows 2 columns for stop. root@zz376p1:~# uname -a Linux zz376p1 4.10.0-26-generic #30~16.04.1-Ubuntu SMP Tue Jun 27 09:38:48 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@zz376p1:~# cat /etc/os-release NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial root@zz376p1:~# cat /proc/cpuinfo | tail processor : 15 cpu : POWER9 (raw), altivec supported clock : 2600.00MHz revision: 1.0 (pvr 004e 0100) timebase: 51200 platform: PowerNV model : 8375-42A machine : PowerNV 8375-42A firmware: OPAL Userspace tool common name: /usr/bin/cpupower The userspace tool has the following bit modes: 64-bit Userspace rpm: linux-tools-common Userspace tool obtained from project website: na *Additional Instructions for pavsu...@in.ibm.com: -Post a private note with access information to the machine that the bug is occuring on. -Attach ltrace and strace of userspace application. . There are 3 idle_stats (3 states) in this system. root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s snoo [T] -> snooze stop [T] -> stop0_lite stop [T] -> stop1_lite root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 3 Available idle states: snooze stop0_lite stop1_lite snooze: Flags/Description: snooze Latency: 0 Usage: 224 Duration: 423 stop0_lite: Flags/Description: stop0_lite Latency: 0 Usage: 1685 Duration: 530522 stop1_lite: Flags/Description: stop1_lite Latency: 4 Usage: 12693 Duration: 5405898106 root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower monitor -l Monitor "Idle_Stats" (3 states) - Might overflow after 4294967295 s snoo [T] -> snooze stop [T] -> stop0_lite stop [T] -> stop1_lite root@zz376p1:/sys/devices/system/cpu/cpu0/cpuidle/state2# cpupower idle-info CPUidle driver: powernv_idle CPUidle governor: menu analyzing CPU 0: Number of idle states: 3 Available idle states: snooze stop0_lite stop1_lite snooze: Flags/Description: snooze Latency: 0 Usage: 272 Duration: 905 stop0_lite: Flags/Description: stop0_lite Latency: 0 Usage: 2141 Duration: 536399 stop1_lite: Flags/Description: stop1_lite Latency: 4 Usage: 15396 Duration: 6625668881 cpu monitor will print the results of all the 3 available idle_stats . The first stop -> stop0_lite stats and The second stop -> stop1_lite stats. cpupower monitor header prints the header list by
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
Aha, cracked it - had to copy the source_linux.py hook to source_linux- hwe.py. Will attach apport from "bad" 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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
On Wed, Mar 6, 2019 at 11:25 AM directhex wrote: > > I can't actually use `apport-collect` without an internet connection, of > course, so can't use it when booted to a "bad" kernel Could you save 'dmesg' output of the bad kernel to a file and upload that once you reboot to working networking? -- 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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
OK, I have functioning networking with 4.15.0-45.48+xr320.1 -- 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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818881] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244117/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244116/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244115/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244106/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244110/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244109/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244111/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244105/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i*
[Kernel-packages] [Bug 1818881] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244107/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244113/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244112/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i*
[Kernel-packages] [Bug 1818881] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244114/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] Re: ath10k_pci crashing
apport information ** Tags added: apport-collected bionic ** Description changed: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias: pci:v168Cd0040sv*sd*bc*sc*i* alias: pci:v168Cd003Esv*sd*bc*sc*i* alias: pci:v168Cd0041sv*sd*bc*sc*i* alias: pci:v168Cd003Csv*sd*bc*sc*i* alias: pci:v0777d11ACsv*sd*bc*sc*i* depends:ath10k_core retpoline: Y
[Kernel-packages] [Bug 1818881] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244108/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818881] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1818881/+attachment/5244104/+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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias:
[Kernel-packages] [Bug 1818294] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1818294/+attachment/5244093/+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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1818294/+attachment/5244099/+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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1818294/+attachment/5244097/+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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1818294/+attachment/5244101/+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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1818294/+attachment/5244100/+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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1818294/+attachment/5244098/+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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1818294/+attachment/5244094/+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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
(I'd love to know how to convince apport-bug to collect A these logs when offline, it seems to only grab the package list when I try it) -- 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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1818294/+attachment/5244095/+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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1818294/+attachment/5244096/+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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
apport information ** Tags added: apport-collected xenial ** Description changed: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf + --- + AlsaDevices: + total 0 + crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq + crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f + IwConfig: Error: [Errno 2] No such file or directory + MachineType: Huawei XR320 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=linux + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 hibmcdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro + ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.157.21 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial xenial xenial xenial + Uname: Linux 4.15.0-43-generic aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 08/07/2018 + dmi.bios.vendor: Huawei + dmi.bios.version: 1.54 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: BC81HPNA + dmi.board.vendor: Huawei + dmi.board.version: VER.A + dmi.chassis.asset.tag: To be filled by O.E.M. + dmi.chassis.type: 17 + dmi.chassis.vendor: Huawei + dmi.chassis.version: To be filled by O.E.M. + dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: XR320 + dmi.product.version: V100R001C00 + dmi.sys.vendor: Huawei ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1818294/+attachment/5244092/+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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45
I can't actually use `apport-collect` without an internet connection, of course, so can't use it when booted to a "bad" kernel And `apport-bug linux` seems to only collect a fraction of the requisite logs. I'll attach a "good" boot, at least, then try your PPA 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/1818294 Title: HiSilicon HNS ethernet broken in 4.15.0-45 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Status in linux source package in Disco: Incomplete Bug description: A number of HiSilicon patches were backported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from 5.0rc1. Subsequently, I lost networking on my Huawei TaiShan XR320 boards. There are 6 commits to drivers/net/ethernet/hisilicon/hns between 5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with a 5.0rc8 mainline build. Can we do another update run for the next 4.15.0 kernel service release, to include HiSilicon changes from 5.0rc8? CC @dannf --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Mar 6 10:17 seq crw-rw+ 1 root audio 116, 33 Mar 6 10:17 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f IwConfig: Error: [Errno 2] No such file or directory MachineType: Huawei XR320 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory Tags: xenial xenial xenial xenial Uname: Linux 4.15.0-43-generic aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 08/07/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.54 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC81HPNA dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Huawei dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: XR320 dmi.product.version: V100R001C00 dmi.sys.vendor: Huawei To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818294/+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 1806392] Re: tun/tap: unable to manage carrier state from userland
** Description changed:
- This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
- change").
+ === SRU Justification ===
+ [Impact]
+ Userspace cannot change tun's carrier state.
+
+ [Fix]
+ Add .ndo_change_carrier callback for tun.
+
+ [Test]
+ User confirm the backport works.
+
+ [Regression Potential]
+ Low. It add a new function and a new case switch for ioctl, but the new
+ code doesn't affect existing behavior.
+ === Original Bug Report ===
+ This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
change").
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=26d31925cd5e
--
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/1806392
Title:
tun/tap: unable to manage carrier state from userland
Status in linux package in Ubuntu:
Triaged
Bug description:
=== SRU Justification ===
[Impact]
Userspace cannot change tun's carrier state.
[Fix]
Add .ndo_change_carrier callback for tun.
[Test]
User confirm the backport works.
[Regression Potential]
Low. It add a new function and a new case switch for ioctl, but the new
code doesn't affect existing behavior.
=== Original Bug Report ===
This upstream patch is missing: 26d31925cd5e ("tun: implement carrier
change").
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
next.git/commit/?id=26d31925cd5e
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806392/+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 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
I've just tried official 4.19.0, and no issue there. So I'm not sure what's going on. -- 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/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 Status in linux package in Ubuntu: Confirmed Bug description: Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+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 1818881] 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 1818881 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: 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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Incomplete Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware:
Re: [Kernel-packages] [Bug 1818253] Missing required logs.
Sorry about that. On Wed, Mar 6, 2019 at 1:41 AM Ubuntu Kernel Bot < kernel-team-...@canonical.com> wrote: > 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 1818253 > > 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 subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1818253 > > Title: > 18.10 when lid closed and opened again no keyboard > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818253/+subscriptions > -- Carlos Silva Alzheimer/Dementia Support Center Board of Directors, IT Administrator 700 McHenry Ave Ste. B Modesto CA, 95350 Center (209) 577-0018 Text?Call (209) 215-5868 www.adsc-modesto.org ** Attachment added: "log messages" https://bugs.launchpad.net/bugs/1818253/+attachment/5244081/+files/log%20messages -- 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/1818253 Title: 18.10 when lid closed and opened again no keyboard Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Using Dell Inspiron 7000 w/Intel corei7. With 18.04 power settings had options for what to do when lid was closed. Now available with Gnome-tweak in 18.10. However does not work correctly. Did Google search happening to others as well especially with detach keyboards which is not my case. With 18.10 and tweak setting to suspend when lid closed, the system does suspend, however when lid is closed it appears that the on board keyboard gets totally dropped when lid is opened back up. Have to use touch screen to switch user, then touch screen again at login to get a screen keyboard, sometimes I get the on board keyboard back, usually have to reboot to get on on board keyboard back. If I power off or restart keyboard works fine. Definite regression this has worked for several older versions of Ubuntu, at least on this system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818253/+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 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
As a note, the issue shows up in the first build attempt which was "linux-image-4.19.0+_4.19.0+-1_amd64.deb". This seems like before the 4.19.27 I did not see the issue in. -- 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/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 Status in linux package in Ubuntu: Confirmed Bug description: Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+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 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
It happens in 4.20-rc1, so should I try to bisect between 4.19 and 4.20-rc1? I gave that a shot, but after labeling the first try "bad", the next make gave me: ... dpkg-source: warning: no source format specified in debian/source/format, see dpkg-source(1) dpkg-source: info: using source format '1.0' dpkg-source: warning: source directory 'linux' is not - 'linux-4.19.0-rc8+-4.19.0-rc8+' dpkg-source: warning: .orig directory name linux.orig is not - (wanted linux-4.19.0-rc8+-4.19.0-rc8+.orig) dpkg-source: info: building linux-4.19.0-rc8+ using existing linux-4.19.0-rc8+_4.19.0-rc8+.orig.tar.gz dpkg-source: info: building linux-4.19.0-rc8+ in linux-4.19.0-rc8+_4.19.0-rc8+-1.diff.gz dpkg-source: error: cannot represent change to vmlinux-gdb.py: dpkg-source: error: new version is symlink to /opt/kernel/linux/scripts/gdb/vmlinux-gdb.py dpkg-source: error: old version is nonexistent dpkg-source: warning: ignoring deletion of file .scmversion, use --include-removal to override dpkg-source: warning: the diff modifies the following upstream files: ... dpkg-source: info: use the '3.0 (quilt)' format to have separate and documented changes to upstream files, see dpkg-source(1) dpkg-source: error: unrepresentable changes to source dpkg-buildpackage: error: dpkg-source -i.git -b linux subprocess returned exit status 1 scripts/package/Makefile:71: recipe for target 'deb-pkg' failed make[1]: *** [deb-pkg] Error 1 Makefile:1357: recipe for target 'deb-pkg' failed make: *** [deb-pkg] Error 2 So I'm not sure where to go from here. -- 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/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 Status in linux package in Ubuntu: Confirmed Bug description: Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+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 1811815] Re: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked
I have the ideapad S130 and had the same issue, but I noticed that the kill switch from `ideapad_laptop` is toggled using the "flight mode"-key (Fn-F7) and I'm unsure, if I should create a patch like the one you submitted above. >From pictures, the keyboard on the ideapad 330 looks identical to the one on the S130. Have you tried if that button actually acts as the "hardware killswitch" for you? Are we actually removing a useful feature by adding the laptops with that key to the blacklist in the kernel module? -- 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/1811815 Title: Lenovo ideapad 330-15ICH Wifi rfkill hard blocked Status in linux package in Ubuntu: Confirmed Bug description: The issue here is that the drivers/platform/x86/ideapad_laptop.c module assumes the Lenovo Ideapad 330-15ICH has a hardware RF-kill switch, reads the I/O port for its state, gets a zero, and therefore reports to the kernel that RFkill is hard-blocked. The current workaround is to blacklist the module to stop it being loaded. I've attached a simple patch for the module that teaches it that this model does not have a hardware RF kill switch. Original Report - Ubuntu 18.10 does not detect the Intel Dual Band Wireless-AC 3165 card, specifically on a Lenovo ideapad 330 laptop. A current workaround: - Blacklist the "ideapad-laptop" module. - Edit/create a file in "/etc/modprobe.d/" and name it "blacklist.conf" or something similar (if it does not already exist), and append "blacklist ideapad-laptop" to the file. Save and reboot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dustin 1948 F pulseaudio /dev/snd/pcmC0D0p: dustin 1948 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 04:08:20 2019 InstallationDate: Installed on 2019-01-15 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210e Acer, Inc Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 3938:1047 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81FK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=fa5d161c-779c-4cf7-aa07-6da06d655747 ro acpi_osi=! "acpi_osi=Windows 2012" quiet splash nouveau.modeset=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7ZCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15ICH dmi.modalias: dmi:bvnLENOVO:bvr7ZCN28WW:bd07/17/2018:svnLENOVO:pn81FK:pvrLenovoideapad330-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15ICH: dmi.product.family: ideapad 330-15ICH dmi.product.name: 81FK dmi.product.sku: LENOVO_MT_81FK_BU_idea_FM_ideapad 330-15ICH dmi.product.version: Lenovo ideapad 330-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811815/+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 1818881] Re: ath10k_pci crashing
** Project changed: launchpad => 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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: New Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias: pci:v168Cd0040sv*sd*bc*sc*i* alias: pci:v168Cd003Esv*sd*bc*sc*i*
[Kernel-packages] [Bug 1818407] Re: Cant access emmc, error -84
Same result... patakija@patakija-TP202NAS:~$ uname -r 4.9.162-0409162-generic patakija@patakija-TP202NAS:~$ dmesg | grep mmc [2.625220] mmc0: SDHCI controller on PCI [:00:1c.0] using ADMA 64-bit [2.845380] mmc0: switch to hs400 failed, err:-84 [2.845395] mmc0: error -84 whilst initialising MMC card [3.075182] mmc0: mmc_select_hs400 failed, error -84 [3.075188] mmc0: error -84 whilst initialising MMC card [3.292230] mmc0: mmc_select_hs400 failed, error -84 [3.292236] mmc0: error -84 whilst initialising MMC card [3.535283] mmc0: mmc_select_hs400 failed, error -84 [3.535289] mmc0: error -84 whilst initialising MMC card patakija@patakija-TP202NAS:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:01 119,1G 0 disk ├─sda1 8:11 1G 0 part /boot/efi ├─sda2 8:21 114,1G 0 part / └─sda3 8:31 4G 0 part [SWAP] patakija@patakija-TP202NAS:~$ -- 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/1818407 Title: Cant access emmc, error -84 Status in linux package in Ubuntu: Confirmed Bug description: Greetings! I just got my new convertible(Asus TP202NAS, brand new) and wanted to install kubuntu 18.10 onto the internal storage, only to find that it cant see it. In dmesg i only got these two error: mc0: mmc_select_hs400 failed, error -84 mc0: error -84 whilst initializing mmc card Tried to google around for a solution but i didnt found any solution to this, also tried the kubuntu IRC channel but didnt got any luck there too /EDIT Submitted from a live session. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-release-upgrader-core 1:18.10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CasperVersion: 1.399 CrashDB: ubuntu Date: Sun Mar 3 13:59:13 2019 LiveMediaBuild: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu3661 F pulseaudio CasperVersion: 1.394 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 LiveMediaBuild: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 003: ID 0781:5581 SanDisk Corp. Ultra Bus 002 Device 002: ID 05e3:0747 Genesys Logic, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:3501 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. TP202NAS Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP202NAS.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP202NAS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP202NAS.209:bd07/19/2018:svnASUSTeKCOMPUTERINC.:pnTP202NAS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP202NAS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: TP202NAS dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+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 1818881] [NEW] ath10k_pci crashing
You have been subscribed to a public bug: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias: pci:v168Cd0050sv*sd*bc*sc*i* alias: pci:v168Cd0042sv*sd*bc*sc*i* alias: pci:v168Cd0046sv*sd*bc*sc*i* alias: pci:v168Cd0056sv*sd*bc*sc*i* alias: pci:v168Cd0040sv*sd*bc*sc*i* alias: pci:v168Cd003Esv*sd*bc*sc*i* alias: pci:v168Cd0041sv*sd*bc*sc*i* alias: pci:v168Cd003Csv*sd*bc*sc*i* alias: pci:v0777d11ACsv*sd*bc*sc*i* depends:ath10k_core retpoline: Y intree: Y name: ath10k_pci vermagic: 4.18.0-15-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: irq_mode:0: auto, 1: legacy, 2:
[Kernel-packages] [Bug 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1809856 Title: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start hearing a static/electric (some internal?) sound if the volume isn't muted. Something similar occurs with my other earbuds with mic, just much quieter and less noticable. It works fine on Windows 10 running on the same machine, and on my Android phone. I don't notice is when something is playing, but the frequency of the sound changes when I play something, then pause it, the background noise will sound slightly different. This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with alsamixer and pavucontrol settings, and nothing fixed this background noise. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: davidkoplik 1891 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 26 20:17:59 2018 InstallationDate: Installed on 2018-12-26 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1818879] Re: pull cirrus.ko into main kernel package
Another alternative would be to have vesa specify a working bpp value, if that is the only problem there. ** Also affects: xorg (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/1818879 Title: pull cirrus.ko into main kernel package Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: In disco, xorg stopped shipping a cirrus module/driver, instead relying on the kernel one. But the kernel one is in the linux-modules- extra--generic package, which is not installed by default in vms. That breaks some assumptions: uvtool, for example, doesn't specify a video device when creating a vm, and the default in libvirt in such cases is to use cirrus. As a conseguence, disco VMs created by tools that do not specify a default video device won't have the cirrus.ko module, and X won't start there. It's a bit more complicated, however, because X just tries other fallbacks, but they also don't work. In particular, vesa doesn't work: [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted value (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/) We can change uvtool and specify a video device instead of leaving it blank (see bug #1818877), but there might be other tools out there spawning guests without telling them which video device to use, and they would also fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818879/+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 1818879] Re: pull cirrus.ko into main kernel package
Adding a test for xorg for their consideration. -- 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/1818879 Title: pull cirrus.ko into main kernel package Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: In disco, xorg stopped shipping a cirrus module/driver, instead relying on the kernel one. But the kernel one is in the linux-modules- extra--generic package, which is not installed by default in vms. That breaks some assumptions: uvtool, for example, doesn't specify a video device when creating a vm, and the default in libvirt in such cases is to use cirrus. As a conseguence, disco VMs created by tools that do not specify a default video device won't have the cirrus.ko module, and X won't start there. It's a bit more complicated, however, because X just tries other fallbacks, but they also don't work. In particular, vesa doesn't work: [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted value (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/) We can change uvtool and specify a video device instead of leaving it blank (see bug #1818877), but there might be other tools out there spawning guests without telling them which video device to use, and they would also fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818879/+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 1818879] 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 1818879 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/1818879 Title: pull cirrus.ko into main kernel package Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: In disco, xorg stopped shipping a cirrus module/driver, instead relying on the kernel one. But the kernel one is in the linux-modules- extra--generic package, which is not installed by default in vms. That breaks some assumptions: uvtool, for example, doesn't specify a video device when creating a vm, and the default in libvirt in such cases is to use cirrus. As a conseguence, disco VMs created by tools that do not specify a default video device won't have the cirrus.ko module, and X won't start there. It's a bit more complicated, however, because X just tries other fallbacks, but they also don't work. In particular, vesa doesn't work: [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted value (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/) We can change uvtool and specify a video device instead of leaving it blank (see bug #1818877), but there might be other tools out there spawning guests without telling them which video device to use, and they would also fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818879/+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 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
It happens in 4.20-rc1, so should I try to bisect between 4.19 and 4.20-rc1? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 Status in linux package in Ubuntu: Confirmed Bug description: Dmesg is a constant barrage of the same error: ``` [ 406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called with n (192) > 32! (kworker/5:1) ``` This does not occur in 4.19 but does occur in all mainline 4.20 releases including 4.20.13 (linux-image-unsigned-4.20.13-042013). Tested with both Ubuntu's included libinput 1.10 and an updated libinput 1.12. Hardware (from lspci) includes a synaptic touchpad. Having the xorg synaptic driver installed makes no difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+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
