Ubuntu
linux package

[Dell Inspiron 1011] compal-laptop module reports bluetooth device, even if not physically present

Bug #1100004 reported by Daniel Kessel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Low
Unassigned

Bug Description

The problem is that the compal-laptop module will ALWAYS create two rfkill entries, regardless of the presence of the hardware.

Upstream URL: http://<email address hidden>/msg04020.html

---
ApportVersion: 2.8-0ubuntu1
Architecture: i386
DistroRelease: Ubuntu 13.04
InstallationDate: Installed on 2013-01-14 (1 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130114)
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
Tags: raring running-unity
Uname: Linux 3.8.0-0-generic i686
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
---
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: daniel 1542 F.... lxpanel
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden
CurrentDmesg: [ 322.454275] perf samples too long (2520 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
DistroRelease: Ubuntu 13.10
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=93c1e22c-2bc9-420d-ab08-cd46637c2ed8
InstallationDate: Installed on 2013-11-30 (37 days ago)
InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MachineType: Dell Inc. Inspiron 1011
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=646ebbc1-911a-4c3f-be8f-736205501730 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-15-generic N/A
 linux-backports-modules-3.11.0-15-generic N/A
 linux-firmware 1.116
StagingDrivers: zram
Tags: saucy staging
Uname: Linux 3.11.0-15-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/29/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: CN0Y53
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A06
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/29/2009:svnDellInc.:pnInspiron1011:pvrA06:rvnDellInc.:rnCN0Y53:rvrA06:cvnDellInc.:ct8:cvrA06:
dmi.product.name: Inspiron 1011
dmi.product.version: A06
dmi.sys.vendor: Dell Inc.

See original description
Daniel Kessel (dkessel)
tags: added: apport-collected raring running-unity
description: updated
Revision history for this message
Stéphane Graber (stgraber) wrote :

We've been debugging this a bit in #ubuntu-devel, apparently the problem is that the compal-laptop module will ALWAYS create two rfkill entries, regardless of the actual hardware.

I tried doing "modprobe compal-laptop force" on a completely different piece of hardware and sure enough I got the two extra rfkill entries.

I believe this module is broken and should rely on ACPI or similar firmware functions to check whether the hardware actually exists.

Revision history for this message
Stéphane Graber (stgraber) wrote :

Can you please install the following packages:
acpidump fwts dmidecode iasl

And then run the following from an empty directory:
 - grep -r . /proc/acpi > acpi
 - sudo acpidump -o acpidump.txt
 - acpixtract acpidump.txt
 - iasl -d DSDT.dat
 - sudo fwts > fwts
 - sudo fwts method > fwts_method
 - sudo dmidecode > dmidecode.log

And attach all the files created in that directory to the bug.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1100004

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel Kessel (dkessel) wrote : Re: compal-laptop reports bluetooth device, even if there is none

grep -r . /proc/acpi > acpi

Revision history for this message
Daniel Kessel (dkessel) wrote :
Revision history for this message
Daniel Kessel (dkessel) wrote :
Revision history for this message
Daniel Kessel (dkessel) wrote :
  • DSDT.dat Edit (19.7 KiB, application/x-ns-proxy-autoconfig)
Revision history for this message
Daniel Kessel (dkessel) wrote :
Revision history for this message
Daniel Kessel (dkessel) wrote :
Revision history for this message
Daniel Kessel (dkessel) wrote :
Revision history for this message
Daniel Kessel (dkessel) wrote :
Revision history for this message
Daniel Kessel (dkessel) wrote :
Revision history for this message
Daniel Kessel (dkessel) wrote :
Revision history for this message
Daniel Kessel (dkessel) wrote :
Revision history for this message
Daniel Kessel (dkessel) wrote :

I cannot use apport-collect, as it will refuse to collect the data, displaying a message about an inofficial kernel. I am using the default kernel in raring.

Revision history for this message
Daniel Kessel (dkessel) wrote :

See comment in bug. apport-collect is impossible, but I attached log files as I was told.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Do you happen to know if this bug also existed in prior releases, or is this new to Raring?

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Daniel Kessel (dkessel) wrote :

I can confirm this also happens when booting from the current precise (12.04.1) iso image.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc3-raring/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Daniel Kessel (dkessel) wrote :

mainline kernel 3.8 rc3 does not fix the problem

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Daniel Kessel (dkessel) wrote :

I sent a mail to the mailing list, but the automatic connection from the mailing list to launchpad did not work.

The mailing list is: <email address hidden>
The mails sent to that list can be seen here: http://<email address hidden>/

I did not know in advance that I would've had to sign the message - so I got this response from Launchpad:

An error occurred while processing a mail you sent to Launchpad's email
interface.

Error message:

The message you sent included commands to modify the bug report,
but you didn't sign the message with an OpenPGP key that is
registered in Launchpad.

Revision history for this message
Daniel Kessel (dkessel) wrote :

There has been no response on the kernel platform driver mailing list.
This was the email I sent.
http://<email address hidden>/msg04020.html

Can we do anything to get some response?

penalvch (penalvch)
tags: added: precise quantal
Changed in linux (Ubuntu):
importance: Medium → Low
status: Triaged → Incomplete
Revision history for this message
Daniel Kessel (dkessel) wrote : AlsaInfo.txt

apport information

tags: added: saucy staging
description: updated
Revision history for this message
Daniel Kessel (dkessel) wrote : BootDmesg.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : IwConfig.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : Lspci.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : Lsusb.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : ProcEnviron.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : ProcModules.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : RfKill.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : UdevDb.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : UdevLog.txt

apport information

Revision history for this message
Daniel Kessel (dkessel) wrote : WifiSyslog.txt

apport information

penalvch (penalvch)
tags: added: latest-bios-a06 needs-trusty-test
Revision history for this message
Daniel Kessel (dkessel) wrote : Re: compal-laptop reports bluetooth device, even if there is none

The bug is still present. tested with current trusty daily kernel and upstream 3.13-rc7

tags: added: kernel-bug-exists-upstream-v3.13-rc7 trusty
removed: latest-bios-a06 needs-trusty-test
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: latest-bios-a06
summary: - compal-laptop reports bluetooth device, even if there is none
+ [Dell Inspiron 1011] Reports bluetooth device, even if there is none
description: updated
description: updated
Changed in linux (Ubuntu):
status: Confirmed → Triaged
penalvch (penalvch)
summary: - [Dell Inspiron 1011] Reports bluetooth device, even if there is none
+ [Dell Inspiron 1011] compal-laptop module reports bluetooth device, even
+ if not physically present
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.