Bug 43008
| Summary: | soft lockup - CPU stuck for 23s! fan-off - Hewlett-Packard HP Compaq nc6400 | ||
|---|---|---|---|
| Product: | ACPI | Reporter: | tolostoi |
| Component: | Power-Fan | Assignee: | Aaron Lu (aaron.lu) |
| Status: | CLOSED INSUFFICIENT_DATA | ||
| Severity: | normal | CC: | aaron.lu, lenb |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.3.0-030300 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
dmesg with 3.3 kernel
kernel log dmesg after lock, hibernate, awake with 3.2 kernel kern.log after stuck, hibbernate and resume syslog 3.3 after stuck, hibernate and resume ACPI dump from Ubuntu's bug page submitted by user |
||
|
Description
tolostoi
2012-03-29 08:09:45 UTC
Created attachment 72740 [details]
dmesg with 3.3 kernel
Created attachment 72741 [details]
kernel log
broken in 3.0 and 3.3.
Did it work with any older kernels?
> DMI: Hewlett-Packard HP Compaq nc6400 (RH484EA#ABB)/30AC, BIOS 68YCD Ver.
> F.0B 09/05/2007
Is Sept 2007 the latest BIOS for this box?
Sounds like a timer issue.
Looks like this system is using the HPET --
have you tried disabling HPET it via "hpet=disable"?
I think this is the latest BIOS, but will check for sure. Always, with any kernel (with any distribution) this notebook worked perfectly. Now try with hpet=disable, and post the result. (In reply to comment #3) > broken in 3.0 and 3.3. > Did it work with any older kernels? > > > DMI: Hewlett-Packard HP Compaq nc6400 (RH484EA#ABB)/30AC, BIOS 68YCD Ver. > F.0B 09/05/2007 > > Is Sept 2007 the latest BIOS for this box? > > Sounds like a timer issue. > Looks like this system is using the HPET -- > have you tried disabling HPET it via "hpet=disable"? Broken with 3.0, 3.2 and 3.3 Yes, my BIOS ver is latest. From hp site: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=1847704&prodTypeId=321957&prodSeriesId=1847703&swLang=8&taskId=135&swEnvOID=1093#120 Latest is: F.0B 5 Sep 2007 # dmidecode 2.11 SMBIOS 2.4 present. 23 structures occupying 1032 bytes. Table at 0x000F3B77. Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: Hewlett-Packard Version: 68YCD Ver. F.0B Release Date: 09/05/2007 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 1024 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported 3.5"/720 kB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported LS-120 boot is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported BIOS Revision: 15.11 Firmware Revision: 86.54 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Hewlett-Packard Product Name: HP Compaq nc6400 (RH484EA#ABB) Version: F.0B Serial Number: CND6470R4M UUID: 00AF2E09-9D7A-DB11-189C-66990C425529 Wake-up Type: Power Switch SKU Number: RH484EA#ABB Family: 103C_5336AN Handle 0x0040, DMI type 126, 11 bytes Inactive Handle 0x0002, DMI type 2, 8 bytes Base Board Information Manufacturer: Hewlett-Packard Product Name: 30AC Version: KBC Version 56.36 Serial Number: Not Specified Handle 0x0003, DMI type 3, 13 bytes Chassis Information Manufacturer: Hewlett-Packard Type: Notebook Lock: Not Present Version: Not Specified Serial Number: CND6470R4M Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: External Interface Enabled Handle 0x0041, DMI type 126, 4 bytes Inactive Handle 0x0004, DMI type 4, 35 bytes Processor Information Socket Designation: U10 Type: Central Processor Family: Pentium M Manufacturer: Intel(R) ID: F6 06 00 00 FF FB EB BF Signature: Type 0, Family 6, Model 15, Stepping 6 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM (Thermal monitor supported) PBE (Pending break enabled) Version: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz Voltage: 1.1 V External Clock: 166 MHz Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: None L1 Cache Handle: 0x0005 L2 Cache Handle: 0x0006 L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Handle 0x0005, DMI type 7, 19 bytes Cache Information Socket Designation: Internal L1 Cache Configuration: Enabled, Not Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 64 kB Maximum Size: 64 kB Supported SRAM Types: Burst Installed SRAM Type: Burst Speed: Unknown Error Correction Type: Unknown System Type: Unified Associativity: 4-way Set-associative Handle 0x0006, DMI type 7, 19 bytes Cache Information Socket Designation: Internal L2 Cache Configuration: Enabled, Not Socketed, Level 2 Operational Mode: Write Back Location: External Installed Size: 4096 kB Maximum Size: 4096 kB Supported SRAM Types: Burst Installed SRAM Type: Burst Speed: Unknown Error Correction Type: None System Type: Unified Associativity: 4-way Set-associative Handle 0x0007, DMI type 9, 13 bytes System Slot Information Designation: PC CARD-Slot 0 Type: 32-bit PC Card (PCMCIA) Current Usage: Available Length: Short ID: Adapter 0, Socket 0 Characteristics: 5.0 V is provided 3.3 V is provided PC Card-16 is supported Cardbus is supported PME signal is supported Handle 0x0008, DMI type 10, 6 bytes On Board Device Information Type: Video Status: Disabled Description: Not Specified Handle 0x0009, DMI type 11, 5 bytes OEM Strings String 1: www.hp.com String 2: ABS 70/71 79 7A 7B 7C 7D Handle 0x000A, DMI type 16, 15 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 4 GB Error Information Handle: No Error Number Of Devices: 2 Handle 0x000B, DMI type 17, 27 bytes Memory Device Array Handle: 0x000A Error Information Handle: No Error Total Width: 64 bits Data Width: 64 bits Size: 1024 MB Form Factor: SODIMM Set: None Locator: DIMM #1 Bank Locator: Not Specified Type: DDR2 Type Detail: Synchronous Speed: 667 MHz Manufacturer: CE00000000000000 Serial Number: F636F1D4 Asset Tag: Not Specified Part Number: M4 70T2953CZ3-CE6 Handle 0x000C, DMI type 17, 27 bytes Memory Device Array Handle: 0x000A Error Information Handle: No Error Total Width: 64 bits Data Width: 64 bits Size: 1024 MB Form Factor: SODIMM Set: None Locator: DIMM #2 Bank Locator: Not Specified Type: DDR2 Type Detail: Synchronous Speed: 667 MHz Manufacturer: 7F7F7F7F7F510000 Serial Number: 03126824 Asset Tag: Not Specified Part Number: 64T128021EDL3SB2 Handle 0x000D, DMI type 19, 15 bytes Memory Array Mapped Address Starting Address: 0x00000000000 Ending Address: 0x0007FFFFFFF Range Size: 2 GB Physical Array Handle: 0x000A Partition Width: 2 Handle 0x000E, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x00000000000 Ending Address: 0x0003FFFFFFF Range Size: 1 GB Physical Device Handle: 0x000B Memory Array Mapped Address Handle: 0x000D Partition Row Position: 1 Handle 0x000F, DMI type 20, 19 bytes Memory Device Mapped Address Starting Address: 0x00040000000 Ending Address: 0x0007FFFFFFF Range Size: 1 GB Physical Device Handle: 0x000C Memory Array Mapped Address Handle: 0x000D Partition Row Position: 2 Handle 0x0010, DMI type 32, 11 bytes System Boot Information Status: No errors detected Handle 0x0085, DMI type 133, 34 bytes OEM-specific Type Header and Data: 85 22 85 00 01 EC 13 CA 0F 99 07 0A 00 9A 00 26 00 50 2B 9D F3 30 2A 02 C0 00 00 00 5E 0E 5E 0E 76 0E Strings: 19196 03/09/2011 HP Handle 0x0086, DMI type 126, 34 bytes Inactive Handle 0x0011, DMI type 144, 26 bytes OEM-specific Type Header and Data: 90 1A 11 00 CA 00 C1 00 13 01 3E 03 7D 00 CC 01 00 00 00 00 01 00 B8 04 00 00 Handle 0x0012, DMI type 127, 4 bytes End Of Table So, with hpet=disable, my screen lock again. I found, taht can login into virtual console, and hibernate the machine, after awake, can continue my work, the desktop is responsive. This test was with kernel 3.2 and hpet=disable, now test with 3.3 kernel. tolostoi@nb5nc6400ub:~$ cat /var/log/kern.log | grep acp Apr 2 20:32:23 nb5nc6400ub kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Apr 2 20:32:23 nb5nc6400ub kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Apr 2 20:32:23 nb5nc6400ub kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Apr 2 20:32:23 nb5nc6400ub kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Apr 2 20:32:23 nb5nc6400ub kernel: [ 0.484163] ACPI: acpi_idle registered with cpuidle Apr 2 20:32:23 nb5nc6400ub kernel: [ 30.478727] acpi device:03: registered as cooling_device13 Apr 3 10:20:35 nb5nc6400ub kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Apr 3 10:20:35 nb5nc6400ub kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Apr 3 10:20:35 nb5nc6400ub kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) Apr 3 10:20:35 nb5nc6400ub kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) Apr 3 10:20:35 nb5nc6400ub kernel: [ 0.404063] Switching to clocksource acpi_pm Apr 3 10:20:35 nb5nc6400ub kernel: [ 0.468237] ACPI: acpi_idle registered with cpuidle Apr 3 10:20:35 nb5nc6400ub kernel: [ 0.980664] hpet_acpi_add: no address or irqs in _CRS Apr 3 10:20:35 nb5nc6400ub kernel: [ 1.024509] acpi PNP0B00:00: hash matches Apr 3 10:20:35 nb5nc6400ub kernel: [ 30.285211] acpi device:03: registered as cooling_device13 Created attachment 72797 [details]
dmesg after lock, hibernate, awake with 3.2 kernel
Stuck with 3.3 kernel too :( Created attachment 72822 [details]
kern.log after stuck, hibbernate and resume
Created attachment 72823 [details]
syslog 3.3 after stuck, hibernate and resume
Hi, again. I re installed Ubuntu, now with x64. The problem still exist. This is the last what can see, after lock. Apr 8 23:30:55 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client 1130[0:0] has disconnected Apr 8 23:30:55 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client 6940[0:0] has disconnected If possible offer to me a workaround, please. uname -a Linux HP-Compaq-nc6400-RH484EA-ABB-tstoi 3.2.0-22-generic #35-Ubuntu SMP Tue Apr 3 18:33:15 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux tolostoi@HP-Compaq-nc6400-RH484EA-ABB-tstoi:~$ cat /var/log/syslog | grep acpid Apr 8 17:23:47 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: starting up with proc fs Apr 8 17:23:49 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 35 rules loaded Apr 8 17:23:49 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: waiting for events: event logging is off Apr 8 17:23:50 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client connected from 1119[0:0] Apr 8 17:23:50 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 1 client rule loaded Apr 8 18:21:00 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client 1119[0:0] has disconnected Apr 8 18:21:00 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client connected from 11571[0:0] Apr 8 18:21:00 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 1 client rule loaded Apr 8 22:52:06 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: starting up with proc fs Apr 8 22:52:08 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 35 rules loaded Apr 8 22:52:08 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: waiting for events: event logging is off Apr 8 22:52:08 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client connected from 1130[0:0] Apr 8 22:52:08 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 1 client rule loaded Apr 8 23:25:20 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client 1130[0:0] has disconnected Apr 8 23:27:55 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client connected from 1130[0:0] Apr 8 23:27:55 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 1 client rule loaded Apr 8 23:28:20 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client 1130[0:0] has disconnected Apr 8 23:28:20 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client connected from 1130[0:0] Apr 8 23:28:20 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 1 client rule loaded Apr 8 23:28:20 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client connected from 6887[0:0] Apr 8 23:28:20 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 1 client rule loaded Apr 8 23:29:21 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client 6887[0:0] has disconnected Apr 8 23:29:21 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client connected from 6909[0:0] Apr 8 23:29:21 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 1 client rule loaded Apr 8 23:29:43 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client 6909[0:0] has disconnected Apr 8 23:29:43 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client connected from 6940[0:0] Apr 8 23:29:43 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 1 client rule loaded Apr 8 23:30:55 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client 1130[0:0] has disconnected Apr 8 23:30:55 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client 6940[0:0] has disconnected Apr 8 23:31:42 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: starting up with proc fs Apr 8 23:31:42 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 35 rules loaded Apr 8 23:31:42 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: waiting for events: event logging is off Apr 8 23:31:42 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: client connected from 1119[0:0] Apr 8 23:31:42 HP-Compaq-nc6400-RH484EA-ABB-tstoi acpid: 1 client rule loaded Created attachment 105571 [details]
ACPI dump from Ubuntu's bug page submitted by user
What's the status of this bug, still lock from time to time? Thanks. Yes, from time to time, but very rarely. Now I'm with Ubuntu 13.04 x86 (kernel ... 3.8.0-23) I can't confirm theese rarely lockups is the same. (In reply to comment #15) > Yes, from time to time, but very rarely. > Now I'm with Ubuntu 13.04 x86 (kernel ... 3.8.0-23) > I can't confirm theese rarely lockups is the same. When it locks, does the computer feels hot? I would like to know if it is due to problem in FAN that caused this lock, thanks. I think is hot. It happened twice ... I leave it to work and when I get back is off, turn it on, and a red inscription (from BIOS) says, that has overheated. Can you please check, during normal use, does the thermal's temperature reads correct? Do the FANs work? Check thermal zone's temperature: $ cat /sys/class/thermal/thermal_zoneX/temp Turn on a FAN: $ sudo echo 1 > /sys/class/thermal/cooling_deviceX/cur_state Make sure the cooling_deviceX's type is FAN. |