Bug 5979 - (net dmfe) Davicom DM9102 Network Card cuts out every 60 secs
Summary: (net dmfe) Davicom DM9102 Network Card cuts out every 60 secs
Status: REJECTED UNREPRODUCIBLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Network (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Jeff Garzik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-30 03:30 UTC by John C. McCabe-Dansted
Modified: 2008-09-23 04:09 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.15.1
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description John C. McCabe-Dansted 2006-01-30 03:30:11 UTC
Most recent kernel where this bug did not occur: Any version without Suspend2
patch applied.
Distribution: Kubuntu 5.10
Hardware Environment: Pentium4, Davicom DM9102
Software Environment: dmfe.c, compiled with gcc 3.4
Problem Description: The Davicom DM9102 Network Card stops working 60 secs after
intialisation, removing and reinserting the network cable causes it to work for
another (exactly) 60 secs.
Steps to reproduce: This bug only occurs with the Suspend2 patch, but the
Suspend2 guys said the problem seemed to be with the driver and to report it
upstream, see: http://bugzilla.suspend2.net/show_bug.cgi?id=181
Comment 1 Nigel Cunningham 2006-01-30 16:50:34 UTC
I encouraged John to push this bug upstream because I can't see anything that 
Suspend2 changes which would be related. We touch kernel thread freezing, but 
the tulip cards don't use a kernel thread. Everything else apart from the 
'doesn't happen without Suspend2 applied' says to me this is a problem in the 
driver itself. 
 
John, could you give more detail regarding the testing you're doing? Without 
Suspend2 applied to a 2.6.15.1 kernel, does everything work ok if you use "echo 
disk > /sys/power/state"? (Assuming you have swsusp compiled in and 
configured). 
 
Regards, 
 
Nigel 
Comment 2 John C. McCabe-Dansted 2006-01-31 03:34:51 UTC
It had nothing to do with the Suspend2 kernel patch, it *does* occur with     
vanilla 2.6.15.1. It was the suspend2 initrd that caused, or rather didn't     
solve the problem.    
     
1) If I use an Ubuntu/Debian kernel with an Ubuntu/Debian initrd it works.      
    
2) If I use an Ubuntu/Debian kernel with a manually built initrd    
 or I use a 2.6.15.1 kernel (patched or not) without an initrd     
 or I use a 2.6.15.1 kernel (patched or not) with a manually built initrd    
 then the networking problem occurs.   
  
However I don't understand why the Ubuntu initrd would fix the problem. I  
assume that the initrd is just there so that it doesn't need to mount a ext3  
partition to load the ext3 module, like in the old "CD-Rom detected, please  
insert MS-Windows CD-Rom" dilemma. Perhaps I was just lucky that it happened to 
work with the original Ubuntu initrd? 
Comment 3 Natalie Protasevich 2008-03-15 11:54:11 UTC
What is the status on this problem? Has it been resolved?
Thanks.
Comment 4 John C. McCabe-Dansted 2008-09-23 04:09:50 UTC
I no-longer have this card, so I will leave this as unreproducible.

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