LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-29-2009, 08:34 PM   #16
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Original Poster
Rep: Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546

Update: the 2.6.28.10 kernel caused no lock-up with my NIC. Unless there is some oddball anomaly with my kernel configs, I'll conclude the problem was introduced in the 2.6.29 series. For now the problem remains, but I feel as though I'm getting closer at least to when the problem started.
 
Old 05-29-2009, 08:40 PM   #17
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.2
Posts: 1,769

Rep: Reputation: 528Reputation: 528Reputation: 528Reputation: 528Reputation: 528Reputation: 528
I did a little looking around and found this http://patchwork.kernel.org/patch/16212/. Not sure if it will work but its worth a look.
 
Old 05-29-2009, 08:43 PM   #18
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.2
Posts: 1,769

Rep: Reputation: 528Reputation: 528Reputation: 528Reputation: 528Reputation: 528Reputation: 528
and one more http://kerneltrap.org/mailarchive/li...ad#mid-5245584
 
Old 05-29-2009, 09:05 PM   #19
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Original Poster
Rep: Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546
Reading ChangeLog-2.6.29 seems to indicate when the problems started. Apparently somebody wanted the PHY device to power down when the interface goes down, which is exactly what I see happening on my box. That desire sort of makes sense but unfortunately, the device remains latched in that condition through a warm reset.

Quote:
I did a little looking around and found this http://patchwork.kernel.org/patch/16212/. Not sure if it will work but its worth a look.
Seems the patch is already in the 2.6.29.4 forcedeth.c source file. I'll try compiling another copy of 2.6.29.4.

Hmm. I found CONFIG_FORCEDETH_NAPI=y in my config. Same option is set in the huge and generic kernels too. When I run/compile another pass I'll disable that option.

Update: Setting CONFIG_FORCEDETH_NAPI=n with the 2.6.29.4 kernel produced the same lock-up problem. The 2.6.28.10 kernel is clean.

Last edited by Woodsman; 05-29-2009 at 09:58 PM.
 
Old 06-19-2009, 10:35 PM   #20
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Original Poster
Rep: Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546
I'm sad to report the 2.6.29.5 kernel causes the same lockup/latching problem.

Same result: From a cold boot the NIC initializes fine. If I perform a warm reboot then the NIC locks and won't reinitialize without a cold restart. I can avoid the lockup if I use the kernel magic keys (Alt-SysRq-R-E-I-S-U-B).

The problem also latches my WRT54GL router. That is, when the NIC shuts down the router latches into an unresponsive state too. Yes, I tried swapping router ports. I can power down and restart my computer, but the NIC LEDs never fire on. Therefore I can only conclude the router is latched and that prevents the NIC from initializing.

I seem to be left with only a few options: buy a new motherboard, buy a separate NIC (and consume more watts), or never update this box past 12.2.

Well, perhaps there is another option: update all of Slackware but keep using the 2.6.27.7 kernel or update to the 2.6.28.10 kernel. As I reported earlier, the 2.6.28.10 kernel does not cause the lockup.

Sigh.
 
Old 06-29-2009, 12:34 AM   #21
Woodsman
Senior Member
 
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482

Original Poster
Rep: Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546Reputation: 546
Good News!

This lock-up problem has been particularly frustrating. Down right discouraging.

Today I compiled and tested the 2.6.30 kernel. Upon rebooting, my NIC continued to function and also did not latch my router!

I compared the 2.6.29.5 forcedeth.c code to 2.6.30 and there are many differences. There is one section of code with a comment about the NIC "persisting after reboot." Apparently this lock-up problem finally has been fixed in 2.6.30.

I did not test anything else with 2.6.30, but I noticed both KDE and Xfce starting and responding much faster. Perhaps some of the ext3 issues really have been resolved with 2.6.30, which is what I use.

I have notified Pat. I'm hoping he'll consider updating Current to 2.6.30 before official release!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Current Huge Kernel Will Not Boot With cx23885 Module Woodsman Slackware 7 05-29-2009 10:46 AM
NIC stops working after first reboot PeterWelzien SUSE / openSUSE 2 03-17-2008 04:27 AM
NIC stops working suddenly mhm Linux - Networking 5 06-10-2007 01:35 PM
NIC stops working after about 4 hours jag7720 Linux - Wireless Networking 1 12-31-2003 09:13 PM
Once Nic card is enabled...xwindows stops working? AnthonyM Linux - General 3 02-28-2003 07:33 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:12 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration