Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #949391
| From | "computer.enthusiastic" <computer.enthusiastic@gmail.com> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#895378: sky2: sky2: did not recover correctly after waking up from S3 |
| Date | 2019-03-11 06:40 +0100 |
| Message-ID | <xAlPj-44S-1@gated-at.bofh.it> (permalink) |
| References | <vD7rc-3lf-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
I have the same issue with the current Debian Buster kernel using an
Acer Aspire 5930G both with suspension and the hibernation; I'm using
the following kernel:
$uname -a
Linux debian 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17)
x86_64 GNU/Linux
After suspension or hibernation, the network connection is not
re-established with a NO-CARRIER error. A first work-around is to
unload and reload the sky2 kernel driver with the folllowing commands:
modprobe -r sky2
modprobe sky2
It seems a kernel bug and it is discussed, for example, in this Ubuntu
bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921
In this message
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798921/comments/28)
the author suggests (on Debian) to start the kernel with the
following parameters to work-around the bug:
pci=nomsi,noaer
I have tried and it works.
Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread
Bug#895378: sky2: sky2: did not recover correctly after waking up from S3 "computer.enthusiastic" <computer.enthusiastic@gmail.com> - 2019-03-11 06:40 +0100
csiph-web