| Summary: | >=gentoo-sources-2.6.19-r5 - forcedeth driver intermittent connection | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | VPN-User <mario.schmidt> |
| Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | 2006.1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| URL: | http://bugzilla.kernel.org/show_bug.cgi?id=8354 | ||
| Whiteboard: | watch-linux-bugzilla | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
dmesg
lspci |
||
|
Description
VPN-User
2007-04-01 19:00:24 UTC
Created attachment 115199 [details]
dmesg
dmesg info
Please try w/ latest vanilla-sources (2.6.20.3) and report back. When trying ~x86 vanilla-sources-2.6.20.3, module-rebuild has problems remerging alsa-driver. Not much relevant whether module-rebuild has a problem w/ your ALSA, just test the forcedeth driver. Tried it. Problem still there. I have an Asus K8N mainboard. I've used the forcedeth driver with all kernel versions the last year. No problems here. 2.6.20-gentoo-r4 is what I use now. I am on amd64 though. Created attachment 115352 [details]
lspci
Comment on attachment 115352 [details]
lspci
I think my hardware is alot newer. Here is what lspci says:
VPN-User: can you reproduce this on the latest development kernel, currently 2.6.21-rc6? How can I get it? I can' t find an ebuild for this one... I tried git-sources-2.6.21_rc3-r6 (which provides forcedeth v0.60) - Still same problem. Within Windows OS using nVidia original driver, there is no problem. Bug still there in gentoo-sources-2.6.20-r6 (stable x86) Are there any previous known working kernels? Please test the latest development kernel, currently 2.6.21-rc7. See http://www.reactivated.net/weblog/archives/2007/04/using-ketchup-to-quickly-install-kernel-sources for one way to get this version. LOL! I solved it by ENABLING CONFIG_PCI_MSI=y in kernel config.
Whyever, it now works. Still a bug, or not? Because no MSI Interrupt is used:
cat /proc/interrupts
CPU0 CPU1
0: 162141 1243 IO-APIC-edge timer
1: 29 2 IO-APIC-edge i8042
6: 1 4 IO-APIC-edge floppy
9: 0 0 IO-APIC-fasteoi acpi
12: 0 4 IO-APIC-edge i8042
14: 5511 12 IO-APIC-edge ide0
16: 73588 5 IO-APIC-fasteoi libata, eth0
17: 10037 5 IO-APIC-fasteoi libata, HDA Intel
18: 39837 1 IO-APIC-fasteoi ohci_hcd:usb1, nvidia
19: 1 1 IO-APIC-fasteoi ehci_hcd:usb2
20: 311 1 IO-APIC-fasteoi eth1
21: 13290 1 IO-APIC-fasteoi wifi0
NMI: 0 0
LOC: 163318 163266
ERR: 1
MIS: 0
Sorry. I thought I solved it. Still disconnections. But a lot more rarely when not traffic is flowing. When traffic is flowing, it still drops about every few seconds: Apr 20 15:30:18 [kernel] eth0: link down. Apr 20 15:30:21 [kernel] eth0: link up. Apr 20 15:32:32 [kernel] eth0: link down. Apr 20 15:32:34 [kernel] eth0: link up. Apr 20 15:32:36 [kernel] eth0: link down. Apr 20 15:32:39 [kernel] eth0: link up. Apr 20 15:32:44 [kernel] eth0: link down. Apr 20 15:32:46 [kernel] eth0: link up. Apr 20 15:32:55 [kernel] eth0: link down. Apr 20 15:32:58 [kernel] eth0: link up. Apr 20 15:36:08 [kernel] eth0: link down. Apr 20 15:36:11 [kernel] eth0: link up. Apr 20 15:36:18 [kernel] eth0: link down. Apr 20 15:36:21 [kernel] eth0: link up. Apr 20 15:36:21 [kernel] eth0: link down. Apr 20 15:36:24 [kernel] eth0: link up. Apr 20 15:37:48 [kernel] eth0: link down. Apr 20 15:37:51 [kernel] eth0: link up. Are those results from 2.6.21-rc7? Yes currently it doent matter which kernel is used, it happens with every kernel. I filed a bug on kernel.org, an nVidia employee has already accepted the bug. Cool thanks - please post the new bug URL here (In reply to comment #18) > Cool thanks - please post the new bug URL here > http://bugzilla.kernel.org/show_bug.cgi?id=8354 |
