Bug 4815 - Dell latitude c610,Charger plug off/on hang the comp
Dell latitude c610,Charger plug off/on hang the comp
Status: REJECTED INSUFFICIENT_DATA
Product: ACPI
Classification: Unclassified
Component: Power-Processor
i386 Linux
: P2 high
Assigned To: acpi_power-processor
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-29 12:17 UTC by Jacek
Modified: 2005-07-21 06:02 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.12.1
Tree: Mainline
Regression: ---


Attachments

Description Jacek 2005-06-29 12:17:14 UTC
Distribution: Slackware 10.1

Hardware Environment: Dell Lltitude C610
/proc/cpu
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 11
model name      : Intel(R) Pentium(R) III Mobile CPU      1200MHz
stepping        : 1
cpu MHz         : 797.602
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat
pse36 mmx fxsr sse
bogomips        : 1581.05

256 Mb memory.

Software Environment: 
??? I have no idea what to write here but IMHO it has no influence to that bug.

Problem Description:

Computer hardly hangs up without any reaction except hadr power off.


Steps to reproduce:

This happens when you plug in or pluf off the external power source during
change of power source from batery to charger or other way.
It happens in any moment after kernel start even when it plug off/plug on is
done before any ide disk or orther periferial device is initialized.
Unfortunately no kernel crash datas is accessible.


This same action gives no crash on 2.6.11.12 with exactly this same .config.
Comment 1 Jacek 2005-06-29 13:44:40 UTC
I find out that the problem is somwhere elswhere - probably in some irda's
modules or Thompson Speedtouch module.

I will report where the problem is, when i find it, sorry for trouble.
Comment 2 Adrian Bunk 2005-07-21 06:02:41 UTC
I;m closing this bug.

Please reopen this bug if you've narrowed down what might cause it or can
provide additional data helping to debug it.

Note You need to log in before you can comment on or make changes to this bug.