- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- dynamic driver, unexpected unload()
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2002 02:49 PM
11-27-2002 02:49 PM
dynamic driver, unexpected unload()
I have a DLKM monolithic PCI interface driver, and see that after running 'kmupdate -M xyz', my load() function is called, my attach(), followed by a call to unload().
Next I load the driver 'kmadmin -L', my load() gets called, by not the attach().
'kmadmin -Q xyz' shows all is fine.
However I end up with isc pointer as 0 in my open() routine when I call wsio_get_isc().
That can't be right:
Q: is the load(), attach(), unload() sequence normal from kmupdate?
Q: why is wsio_get_isc() reporting no errors, yet I get a 0 pointer?
Q: how can I get access to my PCI device without isc pointer?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2003 11:24 PM
02-02-2003 11:24 PM
Re: dynamic driver, unexpected unload()
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2003 01:52 AM
02-03-2003 01:52 AM
Re: dynamic driver, unexpected unload()
From kmupdate man page
Immediate Update of Specified Kernel Modules
kmupdate may be used for immediately updating the loadable image of a
newly created kernel module, without a reboot. If the module_name is
loaded, kmupdate tries to unload it and, if the -i option is specified
and the module cannot be unloaded, kmupdate exits with an error. If
the kernel module was either not loaded or successfully unloaded,
kmupdate checks if it is registered, and if so, unregisters the
module. If the kernel module cannot be unregistered, kmupdate exits
with an error if -i is specified; otherwise the module will be updated
asynchronously. If the unregistration succeeds, kmupdate overlays the
existing loadable image of the module with the newly generated image.
It then registers the module with the latest registry information and
performs module type specific initialization, if required. If the
module was loaded originally, kmupdate reloads the module before
exiting.
Steve Steel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-03-2003 04:07 AM
02-03-2003 04:07 AM
Re: dynamic driver, unexpected unload()
Do you have any answer for my question? during reboot why does "MyDriver" unloads?
-George
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2003 02:47 PM
02-18-2003 02:47 PM
Re: dynamic driver, unexpected unload()
Kym