Bug 137504

Summary:	gentoo-sources-2.6.17 - sky2 driver problems
Product:	Gentoo Linux	Reporter:	João Oliveirinha <joliveirinha>
Component:	[OLD] Core system	Assignee:	Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel>
Status:	RESOLVED NEEDINFO
Severity:	normal	CC:	nerff
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	/proc/interrupts with kernel 2.6.17

Description João Oliveirinha 2006-06-21 11:34:30 UTC

The driver have the same problem... it doesnt work..

Here is the past reports
http://bugs.gentoo.org/show_bug.cgi?id=127367
http://bugs.gentoo.org/show_bug.cgi?id=131274

I am using gentoo-sources 2.6.17.

Comment 1 João Oliveirinha 2006-06-21 11:35:53 UTC

Created attachment 89745 [details]
/proc/interrupts with kernel 2.6.17

Comment 2 Daniel Drake (RETIRED) gentoo-dev

2006-07-17 07:30:06 UTC

Please reproduce it on 2.6.18-rc2 with this patch applied:

http://marc.theaimsgroup.com/?l=linux-netdev&m=115314452123184&q=raw

Comment 3 Jakub Moc (RETIRED) gentoo-dev

2006-08-01 09:20:52 UTC

*** Bug 142439 has been marked as a duplicate of this bug. ***

Comment 4 Vlastimil Babka (Caster) (RETIRED) gentoo-dev

2006-08-02 05:23:42 UTC

I think the report in bug 142439 shows that it can be reproduced with patch from comment 2 (sky2 version 1.5)...

Comment 5 justforkix 2006-08-18 13:16:14 UTC

In reply to comment #2)
> Please reproduce it on 2.6.18-rc2 with this patch applied:
> 
> http://marc.theaimsgroup.com/?l=linux-netdev&m=115314452123184&q=raw
> 

The poblems persists with vanilla-sources 2.6.18-rc4. As far as I can tell, these sources already include patch referenced above. Atleast for me, the problem usually happens on transmit (rsyn from laptop to server). Download is fine. Is there an interest in following this problem here?

Comment 6 Daniel Drake (RETIRED) gentoo-dev

2006-08-20 07:53:35 UTC

Closing this bug as there is no response from Joao.

justforkix: Please open a separate bug for your issue. It may be the same problem as detailed here, but it just gets too hard to track this stuff with interleaved reports on the same bug.