grub goes into rescue mode after renaming 'default' boot environment
Before upgrading from 9.2 to 10.0, I created a new boot environment named 'pcbsd10.0' with beadm. Then I activated it, and renamed the 'default' environment to 'pcbsd9.2'. As a test of the backup BE, I deactivated 'pcbsd10.0', reactivated 'pcbsd9.2', and re-booted. The machine failed to boot, and grub went into rescue mode: GRUB loading. Welcome to GRUB! error: file 'default' not found. Entering rescue mode... grub rescue Apparently, it is still trying to find a BE named 'default'. I finally booted up by doing grub rescue prefix=(hd0,msdos1)/ROOT/pcbsd10.0/@/boot/grub grub rescue insmod normal grub rescue normal But this problem recurs every time I reboot, either into pcbsd10.0 or pcbsd9.2. Kostas ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64 [solved]
Thanks very much to all for your help.
I finally resolved the problem: first, upon logging in, I
changed the window system to fluxbox, instead of my usual
Gnome. The cpu quieted down. This suggested that I had
messed up something having to do with Gnome. So I
adopted the trivial fix: I had done little work on the
system, so I re-installed PC-BSD 9.1. Now I am running Gnome
and both cores are fine.
One small issue remains: the system doesn't suspend
properly. If I suspend it from the Gnome System - Shut
down... menu, it appears to suspend, but the fans keep
running, and it doesn't want to wake up again, even if I
power it off. The only way to wake it up is pull the
power cord and plug it in again, and then it reboots.
Perhaps this is a known ACPI problem?
Excerpt from dmesg:
aesni0: No AESNI support.
acpi0: HPQOEM SLIC-CPC on motherboard
acpi0: Power Button (fixed)
ACPI Error: Field [ASSM] at 524320 exceeds Buffer [BUF0]
size 880 (bits) (20110527/dsopcode-254)
ACPI Error: Method parse/execution failed [\\_SB_.MEM_._CRS]
(Node 0xfe0003cfc380), AE_AML_BUFFER_LIMIT
(20110527/psparse-560)
ACPI Error: Method execution failed [\\_SB_.MEM_._CRS] (Node
0xfe0003cfc380), AE_AML_BUFFER_LIMIT (20110527/uteval-113)
can't fetch resources for \\_SB_.MEM_ - AE_AML_BUFFER_LIMIT
cpu0: ACPI CPU on acpi0
cpu1: ACPI CPU on acpi0
Kostas
- Original Message - From: Kostas Oikonomou
k.oikono...@att.net
To: John Baldwin j...@freebsd.org
Cc: freebsd-amd64@freebsd.org
Sent: Friday, May 31, 2013 9:49 PM
Subject: Re: idle process keeping cpu 150% busy in freebsd
9.1-amd64
The core will always look like it is running in top,
even when it is asleep. That is just how FreeBSD accounts
for idle CPU time. The only thing I was hoping would
change is the fan having to run. You can try kldload'ing
coretemp and seeing if the processor temperatures are
different when deeper CX states are enabled (or when
powerd is running) to see if it is having any affect on
the temperatures in your box.
First the good news. It looks like the problem is solved
on the laptop (Core i7). It took one more reboot after I
put performance_cx_lowest=LOW in /etc/rc.conf.
However, the problem is still there on the HP desktop
(AMD 7550). This has only
Cx state, C1, so performance_cx_lowest=LOW had no effect.
The symptoms with this machine are that top does not show
anything running besides idle, and neither does ps -aux.
Yet the Gnome System monitor applet that I have on the
bottom panel shows significant cpu activity.
And the fan starts running within 5 minutes after the
system finishes booting.
Here is what top -S -H says:
last pid: 2645; load averages: 1.14, 0.78,
0.34 up 0+00:02:17 19:31:35
356 processes: 3 running, 338 sleeping, 15 waiting
CPU: 0.2% user, 0.0% nice, 18.9% system, 0.0%
interrupt, 80.9% idle
Mem: 187M Active, 36M Inact, 354M Wired, 13M Cache, 3323M
Free
Swap: 2048M Total, 2048M Free
PID USERNAME PRI NICE SIZERES STATE C
TIME WCPU COMMAND
11 root 155 ki31 0K32K CPU00 1:45
89.99% idle{idle: cpu0}
11 root 155 ki31 0K32K RUN 1 1:40
83.98% idle{idle: cpu1}
0 root -160 0K 2672K sched 0 1:03
0.00% kernel{swapper}
462 root -21 r31 912M 33216K select 0 0:10
0.00% Xorg
1968 ko 520 209M 7144K select 0 0:04
0.00% pulseaudio{pulseaudio}
1968 ko 520 209M 7144K select 1 0:03
0.00% pulseaudio{pulseaudio}
7 root -16- 0K16K ccb_sc 0 0:02
0.00% xpt_thrd
12 root -84- 0K 240K WAIT1 0:01
0.00% intr{irq1: atkbd0}
12 root -60- 0K 240K WAIT0 0:01
0.00% intr{swi4: clock}
1969 ko 200 323M 21968K select 0 0:00
0.00% gnome-panel{gnome-panel}
12 root -96- 0K 240K WAIT1 0:00
0.00% intr{irq16: vgapci0+}
2196 ko 200 294M 18052K select 0 0:00
0.00% gnome-netstatus-app{gnome-
1811 ko 200 320M 19116K select 1 0:00
0.00% gnome-settings-daem{gnome-
15 root -68- 0K 128K - 1 0:00
0.00% usb{usbus0}
2200 ko 200 360M 21808K select 1 0:00
0.00% clock-applet{clock-applet}
1458 root30 10 10376K 3448K select 0 0:00
0.00% devd
2028 ko 200 218M 25652K select 0 0:00
0.00% python
2272 ko 200 280M 20044K select 1 0:00
0.00% gnome-terminal{gnome-termi
2198 ko 200 295M 20552K select 1 0:00
0.00% stickynotes_applet{stickyn
1405 ko 200 156M 13152K select 0 0:00
0.00% gnome-session{gnome-sessio
417 haldaemon 200 56952K 6136K select 0 0:00
0.00% hald{hald}
Assuming this is a dual core machine, your missing ~25% of
your overall
CPU time, identifying where
Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64
Thanks very much for the reply. Being new to FreeBSD, this still seems weird to me. (My background is Solaris.) On both machines, the core that's running at 150% in the case of the HP machine, and at 400% in the case of the Dell laptop, is causing the fans to come on. Would you call that idle? I'm worried that the cores will eventually be damaged. Kostas On 05/31/13 08:36 AM, John Baldwin wrote: On Thursday, May 30, 2013 4:29:07 pm Kostas Oikonomou wrote: Hello, I am new to FreeBSD. I just installed 9.1-RELEASE-p3 (comes with PC-BSD 9.1) on an HP Pavilion s5100z. The machine has a dual-core AMD Athlon 7750 processor. What happens is that when I am doing nothing on the machine, one core is about 150% busy running the idle process: USERPID %CPU %MEMVSZ RSS TT STAT STARTEDTIME COMMAND root 11 152.9 0.0 032 ?? RL8:19AM 2:14.50 [idle] root 0 0.0 0.1 0 2672 ?? DLs 8:19AM 0:00.36 [kernel] root 1 0.0 0.0 6276 416 ?? SLs 8:19AM 0:00.05 /sbin/init -- I have read [1]http://forums.freebsd.org/showthread.php?t=38757, which seems to be relevant, and I tried sysctl -w kern.eventtimer.timer=various choices as they suggest, but to no avail. The same problem also on my Dell E6510 laptop, which has an Intel Core i7: the idle process is making one core run at about 400%. Any help would be greatly appreciated. Kostas This is normal. The idle process has a thread per-CPU that the scheduler runs when the CPU is idle. Even if the CPU is actually asleep in a Cx state, the time it is asleep is accounted to the idle thread. I added a 'Z' flag to hide the idle threads in top (they are especially noisy on an idle machine with a lot of CPUs if you use top -SH). ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64
John, Thanks. I am trying your suggestions on my Dell laptop (Intel Core i7, 4 cores). First off, my /etc/rc.conf already had # powerd: adaptive speed while on AC power, adaptive while on battery power powerd_enable=YES powerd_flags=-a hiadaptive -b adaptive # set CPU frequency and powerd was running. With that, the output of sysctl was like what you sent (the default). Now my /etc/rc.conf reads # powerd: adaptive speed while on AC power, adaptive while on battery power powerd_enable=YES powerd_flags=-a hiadaptive -b adaptive # set CPU frequency # per John Baldwin email performance_cx_lowest=LOW and I rebooted. This is what sysctl shows now: [ko@hui-neng ~]$ sysctl dev.cpu | grep cx_ dev.cpu.0.cx_supported: C1/3 C2/205 C3/245 dev.cpu.0.cx_lowest: C3 dev.cpu.0.cx_usage: 18.65% 3.89% 77.44% last 2564us dev.cpu.1.cx_supported: C1/3 C2/205 C3/245 dev.cpu.1.cx_lowest: C3 dev.cpu.1.cx_usage: 18.05% 3.42% 78.52% last 2426us dev.cpu.2.cx_supported: C1/3 C2/205 C3/245 dev.cpu.2.cx_lowest: C3 dev.cpu.2.cx_usage: 16.73% 3.63% 79.62% last 6272us dev.cpu.3.cx_supported: C1/3 C2/205 C3/245 dev.cpu.3.cx_lowest: C3 dev.cpu.3.cx_usage: 15.78% 3.42% 80.78% last 2413us But still one core is at 400%, and the fan started running: [ko@hui-neng ~]$ ps -aux | head USERPID %CPU %MEMVSZ RSS TT STAT STARTEDTIME COMMAND root 11 398.0 0.0 064 ?? RL 12:28PM 5:24.77 [idle] root 0 0.0 0.1 0 2832 ?? DLs 12:28PM 0:00.54 [kernel] root 1 0.0 0.0 6276 416 ?? SLs 12:28PM 0:00.05 /sbin/init -- root 2 0.0 0.0 016 ?? DL 12:28PM 0:00.00 [crypto] root 3 0.0 0.0 016 ?? DL 12:28PM 0:00.00 [crypto return root 4 0.0 0.0 016 ?? DL 12:28PM 0:00.00 [ctl_thrd] root 5 0.0 0.0 016 ?? DL 12:28PM 0:00.00 [cbb0 event th root 6 0.0 0.0 016 ?? IL 12:28PM 0:00.00 [fw0_probe] root 7 0.0 0.0 096 ?? DL 12:28PM 0:00.02 [zfskern] [ko@hui-neng ~]$ Kostas On 05/31/2013 11:27, John Baldwin wrote: On Friday, May 31, 2013 10:47:34 am Kostas Oikonomou wrote: Thanks very much for the reply. Being new to FreeBSD, this still seems weird to me. (My background is Solaris.) On both machines, the core that's running at 150% in the case of the HP machine, and at 400% in the case of the Dell laptop, is causing the fans to come on. Would you call that idle? I'm worried that the cores will eventually be damaged. Do you have deeper Cx states enabled? By default FreeBSD will only enter C1. Try setting 'performance_cx_lowest=LOW' in /etc/rc.conf and either rebooting or running '/etc/rc.d/power_profile start' to see if that helps. You can see which Cx states are being used by running 'sysctl dev.cpu | grep cx_'. For example: dev.cpu.0.cx_supported: C1/3 C2/59 C3/93 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% 0.00% last 324us dev.cpu.1.cx_supported: C1/3 C2/59 C3/93 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% 0.00% 0.00% last 300us dev.cpu.2.cx_supported: C1/3 C2/59 C3/93 dev.cpu.2.cx_lowest: C1 dev.cpu.2.cx_usage: 100.00% 0.00% 0.00% last 192us dev.cpu.3.cx_supported: C1/3 C2/59 C3/93 dev.cpu.3.cx_lowest: C1 dev.cpu.3.cx_usage: 100.00% 0.00% 0.00% last 157us This is on a machine with the default setup. After changing it to use the lowest setting: dev.cpu.0.cx_supported: C1/3 C2/59 C3/93 dev.cpu.0.cx_lowest: C3 dev.cpu.0.cx_usage: 5.84% 92.86% 1.28% last 145us dev.cpu.1.cx_supported: C1/3 C2/59 C3/93 dev.cpu.1.cx_lowest: C3 dev.cpu.1.cx_usage: 0.99% 94.92% 4.08% last 293us dev.cpu.2.cx_supported: C1/3 C2/59 C3/93 dev.cpu.2.cx_lowest: C3 dev.cpu.2.cx_usage: 0.45% 88.50% 11.04% last 174us dev.cpu.3.cx_supported: C1/3 C2/59 C3/93 dev.cpu.3.cx_lowest: C3 dev.cpu.3.cx_usage: 6.40% 86.89% 6.69% last 203us Another option is to run powerd which will throttle your CPUs down to lower clock speeds when they are idle. You can enable this by setting powerd_enable=YES in /etc/rc.conf and running '/etc/rc.d/powerd start'. ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
Re: idle process keeping cpu 150% busy in freebsd 9.1-amd64
The core will always look like it is running in top, even when it is
asleep. That is just how FreeBSD accounts for idle CPU time. The only
thing I was hoping would change is the fan having to run. You can try
kldload'ing coretemp and seeing if the processor temperatures are
different when deeper CX states are enabled (or when powerd is running)
to see if it is having any affect on the temperatures in your box.
First the good news. It looks like the problem is solved on the laptop (Core i7). It
took one more reboot after I put performance_cx_lowest=LOW in /etc/rc.conf.
However, the problem is still there on the HP desktop (AMD 7550). This has only
Cx state, C1, so performance_cx_lowest=LOW had no effect.
The symptoms with this machine are that top does not show anything running
besides idle, and neither does ps -aux. Yet the Gnome System monitor applet
that I have on the bottom panel shows significant cpu activity.
And the fan starts running within 5 minutes after the system finishes booting.
Here is what top -S -H says:
last pid: 2645; load averages: 1.14, 0.78, 0.34 up
0+00:02:17 19:31:35
356 processes: 3 running, 338 sleeping, 15 waiting
CPU: 0.2% user, 0.0% nice, 18.9% system, 0.0% interrupt, 80.9% idle
Mem: 187M Active, 36M Inact, 354M Wired, 13M Cache, 3323M Free
Swap: 2048M Total, 2048M Free
PID USERNAME PRI NICE SIZERES STATE C TIME WCPU COMMAND
11 root 155 ki31 0K32K CPU00 1:45 89.99% idle{idle: cpu0}
11 root 155 ki31 0K32K RUN 1 1:40 83.98% idle{idle: cpu1}
0 root -160 0K 2672K sched 0 1:03 0.00% kernel{swapper}
462 root -21 r31 912M 33216K select 0 0:10 0.00% Xorg
1968 ko 520 209M 7144K select 0 0:04 0.00%
pulseaudio{pulseaudio}
1968 ko 520 209M 7144K select 1 0:03 0.00%
pulseaudio{pulseaudio}
7 root -16- 0K16K ccb_sc 0 0:02 0.00% xpt_thrd
12 root -84- 0K 240K WAIT1 0:01 0.00% intr{irq1:
atkbd0}
12 root -60- 0K 240K WAIT0 0:01 0.00% intr{swi4:
clock}
1969 ko 200 323M 21968K select 0 0:00 0.00%
gnome-panel{gnome-panel}
12 root -96- 0K 240K WAIT1 0:00 0.00% intr{irq16:
vgapci0+}
2196 ko 200 294M 18052K select 0 0:00 0.00%
gnome-netstatus-app{gnome-
1811 ko 200 320M 19116K select 1 0:00 0.00%
gnome-settings-daem{gnome-
15 root -68- 0K 128K - 1 0:00 0.00% usb{usbus0}
2200 ko 200 360M 21808K select 1 0:00 0.00%
clock-applet{clock-applet}
1458 root30 10 10376K 3448K select 0 0:00 0.00% devd
2028 ko 200 218M 25652K select 0 0:00 0.00% python
2272 ko 200 280M 20044K select 1 0:00 0.00%
gnome-terminal{gnome-termi
2198 ko 200 295M 20552K select 1 0:00 0.00%
stickynotes_applet{stickyn
1405 ko 200 156M 13152K select 0 0:00 0.00%
gnome-session{gnome-sessio
417 haldaemon 200 56952K 6136K select 0 0:00 0.00% hald{hald}
And ps -aux | head:
[ko@wiley ~]$ ps -aux | head
USERPID %CPU %MEMVSZ RSS TT STAT STARTEDTIME COMMAND
root 11 175.9 0.0 032 ?? RL7:29PM 6:53.36 [idle]
root 0 0.0 0.1 0 2672 ?? DLs 7:29PM 0:00.37 [kernel]
root 1 0.0 0.0 6276 416 ?? SLs 7:29PM 0:00.07 /sbin/init --
root 2 0.0 0.0 016 ?? DL7:29PM 0:00.00 [crypto]
root 3 0.0 0.0 016 ?? DL7:29PM 0:00.00 [crypto
returns]
root 4 0.0 0.0 016 ?? DL7:29PM 0:00.00 [ctl_thrd]
root 5 0.0 0.0 096 ?? DL7:29PM 0:00.03 [zfskern]
I don't understand what is going on.
Kostas
___
freebsd-amd64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
idle process keeping cpu 150% busy in freebsd 9.1-amd64
Hello, I am new to FreeBSD. I just installed 9.1-RELEASE-p3 (comes with PC-BSD 9.1) on an HP Pavilion s5100z. The machine has a dual-core AMD Athlon 7750 processor. What happens is that when I am doing nothing on the machine, one core is about 150% busy running the idle process: USERPID %CPU %MEMVSZ RSS TT STAT STARTEDTIME COMMAND root 11 152.9 0.0 032 ?? RL8:19AM 2:14.50 [idle] root 0 0.0 0.1 0 2672 ?? DLs 8:19AM 0:00.36 [kernel] root 1 0.0 0.0 6276 416 ?? SLs 8:19AM 0:00.05 /sbin/init -- I have read [1]http://forums.freebsd.org/showthread.php?t=38757, which seems to be relevant, and I tried sysctl -w kern.eventtimer.timer=various choices as they suggest, but to no avail. The same problem also on my Dell E6510 laptop, which has an Intel Core i7: the idle process is making one core run at about 400%. Any help would be greatly appreciated. Kostas References 1. http://forums.freebsd.org/showthread.php?t=38757 ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to freebsd-amd64-unsubscr...@freebsd.org
