From: Stefan Schweizer <genstef@gentoo.org>
To: linux-kernel@vger.kernel.org
Cc: i4ldeveloper@listserv.isdn4linux.de
Subject: [PATCH 2.6.17-rc3] Fix capi reload by unregistering the correct major
Date: Sat, 29 Apr 2006 19:25:12 +0200 [thread overview]
Message-ID: <e307i4$f1h$1@sea.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I am having the bug
FATAL: Error inserting capi ([..]/capi.ko): Device or resource busy
when I try to reload capi after loading it.
in dmesg: capi20: unable to get major 68
I attached a patch to fix the issue which is caused by setting the major to
zero when registering the chrdev succeeded. Please apply
- - Stefan
errors in the dmesg:
CAPI Subsystem Rev 1.1.2.8
capifs: Rev 1.1.2.3
capi20: Rev 1.1.2.7: started up with major 0 (middleware+capifs)
<-- here you see that it was set to 0.
(after unload and retry)
capi: Rev 1.1.2.7: unloaded
CAPI Subsystem Rev 1.1.2.8
capi20: unable to get major 68
<-- the chrdev has not been unlinked
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEU6GBNJowsmZ/PzARArMZAJ9tfOoFGJ5wNd86DA15JiaZJFLsAQCfaYr7
9XF6cTgYU7Y9hzvGLgXkJqU=
=qvpL
-----END PGP SIGNATURE-----
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: capi --]
[-- Type: text/x-diff; name="capi", Size: 398 bytes --]
--- drivers/isdn/capi/capi.c.orig 2006-04-29 18:40:25.000000000 +0200
+++ drivers/isdn/capi/capi.c 2006-04-29 18:27:22.000000000 +0200
@@ -1499,7 +1499,6 @@
printk(KERN_ERR "capi20: unable to get major %d\n", capi_major);
return major_ret;
}
- capi_major = major_ret;
capi_class = class_create(THIS_MODULE, "capi");
if (IS_ERR(capi_class)) {
unregister_chrdev(capi_major, "capi20");
next reply other threads:[~2006-04-29 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 17:25 Stefan Schweizer [this message]
2006-05-08 20:00 ` [PATCH 2.6.17-rc3] Fix capi reload by unregistering the correct major Andrew Morton
2006-05-09 17:12 ` Stefan Schweizer
2006-05-12 22:16 ` Stefan Schweizer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e307i4$f1h$1@sea.gmane.org' \
--to=genstef@gentoo.org \
--cc=i4ldeveloper@listserv.isdn4linux.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox