hald-addon-acpi[5115]: segfault at 0000000025c831f8...error 4, 2.6.22-9 kernel acpi segfault
Bug #130221 reported by
Snipersnest
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
hal (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
/var/log/syslog shows this
Aug 3 12:33:40 nate-laptop kernel: [ 190.347637] hald-addon-
I'm not sure if this is because I load the computer with the noacpi option.
description: | updated |
Changed in linux-source-2.6.22: | |
assignee: | nobody → ubuntu-kernel-acpi |
Changed in linux-source-2.6.22: | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Changed in linux: | |
status: | Unknown → Fix Released |
Changed in linux: | |
importance: | Unknown → Medium |
Changed in linux: | |
importance: | Medium → Unknown |
Changed in linux: | |
importance: | Unknown → Medium |
Changed in hal (Ubuntu): | |
assignee: | Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) → nobody |
To post a comment you must log in.
Are you using noacpi option because you had a problem without it?
If so, what was it? If not, please try without this option.
Is it LiveCD or installed system?
Is it Ubuntu or Kubuntu (or other)?
Which version?
Does it do that each time you use computer?
When?
Does the system works more or less normally after that?
If so, could you please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
4. Please run the command "sudo dmidecode > dmidecode.log" and attach the resulting file "dmidecode.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http:// wiki.ubuntu. com/KernelTeamB ugPolicies.
Thanks in advance!