Bug 3234 - VIA Rhine-II works only with acpi=off
Summary: VIA Rhine-II works only with acpi=off
Status: CLOSED PATCH_ALREADY_AVAILABLE
Alias: None
Product: ACPI
Classification: Unclassified
Component: Config-Interrupts (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Len Brown
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-18 08:35 UTC by Jukka Neppius
Modified: 2007-09-03 01:54 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.6, 2.6.7, 2.6.8
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
lspci -vvv with 2.6.8 (8.11 KB, text/plain)
2004-08-18 08:40 UTC, Jukka Neppius
Details
dmidecode ( 2.6.8 apic) (10.84 KB, text/plain)
2004-08-18 08:47 UTC, Jukka Neppius
Details
dmesg (11.85 KB, text/plain)
2004-08-18 08:48 UTC, Jukka Neppius
Details
interrupts (462 bytes, text/plain)
2004-08-18 09:11 UTC, Jukka Neppius
Details
/var/log/messages after NFS client crash (24.06 KB, text/plain)
2004-09-03 06:53 UTC, Jukka Neppius
Details

Description Jukka Neppius 2004-08-18 08:35:02 UTC
Distribution:Debian testing (Sarge) 
Hardware Environment:A PC with AMD XP 
Software Environment: 
Problem Description:With kernel 2.6.5 ethernet interface  
(VT6102 [Rhine-II] (rev 78) on MB (Epox 8K9A7I) works OK. 
With 2.6.6 - 2.6.8 ethernet is completely dead. Not even ping works. 
With 2.6.8 acpi=off boot parameter ethernet interface works perfectly. 
 
I tested with kernels from ftp.funet.fi, without Debian patches. 
I used make-kpkg to compile and dpkg to instal kernels. 
 
Steps to reproduce:
Comment 1 Jukka Neppius 2004-08-18 08:40:10 UTC
Created attachment 3522 [details]
lspci -vvv  with 2.6.8
Comment 2 Jukka Neppius 2004-08-18 08:47:29 UTC
Created attachment 3523 [details]
dmidecode   ( 2.6.8 apic)
Comment 3 Jukka Neppius 2004-08-18 08:48:37 UTC
Created attachment 3524 [details]
dmesg
Comment 4 Jukka Neppius 2004-08-18 09:11:35 UTC
Created attachment 3526 [details]
interrupts
Comment 5 Shaohua 2004-09-03 02:25:59 UTC
Does this workaround help? (comment one line 'link->irq.active = 0;' in 
drivers/acpi/pci_link.c)
	/*
	 * forget active IRQ that is not in possible list
	 */
	if (i == link->irq.possible_count) {
		if (acpi_strict)
			printk(KERN_WARNING PREFIX "_CRS %d not found"
				" in _PRS\n", link->irq.active);
+//		link->irq.active = 0;
	}
Comment 6 Jukka Neppius 2004-09-03 06:53:28 UTC
Created attachment 3629 [details]
/var/log/messages after NFS client crash

I removed line 'link->irq.active = 0;' from drivers/acpi/pci_link.c.  Now
kernel works exactly as before fix with acpi=off.  Everything except NSF client
seems to work.	I can cd to NFS mounted dir and see contents with ls.  But
trying to access a file with less or cat, causes a crash.  kill -9 does not
kill less process!  var/log/messages included.	This could be a separate bug.  

NFS works well with 2.6.5
Comment 7 Len Brown 2004-11-14 21:19:14 UTC
i assume this is the same in 2.6.9? 
Comment 8 Jukka Neppius 2004-11-18 01:47:08 UTC
Yes! Network interface of 2.6.9 works only with acpi=off 
 
Comment 9 Len Brown 2005-01-03 18:11:11 UTC
please re-test with an un-patched 2.6.10, as we made some updates there.
Comment 10 Jukka Neppius 2005-01-06 12:49:55 UTC
Unfortunately 2.6.10 behaves exactly like earlier versions (6 - 9):
Network (Ethernet) seems to be completely dead. 
With acpi=off I didn't find any problems.
Comment 11 Kevin Barry 2005-01-26 17:44:46 UTC
I had a similar problem on a similar computer. My Rhine also has IRQ 11 like
many other devices (same situation as yours). The Rhine would not work (Though
it'd modprobe and everything) if I used DRI for the graphics card. Now my
graphics card is Unichrome not nVidia, but we both have VIA boards so it might
be related.

Are you using DRI? Try disabling it and testing. Also check your dmesg to see
anything about "IRQ 11: nobody cared'

See http://averatecforums.com/viewtopic.php?t=694 for some more information.
Good luck!
Comment 12 Eugene Seppel 2006-02-18 14:52:15 UTC
I also have Via-rhine-II NIC
Bug
http://bugzilla.kernel.org/show_bug.cgi?id=6100 
is the same but describing more general situation with all PCI devices.
Comment 13 Len Brown 2007-08-18 11:57:34 UTC
Eugene,
re: comment #12
The issue in bug #6100 is different -- lets work that one in that bug report.

Jukka,
What is the answer to Kevin's question about DRI?
Can you still reproduce this issue with 2.6.22.stable?
Comment 14 Jukka Neppius 2007-08-21 00:32:05 UTC
bugme-daemon@bugzilla.kernel.org writes:

> ------- Comment #13 from len.brown@intel.com  2007-08-18 11:57 -------
>
> Jukka,
> What is the answer to Kevin's question about DRI?
> Can you still reproduce this issue with 2.6.22.stable?

I had forgotten this!  


Situation is much better now.  No problems in quick test with 2.6.22.
Debian stable kernel had problems. Next one I tried only had strange
problems with NFS (configuration?). I'll test more
soon.

- Jukka
Comment 15 Jukka Neppius 2007-08-25 09:23:29 UTC
bugme-daemon@bugzilla.kernel.org writes:

> Can you still reproduce this issue with 2.6.22.stable?

I compiled 2.6.22.3 with Debian configs, but without any Debian or
other patches. I cannot reproduce this bug any more. So it seems to be
fixed. (My config: http://www.iki.fi/~jkn/config-2.6.22.3k7jkn)

Thank you!

- Jukka

Note You need to log in before you can comment on or make changes to this bug.