[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#991626: marked as done (firmware-misc-nonfree: Upgrade from 20210315-2 to 20210315-3 crashes system)

Your message dated Fri, 30 Jul 2021 20:05:13 +0200
with message-id <9226b31667044a3492b8650b944fcdcce9ad3784.camel@decadent.org.uk>
and subject line Re: Bug#991626: firmware-misc-nonfree: Upgrade from 20210315-2 to 20210315-3 crashes system
has caused the Debian Bug report #991626,
regarding firmware-misc-nonfree: Upgrade from 20210315-2 to 20210315-3 crashes system
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
991626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991626
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: firmware-misc-nonfree
Version: 20210315-3
Severity: normal

Dear Maintainer,

This is a low-quality error report. First, it is likely that I can't repeat this problem because it occurred during upgrade of the package ; package is now upgraded.. Haven't tried forcibly installing older version and then upgrading again to see if problem persists. Secondly, I'm not 100% sure this is the package to blame. Thirdly, I don't have proper log files because after the incident my filesystem was in read-only mode so I don't really have proper trace about events leading to situation described below. 

Steps for producing the problem:
0) Have debian testing in lenovo e15 gen2 with intel cpu
1) apt-get update ; apt-get -f dist-upgrade

What happens: dist-upgrade got stuck when it was extracting files from  package  firmware-misc-nonfree or setting it up - can't remember which. Filesystem went to ro-mode so nothing really worked so I had to power-cycle the computer so everything I had in progress was lost. After the power-cycle system booted up ok, I did "dpkg --configure -a" and "apt-get -f install" and at that point it reconfigured package firmware-misc-nonfree:amd64 (20210315-2, 20210315-3) and everything has been fine since that. For unexperienced user it still might be confusing to have apt-get stuck and having to have forcibly reboot the system to continue working.

History.log of apt looks really bad, namely like this:
@^@^@^@^@^@^@^@^@^@^@
Start-Date: 2021-07-28  11:59:51
Commandline: apt-get -f install
Upgrade: firmware-misc-nonfree:amd64 (20210315-2, 20210315-3)
End-Date: 2021-07-28  12:00:04

and log file contains some kilobytes of ascii 0 (^@) and then this
Commandline: apt-get -f install
that is after the reboot, from situation where I triggered apt-get -f install
manually. 

Kern.log has one entry that points into microcode direction, it says
Jul 28 11:58:43 pikkufisu kernel: [    0.000000] microcode: microcode updated e\
arly to revision 0x88, date = 2021-03-31
just before actual "boot" message:
Jul 28 11:58:43 pikkufisu kernel: [    0.000000] Linux version 5.10.0-8-amd64 (\
debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU \
ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-2 (2021-07-20)
that has been logged after the reboot.

Before microcode upgrade there are things in kern.log regarding wlan:
Jul 28 11:25:54 pikkufisu kernel: [593181.653751] wlp0s20f3: send auth to 54:a0\
:50:72:f0:00 (try 1/3)
Jul 28 11:25:55 pikkufisu kernel: [593181.776572] wlp0s20f3: authenticated
Jul 28 11:25:55 pikkufisu kernel: [593181.782350] wlp0s20f3: associate with 54:\
a0:50:72:f0:00 (try 1/3)
Jul 28 11:25:55 pikkufisu kernel: [593181.786709] wlp0s20f3: RX AssocResp from \
54:a0:50:72:f0:00 (capab=0x431 status=0 aid=5)
Jul 28 11:25:55 pikkufisu kernel: [593181.791057] wlp0s20f3: associated
Jul 28 11:25:55 pikkufisu kernel: [593182.017261] IPv6: ADDRCONF(NETDEV_CHANGE)\
: wlp0s20f3: link becomes ready

Those are 3 minutes before I had to reboot the system so this problem just might have something to do with
00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)
being reconfigured? If I remember correctly, this Wi-Fi card was the actual reason why I had to install firmware-misc-nonfree in the first place.

There is slightly similar occurrence described in
https://bbs.archlinux.org/viewtopic.php?id=263040&p=5
but there sympton is not a hanging system or that's how I understand.

I'm insert below exerpt from /var/log/syslog but I'm not absolutely sure if it is from period before or after the reset button. Reason for reset button was that root-fs was mounted ro so I kind of doupt that there would be any log entries from time before the boot. 

--
Antti

