Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #73227 > unrolled thread

Bug#995927: linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend

Back to article view | Back to linux.debian.kernel

Contents

  Bug#995927: linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend hikaru <hikaru.debian@web.de> - 2021-10-08 12:10 +0200
    Bug#995927: linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend Salvatore Bonaccorso <carnil@debian.org> - 2021-10-13 22:30 +0200
      Bug#995927: Aw: Re: Bug#995927: linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend hikaru.debian@web.de - 2021-10-14 12:20 +0200
    Processed: Re: Bug#995927: linux-image-amd64: since kernel 5.9  module e100 causes system-wide problems after suspend "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-10-13 22:30 +0200
    Bug#995927: duplicate Alexey Kuznetsov <kuznetsov.alexey@gmail.com> - 2021-11-04 19:30 +0100
    Bug#995927: marked as done (linux-image-amd64: since kernel 5.9  module e100 causes system-wide problems after suspend) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-11-26 17:10 +0100

#73227 — Bug#995927: linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend

Package: linux-image-amd64
Version: 5.10.46-5
Severity: normal
Tags: upstream
X-Debbugs-Cc: hikaru.debian@web.de

Dear Maintainers,

I own an old notebook with the following wired ethernet adapter:

07:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 02)
	Subsystem: Fujitsu Technology Solutions PRO/100 VE Network Connection
	Flags: bus master, medium devsel, latency 64, IRQ 20
	Memory at dc000000 (32-bit, non-prefetchable) [size=4K]
	I/O ports at 5000 [size=64]
	Capabilities: [dc] Power Management version 2
	Kernel driver in use: e100
	Kernel modules: e100

Under Bullseye (kernel 5.10), after a suspend2RAM/resume cycle, e100 causes
problems which seem to be related to "e100: use generic power management" [1],
which wass introduced with kernel 5.9. In the comment it says:
"Compile-tested only."


The symptoms are not always consistent, but usually they are as follows:

1. After resume, there is no network at all (not only via the wired adapter,
but also via the intel wifi adapter), at least for several (5?) minutes.
Network may or may not return after that time.

2. During that time, certain interactions with the system just stall -
especially those connected to network tasks (e.g. network-manager-gnome, ip).
In case "ip a" is successful it will usually show that there is a
network connection (ip adress obtained via dhcp), but no network activity is
possible (e.g. ping).
(I ruled out network manager as the culprit, by uninstalling it. The problems
remained the same.)

3. When performing a shutdown or reboot after such a suspend/resume cycle, the
operating system and the HDD will shut down, but the computer will not
actually power off/reboot. Instead it will stay on indefinitely while messages
like these remain on the screen:

Okt 06 18:32:19 amilo systemd[1]: Reached target Reboot.
Okt 06 18:32:19 amilo systemd[1]: Shutting down.
Okt 06 18:32:19 amilo systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog
Okt 06 18:32:19 amilo systemd[1]: Set hardware watchdog to 10min.
Okt 06 18:32:19 amilo kernel: watchdog: watchdog0: watchdog did not stop!
Okt 06 18:32:19 amilo systemd-shutdown[1]: Syncing filesystems and block devices.
Okt 06 18:32:19 amilo systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Okt 06 18:32:19 amilo systemd-journald[213]: Journal stopped

4. During that shutdown the kernel may or may not throw exceptions, of
which I have a photo, but no easily accessible log.


Buster (kernel 4.19, up to bpo kernel 5.8) does not exhibit this behavior.
However, it does with bpo kernels 5.9 and 5.10.

The problems disappear (with kernels >= 5.9) when disabling the
ethernet adapter in the BIOS or when blacklisting e100.

For sake of transparency, I opened a thread in the unofficial German
debianforum.de, which led me to file this bug report. [2]


[1] https://github.com/torvalds/linux/commit/69a74aef8a18eef20fb0044b5e164af41b84db21
[2] https://debianforum.de/forum/viewtopic.php?f=26&t=182239

kind regards
hikaru


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

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-5.10.0-8-amd64  5.10.46-5

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

[toc] | [next] | [standalone]

#73277

Control: tags -1 + moreinfo

Hi,

On Fri, Oct 08, 2021 at 12:03:01PM +0200, hikaru wrote:
> Package: linux-image-amd64
> Version: 5.10.46-5
> Severity: normal
> Tags: upstream
> X-Debbugs-Cc: hikaru.debian@web.de
> 
> Dear Maintainers,
> 
> I own an old notebook with the following wired ethernet adapter:
> 
> 07:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 02)
> 	Subsystem: Fujitsu Technology Solutions PRO/100 VE Network Connection
> 	Flags: bus master, medium devsel, latency 64, IRQ 20
> 	Memory at dc000000 (32-bit, non-prefetchable) [size=4K]
> 	I/O ports at 5000 [size=64]
> 	Capabilities: [dc] Power Management version 2
> 	Kernel driver in use: e100
> 	Kernel modules: e100
> 
> Under Bullseye (kernel 5.10), after a suspend2RAM/resume cycle, e100 causes
> problems which seem to be related to "e100: use generic power management" [1],
> which wass introduced with kernel 5.9. In the comment it says:
> "Compile-tested only."
> 
> 
> The symptoms are not always consistent, but usually they are as follows:
> 
> 1. After resume, there is no network at all (not only via the wired adapter,
> but also via the intel wifi adapter), at least for several (5?) minutes.
> Network may or may not return after that time.
> 
> 2. During that time, certain interactions with the system just stall -
> especially those connected to network tasks (e.g. network-manager-gnome, ip).
> In case "ip a" is successful it will usually show that there is a
> network connection (ip adress obtained via dhcp), but no network activity is
> possible (e.g. ping).
> (I ruled out network manager as the culprit, by uninstalling it. The problems
> remained the same.)
> 
> 3. When performing a shutdown or reboot after such a suspend/resume cycle, the
> operating system and the HDD will shut down, but the computer will not
> actually power off/reboot. Instead it will stay on indefinitely while messages
> like these remain on the screen:
> 
> Okt 06 18:32:19 amilo systemd[1]: Reached target Reboot.
> Okt 06 18:32:19 amilo systemd[1]: Shutting down.
> Okt 06 18:32:19 amilo systemd[1]: Using hardware watchdog 'iTCO_wdt', version 0, device /dev/watchdog
> Okt 06 18:32:19 amilo systemd[1]: Set hardware watchdog to 10min.
> Okt 06 18:32:19 amilo kernel: watchdog: watchdog0: watchdog did not stop!
> Okt 06 18:32:19 amilo systemd-shutdown[1]: Syncing filesystems and block devices.
> Okt 06 18:32:19 amilo systemd-shutdown[1]: Sending SIGTERM to remaining processes...
> Okt 06 18:32:19 amilo systemd-journald[213]: Journal stopped
> 
> 4. During that shutdown the kernel may or may not throw exceptions, of
> which I have a photo, but no easily accessible log.
> 
> 
> Buster (kernel 4.19, up to bpo kernel 5.8) does not exhibit this behavior.
> However, it does with bpo kernels 5.9 and 5.10.
> 
> The problems disappear (with kernels >= 5.9) when disabling the
> ethernet adapter in the BIOS or when blacklisting e100.
> 
> For sake of transparency, I opened a thread in the unofficial German
> debianforum.de, which led me to file this bug report. [2]
> 
> 
> [1] https://github.com/torvalds/linux/commit/69a74aef8a18eef20fb0044b5e164af41b84db21
> [2] https://debianforum.de/forum/viewtopic.php?f=26&t=182239

Can you report the upstream directly to upstream people (and ideally
keep us in the loop)?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#73290 — Bug#995927: Aw: Re: Bug#995927: linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend

Dear Salvatore,

thank your for your response!

I'd gladly report the issue upstream, but I'm not sure on how to approach that.
I'm aware of Bugzilla [1], but so far I have no account there. And the
documentation [2] says, that Bugzilla is likely not the right address anyway:

> Locate the driver or kernel subsystem that seems to be causing the issue.
> Find out how and where its developers expect reports. Note: most of the time
> this won’t be bugzilla.kernel.org, as issues typically need to be sent by mail
> to a maintainer and a public mailing list.

I have very little experience when it comes to the kernel.
The maintainers list [3] and the code of e100 [4] suggest different e-mail
addresses, according to the e1000 Sourceforge site [5], depending on whether the
e100 module would be considered "in" or "out of tree". 
I'm also not sure which formal rules (e.g. tags) I need to follow to get through
with the matter at a big company like Intel.

Can you give me some advice please?


[1] https://bugzilla.kernel.org/
[2] https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html#step-by-step-guide-how-to-report-issues-to-the-kernel-maintainers
[3] https://www.kernel.org/doc/html/latest/process/maintainers.html#intel-ethernet-drivers
[4] https://sources.debian.org/src/linux/5.14.9-2/Documentation/networking/device_drivers/ethernet/intel/e100.rst/
[5] https://sourceforge.net/projects/e1000/


regards
hikaru

[toc] | [prev] | [next] | [standalone]

#73279 — Processed: Re: Bug#995927: linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend

Processing control commands:

> tags -1 + moreinfo
Bug #995927 [src:linux] linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend
Added tag(s) moreinfo.

-- 
995927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995927
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#73605 — Bug#995927: duplicate

[Multipart message — attachments visible in raw view] — view raw

Duplicate of:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982956

I have exactly the same issues and 'bisected' to the same problematic
commit you are referring to.

-- AK

[toc] | [prev] | [next] | [standalone]

#73806 — Bug#995927: marked as done (linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Fri, 26 Nov 2021 16:00:11 +0000
with message-id <E1mqddz-0003oO-Jb@fasolo.debian.org>
and subject line Bug#995927: fixed in linux 5.15.5-1
has caused the Debian Bug report #995927,
regarding linux-image-amd64: since kernel 5.9 module e100 causes system-wide problems after suspend
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.)


-- 
995927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995927
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web