home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!newsserver.jvnc.net!yale.edu!ira.uka.de!math.fu-berlin.de!umn.edu!csus.edu!netcom.com!netcomsv!mbeckman!mbeckman
- From: mbeckman@mbeckman.mbeckman.com (Mel Beckman)
- Newsgroups: comp.unix.aix
- Subject: Device driver hangs in ioctl
- Date: Sat, 23 Jan 93 22:00:55 PST
- Organization: Beckman Software Engineering
- Message-ID: <01050810.oes4n3@mbeckman.mbeckman.com>
- Reply-To: mbeckman@mbeckman.com
- Distribution: world
- X-Mailer: uAccess LITE - Macintosh Release: 1.5v5
- Lines: 26
-
- We're using a third-party proprietary-network device driver that works well
- most of the time, but every once in a while hangs in an infinite loop. With
- xdb I've narrowed the problem down to a loop where the driver keeps calling
- ioctl with (0x0, 0xdeadbeef, 0xdeadbeef). I think that ioctl just hates
- these arguments, and so immediately returns to the driver, which seems to
- be coded to keep trying the ioctl call.
-
- Am I correct in assuming that 0xdeadbeef is an invalid argument? I know
- deadbeef is uninititialized (by the process) storage, right? If the driver
- definitely is giving garbage to ioctl, I can take that to the vendor and
- get him to fix it (I hope <grin>).
-
- But I'm not sure that perhaps 0xdeadbeef is just innocuous here.
-
- Make me smarter!
-
- -mel
-
- _____________________________________________________________________
- | Mel beckman | Internet: mbeckman@mbeckman.com |
- | Beckman Software Engineering | Compuserve: 75226,2257 |
- | 1201 Nilgai Place | Voice: 805/647-1641 |
- | Ventura, CA 93003 | Fax: 805/647-3125 |
- |______________________________|____________________________________|
- "Internet is big. Really Big. It gives the idea of
- infinity much better than infinity itself."
- (with apologies to Douglas Adams)
-