Here the log excerpt goes:
Jul 28 11:25:47 pikkufisu kernel: [557940.692344] Freezing user space processes ... (elapsed 0.002 seconds) done.
Jul 28 11:25:47 pikkufisu kernel: [557940.695032] OOM killer disabled.
Jul 28 11:25:47 pikkufisu kernel: [557940.695033] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jul 28 11:25:47 pikkufisu kernel: [557940.696347] printk: Suspending console(s) (use no_console_suspend to debug)
Jul 28 11:25:47 pikkufisu kernel: [557942.579473] ACPI: EC: interrupt blocked
Jul 28 11:25:47 pikkufisu kernel: [593171.768926] ACPI: EC: interrupt unblocked
Jul 28 11:25:47 pikkufisu kernel: [593173.925423] nvme nvme1: Shutdown timeout set to 8 seconds
Jul 28 11:25:47 pikkufisu kernel: [593173.938519] r8169 0000:04:00.0 enp4s0: Link is Down
Jul 28 11:25:47 pikkufisu kernel: [593173.968098] thinkpad_acpi: Unknown/reserved multi mode value 0x0000 for type 4, please report this to ibm-acpi-devel@lists.sourceforge.net
Jul 28 11:25:47 pikkufisu kernel: [593173.983776] nvme nvme1: 8/0/0 default/read/poll queues
Jul 28 11:25:47 pikkufisu kernel: [593174.111760] OOM killer enabled.
Jul 28 11:25:47 pikkufisu dhclient[496]: No DHCPOFFERS received.
Jul 28 11:25:47 pikkufisu dhclient[496]: No working leases in persistent database - sleeping.
Jul 28 11:25:47 pikkufisu kernel: [593174.111761] Restarting tasks ... done.
Jul 28 11:25:47 pikkufisu kernel: [593174.118107] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Jul 28 11:25:47 pikkufisu systemd[1]: Started Run anacron jobs.
Jul 28 11:25:47 pikkufisu systemd[1]: Starting Daily apt upgrade and clean activities...
Jul 28 11:25:47 pikkufisu systemd[1]: Starting Refresh fwupd metadata and update motd...
Jul 28 11:25:47 pikkufisu gnome-software[2097]: not handling error download-failed for action refresh: failed to download https://cdn.fwupd.org/downloads/firmware.xml.gz.jcat: Cannot resolve hostname
Jul 28 11:25:47 pikkufisu anacron[96397]: Anacron 2.3 started on 2021-07-28
Jul 28 11:25:47 pikkufisu anacron[96397]: Will run job `cron.daily' in 5 min.
Jul 28 11:25:47 pikkufisu anacron[96397]: Jobs will be executed sequentially
Jul 28 11:25:47 pikkufisu root: /etc/dhcp/dhclient-exit-hooks.d/zzz_avahi-autoipd returned non-zero exit status 1
Jul 28 11:25:47 pikkufisu fwupdmgr[96402]: Päivittää lvfs
Jul 28 11:25:47 pikkufisu systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
Jul 28 11:25:47 pikkufisu systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'.
Jul 28 11:25:47 pikkufisu systemd[1]: Failed to start Refresh fwupd metadata and update motd.
Jul 28 11:25:47 pikkufisu systemd-sleep[96310]: System resumed.
Jul 28 11:25:47 pikkufisu kernel: [593174.175711] PM: suspend exit
Jul 28 11:25:47 pikkufisu systemd[1]: systemd-suspend.service: Succeeded.
Jul 28 11:25:47 pikkufisu systemd[1]: Finished Suspend.
Jul 28 11:25:47 pikkufisu systemd[1]: Stopped target Sleep.
Jul 28 11:25:47 pikkufisu systemd[1]: Reached target Suspend.
Jul 28 11:25:47 pikkufisu systemd[1]: Stopped target Suspend.
Jul 28 11:25:47 pikkufisu NetworkManager[512]: <info>  [1627460747.4366] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jul 28 11:25:47 pikkufisu NetworkManager[512]: <info>  [1627460747.4367] device (wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jul 28 11:25:47 pikkufisu ModemManager[578]: <info>  [sleep-monitor] system is resuming
Jul 28 11:25:47 pikkufisu NetworkManager[512]: <info>  [1627460747.4497] device (wlp0s20f3): set-hw-addr: set MAC address to 1E:D6:3A:02:72:00 (scanning)
Jul 28 11:25:47 pikkufisu NetworkManager[512]: <info>  [1627460747.6353] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jul 28 11:25:47 pikkufisu packagekitd[1434]: http://deb.debian.org/debian testing InRelease is not (yet) available (Nimeä "deb.debian.org" ei voitu selvittää)


-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.140

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Thu, 2021-07-29 at 02:17 +0300, Antti Järvinen wrote:
> Package: firmware-misc-nonfree
> Version: 20210315-3
> Severity: normal
> 
> Dear Maintainer,
> 
> This is a low-quality error report. First, it is likely that I can't
> repeat this problem because it occurred during upgrade of the package
> ; package is now upgraded.. Haven't tried forcibly installing older
> version and then upgrading again to see if problem persists.
> Secondly, I'm not 100% sure this is the package to blame. Thirdly, I
> don't have proper log files because after the incident my filesystem
> was in read-only mode so I don't really have proper trace about
> events leading to situation described below. 
[...]

There were no changes to the firmware in this version.  The problem
lies elsewhere.  Unfortunately the logs you have don't provide any clue
as to what actually went wrong.

> Kern.log has one entry that points into microcode direction, it says
> Jul 28 11:58:43 pikkufisu kernel: [    0.000000] microcode: microcode updated e\
> arly to revision 0x88, date = 2021-03-31
[...]

This update is done on every boot.  Also, microcode updates are
packaged in intel-microcode and amd64-microcode.

Ben.

-- 
Ben Hutchings
It is a miracle that curiosity survives formal education.
                                                      - Albert Einstein

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: