Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #65567 > unrolled thread
| Started by | Dietz Proepper <dietz.debian@scanthis.de> |
|---|---|
| First post | 2019-11-06 18:30 +0100 |
| Last post | 2020-02-03 22:20 +0100 |
| Articles | 4 — 4 participants |
Back to article view | Back to linux.debian.kernel
Bug#944251: e1000e: Link not detected after resume Dietz Proepper <dietz.debian@scanthis.de> - 2019-11-06 18:30 +0100
Bug#944251: e1000e: Link not detected after resume Salvatore Bonaccorso <carnil@debian.org> - 2020-02-03 22:20 +0100
Bug#944251: e1000e: Link not detected after resume Dietz Proepper <dietz@scanthis.de> - 2020-02-09 12:50 +0100
Processed: Re: Bug#944251: e1000e: Link not detected after resume "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-02-03 22:20 +0100
| From | Dietz Proepper <dietz.debian@scanthis.de> |
|---|---|
| Date | 2019-11-06 18:30 +0100 |
| Subject | Bug#944251: e1000e: Link not detected after resume |
| Message-ID | <yZxi1-6gx-3@gated-at.bofh.it> |
Package: linux-image-5.3.0-1-amd64 Version: 5.3.7-1 Severity: important Tags: upstream Hi, there might be a regression in the e1000e ethernet driver: After upgrade from 5.2.13 (handbuilt) to the precompiled kernel from above, the ethernet interface does sometimes (3 out of 5 times I think) not detect the cable connected after a resume. Reverting to 5.2.x resolves the problem. I already opened a bug at kernel.org, https://bugzilla.kernel.org/show_bug.cgi?id=205357, there are some additional infos. -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.13 (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.3.0-1-amd64 depends on: ii dracut [linux-initramfs-tool] 048+80-2 ii kmod 26-3 pn linux-base <none> Versions of packages linux-image-5.3.0-1-amd64 recommends: ii apparmor 2.13.3-6 ii firmware-linux-free 3.4 Versions of packages linux-image-5.3.0-1-amd64 suggests: pn debian-kernel-handbook <none> ii grub-efi-amd64 2.04-3 pn linux-doc-5.3 <none>
[toc] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2020-02-03 22:20 +0100 |
| Message-ID | <zvRip-3wr-1@gated-at.bofh.it> |
| In reply to | #65567 |
Control: tags -1 + moreinfo Hi, On Wed, Nov 06, 2019 at 06:23:34PM +0100, Dietz Proepper wrote: > Package: linux-image-5.3.0-1-amd64 > Version: 5.3.7-1 > Severity: important > Tags: upstream > > Hi, > > there might be a regression in the e1000e ethernet driver: > > After upgrade from 5.2.13 (handbuilt) to the precompiled kernel from above, > the ethernet interface does sometimes (3 out of 5 times I think) not detect > the cable connected after a resume. > > Reverting to 5.2.x resolves the problem. > > I already opened a bug at kernel.org, https://bugzilla.kernel.org/show_bug.cgi?id=205357, > there are some additional infos. According to the provided information on the upstream issue you were not able to reproduce the issue anymore with 5.5. Can you confirm the same is for the Debian packages based on 5.5~rc5-1~exp1 (currently in experimental)? Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | Dietz Proepper <dietz@scanthis.de> |
|---|---|
| Date | 2020-02-09 12:50 +0100 |
| Message-ID | <zxTg6-6hb-9@gated-at.bofh.it> |
| In reply to | #66297 |
[Multipart message — attachments visible in raw view] — view raw
Hi Salvatore, Am Montag, 3. Februar 2020, 22:15:31 CET schrieb Salvatore Bonaccorso: > > I already opened a bug at kernel.org, > > https://bugzilla.kernel.org/show_bug.cgi?id=205357, there are some > > additional infos. > > According to the provided information on the upstream issue you were > not able to reproduce the issue anymore with 5.5. Can you confirm the > same is for the Debian packages based on 5.5~rc5-1~exp1 (currently in > experimental)? Just booted into 5.5~rc5-1~exp1 and could not reproduce that issue. But I noticed some other anormalities: - suspending takes considerable time (around 20s). - a dock-connected keyboard got not rediscovered after resume. - I had to do a hard shutdown (by means of pressing the power button for several seconds) Kindest regards, Dietz
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2020-02-03 22:20 +0100 |
| Subject | Processed: Re: Bug#944251: e1000e: Link not detected after resume |
| Message-ID | <zvRir-3wr-11@gated-at.bofh.it> |
| In reply to | #65567 |
Processing control commands: > tags -1 + moreinfo Bug #944251 [src:linux] e1000e: Link not detected after resume Added tag(s) moreinfo. -- 944251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944251 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web