From: Stian Jordet <liste@jordet.nu>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: irtty_sir cannot be unloaded
Date: 23 May 2003 03:10:00 +0200 [thread overview]
Message-ID: <1053652200.709.6.camel@chevrolet.hybel> (raw)
In-Reply-To: <20030522233609.GA11706@bougret.hpl.hp.com>
fre, 23.05.2003 kl. 01.36 skrev Jean Tourrilhes:
> Stian Jordet wrote :
> >
> > Module irtty_sir cannot be unloaded due to unsafe usage in
> > include/linux/module.h:456
> >
> > I get this message when trying to use irda with 2.5.x. I know it has
> > been there for a long time, but since nothing happens
>
> This is fixed in the patches I've send to Jeff :
> http://marc.theaimsgroup.com/?l=linux-kernel&m=105286597418927&w=2
> Just be patient ;-)
Well, this got rid of the warning :) But actually when I stop irattach
(using Debian's init-script (/etc/init.d/irda stop)) my computer
freezes. This works (of course) fine with 2.4.21-rc2. I thought the
problem was the module unloading, but it seems to be something with
irattach instead. Sorry about that.
> I guess that if it's the only complain, this means that the
> rest of the IrDA stack works for you in 2.5.X. At least, I'm not the
> only one testing it...
It works, but I get lots of weird/ugly/different messages. This is with
a SonyEricsson P800. Except for those annoying messages in my logs, it
works perfect :-)
irlap_change_speed(), setting speed to 9600
sirdev_open - done, speed = 0
sirdev_schedule_request - state=0x0700 / param=9600
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 115200
sirdev_schedule_request - state=0x0700 / param=115200
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 9600
sirdev_schedule_request - state=0x0700 / param=9600
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 115200
sirdev_schedule_request - state=0x0700 / param=115200
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 9600
sirdev_schedule_request - state=0x0700 / param=9600
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 115200
sirdev_schedule_request - state=0x0700 / param=115200
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 9600
sirdev_schedule_request - state=0x0700 / param=9600
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 115200
sirdev_schedule_request - state=0x0700 / param=115200
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 9600
sirdev_schedule_request - state=0x0700 / param=9600
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 115200
sirdev_schedule_request - state=0x0700 / param=115200
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 9600
sirdev_schedule_request - state=0x0700 / param=9600
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 115200
sirdev_schedule_request - state=0x0700 / param=115200
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 9600
sirdev_schedule_request - state=0x0700 / param=9600
sirdev_schedule_request - down
irda_config_fsm - up
Module ircomm_tty cannot be unloaded due to unsafe usage in
include/linux/module.h:456
ircomm_tty_attach_cable()
ircomm_tty_ias_register()
ircomm_tty_close()
ircomm_tty_close(), open count > 0
irlap_change_speed(), setting speed to 115200
sirdev_schedule_request - state=0x0700 / param=115200
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 9600
sirdev_schedule_request - state=0x0700 / param=9600
sirdev_schedule_request - down
irda_config_fsm - up
irlap_change_speed(), setting speed to 115200
sirdev_schedule_request - state=0x0700 / param=115200
sirdev_schedule_request - down
irda_config_fsm - up
ircomm_param_xon_xoff(), XON/XOFF = 0x11,0x13
ircomm_param_enq_ack(), ENQ/ACK = 0x00,0x00
ircomm_tty_check_modem_status()
I see I have gotten a ircomm_tty can't be unloaded as well. Hmm. Well,
as I said, it works perfect, except for stopping irattach.
Thanks.
Best regards,
Stian
next prev parent reply other threads:[~2003-05-23 0:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 23:36 Jean Tourrilhes
2003-05-23 1:10 ` Stian Jordet [this message]
2003-05-23 1:13 ` Jean Tourrilhes
2003-05-23 1:44 ` Stian Jordet
2003-05-23 6:38 ` Martin Diehl
2003-05-23 14:42 ` Stian Jordet
2003-05-23 23:31 ` Martin Diehl
2003-05-23 6:30 ` Martin Diehl
2003-05-23 6:58 ` DevilKin
2003-05-23 7:13 ` Martin Diehl
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 23:19 Stian Jordet
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=1053652200.709.6.camel@chevrolet.hybel \
--to=liste@jordet.nu \
--cc=jt@hpl.hp.com \
--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
all inboxes | Powered by JetHome®