[Bluez-devel] snd-bt-sco module prevents ACPI S3

[Bluez-devel] snd-bt-sco module prevents ACPI S3

[Rene Mayrhofer]

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

Hi all,

[Please CC me in replies, I am not subscribed to this list.]

I am a happy user of the alsa bluetooth driver, i.e. snd-bt-sco and btsco. 
There are just two things that seem to be broken in snd-bt-sco (CVS version 
as of a month ago):

1. It's name in the lsmod list is different from the module name, i.e. 
modprobe and rmmod must be used with different names.
2. It breaks ACPI S3 (suspend to RAM), making it pretty much unusable on 
laptops where S3 is used (like mine). Unloading snd-bt-sco does not work (I 
do that with a few other modules); as soon as it has been loaded once (even 
if it has not been used and/or has been unloaded), the kernel (2.6.14-rc5) is 
unable to enter ACPI S3. 

with best regards,
Rene

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [Bluez-devel] snd-bt-sco module prevents ACPI S3

[Brad Midgley]

Rene

> 1. It's name in the lsmod list is different from the module name, i.e. 
> modprobe and rmmod must be used with different names.

Do you want to submit a patch (or at least tell us what the different
names are?)

> 2. It breaks ACPI S3 (suspend to RAM), making it pretty much unusable on 
> laptops where S3 is used (like mine). Unloading snd-bt-sco does not work (I 
> do that with a few other modules); as soon as it has been loaded once (even 
> if it has not been used and/or has been unloaded), the kernel (2.6.14-rc5) is 
> unable to enter ACPI S3. 

This may be the result of something we did but it's much more likely to
be a change in the kernel.

What exactly happens when you try & fail to go to S3?

Brad


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] snd-bt-sco module prevents ACPI S3

[Lenz Grimmer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

some input from me, as I noticed the same issues.

Brad Midgley wrote:

> > 1. It's name in the lsmod list is different from the module name, i.e. 
> > modprobe and rmmod must be used with different names.
> 
> Do you want to submit a patch (or at least tell us what the different
> names are?)

The module file is named "snd-bt-sco.ko", while "lsmod" displays it as
"snd_bt_sco". Not a biggie, but weird.

> > 2. It breaks ACPI S3 (suspend to RAM), making it pretty much unusable on 
> > laptops where S3 is used (like mine). Unloading snd-bt-sco does not work (I 
> > do that with a few other modules); as soon as it has been loaded once (even 
> > if it has not been used and/or has been unloaded), the kernel (2.6.14-rc5) is 
> > unable to enter ACPI S3. 
> 
> This may be the result of something we did but it's much more likely to
> be a change in the kernel.
> 
> What exactly happens when you try & fail to go to S3?

I can confirm this here (SUSE Linux 10.0, Kernel 2.6.13) - suspending
begins, but aborts at some point:

PM: Preparing system for suspend
Stopping tasks:
==================================================================================================================================
stopping tasks failed (1 tasks remaining)
Restarting tasks...<6> Strange, snd-bt-scod not stopped
done

It has been reported as BUG#1218671 in the bug tracker on SourceForge
some time ago:
http://sourceforge.net/tracker/index.php?func=detail&aid=1218671&group_id=116589&atid=678258

This report even contains a patch, but it does not seem to match/apply
anymore.

There is a second bug report, even though the subject line is misleading:
http://sourceforge.net/tracker/index.php?func=detail&aid=1170421&group_id=116589&atid=678258

Does anybody actually check the bug reports that are filed at Bug
Tracking system at http://sourceforge.net/projects/bluetooth-alsa/ :
http://sourceforge.net/tracker/?atid=678258&group_id=116589&func=browse

There are about 27 open bugs.

Bye,
	LenZ
- --
- ------------------------------------------------------------------
 Lenz Grimmer <lenz@grimmer.com>                             -o)
 [ICQ: 160767607 | Jabber: LenZGr@jabber.org]                /\\
 http://www.lenzg.org/                                       V_V
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDZg/rSVDhKrJykfIRAvzcAJ9YDcUCQtLlB1wDlikx1ZbK/6YOWgCfSnoc
xRVkKjjRUYuNpps/PaR4C/4=
=Ra14
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] snd-bt-sco module prevents ACPI S3

