From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Cc: Antonio-Blasco Bonito <blasco.bonito@email.it>
Subject: Re: [Bluez-devel] Fwd: alsa bluetooth module
Date: Thu, 17 Mar 2005 15:36:06 -0700 [thread overview]
Message-ID: <423A0656.3030409@xmission.com> (raw)
In-Reply-To: <e36f1e61ac13a554d52d2f7b8d7a5df4@freezone.co.uk>
hi
I have never seen the kcalloc error. Kernel taint is a bad sign... can
he reproduce it without loading anything that taints the kernel?
brad
ms419@freezone.co.uk wrote:
> I maintain a Debian package of bluetooth-alsa - for my convenience - but
> bluetooth-alsa is so popular, some others use this package also -
> http://cgi.sfu.ca/~jdbates/moin/moin.cgi/Bluetooth&ALSA
>
> Blasco contacted me with this problem, but truth is - I haven't got
> bluetooth-alsa working myself. Perhaps someone else can be more helpful
> to him?
>
> Many thanks!
>
> Jack
>
> Begin forwarded message:
>
>> From: Antonio-Blasco Bonito <blasco.bonito@email.it>
>> Date: March 17, 2005 4:02:35 AM PST
>> To: ms419@freezone.co.uk
>> Subject: Re: alsa bluetooth module
>
>
> [...]
>
>> I get:
>> # modprobe snd-bt-sco
>> FATAL: Error inserting snd_bt_sco
>> (/lib/modules/2.6.8-2-686/extra/snd-bt-sco.ko): Unknown symbol in
>> module, or unknown parameter (see dmesg)
>>
>> # dmesg|tail
>> ...
>> snd_bt_sco: no version for "struct_module" found: kernel tainted.
>> snd_bt_sco: Unknown symbol kcalloc
>>
>> I looked in alsa sources in the kernel and I only found
>> "snd_magic_kcalloc"
>> Maybe kcalloc calls should be renamed as such?
>>
>> Cheers,
>> Blasco
>> --
>> Email.it, the professional e-mail, gratis per te: http://www.email.it/f
>> Sponsor:
>> Bisogno di liquidità? Non devi spiegare per cosa. Fino a 4.000 € a
>> casa tua
>> Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2291&d=17-3
>>
>>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-deve
> l
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-03-17 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 22:05 [Bluez-devel] Fwd: alsa bluetooth module ms419
2005-03-17 22:34 ` Fredrik Tolf
2005-03-18 23:33 ` Antonio-Blasco Bonito
2005-03-19 14:18 ` Fredrik Tolf
2005-03-19 23:13 ` Antonio-Blasco Bonito
2005-03-17 22:36 ` Brad Midgley [this message]
2005-03-17 22:42 ` Fredrik Tolf
2005-03-17 22:45 ` Brad Midgley
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=423A0656.3030409@xmission.com \
--to=bmidgley@xmission.com \
--cc=blasco.bonito@email.it \
--cc=bluez-devel@lists.sourceforge.net \
/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