Freebsd-stable Archive

List Statistics

  • Total Threads: 2123
  • Total Posts: 4994
  #1  
03-05-2010 10:36 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #2  
03-05-2010 10:57 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #3  
03-05-2010 11:30 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #4  
03-05-2010 11:37 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #5  
03-05-2010 11:42 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #6  
04-05-2010 09:37 AM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #7  
04-05-2010 09:41 AM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #8  
04-05-2010 09:53 AM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #9  
04-05-2010 11:51 AM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #10  
04-05-2010 05:35 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #11  
04-05-2010 09:27 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. > On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>> Good news ! It worked, check the picture here :
>>
>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>
> Please try adding code fragment like this:
>        if (cx_next->p_lvlx == NULL)
>                printf("Going to panic.
");
> to  dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>    CPU_GET_REG(cx_next->p_lvlx, 1);
> line and see if it prints the message immediately before the panic.
>

Yes it does at the beginning of the kernel panic.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #12  
05-05-2010 01:19 AM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. > On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>> Good news ! It worked, check the picture here :
>>
>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>
> Please try adding code fragment like this:
>        if (cx_next->p_lvlx == NULL)
>                printf("Going to panic.
");
> to  dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>    CPU_GET_REG(cx_next->p_lvlx, 1);
> line and see if it prints the message immediately before the panic.
>

Yes it does at the beginning of the kernel panic.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 4 May 2010, at 21:38, Kostik Belousov wrote:

> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>> 2010/5/4 Kostik Belousov <>:
>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>> Good news ! It worked, check the picture here :
>>>>
>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>
>>> Please try adding code fragment like this:
>>> if (cx_next->p_lvlx == NULL)
>>> printf("Going to panic.\n");
>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>> line and see if it prints the message immediately before the panic.
>>>
>>
>> Yes it does at the beginning of the kernel panic.
>
> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> about the cause and possible solution.

I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #13  
05-05-2010 08:40 AM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. > On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>> Good news ! It worked, check the picture here :
>>
>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>
> Please try adding code fragment like this:
>        if (cx_next->p_lvlx == NULL)
>                printf("Going to panic.
");
> to  dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>    CPU_GET_REG(cx_next->p_lvlx, 1);
> line and see if it prints the message immediately before the panic.
>

Yes it does at the beginning of the kernel panic.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 4 May 2010, at 21:38, Kostik Belousov wrote:

> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>> 2010/5/4 Kostik Belousov <>:
>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>> Good news ! It worked, check the picture here :
>>>>
>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>
>>> Please try adding code fragment like this:
>>> if (cx_next->p_lvlx == NULL)
>>> printf("Going to panic.\n");
>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>> line and see if it prints the message immediately before the panic.
>>>
>>
>> Yes it does at the beginning of the kernel panic.
>
> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> about the cause and possible solution.

I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>
> > On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >> 2010/5/4 Kostik Belousov <>:
> >>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>> Good news ! It worked, check the picture here :
> >>>>
> >>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>
> >>> Please try adding code fragment like this:
> >>> if (cx_next->p_lvlx == NULL)
> >>> printf("Going to panic.\n");
> >>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>> line and see if it prints the message immediately before the panic.
> >>>
> >>
> >> Yes it does at the beginning of the kernel panic.
> >
> > Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> > With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> > about the cause and possible solution.
>
> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>

May 4 15:48:32 Melon power_profile: changed to 'economy'
May 4 15:48:35 Melon power_profile: changed to 'performance'

I think yes.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #14  
05-05-2010 10:49 AM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. > On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>> Good news ! It worked, check the picture here :
>>
>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>
> Please try adding code fragment like this:
>        if (cx_next->p_lvlx == NULL)
>                printf("Going to panic.
");
> to  dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>    CPU_GET_REG(cx_next->p_lvlx, 1);
> line and see if it prints the message immediately before the panic.
>

Yes it does at the beginning of the kernel panic.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 4 May 2010, at 21:38, Kostik Belousov wrote:

> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>> 2010/5/4 Kostik Belousov <>:
>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>> Good news ! It worked, check the picture here :
>>>>
>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>
>>> Please try adding code fragment like this:
>>> if (cx_next->p_lvlx == NULL)
>>> printf("Going to panic.\n");
>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>> line and see if it prints the message immediately before the panic.
>>>
>>
>> Yes it does at the beginning of the kernel panic.
>
> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> about the cause and possible solution.

I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>
> > On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >> 2010/5/4 Kostik Belousov <>:
> >>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>> Good news ! It worked, check the picture here :
> >>>>
> >>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>
> >>> Please try adding code fragment like this:
> >>> if (cx_next->p_lvlx == NULL)
> >>> printf("Going to panic.\n");
> >>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>> line and see if it prints the message immediately before the panic.
> >>>
> >>
> >> Yes it does at the beginning of the kernel panic.
> >
> > Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> > With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> > about the cause and possible solution.
>
> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>

May 4 15:48:32 Melon power_profile: changed to 'economy'
May 4 15:48:35 Melon power_profile: changed to 'performance'

I think yes.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 5 May 2010, at 08:40, Demelier David wrote:

> On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
>> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>>
>>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>>>> 2010/5/4 Kostik Belousov <>:
>>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>>>> Good news ! It worked, check the picture here :
>>>>>>
>>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>>>
>>>>> Please try adding code fragment like this:
>>>>> if (cx_next->p_lvlx == NULL)
>>>>> printf("Going to panic.\n");
>>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>>>> line and see if it prints the message immediately before the panic.
>>>>>
>>>>
>>>> Yes it does at the beginning of the kernel panic.
>>>
>>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
>>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
>>> about the cause and possible solution.
>>
>> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>>
>
> May 4 15:48:32 Melon power_profile: changed to 'economy'
> May 4 15:48:35 Melon power_profile: changed to 'performance'

I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #15  
05-05-2010 12:03 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. > On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>> Good news ! It worked, check the picture here :
>>
>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>
> Please try adding code fragment like this:
>        if (cx_next->p_lvlx == NULL)
>                printf("Going to panic.
");
> to  dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>    CPU_GET_REG(cx_next->p_lvlx, 1);
> line and see if it prints the message immediately before the panic.
>

Yes it does at the beginning of the kernel panic.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 4 May 2010, at 21:38, Kostik Belousov wrote:

> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>> 2010/5/4 Kostik Belousov <>:
>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>> Good news ! It worked, check the picture here :
>>>>
>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>
>>> Please try adding code fragment like this:
>>> if (cx_next->p_lvlx == NULL)
>>> printf("Going to panic.\n");
>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>> line and see if it prints the message immediately before the panic.
>>>
>>
>> Yes it does at the beginning of the kernel panic.
>
> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> about the cause and possible solution.

I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>
> > On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >> 2010/5/4 Kostik Belousov <>:
> >>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>> Good news ! It worked, check the picture here :
> >>>>
> >>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>
> >>> Please try adding code fragment like this:
> >>> if (cx_next->p_lvlx == NULL)
> >>> printf("Going to panic.\n");
> >>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>> line and see if it prints the message immediately before the panic.
> >>>
> >>
> >> Yes it does at the beginning of the kernel panic.
> >
> > Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> > With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> > about the cause and possible solution.
>
> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>

May 4 15:48:32 Melon power_profile: changed to 'economy'
May 4 15:48:35 Melon power_profile: changed to 'performance'

I think yes.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 5 May 2010, at 08:40, Demelier David wrote:

> On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
>> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>>
>>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>>>> 2010/5/4 Kostik Belousov <>:
>>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>>>> Good news ! It worked, check the picture here :
>>>>>>
>>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>>>
>>>>> Please try adding code fragment like this:
>>>>> if (cx_next->p_lvlx == NULL)
>>>>> printf("Going to panic.\n");
>>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>>>> line and see if it prints the message immediately before the panic.
>>>>>
>>>>
>>>> Yes it does at the beginning of the kernel panic.
>>>
>>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
>>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
>>> about the cause and possible solution.
>>
>> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>>
>
> May 4 15:48:32 Melon power_profile: changed to 'economy'
> May 4 15:48:35 Melon power_profile: changed to 'performance'

I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 10:49:23AM +0100, Rui Paulo wrote:
>
> On 5 May 2010, at 08:40, Demelier David wrote:
>
> > On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> >> On 4 May 2010, at 21:38, Kostik Belousov wrote:
> >>
> >>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >>>> 2010/5/4 Kostik Belousov <>:
> >>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>>>> Good news ! It worked, check the picture here :
> >>>>>>
> >>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>>>
> >>>>> Please try adding code fragment like this:
> >>>>> if (cx_next->p_lvlx == NULL)
> >>>>> printf("Going to panic.\n");
> >>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>>>> line and see if it prints the message immediately before the panic.
> >>>>>
> >>>>
> >>>> Yes it does at the beginning of the kernel panic.
> >>>
> >>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> >>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> >>> about the cause and possible solution.
> >>
> >> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
> >>
> >
> > May 4 15:48:32 Melon power_profile: changed to 'economy'
> > May 4 15:48:35 Melon power_profile: changed to 'performance'
>
> I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.
>

That is when I have ac unplugged :

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1200
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000
1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_usage: 7.22% 92.77% last 2482us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C2
dev.cpu.1.cx_usage: 5.55% 94.44% last 7724us

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #16  
05-05-2010 12:45 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. > On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>> Good news ! It worked, check the picture here :
>>
>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>
> Please try adding code fragment like this:
>        if (cx_next->p_lvlx == NULL)
>                printf("Going to panic.
");
> to  dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>    CPU_GET_REG(cx_next->p_lvlx, 1);
> line and see if it prints the message immediately before the panic.
>

Yes it does at the beginning of the kernel panic.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 4 May 2010, at 21:38, Kostik Belousov wrote:

> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>> 2010/5/4 Kostik Belousov <>:
>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>> Good news ! It worked, check the picture here :
>>>>
>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>
>>> Please try adding code fragment like this:
>>> if (cx_next->p_lvlx == NULL)
>>> printf("Going to panic.\n");
>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>> line and see if it prints the message immediately before the panic.
>>>
>>
>> Yes it does at the beginning of the kernel panic.
>
> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> about the cause and possible solution.

I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>
> > On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >> 2010/5/4 Kostik Belousov <>:
> >>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>> Good news ! It worked, check the picture here :
> >>>>
> >>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>
> >>> Please try adding code fragment like this:
> >>> if (cx_next->p_lvlx == NULL)
> >>> printf("Going to panic.\n");
> >>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>> line and see if it prints the message immediately before the panic.
> >>>
> >>
> >> Yes it does at the beginning of the kernel panic.
> >
> > Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> > With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> > about the cause and possible solution.
>
> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>

May 4 15:48:32 Melon power_profile: changed to 'economy'
May 4 15:48:35 Melon power_profile: changed to 'performance'

I think yes.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 5 May 2010, at 08:40, Demelier David wrote:

> On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
>> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>>
>>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>>>> 2010/5/4 Kostik Belousov <>:
>>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>>>> Good news ! It worked, check the picture here :
>>>>>>
>>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>>>
>>>>> Please try adding code fragment like this:
>>>>> if (cx_next->p_lvlx == NULL)
>>>>> printf("Going to panic.\n");
>>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>>>> line and see if it prints the message immediately before the panic.
>>>>>
>>>>
>>>> Yes it does at the beginning of the kernel panic.
>>>
>>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
>>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
>>> about the cause and possible solution.
>>
>> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>>
>
> May 4 15:48:32 Melon power_profile: changed to 'economy'
> May 4 15:48:35 Melon power_profile: changed to 'performance'

I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 10:49:23AM +0100, Rui Paulo wrote:
>
> On 5 May 2010, at 08:40, Demelier David wrote:
>
> > On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> >> On 4 May 2010, at 21:38, Kostik Belousov wrote:
> >>
> >>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >>>> 2010/5/4 Kostik Belousov <>:
> >>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>>>> Good news ! It worked, check the picture here :
> >>>>>>
> >>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>>>
> >>>>> Please try adding code fragment like this:
> >>>>> if (cx_next->p_lvlx == NULL)
> >>>>> printf("Going to panic.\n");
> >>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>>>> line and see if it prints the message immediately before the panic.
> >>>>>
> >>>>
> >>>> Yes it does at the beginning of the kernel panic.
> >>>
> >>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> >>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> >>> about the cause and possible solution.
> >>
> >> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
> >>
> >
> > May 4 15:48:32 Melon power_profile: changed to 'economy'
> > May 4 15:48:35 Melon power_profile: changed to 'performance'
>
> I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.
>

That is when I have ac unplugged :

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1200
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000
1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_usage: 7.22% 92.77% last 2482us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C2
dev.cpu.1.cx_usage: 5.55% 94.44% last 7724us

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Please try this patch:

Index: acpi_cpu.c
===================================================================
--- acpi_cpu.c (revision 207322)
+++ acpi_cpu.c (working copy)
@@ -997,12 +997,12 @@
if (notify != ACPI_NOTIFY_CX_STATES)
return;

+ ACPI_SERIAL_BEGIN(cpu);
/* Update the list of Cx states. */
acpi_cpu_cx_cst(sc);
acpi_cpu_cx_list(sc);

/* Update the new lowest useable Cx state for all CPUs. */
- ACPI_SERIAL_BEGIN(cpu);
cpu_cx_count = 0;
for (i = 0; i < cpu_ndevices; i++) {
isc = device_get_softc(cpu_devices[i]);


Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #17  
05-05-2010 02:57 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. > On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>> Good news ! It worked, check the picture here :
>>
>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>
> Please try adding code fragment like this:
>        if (cx_next->p_lvlx == NULL)
>                printf("Going to panic.
");
> to  dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>    CPU_GET_REG(cx_next->p_lvlx, 1);
> line and see if it prints the message immediately before the panic.
>

Yes it does at the beginning of the kernel panic.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 4 May 2010, at 21:38, Kostik Belousov wrote:

> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>> 2010/5/4 Kostik Belousov <>:
>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>> Good news ! It worked, check the picture here :
>>>>
>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>
>>> Please try adding code fragment like this:
>>> if (cx_next->p_lvlx == NULL)
>>> printf("Going to panic.\n");
>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>> line and see if it prints the message immediately before the panic.
>>>
>>
>> Yes it does at the beginning of the kernel panic.
>
> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> about the cause and possible solution.

I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>
> > On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >> 2010/5/4 Kostik Belousov <>:
> >>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>> Good news ! It worked, check the picture here :
> >>>>
> >>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>
> >>> Please try adding code fragment like this:
> >>> if (cx_next->p_lvlx == NULL)
> >>> printf("Going to panic.\n");
> >>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>> line and see if it prints the message immediately before the panic.
> >>>
> >>
> >> Yes it does at the beginning of the kernel panic.
> >
> > Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> > With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> > about the cause and possible solution.
>
> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>

May 4 15:48:32 Melon power_profile: changed to 'economy'
May 4 15:48:35 Melon power_profile: changed to 'performance'

I think yes.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 5 May 2010, at 08:40, Demelier David wrote:

> On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
>> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>>
>>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>>>> 2010/5/4 Kostik Belousov <>:
>>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>>>> Good news ! It worked, check the picture here :
>>>>>>
>>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>>>
>>>>> Please try adding code fragment like this:
>>>>> if (cx_next->p_lvlx == NULL)
>>>>> printf("Going to panic.\n");
>>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>>>> line and see if it prints the message immediately before the panic.
>>>>>
>>>>
>>>> Yes it does at the beginning of the kernel panic.
>>>
>>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
>>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
>>> about the cause and possible solution.
>>
>> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>>
>
> May 4 15:48:32 Melon power_profile: changed to 'economy'
> May 4 15:48:35 Melon power_profile: changed to 'performance'

I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 10:49:23AM +0100, Rui Paulo wrote:
>
> On 5 May 2010, at 08:40, Demelier David wrote:
>
> > On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> >> On 4 May 2010, at 21:38, Kostik Belousov wrote:
> >>
> >>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >>>> 2010/5/4 Kostik Belousov <>:
> >>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>>>> Good news ! It worked, check the picture here :
> >>>>>>
> >>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>>>
> >>>>> Please try adding code fragment like this:
> >>>>> if (cx_next->p_lvlx == NULL)
> >>>>> printf("Going to panic.\n");
> >>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>>>> line and see if it prints the message immediately before the panic.
> >>>>>
> >>>>
> >>>> Yes it does at the beginning of the kernel panic.
> >>>
> >>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> >>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> >>> about the cause and possible solution.
> >>
> >> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
> >>
> >
> > May 4 15:48:32 Melon power_profile: changed to 'economy'
> > May 4 15:48:35 Melon power_profile: changed to 'performance'
>
> I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.
>

That is when I have ac unplugged :

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1200
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000
1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_usage: 7.22% 92.77% last 2482us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C2
dev.cpu.1.cx_usage: 5.55% 94.44% last 7724us

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Please try this patch:

Index: acpi_cpu.c
===================================================================
--- acpi_cpu.c (revision 207322)
+++ acpi_cpu.c (working copy)
@@ -997,12 +997,12 @@
if (notify != ACPI_NOTIFY_CX_STATES)
return;

+ ACPI_SERIAL_BEGIN(cpu);
/* Update the list of Cx states. */
acpi_cpu_cx_cst(sc);
acpi_cpu_cx_list(sc);

/* Update the new lowest useable Cx state for all CPUs. */
- ACPI_SERIAL_BEGIN(cpu);
cpu_cx_count = 0;
for (i = 0; i < cpu_ndevices; i++) {
isc = device_get_softc(cpu_devices[i]);


Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 12:45:46PM +0100, Rui Paulo wrote:
> Please try this patch:
>
> Index: acpi_cpu.c
> ===================================================================
> --- acpi_cpu.c (revision 207322)
> +++ acpi_cpu.c (working copy)
> @@ -997,12 +997,12 @@
> if (notify != ACPI_NOTIFY_CX_STATES)
> return;
>
> + ACPI_SERIAL_BEGIN(cpu);
> /* Update the list of Cx states. */
> acpi_cpu_cx_cst(sc);
> acpi_cpu_cx_list(sc);
>
> /* Update the new lowest useable Cx state for all CPUs. */
> - ACPI_SERIAL_BEGIN(cpu);
> cpu_cx_count = 0;
> for (i = 0; i < cpu_ndevices; i++) {
> isc = device_get_softc(cpu_devices[i]);
>

Tested, but exactly same panic an backtrace.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #18  
05-05-2010 10:07 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. > On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>> Good news ! It worked, check the picture here :
>>
>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>
> Please try adding code fragment like this:
>        if (cx_next->p_lvlx == NULL)
>                printf("Going to panic.
");
> to  dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>    CPU_GET_REG(cx_next->p_lvlx, 1);
> line and see if it prints the message immediately before the panic.
>

Yes it does at the beginning of the kernel panic.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 4 May 2010, at 21:38, Kostik Belousov wrote:

> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>> 2010/5/4 Kostik Belousov <>:
>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>> Good news ! It worked, check the picture here :
>>>>
>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>
>>> Please try adding code fragment like this:
>>> if (cx_next->p_lvlx == NULL)
>>> printf("Going to panic.\n");
>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>> line and see if it prints the message immediately before the panic.
>>>
>>
>> Yes it does at the beginning of the kernel panic.
>
> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> about the cause and possible solution.

I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>
> > On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >> 2010/5/4 Kostik Belousov <>:
> >>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>> Good news ! It worked, check the picture here :
> >>>>
> >>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>
> >>> Please try adding code fragment like this:
> >>> if (cx_next->p_lvlx == NULL)
> >>> printf("Going to panic.\n");
> >>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>> line and see if it prints the message immediately before the panic.
> >>>
> >>
> >> Yes it does at the beginning of the kernel panic.
> >
> > Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> > With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> > about the cause and possible solution.
>
> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>

May 4 15:48:32 Melon power_profile: changed to 'economy'
May 4 15:48:35 Melon power_profile: changed to 'performance'

I think yes.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 5 May 2010, at 08:40, Demelier David wrote:

> On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
>> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>>
>>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>>>> 2010/5/4 Kostik Belousov <>:
>>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>>>> Good news ! It worked, check the picture here :
>>>>>>
>>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>>>
>>>>> Please try adding code fragment like this:
>>>>> if (cx_next->p_lvlx == NULL)
>>>>> printf("Going to panic.\n");
>>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>>>> line and see if it prints the message immediately before the panic.
>>>>>
>>>>
>>>> Yes it does at the beginning of the kernel panic.
>>>
>>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
>>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
>>> about the cause and possible solution.
>>
>> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>>
>
> May 4 15:48:32 Melon power_profile: changed to 'economy'
> May 4 15:48:35 Melon power_profile: changed to 'performance'

I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 10:49:23AM +0100, Rui Paulo wrote:
>
> On 5 May 2010, at 08:40, Demelier David wrote:
>
> > On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> >> On 4 May 2010, at 21:38, Kostik Belousov wrote:
> >>
> >>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >>>> 2010/5/4 Kostik Belousov <>:
> >>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>>>> Good news ! It worked, check the picture here :
> >>>>>>
> >>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>>>
> >>>>> Please try adding code fragment like this:
> >>>>> if (cx_next->p_lvlx == NULL)
> >>>>> printf("Going to panic.\n");
> >>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>>>> line and see if it prints the message immediately before the panic.
> >>>>>
> >>>>
> >>>> Yes it does at the beginning of the kernel panic.
> >>>
> >>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> >>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> >>> about the cause and possible solution.
> >>
> >> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
> >>
> >
> > May 4 15:48:32 Melon power_profile: changed to 'economy'
> > May 4 15:48:35 Melon power_profile: changed to 'performance'
>
> I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.
>

That is when I have ac unplugged :

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1200
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000
1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_usage: 7.22% 92.77% last 2482us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C2
dev.cpu.1.cx_usage: 5.55% 94.44% last 7724us

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Please try this patch:

Index: acpi_cpu.c
===================================================================
--- acpi_cpu.c (revision 207322)
+++ acpi_cpu.c (working copy)
@@ -997,12 +997,12 @@
if (notify != ACPI_NOTIFY_CX_STATES)
return;

+ ACPI_SERIAL_BEGIN(cpu);
/* Update the list of Cx states. */
acpi_cpu_cx_cst(sc);
acpi_cpu_cx_list(sc);

/* Update the new lowest useable Cx state for all CPUs. */
- ACPI_SERIAL_BEGIN(cpu);
cpu_cx_count = 0;
for (i = 0; i < cpu_ndevices; i++) {
isc = device_get_softc(cpu_devices[i]);


Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 12:45:46PM +0100, Rui Paulo wrote:
> Please try this patch:
>
> Index: acpi_cpu.c
> ===================================================================
> --- acpi_cpu.c (revision 207322)
> +++ acpi_cpu.c (working copy)
> @@ -997,12 +997,12 @@
> if (notify != ACPI_NOTIFY_CX_STATES)
> return;
>
> + ACPI_SERIAL_BEGIN(cpu);
> /* Update the list of Cx states. */
> acpi_cpu_cx_cst(sc);
> acpi_cpu_cx_list(sc);
>
> /* Update the new lowest useable Cx state for all CPUs. */
> - ACPI_SERIAL_BEGIN(cpu);
> cpu_cx_count = 0;
> for (i = 0; i < cpu_ndevices; i++) {
> isc = device_get_softc(cpu_devices[i]);
>

Tested, but exactly same panic an backtrace.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Would you be so kind to try to revert this patch?
I'm just guessing

You have to pass -R flag to patch program to apply the patch

=========================

--- head/sys/dev/acpica/acpi_acad.c 2009/06/05 18:44:36 193530
+++ head/sys/dev/acpica/acpi_acad.c 2009/09/30 17:07:49 197649
@@ -109,13 +109,14 @@
ACPI_SERIAL_BEGIN(acad);
if (newstatus != -1 && sc->status != newstatus) {
sc->status = newstatus;
+ ACPI_SERIAL_END(acad);
power_profile_set_state(newstatus ? POWER_PROFILE_PERFORMANCE :
POWER_PROFILE_ECONOMY);
ACPI_VPRINT(dev, acpi_device_get_parent_softc(dev),
"%s Line\n", newstatus ? "On" : "Off");
acpi_UserNotify("ACAD", h, newstatus);
- }
- ACPI_SERIAL_END(acad);
+ } else
+ ACPI_SERIAL_END(acad);
}

static void
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #19  
07-05-2010 07:33 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. > On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>> Good news ! It worked, check the picture here :
>>
>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>
> Please try adding code fragment like this:
>        if (cx_next->p_lvlx == NULL)
>                printf("Going to panic.
");
> to  dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>    CPU_GET_REG(cx_next->p_lvlx, 1);
> line and see if it prints the message immediately before the panic.
>

Yes it does at the beginning of the kernel panic.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 4 May 2010, at 21:38, Kostik Belousov wrote:

> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>> 2010/5/4 Kostik Belousov <>:
>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>> Good news ! It worked, check the picture here :
>>>>
>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>
>>> Please try adding code fragment like this:
>>> if (cx_next->p_lvlx == NULL)
>>> printf("Going to panic.\n");
>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>> line and see if it prints the message immediately before the panic.
>>>
>>
>> Yes it does at the beginning of the kernel panic.
>
> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> about the cause and possible solution.

I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>
> > On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >> 2010/5/4 Kostik Belousov <>:
> >>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>> Good news ! It worked, check the picture here :
> >>>>
> >>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>
> >>> Please try adding code fragment like this:
> >>> if (cx_next->p_lvlx == NULL)
> >>> printf("Going to panic.\n");
> >>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>> line and see if it prints the message immediately before the panic.
> >>>
> >>
> >> Yes it does at the beginning of the kernel panic.
> >
> > Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> > With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> > about the cause and possible solution.
>
> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>

May 4 15:48:32 Melon power_profile: changed to 'economy'
May 4 15:48:35 Melon power_profile: changed to 'performance'

I think yes.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 5 May 2010, at 08:40, Demelier David wrote:

> On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
>> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>>
>>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>>>> 2010/5/4 Kostik Belousov <>:
>>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>>>> Good news ! It worked, check the picture here :
>>>>>>
>>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>>>
>>>>> Please try adding code fragment like this:
>>>>> if (cx_next->p_lvlx == NULL)
>>>>> printf("Going to panic.\n");
>>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>>>> line and see if it prints the message immediately before the panic.
>>>>>
>>>>
>>>> Yes it does at the beginning of the kernel panic.
>>>
>>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
>>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
>>> about the cause and possible solution.
>>
>> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>>
>
> May 4 15:48:32 Melon power_profile: changed to 'economy'
> May 4 15:48:35 Melon power_profile: changed to 'performance'

I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 10:49:23AM +0100, Rui Paulo wrote:
>
> On 5 May 2010, at 08:40, Demelier David wrote:
>
> > On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> >> On 4 May 2010, at 21:38, Kostik Belousov wrote:
> >>
> >>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >>>> 2010/5/4 Kostik Belousov <>:
> >>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>>>> Good news ! It worked, check the picture here :
> >>>>>>
> >>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>>>
> >>>>> Please try adding code fragment like this:
> >>>>> if (cx_next->p_lvlx == NULL)
> >>>>> printf("Going to panic.\n");
> >>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>>>> line and see if it prints the message immediately before the panic.
> >>>>>
> >>>>
> >>>> Yes it does at the beginning of the kernel panic.
> >>>
> >>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> >>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> >>> about the cause and possible solution.
> >>
> >> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
> >>
> >
> > May 4 15:48:32 Melon power_profile: changed to 'economy'
> > May 4 15:48:35 Melon power_profile: changed to 'performance'
>
> I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.
>

That is when I have ac unplugged :

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1200
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000
1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_usage: 7.22% 92.77% last 2482us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C2
dev.cpu.1.cx_usage: 5.55% 94.44% last 7724us

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Please try this patch:

Index: acpi_cpu.c
===================================================================
--- acpi_cpu.c (revision 207322)
+++ acpi_cpu.c (working copy)
@@ -997,12 +997,12 @@
if (notify != ACPI_NOTIFY_CX_STATES)
return;

+ ACPI_SERIAL_BEGIN(cpu);
/* Update the list of Cx states. */
acpi_cpu_cx_cst(sc);
acpi_cpu_cx_list(sc);

/* Update the new lowest useable Cx state for all CPUs. */
- ACPI_SERIAL_BEGIN(cpu);
cpu_cx_count = 0;
for (i = 0; i < cpu_ndevices; i++) {
isc = device_get_softc(cpu_devices[i]);


Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 12:45:46PM +0100, Rui Paulo wrote:
> Please try this patch:
>
> Index: acpi_cpu.c
> ===================================================================
> --- acpi_cpu.c (revision 207322)
> +++ acpi_cpu.c (working copy)
> @@ -997,12 +997,12 @@
> if (notify != ACPI_NOTIFY_CX_STATES)
> return;
>
> + ACPI_SERIAL_BEGIN(cpu);
> /* Update the list of Cx states. */
> acpi_cpu_cx_cst(sc);
> acpi_cpu_cx_list(sc);
>
> /* Update the new lowest useable Cx state for all CPUs. */
> - ACPI_SERIAL_BEGIN(cpu);
> cpu_cx_count = 0;
> for (i = 0; i < cpu_ndevices; i++) {
> isc = device_get_softc(cpu_devices[i]);
>

Tested, but exactly same panic an backtrace.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Would you be so kind to try to revert this patch?
I'm just guessing

You have to pass -R flag to patch program to apply the patch

=========================

--- head/sys/dev/acpica/acpi_acad.c 2009/06/05 18:44:36 193530
+++ head/sys/dev/acpica/acpi_acad.c 2009/09/30 17:07:49 197649
@@ -109,13 +109,14 @@
ACPI_SERIAL_BEGIN(acad);
if (newstatus != -1 && sc->status != newstatus) {
sc->status = newstatus;
+ ACPI_SERIAL_END(acad);
power_profile_set_state(newstatus ? POWER_PROFILE_PERFORMANCE :
POWER_PROFILE_ECONOMY);
ACPI_VPRINT(dev, acpi_device_get_parent_softc(dev),
"%s Line\n", newstatus ? "On" : "Off");
acpi_UserNotify("ACAD", h, newstatus);
- }
- ACPI_SERIAL_END(acad);
+ } else
+ ACPI_SERIAL_END(acad);
}

static void
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Le Vendredi 07 mai 2010 à 18:22 +0200, Giovanni Trematerra a écrit :
> On Fri, May 7, 2010 at 2:08 PM, Demelier David <> wrote:
> > Hi,
> > I noticed that pluggin the AC adaptor when I boot without it does not
> > panic. It only panic when removing it.
> >
> > Maybe that could help ?
> >
>
> Good to know. The problem lies somewhere when performance state change.
> In your case it happens when you remove AC adaptor. Let's hope someone on
> acpi@ ml comes up with a good idea.
>

Okay so for the moment no change, I'll wait for someone with an idea
that could solve my problem. For me because the panic only happens when
changing profile from ac plugged -> ac unplugged (and not the reverse) I
would think it's a cpu related acpi issue.

David.

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.

  #20  
07-05-2010 08:26 PM
Freebsd-stable member admin is online now
User
 

Hi,

I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?

It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/3 David DEMELIER <>:
> Hi,
>
> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> this related to the cpufreq and related stuff ?
>
> It also says cannot dump. Device not defined or unavailable so I can't
> give you more infos now.
>

I can confirm that :

#performance_cx_lowest="HIGH"
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest="LOW"
#economy_cpu_freq=${economy_cx_lowest}

in rc.conf was the problem.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 2:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Set dumpdev in /boot/loader.conf to your swap device, reboot, and
then try to reproduce the issue.
Cheers,
-Garrett
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 3, 2010 at 4:57 PM, David DEMELIER <> wrote:
> 2010/5/3 David DEMELIER <>:
>> Hi,
>>
>> I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
>> panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
>> this related to the cpufreq and related stuff ?
>>
>> It also says cannot dump. Device not defined or unavailable so I can't
>> give you more infos now.
>>
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

Can you get a backtrace? I've been experiencing something strange
lately after applying optimization settings from:

http://wiki.freebsd.org/TuningPowerConsumption

I can't get a useful dump either, the machine is idle, and the
backtrace is strange to me:

db> show allpcpu

Current CPU: 0

cpuid = 0
dynamic pcpu = 0x692d00
curthread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpcb = 0xffffff8000039d40
fpcurthread = none
idlethread = 0xffffff0001507390: pid 11 "idle: cpu0"
curpmap = 0
tssp = 0xffffffff80840580
commontssp = 0xffffffff80840580
rsp0 = 0xffffff8000039d40
gs32p = 0xffffffff8083f3b8
ldt = 0xffffffff8083f3f8
tss = 0xffffffff8083f3e8

cpuid = 1
dynamic pcpu = 0xffffff807f85ed00
curthread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpcb = 0xffffff8000034d40
fpcurthread = none
idlethread = 0xffffff0001507720: pid 11 "idle: cpu1"
curpmap = 0
tssp = 0xffffffff808405e8
commontssp = 0xffffffff808405e8
rsp0 = 0xffffff8000034d40
gs32p = 0xffffffff8083f420
ldt = 0xffffffff8083f460
tss = 0xffffffff8083f450

db> bt

Tracing pid 11 tid 100004 td 0xffffff0001507390
rman_get_bushandle() at rman_get_bushandle+0x1
sched_idletd() at sched_idletd+0x123
fork_exit() at fork_exit+0x118
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8000039d30, rbp = 0 ---

-Brandon
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Mon, May 03, 2010 at 11:57:28PM +0200, David DEMELIER wrote:
> 2010/5/3 David DEMELIER <>:
> > Hi,
> >
> > I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
> > panics when I unplug my AC.  The current process = 11 (idle: cpu1) is
> > this related to the cpufreq and related stuff ?
> >
> > It also says cannot dump. Device not defined or unavailable so I can't
> > give you more infos now.
> >
>
> I can confirm that :
>
> #performance_cx_lowest="HIGH"
> #performance_cpu_freq=${performance_cx_lowest}
> #economy_cx_lowest="LOW"
> #economy_cpu_freq=${economy_cx_lowest}
>
> in rc.conf was the problem.

When these are commented out, can you provide the output from:

sysctl -a dev.cpu

Can you confirm whether or not powerd(8) is in use on this system when
it panics? If so, does the problem go away if you disable powerd(8) but
leave in (uncommented) the above rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> not panic anymore ...
>
> I'm not lucky (or ?).

1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
Putting in in /boot/loader.conf will change/do nothing. You should
probably be using 'dumpdev="auto"' anyway (it then uses whatever you
define as swap in /etc/fstab).

2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
setting dumpdev shouldn't fix your problem. I think it's a red herring.

3) You sent the above to me directly; please keep the mailing list CC'd,
as others need to know what you've tried/done. Thanks.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. 2010/5/4 Jeremy Chadwick <>:
> On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
>> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
>> not panic anymore ...
>>
>> I'm not lucky (or ?).
>
> 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> Putting in in /boot/loader.conf will change/do nothing.  You should
> probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> define as swap in /etc/fstab).
>
> 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> setting dumpdev shouldn't fix your problem.  I think it's a red herring.
>
> 3) You sent the above to me directly; please keep the mailing list CC'd,
> as others need to know what you've tried/done.  Thanks.
>

Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
was Garett who told me to add it to loader.conf.

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us

(I used Cc: entry I hope it sends to all)

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Tue, May 04, 2010 at 10:41:18AM +0200, David DEMELIER wrote:
> 2010/5/4 Jeremy Chadwick <>:
> > On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote:
> >> Since I added dumpdev="/dev/ad4s1b" in my /boot/loader.conf it does
> >> not panic anymore ...
> >>
> >> I'm not lucky (or ?).
> >
> > 1) dumpdev="****" should go into /etc/rc.conf, not /boot/loader.conf.
> > Putting in in /boot/loader.conf will change/do nothing.  You should
> > probably be using 'dumpdev="auto"' anyway (it then uses whatever you
> > define as swap in /etc/fstab).
> >
> > 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf,
> > setting dumpdev shouldn't fix your problem.  I think it's a red herring.
> >
> > 3) You sent the above to me directly; please keep the mailing list CC'd,
> > as others need to know what you've tried/done.  Thanks.
>
> Yes I also added dumpdev="AUTO" in /etc/rc.conf at the beginning. That
> was Garett who told me to add it to loader.conf.

I think he meant /etc/rc.conf. That's okay -- mistakes happen.

All dumpdev="auto" will do is configure FreeBSD to automatically dump
all kernel memory to swap + reboot the system. When FreeBSD next boots,
it will use savecore(8) to save the contents of swap to a series of
files in /var/crash for later debugging.

> $ sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 2101
> dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
> dev.cpu.0.cx_supported: C1/1 C2/57
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
> dev.cpu.1.%desc: ACPI CPU
> dev.cpu.1.%driver: cpu
> dev.cpu.1.%location: handle=\_PR_.CPU1
> dev.cpu.1.%pnpinfo: _HID=none _UID=0
> dev.cpu.1.%parent: acpi0
> dev.cpu.1.cx_supported: C1/1 C2/57
> dev.cpu.1.cx_lowest: C1
> dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
>
> (I used Cc: entry I hope it sends to all)

Can you confirm whether or not powerd(8) is in use on this system when
it panics?

If so, does the problem go away if you disable powerd(8) but leave in
(uncommented) the performance_* and economy_* rc.conf settings?

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. I made a panic and it said Dumping 1176Mb but even after 5 minutes
there was no output. Usually you'll have something like Dumping
1176Mb: 1176 1040 960 ... etc ?

Here it's stays at Dumping 1176Mb: and no changes.

Cheers,
David.
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Good news ! It worked, check the picture here :

http://img63.imageshack.us/img63/4244/dsc00361g.jpg
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. > On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>> Good news ! It worked, check the picture here :
>>
>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>
> Please try adding code fragment like this:
>        if (cx_next->p_lvlx == NULL)
>                printf("Going to panic.
");
> to  dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>    CPU_GET_REG(cx_next->p_lvlx, 1);
> line and see if it prints the message immediately before the panic.
>

Yes it does at the beginning of the kernel panic.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 4 May 2010, at 21:38, Kostik Belousov wrote:

> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>> 2010/5/4 Kostik Belousov <>:
>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>> Good news ! It worked, check the picture here :
>>>>
>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>
>>> Please try adding code fragment like this:
>>> if (cx_next->p_lvlx == NULL)
>>> printf("Going to panic.\n");
>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>> line and see if it prints the message immediately before the panic.
>>>
>>
>> Yes it does at the beginning of the kernel panic.
>
> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> about the cause and possible solution.

I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>
> > On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >> 2010/5/4 Kostik Belousov <>:
> >>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>> Good news ! It worked, check the picture here :
> >>>>
> >>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>
> >>> Please try adding code fragment like this:
> >>> if (cx_next->p_lvlx == NULL)
> >>> printf("Going to panic.\n");
> >>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>> line and see if it prints the message immediately before the panic.
> >>>
> >>
> >> Yes it does at the beginning of the kernel panic.
> >
> > Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> > With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> > about the cause and possible solution.
>
> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>

May 4 15:48:32 Melon power_profile: changed to 'economy'
May 4 15:48:35 Melon power_profile: changed to 'performance'

I think yes.

King regards.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On 5 May 2010, at 08:40, Demelier David wrote:

> On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
>> On 4 May 2010, at 21:38, Kostik Belousov wrote:
>>
>>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
>>>> 2010/5/4 Kostik Belousov <>:
>>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
>>>>>> Good news ! It worked, check the picture here :
>>>>>>
>>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
>>>>>
>>>>> Please try adding code fragment like this:
>>>>> if (cx_next->p_lvlx == NULL)
>>>>> printf("Going to panic.\n");
>>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
>>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
>>>>> line and see if it prints the message immediately before the panic.
>>>>>
>>>>
>>>> Yes it does at the beginning of the kernel panic.
>>>
>>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
>>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
>>> about the cause and possible solution.
>>
>> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
>>
>
> May 4 15:48:32 Melon power_profile: changed to 'economy'
> May 4 15:48:35 Melon power_profile: changed to 'performance'

I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.

Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 10:49:23AM +0100, Rui Paulo wrote:
>
> On 5 May 2010, at 08:40, Demelier David wrote:
>
> > On Wed, May 05, 2010 at 01:19:45AM +0100, Rui Paulo wrote:
> >> On 4 May 2010, at 21:38, Kostik Belousov wrote:
> >>
> >>> On Tue, May 04, 2010 at 10:27:23PM +0200, David DEMELIER wrote:
> >>>> 2010/5/4 Kostik Belousov <>:
> >>>>> On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote:
> >>>>>> Good news ! It worked, check the picture here :
> >>>>>>
> >>>>>> http://img63.imageshack.us/img63/4244/dsc00361g.jpg
> >>>>>
> >>>>> Please try adding code fragment like this:
> >>>>> if (cx_next->p_lvlx == NULL)
> >>>>> printf("Going to panic.\n");
> >>>>> to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before
> >>>>> CPU_GET_REG(cx_next->p_lvlx, 1);
> >>>>> line and see if it prints the message immediately before the panic.
> >>>>>
> >>>>
> >>>> Yes it does at the beginning of the kernel panic.
> >>>
> >>> Ok, so the point of panic is found, it is NULL cx_next->p_lvlx resource.
> >>> With the data in hand, I recommend you to ask on acpi@ (added a Cc:)
> >>> about the cause and possible solution.
> >>
> >> I don't remember the details, but I've seen this before. Does your CPU Cx levels change when you plug/unplug the AC adapter?
> >>
> >
> > May 4 15:48:32 Melon power_profile: changed to 'economy'
> > May 4 15:48:35 Melon power_profile: changed to 'performance'
>
> I wasn't asking about the profiles. Show us the output of sysctl dev.cpu with and without the AC cord plugged in.
>

That is when I have ac unplugged :

$ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1200
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000
1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C2
dev.cpu.0.cx_usage: 7.22% 92.77% last 2482us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C2
dev.cpu.1.cx_usage: 5.55% 94.44% last 7724us

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Please try this patch:

Index: acpi_cpu.c
===================================================================
--- acpi_cpu.c (revision 207322)
+++ acpi_cpu.c (working copy)
@@ -997,12 +997,12 @@
if (notify != ACPI_NOTIFY_CX_STATES)
return;

+ ACPI_SERIAL_BEGIN(cpu);
/* Update the list of Cx states. */
acpi_cpu_cx_cst(sc);
acpi_cpu_cx_list(sc);

/* Update the new lowest useable Cx state for all CPUs. */
- ACPI_SERIAL_BEGIN(cpu);
cpu_cx_count = 0;
for (i = 0; i < cpu_ndevices; i++) {
isc = device_get_softc(cpu_devices[i]);


Regards,
--
Rui Paulo


_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Wed, May 05, 2010 at 12:45:46PM +0100, Rui Paulo wrote:
> Please try this patch:
>
> Index: acpi_cpu.c
> ===================================================================
> --- acpi_cpu.c (revision 207322)
> +++ acpi_cpu.c (working copy)
> @@ -997,12 +997,12 @@
> if (notify != ACPI_NOTIFY_CX_STATES)
> return;
>
> + ACPI_SERIAL_BEGIN(cpu);
> /* Update the list of Cx states. */
> acpi_cpu_cx_cst(sc);
> acpi_cpu_cx_list(sc);
>
> /* Update the new lowest useable Cx state for all CPUs. */
> - ACPI_SERIAL_BEGIN(cpu);
> cpu_cx_count = 0;
> for (i = 0; i < cpu_ndevices; i++) {
> isc = device_get_softc(cpu_devices[i]);
>

Tested, but exactly same panic an backtrace.

Cheers.

--
Demelier David
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Would you be so kind to try to revert this patch?
I'm just guessing

You have to pass -R flag to patch program to apply the patch

=========================

--- head/sys/dev/acpica/acpi_acad.c 2009/06/05 18:44:36 193530
+++ head/sys/dev/acpica/acpi_acad.c 2009/09/30 17:07:49 197649
@@ -109,13 +109,14 @@
ACPI_SERIAL_BEGIN(acad);
if (newstatus != -1 && sc->status != newstatus) {
sc->status = newstatus;
+ ACPI_SERIAL_END(acad);
power_profile_set_state(newstatus ? POWER_PROFILE_PERFORMANCE :
POWER_PROFILE_ECONOMY);
ACPI_VPRINT(dev, acpi_device_get_parent_softc(dev),
"%s Line\n", newstatus ? "On" : "Off");
acpi_UserNotify("ACAD", h, newstatus);
- }
- ACPI_SERIAL_END(acad);
+ } else
+ ACPI_SERIAL_END(acad);
}

static void
_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. Le Vendredi 07 mai 2010 à 18:22 +0200, Giovanni Trematerra a écrit :
> On Fri, May 7, 2010 at 2:08 PM, Demelier David <> wrote:
> > Hi,
> > I noticed that pluggin the AC adaptor when I boot without it does not
> > panic. It only panic when removing it.
> >
> > Maybe that could help ?
> >
>
> Good to know. The problem lies somewhere when performance state change.
> In your case it happens when you remove AC adaptor. Let's hope someone on
> acpi@ ml comes up with a good idea.
>

Okay so for the moment no change, I'll wait for someone with an idea
that could solve my problem. For me because the panic only happens when
changing profile from ac plugged -> ac unplugged (and not the reverse) I
would think it's a cpu related acpi issue.

David.

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe. On Fri, May 07, 2010 at 08:33:46PM +0200, Demelier David wrote:
> Le Vendredi 07 mai 2010 à 18:22 +0200, Giovanni Trematerra a écrit :
> > On Fri, May 7, 2010 at 2:08 PM, Demelier David <> wrote:
> > > Hi,
> > > I noticed that pluggin the AC adaptor when I boot without it does not
> > > panic. It only panic when removing it.
> > >
> > > Maybe that could help ?
> > >
> >
> > Good to know. The problem lies somewhere when performance state change.
> > In your case it happens when you remove AC adaptor. Let's hope someone on
> > acpi@ ml comes up with a good idea.
> >
>
> Okay so for the moment no change, I'll wait for someone with an idea
> that could solve my problem. For me because the panic only happens when
> changing profile from ac plugged -> ac unplugged (and not the reverse) I
> would think it's a cpu related acpi issue.

This is one of the reasons why I asked you to provide sysctl dev.cpu
output (which you did -- thanks!). There's a known situation where CPUs
going into C3 (but not C1 or C2) state causes problems. In your case
your CPUs only advertise up to C2, so you're unaffected by that issue.

--
| Jeremy Chadwick |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |

_______________________________________________
___________________________________________________

Posted on the Freebsd-stable mailing list. Go to http://lists.freebsd.org/mailman/listinfo/freebsd-stable to subscribe.





NewsArc Lists  |  Culture Pages   |  Computing Archive  |  Media-Pages
Link to this page on your blog or website by copying the HTML code below and pasting it into your site: