linux-kernel - Something has gone aglay in the bluetooth build

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 31 Dec 2010 12:38:29 -0500
From:	gene heskett <gheskett@...v.com>
To:	linux-bluetooth@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Something has gone aglay in the bluetooth build

Greetings all;

AFAIK, std kernel build, but I am getting tons of errors when I try to 
modprobe the modules that 3 days ago, made rfcomm0 and a broadcom bt button 
work flawlessly.

But today, a sata cable failed (what else is new, I wish they would outlaw 
the importation of any far eastern cable product that uses that red dye in 
the jackets, its a damned time bomb and has been since at least 1972)

Anyway, after replacing the cable with another one just like it (snort) and 
of course doing a power down reboot to do that, my logs and screens are 
full of this sort of messages when attempting to bring this device to life.

from dmesg:

[ 2844.653595] usb 1-10.1.3: new full speed USB device using ehci_hcd and 
address 24
[ 2844.741717] usb 1-10.1.3: New USB device found, idVendor=0a5c, 
idProduct=2148
[ 2844.741721] usb 1-10.1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[ 2844.741725] usb 1-10.1.3: Product: BCM92046DG-CL1ROM
[ 2844.741727] usb 1-10.1.3: Manufacturer: Broadcom Corp
[ 2844.741729] usb 1-10.1.3: SerialNumber: 000272A176A4
[ 2844.766545] btusb: Unknown symbol hci_free_dev (err 0)
[ 2844.767534] btusb: Unknown symbol hci_alloc_dev (err 0)
[ 2844.767957] btusb: Unknown symbol hci_unregister_dev (err 0)
[ 2844.768322] btusb: Unknown symbol hci_recv_fragment (err 0)
[ 2844.768425] btusb: Unknown symbol hci_register_dev (err 0)
[ 2844.769378] btusb: Unknown symbol hci_free_dev (err 0)
[ 2844.770397] btusb: Unknown symbol hci_alloc_dev (err 0)
[ 2844.770822] btusb: Unknown symbol hci_unregister_dev (err 0)
[ 2844.771251] btusb: Unknown symbol hci_recv_fragment (err 0)
[ 2844.771353] btusb: Unknown symbol hci_register_dev (err 0)
[ 2844.772379] btusb: Unknown symbol hci_free_dev (err 0)
[ 2844.773400] btusb: Unknown symbol hci_alloc_dev (err 0)
[ 2844.773834] btusb: Unknown symbol hci_unregister_dev (err 0)
[ 2844.774209] btusb: Unknown symbol hci_recv_fragment (err 0)
[ 2844.774314] btusb: Unknown symbol hci_register_dev (err 0)
[ 2844.777025] btusb: Unknown symbol hci_free_dev (err 0)
[ 2844.778013] btusb: Unknown symbol hci_alloc_dev (err 0)
[ 2844.778435] btusb: Unknown symbol hci_unregister_dev (err 0)
[ 2844.778807] btusb: Unknown symbol hci_recv_fragment (err 0)
[ 2844.778908] btusb: Unknown symbol hci_register_dev (err 0)
[ 3102.216439] hci_uart: Unknown symbol hci_free_dev (err 0)
[ 3102.216892] hci_uart: Unknown symbol hci_alloc_dev (err 0)
[ 3102.217244] hci_uart: Unknown symbol hci_unregister_dev (err 0)
[ 3102.217345] hci_uart: Unknown symbol hci_recv_frame (err 0)
[ 3102.217575] hci_uart: Unknown symbol hci_register_dev (err 0)
[ 3102.217688] hci_uart: Unknown symbol hci_recv_stream_fragment (err 0)

And this is a freshly rebuilt 1.5 hours ago, 2.6.37-rc8 kernel, which 
reported only a few (5)section miss-matches during the build and install.

depmod -a -e `uname -r` output is a null return.

Does anyone have a clue to spare?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
nominal egg:
	New Yorkerese for expensive.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/