Ubuntu
linux package

CPU turbo mode frequency issue with Kernel 3.11 under Saucy 13.10 (Intel I7)

Bug #1252462 reported by Guilhem Marchand
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Hi,

I am opening this bug because i'm suspecting my processor not to run under good frequencies under 13.10 with default kernel 3.11.

My computer is an Asus UX52VS running in Intel i7: Intel Core i7-3537U (See http://www.cpu-world.com/CPUs/Core_i7/Intel-Core%20i7-3537U%20Mobile%20processor%20-%20AV8063801119700.html)

It's normal frequency is 2 Ghz with a turbo mode up to 2,9 Ghz in case of CPU Load.

When running Kernel 3.11, cpufreq-info gives me following informations:

cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 775 MHz - 2.50 GHz
  available frequency steps: 2.50 GHz, 2.50 GHz, 2.40 GHz, 2.20 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 800 MHz, 775 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 775 MHz and 2.00 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.50 GHz (asserted by call to hardware).
  cpufreq stats: 2.50 GHz:-nan%, 2.50 GHz:-nan%, 2.40 GHz:-nan%, 2.20 GHz:-nan%, 2.10 GHz:-nan%, 2.00 GHz:-nan%, 1.90 GHz:-nan%, 1.70 GHz:-nan%, 1.60 GHz:-nan%, 1.50 GHz:-nan%, 1.30 GHz:-nan%, 1.20 GHz:-nan%, 1.10 GHz:-nan%, 1000 MHz:-nan%, 800 MHz:-nan%, 775 MHz:-nan% (582)
analyzing CPU 1:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 10.0 us.
  hardware limits: 775 MHz - 2.50 GHz
  available frequency steps: 2.50 GHz, 2.50 GHz, 2.40 GHz, 2.20 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 800 MHz, 775 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 775 MHz and 2.00 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.50 GHz (asserted by call to hardware).
  cpufreq stats: 2.50 GHz:-nan%, 2.50 GHz:-nan%, 2.40 GHz:-nan%, 2.20 GHz:-nan%, 2.10 GHz:-nan%, 2.00 GHz:-nan%, 1.90 GHz:-nan%, 1.70 GHz:-nan%, 1.60 GHz:-nan%, 1.50 GHz:-nan%, 1.30 GHz:-nan%, 1.20 GHz:-nan%, 1.10 GHz:-nan%, 1000 MHz:-nan%, 800 MHz:-nan%, 775 MHz:-nan% (958)
analyzing CPU 2:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 10.0 us.
  hardware limits: 775 MHz - 2.50 GHz
  available frequency steps: 2.50 GHz, 2.50 GHz, 2.40 GHz, 2.20 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 800 MHz, 775 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 775 MHz and 2.00 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.50 GHz (asserted by call to hardware).
  cpufreq stats: 2.50 GHz:-nan%, 2.50 GHz:-nan%, 2.40 GHz:-nan%, 2.20 GHz:-nan%, 2.10 GHz:-nan%, 2.00 GHz:-nan%, 1.90 GHz:-nan%, 1.70 GHz:-nan%, 1.60 GHz:-nan%, 1.50 GHz:-nan%, 1.30 GHz:-nan%, 1.20 GHz:-nan%, 1.10 GHz:-nan%, 1000 MHz:-nan%, 800 MHz:-nan%, 775 MHz:-nan% (439)
analyzing CPU 3:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 10.0 us.
  hardware limits: 775 MHz - 2.50 GHz
  available frequency steps: 2.50 GHz, 2.50 GHz, 2.40 GHz, 2.20 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 800 MHz, 775 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 775 MHz and 2.00 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 2.00 GHz (asserted by call to hardware).
  cpufreq stats: 2.50 GHz:-nan%, 2.50 GHz:-nan%, 2.40 GHz:-nan%, 2.20 GHz:-nan%, 2.10 GHz:-nan%, 2.00 GHz:-nan%, 1.90 GHz:-nan%, 1.70 GHz:-nan%, 1.60 GHz:-nan%, 1.50 GHz:-nan%, 1.30 GHz:-nan%, 1.20 GHz:-nan%, 1.10 GHz:-nan%, 1000 MHz:-nan%, 800 MHz:-nan%,

I don't understand why "frequency should be within 775 MHz and 2.00 GHz." ?

As far as i can see with various tools, the current frequency nevers goes up to 2 Ghz which is far away from the turbo hardware limit...

Another tool says almost the same:

analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 775 MHz - 2.50 GHz
  available frequency steps: 2.50 GHz, 2.50 GHz, 2.40 GHz, 2.20 GHz, 2.10 GHz, 2.00 GHz, 1.90 GHz, 1.70 GHz, 1.60 GHz, 1.50 GHz, 1.30 GHz, 1.20 GHz, 1.10 GHz, 1000 MHz, 800 MHz, 775 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 775 MHz and 2.00 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.60 GHz.
  cpufreq stats: 2.50 GHz:-nan%, 2.50 GHz:-nan%, 2.40 GHz:-nan%, 2.20 GHz:-nan%, 2.10 GHz:-nan%, 2.00 GHz:-nan%, 1.90 GHz:-nan%, 1.70 GHz:-nan%, 1.60 GHz:-nan%, 1.50 GHz:-nan%, 1.30 GHz:-nan%, 1.20 GHz:-nan%, 1.10 GHz:-nan%, 1000 MHz:-nan%, 800 MHz:-nan%, 775 MHz:-nan% (3159)
  boost state support:
    Supported: yes
    Active: yes
    25500 MHz max turbo 4 active cores
    25500 MHz max turbo 3 active cores
    25500 MHz max turbo 2 active cores
    25500 MHz max turbo 1 active cores

Running under very high CPU load, i can see using turbostat:

cor CPU %c0 GHz TSC SMI %c1 %c3 %c6 %c7 CTMP PTMP %pc2 %pc3 %pc6 %pc7 Pkg_W Cor_W GFX_W
         84.87 2.88 2.49 0 15.13 0.00 0.00 0.00 84 84 0.00 0.00 0.00 0.00 16.07 11.10 0.19
  0 0 78.49 2.88 2.50 0 21.51 0.00 0.00 0.00 81 84 0.00 0.00 0.00 0.00 16.07 11.10 0.19
  0 2 88.18 2.88 2.50 0 11.81
  1 1 80.60 2.88 2.49 0 19.40 0.00 0.00 0.00 84
  1 3 92.23 2.88 2.49 0 7.77
cor CPU %c0 GHz TSC SMI %c1 %c3 %c6 %c7 CTMP PTMP %pc2 %pc3 %pc6 %pc7 Pkg_W Cor_W GFX_W
         85.58 2.89 2.49 0 14.39 0.03 0.00 0.00 84 84 0.00 0.00 0.00 0.00 16.20 11.25 0.17
  0 0 92.59 2.89 2.49 0 7.36 0.05 0.00 0.00 82 84 0.00 0.00 0.00 0.00 16.20 11.25 0.17
  0 2 78.25 2.89 2.49 0 21.70
  1 1 85.93 2.89 2.49 0 14.07 0.00 0.00 0.00 84
  1 3 85.56 2.89 2.49 0 14.44
cor CPU %c0 GHz TSC SMI %c1 %c3 %c6 %c7 CTMP PTMP %pc2 %pc3 %pc6 %pc7 Pkg_W Cor_W GFX_W
         84.59 2.89 2.49 0 15.41 0.00 0.00 0.00 83 83 0.00 0.00 0.00 0.00 16.01 11.14 0.11
  0 0 95.59 2.89 2.49 0 4.41 0.00 0.00 0.00 81 83 0.00 0.00 0.00 0.00 16.01 11.14 0.11
  0 2 62.31 2.88 2.49 0 37.69
  1 1 87.46 2.89 2.49 0 12.54 0.00 0.00 0.00 83
  1 3 93.02 2.89 2.49 0 6.98

But, when using the last Kernel 3.12 (rc7) revision what i see is completely different!

With running kernel 3.12:

cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.90 GHz (asserted by call to hardware).
analyzing CPU 1:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.90 GHz (asserted by call to hardware).
analyzing CPU 2:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.90 GHz (asserted by call to hardware).
analyzing CPU 3:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.90 GHz (asserted by call to hardware).

As you can see the 2 kernels does not seem to use the same driver, intel_pstate for Kernel 3.12 and acpi-cpufreq for Kernel 3.11.

Reported speed are correct for Kernel 3.12 and the system works much better and more fluent, i can really feal the difference.

Frequency tools report a good frequency, going up to 3 Ghz under high CPU Load. (under Kernel 3.12 i can't use turbostat, gives me an error :
turbostat not found for kernel 3.12.0-031200rc7
You may need to install linux-tools-3.12.0-031200rc7-generic
)

So what does that mean ?
Is a 3.11 kernel unable to manage correctly that kind of processor ? Anything else to do to correct that ?

Many people have that kind of modern processor in recent laptops, i guess many shall be interested in...

Thank you in advance for your help !

---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: guilhem 2323 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=167b604e-be33-4115-84e6-f8956fea9fac
InstallationDate: Installed on 2013-11-18 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: ASUSTeK COMPUTER INC. UX52VS
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=3c164fba-bc7c-4e5f-b716-4006086b4efd ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-13-generic N/A
 linux-backports-modules-3.11.0-13-generic N/A
 linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 10/25/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX52VS.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX52VS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX52VS.202:bd10/25/2012:svnASUSTeKCOMPUTERINC.:pnUX52VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX52VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX52VS
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
---
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: guilhem 2087 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=167b604e-be33-4115-84e6-f8956fea9fac
InstallationDate: Installed on 2013-11-18 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: ASUSTeK COMPUTER INC. UX52VS
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=3c164fba-bc7c-4e5f-b716-4006086b4efd ro quiet splash intel_pstate=enable vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-13-generic N/A
 linux-backports-modules-3.11.0-13-generic N/A
 linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 10/25/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX52VS.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX52VS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX52VS.202:bd10/25/2012:svnASUSTeKCOMPUTERINC.:pnUX52VS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX52VS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX52VS
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

See original description
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1252462/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Brian Murray (brian-murray)
affects: ubuntu → linux (Ubuntu)
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 1252462

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
tags: added: saucy
Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : BootDmesg.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : CRDA.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : IwConfig.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : Lspci.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : Lsusb.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : ProcEnviron.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : ProcModules.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : PulseList.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : RfKill.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : UdevDb.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : UdevLog.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote :

Some update:

After some search, i discovered that the intel_pstate seems to have to be enable running default Ubuntu kernel adding :

/etc/default/grub

Add:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_pstate=enable"
 then sudo update-grub

After reboot, i can see the good configuration i was seing it with kernel 3.12:

cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to <email address hidden>, please.
analyzing CPU 0:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.18 GHz (asserted by call to hardware).
analyzing CPU 1:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 1
  CPUs which need to have their frequency coordinated by software: 1
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 3.03 GHz (asserted by call to hardware).
analyzing CPU 2:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 2
  CPUs which need to have their frequency coordinated by software: 2
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.40 GHz (asserted by call to hardware).
analyzing CPU 3:
  driver: intel_pstate
  CPUs which run at the same hardware frequency: 3
  CPUs which need to have their frequency coordinated by software: 3
  maximum transition latency: 0.97 ms.
  hardware limits: 800 MHz - 3.10 GHz
  available cpufreq governors: performance, powersave
  current policy: frequency should be within 800 MHz and 3.10 GHz.
                  The governor "powersave" may decide which speed to use
                  within this range.
  current CPU frequency is 2.55 GHz (asserted by call to hardware).

What does explain the difference between the 2 situations ?
With kernel 3.12 we don't have to manually enable intel_pstate... not sure most user would think about that to take all the benefit of last computers...

description: updated
Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : AlsaInfo.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : BootDmesg.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : CRDA.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : IwConfig.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : Lspci.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : Lsusb.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : ProcEnviron.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : ProcModules.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : PulseList.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : RfKill.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : UdevDb.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : UdevLog.txt

apport information

Revision history for this message
Guilhem Marchand (guilhem-marchand) wrote : WifiSyslog.txt

apport information

Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.