lkml.org 
[lkml]   [1997]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[2.0.31] Serial module irregularity
Date

I was fooling around with some hardware, and set up an IRQ conflict between
cua1 and an ethernet card. The ethernet card grabbed the IRQ. The serial
module started up correctly. cua0 was accessible, and a daemon grabbed it,
setting serial's "Used by" value of 1. Attempts to access cua1 failed. So
far, so good. Weirdly, attempts to access the cua1 decreased the "used by"
value with each attempt, even past 0, so, at one point, lsmod returned lines
like this:

serial 7 536870911 (autoclean)
3c509 2 1 (autoclean)
ipx 3 0 (autoclean)

Since this is only happening when there are hardware conflicts that
shouldn't exist anyway, it might not be something you guys care about. But
i'm reporting anyway, just in case. :) This would be on an i386 2.0.31.

--
Mordechai T. Abzug
morty@umbc.edu morty@sled.gsfc.nasa.gov http://umbc.edu/~morty
>>>>> My employer isn't paying for my opinions, so they must be *mine*. <<<<<
If you have any trouble sounding condescending, find a Unix user to show you
how it's done. -Scott Adams (of Dilbert fame)

\
 
 \ /
  Last update: 2005-03-22 13:40    [W:0.029 / U:26.088 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site