You are not logged in.
Since the latest kernel update yesterday, I get the error
kernel: e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
TDH <0>
TDT <1>
next_to_use <1>
next_to_clean <0>
buffer_info[next_to_clean]:
time_stamp <fffeab29>
next_to_watch <0>
jiffies <fffeadc0>
next_to_watch.status <0>
MAC Status <80080>
PHY Status <7949>
PHY 1000BASE-T Status <0>
PHY Extended Status <3000>
PCI Status <10>
Any hint how to debug it?
Offline
https://cdn.kernel.org/pub/linux/kernel … eLog-5.0.7 contains three commits referencing the e1000e. If you revert those commits is the issue still present?
Offline
Thanks.
I was trying to edit the pkgbuild of linux-git, including a line like e.g.
git revert b503ea08fe0dcf03a5e78a558ea0bd7b5dcbd164
in pkgver(), but it does not work.
What is the proper way? Also, how do I tell it I want to use 5.0.7 kernel?
Offline
I've seen two of these since upgrading from 5.0.6 to 5.0.7-arch1-1-ARCH an hour ago. Ethernet seems to function okay.
Apr 09 13:46:41 thinkpad-t480s kernel: e1000e 0000:00:1f.6 enp0s31f6: Detected Hardware Unit Hang:
TDH <0>
TDT <2>
next_to_use <2>
next_to_clean <0>
buffer_info[next_to_clean]:
time_stamp <1001c27f1>
next_to_watch <1>
jiffies <1001c2a00>
next_to_watch.status <0>
MAC Status <40080080>
PHY Status <7949>
PHY 1000BASE-T Status <800>
PHY Extended Status <3000>
PCI Status <10>
Offline
pkgver() updates the value of the pkgver variable it is used to set the version string.
To set the initial checkout for git repository you can use #tag or #commit fragments the following adds a variable set to the tag it also specifies the tag is signed
_tag=v5.0.7
source=("git+https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git#tag=${_tag}?signed"
Add the keyid to be used for verifying the tag signature (remember to import that keyid)
validpgpkeys=(
'647F28654894E3BD457199BE38DBBDC86092693E' # Greg Kroah-Hartman
)
Start of prepare() revert the last of the commits to be applied use -n so not to create a commit
prepare() {
cd "${_srcname}"
git revert -n b503ea08fe0dcf03a5e78a558ea0bd7b5dcbd164
# git revert -n 7f0a3a436e88a71b96694c029f01a9a8eade3d5d
# git revert -n a782956c2a305551a49962ad6bd784d14af769e7
After building that package if you need to revert the second commit
cd src/linux
git revert -n 7f0a3a436e88a71b96694c029f01a9a8eade3d5d
cd ../..
makepkg -ers #-e use the existing src dir so only changed files needs to be rebuilt and preserves the second git revert
Offline
Thanks, I will now try it.
Ethernet works for me as well, I just get the errors.
Offline
Reverting first commit did not solve the issue.
Also, should I use -f option?
$ cd Projects/linux-git/src/linux
$ git revert -n 7f0a3a436e88a71b96694c029f01a9a8eade3d5d
$ cd ../..
$ makepkg -ers
==> Making package: linux-git 5.0.7.r0.g8b298d3a0bd5-1 (Tue 09 Apr 2019 03:48:18 PM EDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> ERROR: The package group has already been built. (use -f to overwrite)
Offline
Reverting the second commit 7f0a3a436e88a71b96694c029f01a9a8eade3d5d seems to solve the problem for me.
Can anyone else confirm?
Should I 're-revert' the first one to confirm it is just the second by itself to produce the error? how to do that?
Offline
Two ways to apply the commit again cherry-pick that commit
cd src/linuix
git cherry-pick -n b503ea08fe0dcf03a5e78a558ea0bd7b5dcbd164
or reset the tree to 5.07 then just revert the second commit
cd src/linux
git reset --hard
git revert -n 7f0a3a436e88a71b96694c029f01a9a8eade3d5d
Offline
Thanks again.
I confirm: it is the second commit alone that is responsible for the error.
Should I file a bug?
Offline
Offline