[Luca Capello]

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

Hello!

On Mon 31 Oct 2005 13:37 +0100, Lenz Grimmer wrote:
> Brad Midgley wrote:
>
>> > 1. It's name in the lsmod list is different from the module name,
>> > i.e.  modprobe and rmmod must be used with different names.
>> 
>> Do you want to submit a patch (or at least tell us what the
>> different names are?)
>
> The module file is named "snd-bt-sco.ko", while "lsmod" displays it
> as "snd_bt_sco". Not a biggie, but weird.

AFAIK this is the normal situation for *any* ALSA driver:
=====
gismo:/home/luca# lsmod | grep snd
snd_intel8x0           30272  0 
snd_intel8x0m          17732  0 
snd_ac97_codec         72444  2 snd_intel8x0,snd_intel8x0m
snd_pcm                78472  3
snd_intel8x0,snd_intel8x0m,snd_ac97_codec
snd_timer              21764  1 snd_pcm
snd                    48100  5
snd_intel8x0,snd_intel8x0m,snd_ac97_codec,snd_pcm,snd_timer
soundcore               8800  1 snd
snd_page_alloc          9604  3 snd_intel8x0,snd_intel8x0m,snd_pcm

gismo:/home/luca# modinfo snd [TAB]
snd                 snd-hpet            snd-mpu401
snd-rawmidi         snd-seq-midi        snd-timer           
snd-ac97-codec      snd-hwdep           snd-mpu401-uart
snd-rtctimer        snd-seq-midi-emul   snd-usb-audio       
snd-emu10k1         snd-intel8x0        snd-page-alloc
snd-seq             snd-seq-midi-event  snd-usb-lib         
snd-emu10k1-synth   snd-intel8x0m       snd-pcm
snd-seq-device      snd-seq-oss         snd-util-mem        
snd-emux-synth      snd-mixer-oss       snd-pcm-oss
snd-seq-dummy       snd-seq-virmidi     
=====

I don't know why, but it's so :-(

Thx, bye,
Gismo / Luca

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

Re: [Bluez-devel] snd-bt-sco module prevents ACPI S3

[Rene Mayrhofer]

[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]

Am Sunday 30 October 2005 23:30 schrieben Sie:
> > 1. It's name in the lsmod list is different from the module name, i.e.
> > modprobe and rmmod must be used with different names.
>
> Do you want to submit a patch (or at least tell us what the different
> names are?)
Checking again, the module file is called snd-bt-sco.ko, but in lsmod it 
appears as snd_bt_sco. I could probably find the problem in the code and 
submit a patch, unless anybody here knows already what needs to be changed.

> > 2. It breaks ACPI S3 (suspend to RAM), making it pretty much unusable on
> > laptops where S3 is used (like mine). Unloading snd-bt-sco does not work
> > (I do that with a few other modules); as soon as it has been loaded once
> > (even if it has not been used and/or has been unloaded), the kernel
> > (2.6.14-rc5) is unable to enter ACPI S3.
>
> This may be the result of something we did but it's much more likely to
> be a change in the kernel.
It did not work with previous kernels either. Can anybody confirm that 
snd-bt-sco and S3 work together?

> What exactly happens when you try & fail to go to S3?
It goes through all the steps until "Stopping all tasks" and then - instead of 
turning off - just continues as if the wakeup signal had been received 
immediately. The real wakeup signal (in my case, releasing the lid button) 
tries to suspend again, and fails again, i.e. the system immediately comes up 
again without switching off.

If you need more test data, I'll be able to test it on roughly a daily basis 
(although this means that I need to reboot that machine for every test, which 
I hardly ever do - therefore my need for a working S3).

regards,
Rene

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]