| Summary: | sys-kernel/gentoo-sources-5.15.59 network driver problem | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Frank Noack <fgroups> |
| Component: | Current packages | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
lspci at coldstart
lspci at reboot/warmstart bootlog coldstart bootlog reboot/warmstart kernel config lspci -vvv cold start lspci -vvv warm start |
||
|
Description
Frank Noack
2022-08-21 19:44:30 UTC
Created attachment 800381 [details]
lspci at coldstart
Created attachment 800383 [details]
lspci at reboot/warmstart
Created attachment 800385 [details]
bootlog coldstart
Created attachment 800387 [details]
bootlog reboot/warmstart
Created attachment 800389 [details]
kernel config
Can you attach both lspci outputs with more verbose info ? lspci -vvv Also, can you please test with the latest 5.15 which is 5.15.62 as of this writing. Unfortunately it seem to be a hardware problem. I have checked the behavior with another distribution (Kubuntu boot-stick). The same problem appears. If I start cold, in Bios the LAN is not shown. If I re-start (warm start) the LAN information is shown in BIOS. Yes I have upgraded the kernel to 5.15.62 now. If you assume that it is still a kernel problem, I will send requested information. Can you attach both lspci outputs with more verbose info ? lspci -vvv Created attachment 801178 [details]
lspci -vvv cold start
Created attachment 801181 [details]
lspci -vvv warm start
Done Thanks, there is a race condition fix released in 5.15.63 for igb. Would you mind testing that, and also the latest 5.19.7? If they both fail, can you do a bisect from the last working kernel to the first non-working kernel? I tried both Kernels without success. Always the same result. There was no older kernel working with this mainboard in the past. It was a new bord I tried out. I started with chroot fromm Ubuntu with the same problem. So I returned the Board now. If I get an identical board, I test it again and report the result. If I get a refund, I buy another board I think. (In reply to Frank Noack from comment #14) > I tried both Kernels without success. Always the same result. There was no > older kernel working with this mainboard in the past. It was a new bord I > tried out. I started with chroot fromm Ubuntu with the same problem. So I > returned the Board now. If I get an identical board, I test it again and > report the result. If I get a refund, I buy another board I think. Ok, thanks. I'm going to close this now while you go through the return / new board / test. Please re-open if you experience the same issue. |
