Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
07-31-2001, 12:28 PM
|
#1
|
LQ Newbie
Registered: Jul 2001
Location: Madison, AL
Distribution: Red Hat
Posts: 7
Rep:
|
Bus-Master....Dirty
Our machine has been working find under the current kernel for about a month and then suddenly out of nowhere these messages start appearing in the message log:
Jul 31 11:17:36 vortex kernel: Flags; bus-master 1, dirty 96429(13) current 96431(15)
Jul 31 11:17:36 vortex kernel: Transmit list 00000000 vs. cefd5540.
Jul 31 11:17:36 vortex kernel: 0: @cefd5200 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 1: @cefd5240 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 2: @cefd5280 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 3: @cefd52c0 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 4: @cefd5300 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 5: @cefd5340 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 6: @cefd5380 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 7: @cefd53c0 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 8: @cefd5400 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 9: @cefd5440 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 10: @cefd5480 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 11: @cefd54c0 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 12: @cefd5500 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 13: @cefd5540 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 14: @cefd5580 length 8000059a status 8001059a
Jul 31 11:17:36 vortex kernel: 15: @cefd55c0 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: Flags; bus-master 1, dirty 96484(4) current 96484(4)
Jul 31 11:17:36 vortex kernel: Transmit list 00000000 vs. cefd5300.
Jul 31 11:17:36 vortex kernel: 0: @cefd5200 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 1: @cefd5240 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 2: @cefd5280 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 3: @cefd52c0 length 8000059a status 8001059a
Jul 31 11:17:36 vortex kernel: 4: @cefd5300 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 5: @cefd5340 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 6: @cefd5380 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 7: @cefd53c0 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 8: @cefd5400 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 9: @cefd5440 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 10: @cefd5480 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 11: @cefd54c0 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 12: @cefd5500 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 13: @cefd5540 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 14: @cefd5580 length 8000059a status 0001059a
Jul 31 11:17:36 vortex kernel: 15: @cefd55c0 length 8000059a status 0001059a
There are lines and lines of this. Any idea what may have caused it and how to make it stop.
Thanks
|
|
|
07-31-2001, 03:26 PM
|
#2
|
Senior Member
Registered: May 2001
Location: Bristol, UK
Distribution: Slackware, Fedora, RHES
Posts: 2,243
Rep:
|
Uhm... as per your other thread I'd start to look into some hardware diags. It might be a kernel issue, but I recon its more likely to be hardware.
cheers
Jamie...
|
|
|
07-31-2001, 03:34 PM
|
#3
|
LQ Newbie
Registered: Jul 2001
Location: Madison, AL
Distribution: Red Hat
Posts: 7
Original Poster
Rep:
|
Two Different Machines
My posts come from two different machines that aren't connected in anyway. This one is a stand alone server and the other is a raid cluster.
Thanks,
Wayne
|
|
|
07-31-2001, 03:39 PM
|
#4
|
Senior Member
Registered: May 2001
Location: Bristol, UK
Distribution: Slackware, Fedora, RHES
Posts: 2,243
Rep:
|
Really! You had any power problems recently or have you got them spike filetered an UPS... As you said that the network performance was slow on the other machine, and I'm assuming that the above errors are from a 3C905 network card (aka Vortex) right? Seems odd to have a slow network on one machine, and a moaning network card on another. When you do an ifconfig do you see a lot of errors in your TX or RX count??
cheers
Jamie...
|
|
|
07-31-2001, 03:42 PM
|
#5
|
Senior Member
Registered: May 2001
Location: Bristol, UK
Distribution: Slackware, Fedora, RHES
Posts: 2,243
Rep:
|
Another though - how tolerant is mosix of bad data being recieved over the network while its shifting processes around. Just wondering if this would be related to your other thread's problems, as I imagine that it would be a pretty good was to cause the kernel to oops.
cheers
Jamie...
|
|
|
07-31-2001, 05:13 PM
|
#6
|
LQ Newbie
Registered: Jul 2001
Location: Madison, AL
Distribution: Red Hat
Posts: 7
Original Poster
Rep:
|
The Card
Well it looks like the ethernet card went out. We replaced it and things seem to be chuging smooth now.
thanks,
Wayne P
|
|
|
All times are GMT -5. The time now is 07:19 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|