axet, thank you for reporting this and helping make Ubuntu better. In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest mainline kernel? Please keep in mind the following: 1) The one to test is in a folder at the very top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .
If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the mainline kernel, please comment on which kernel version specifically you tested. If this issue is not reproducible in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the Bug Description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the issue is reproducible with the mainline kernel, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Also, you don't need to apport-collect further unless specifically requested to do so. In addition, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available. Lastly, it is most helpful that after testing of the latest mainline kernel is complete, you mark this report Status Confirmed. Thank you for your help. ** Tags added: latest-bios-0207 ** Description changed: - Hello! I have connection issues with my old notebook running ubuntu - 18.04 LTS. This is long story and I add referencies below. In short. I - got a lot of "ipw2100: Fatal interrupt. Scheduling firmware restart" - following by "ipw2100: wlp1s4: Failed to start the firmware" which force - me to reboot the machine. + I have connection issues with my ASUS M3N Notebook ( https://www.asus.com/supportonly/M3N/HelpDesk_BIOS/ ) running ubuntu 18.04 LTS. As per dmesg: + ipw2100: Fatal interrupt. Scheduling firmware restart + + following by: + ipw2100: wlp1s4: Failed to start the firmware + + Reported upstream at: + https://bugzilla.kernel.org/show_bug.cgi?id=203915 + + WORKAROUND: Reboot the machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic i686 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC0: axet 1613 F.... pulseaudio - /dev/snd/pcmC1D0p: axet 1613 F...m pulseaudio - /dev/snd/controlC1: axet 1613 F.... pulseaudio + USER PID ACCESS COMMAND + /dev/snd/controlC0: axet 1613 F.... pulseaudio + /dev/snd/pcmC1D0p: axet 1613 F...m pulseaudio + /dev/snd/controlC1: axet 1613 F.... pulseaudio CurrentDesktop: GNOME-Flashback:GNOME Date: Sun Jul 14 16:46:10 2019 HibernationDevice: RESUME=UUID=5431e7a1-fb6f-4411-ac30-21f6ecd48ac4 InstallationDate: Installed on 2017-02-06 (888 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) MachineType: ASUSTeK Computer Inc. M3N PccardctlStatus: - Socket 0: - 5.0V - 16-bit - PC Card - Subdevice 0 (function 0) bound to driver "serial_cs" + Socket 0: + 5.0V + 16-bit + PC Card + Subdevice 0 (function 0) bound to driver "serial_cs" ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=8a9a2822-70c7-45c0-a01b-379c952d190d ro forcepae mem=2000M priority=low log_buf_len=1M RelatedPackageVersions: - linux-restricted-modules-4.15.0-54-generic N/A - linux-backports-modules-4.15.0-54-generic N/A - linux-firmware 1.173.8 + linux-restricted-modules-4.15.0-54-generic N/A + linux-backports-modules-4.15.0-54-generic N/A + linux-firmware 1.173.8 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: linux StagingDrivers: nsc_ircc irda UpgradeStatus: Upgraded to bionic on 2019-04-19 (86 days ago) dmi.bios.date: 03/16/2004 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0207 dmi.board.name: M3N dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0207:bd03/16/2004:svnASUSTeKComputerInc.:pnM3N:pvr1.0:rvnASUSTeKComputerInc.:rnM3N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M3N dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836483 Title: ipw2100: wlp1s4: Failed to start the firmware Status in linux package in Ubuntu: Incomplete Bug description: I have connection issues with my ASUS M3N Notebook ( https://www.asus.com/supportonly/M3N/HelpDesk_BIOS/ ) running ubuntu 18.04 LTS. As per dmesg: ipw2100: Fatal interrupt. Scheduling firmware restart following by: ipw2100: wlp1s4: Failed to start the firmware Reported upstream at: https://bugzilla.kernel.org/show_bug.cgi?id=203915 WORKAROUND: Reboot the machine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic i686 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: axet 1613 F.... pulseaudio /dev/snd/pcmC1D0p: axet 1613 F...m pulseaudio /dev/snd/controlC1: axet 1613 F.... pulseaudio CurrentDesktop: GNOME-Flashback:GNOME Date: Sun Jul 14 16:46:10 2019 HibernationDevice: RESUME=UUID=5431e7a1-fb6f-4411-ac30-21f6ecd48ac4 InstallationDate: Installed on 2017-02-06 (888 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) MachineType: ASUSTeK Computer Inc. M3N PccardctlStatus: Socket 0: 5.0V 16-bit PC Card Subdevice 0 (function 0) bound to driver "serial_cs" ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=8a9a2822-70c7-45c0-a01b-379c952d190d ro forcepae mem=2000M priority=low log_buf_len=1M RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.8 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: nsc_ircc irda UpgradeStatus: Upgraded to bionic on 2019-04-19 (86 days ago) dmi.bios.date: 03/16/2004 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0207 dmi.board.name: M3N dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0207:bd03/16/2004:svnASUSTeKComputerInc.:pnM3N:pvr1.0:rvnASUSTeKComputerInc.:rnM3N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M3N 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/1836483/+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