Re: livelocks and deadlocks on 8.0BETA2
On Friday 21 August 2009 02:56, Kevin Oberman wrote: > I have a quad-core system that I updated to 8.0 about 2 weeks ago. It > ran fine until yesterday when I used the PATA/ATAPI DVD drive to read a > disk. Then the fun began. I saw two totally different presentations, but > I hope that they both are manifestations of the same problem. > [snip] i have no idea about the second problem, but the 1st one it's not fbsd-specific. it has happened to me on a linux box. repeatedly i might add. after a couple of hours playing videos, X would use 100% of cpu and i wasn't able to switch to a VTY or kill it via ctrl-alt- backspace. i think it might be a problem related to mplayer, but i'm not sure, cause it did not crash, so no bad-behavour log. on the linux box, it's easy to handle (just /etc/rc.d/kdm restart via ssh). But since fbsd doesn't use kdm it's only reboot. i don't use mplayer or X on my fbsd box so i don't really know on what version X or mplayer are. The problem has stopped happening on the linux box. it uses mplayer 29411-3 and xorg-server 1.6.3-3. just my 2 cents signature.asc Description: This is a digitally signed message part.
Upgrade FreeBSD 7.1 to 7.2
Hi list, I would like to do a binary upgrade from 7.1 to 7.2. I've seen the instructions here: http://www.freebsd.org/releases/7.2R/announce.html I've heard that it's safest to start the machine in single user mode when doing upgrades, but I see no notice about it in the announcement. So my question is: Is it ok to do this binary upgrade without start single user mode first? If no, must I reboot my machine to enter single user mode? TIA, Mikael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: livelocks and deadlocks on 8.0BETA2
> From: Ed Jobs > Date: Fri, 21 Aug 2009 10:52:30 +0300 > Sender: owner-freebsd-sta...@freebsd.org > > On Friday 21 August 2009 02:56, Kevin Oberman wrote: > > I have a quad-core system that I updated to 8.0 about 2 weeks > ago. It > > ran fine until yesterday when I used the PATA/ATAPI DVD drive to > read a > > disk. Then the fun began. I saw two totally different presentations, > but > > I hope that they both are manifestations of the same problem. > > > > [snip] > > i have no idea about the second problem, but the 1st one it's not > fbsd-specific. it has happened to me on a linux box. repeatedly i > might add. after a couple of hours playing videos, X would use 100% > of cpu and i wasn't able to switch to a VTY or kill it via ctrl-alt- > backspace. > i think it might be a problem related to mplayer, but i'm not sure, > cause it did not crash, so no bad-behavour log. > on the linux box, it's easy to handle (just /etc/rc.d/kdm restart via > ssh). But since fbsd doesn't use kdm it's only reboot. > > i don't use mplayer or X on my fbsd box so i don't really know on what > version X or mplayer are. The problem has stopped happening on the > linux box. it uses mplayer 29411-3 and xorg-server 1.6.3-3. Okay. Since it shows up with very different players (mplayer and xine), it sounds like an Xorg issue. Could you tell me what graphics card you are running on the Linux box? I have an NVIDIA GeForce 7800 GT with the NV driver and a pair of 1280x1024 screens. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: livelocks and deadlocks on 8.0BETA2
On Friday 21 August 2009 18:15, Kevin Oberman wrote: > > From: Ed Jobs > > Date: Fri, 21 Aug 2009 10:52:30 +0300 > > Sender: owner-freebsd-sta...@freebsd.org > > > > On Friday 21 August 2009 02:56, Kevin Oberman wrote: > > > I have a quad-core system that I updated to 8.0 about 2 weeks > > > > ago. It > > > > > ran fine until yesterday when I used the PATA/ATAPI DVD drive to > > > > read a > > > > > disk. Then the fun began. I saw two totally different presentations, > > > > but > > > > > I hope that they both are manifestations of the same problem. > > > > [snip] > > > > i have no idea about the second problem, but the 1st one it's not > > fbsd-specific. it has happened to me on a linux box. repeatedly i > > might add. after a couple of hours playing videos, X would use 100% > > of cpu and i wasn't able to switch to a VTY or kill it via ctrl-alt- > > backspace. > > i think it might be a problem related to mplayer, but i'm not sure, > > cause it did not crash, so no bad-behavour log. > > on the linux box, it's easy to handle (just /etc/rc.d/kdm restart via > > ssh). But since fbsd doesn't use kdm it's only reboot. > > > > i don't use mplayer or X on my fbsd box so i don't really know on what > > version X or mplayer are. The problem has stopped happening on the > > linux box. it uses mplayer 29411-3 and xorg-server 1.6.3-3. > > Okay. Since it shows up with very different players (mplayer and xine), > it sounds like an Xorg issue. Could you tell me what graphics card you > are running on the Linux box? > > I have an NVIDIA GeForce 7800 GT with the NV driver and a pair of > 1280x1024 screens. i use the nvidia driver on a GTX280 driver version: 185.18.31 signature.asc Description: This is a digitally signed message part.
Compilation problem in 7.2-STABLE - module cpuctl.c
when compiling a 7.2 STABLE kernel in an amd64 machine I found: ===> coda5 (all) ===> coretemp (all) ===> cpuctl (all) cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -std=c99 -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/src/sys/amd64/compile/A027/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -I/usr/src/sys/amd64/compile/A027 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /usr/src/sys/modules/cpuctl/../../dev/cpuctl/cpuctl.c /usr/src/sys/modules/cpuctl/../../dev/cpuctl/cpuctl.c: In function 'cpuctl_ioctl': /usr/src/sys/modules/cpuctl/../../dev/cpuctl/cpuctl.c:162: error: 'CPUCTL_MSRSBIT' undeclared (first use in this function) /usr/src/sys/modules/cpuctl/../../dev/cpuctl/cpuctl.c:162: error: (Each undeclared identifier is reported only once /usr/src/sys/modules/cpuctl/../../dev/cpuctl/cpuctl.c:162: error: for each function it appears in.) /usr/src/sys/modules/cpuctl/../../dev/cpuctl/cpuctl.c:163: error: 'CPUCTL_MSRCBIT' undeclared (first use in this function) /usr/src/sys/modules/cpuctl/../../dev/cpuctl/cpuctl.c: In function 'cpuctl_do_msr': /usr/src/sys/modules/cpuctl/../../dev/cpuctl/cpuctl.c:239: error: 'CPUCTL_MSRSBIT' undeclared (first use in this function) /usr/src/sys/modules/cpuctl/../../dev/cpuctl/cpuctl.c:245: error: 'CPUCTL_MSRCBIT' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/sys/modules/cpuctl. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/src/sys/amd64/compile/A027. a027# Someone with the same problem? Do you know a solution? Paniago. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrade FreeBSD 7.1 to 7.2
Mikael Bak wrote: Hi list, I would like to do a binary upgrade from 7.1 to 7.2. I've seen the instructions here: http://www.freebsd.org/releases/7.2R/announce.html I've heard that it's safest to start the machine in single user mode when doing upgrades, but I see no notice about it in the announcement. So my question is: Is it ok to do this binary upgrade without start single user mode first? If no, must I reboot my machine to enter single user mode? I always did upgrade in multiuser for minimalising the downtime of servers. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrade FreeBSD 7.1 to 7.2
Mikael Bak writes: > I would like to do a binary upgrade from 7.1 to 7.2. I've seen the > instructions here: > http://www.freebsd.org/releases/7.2R/announce.html > > I've heard that it's safest to start the machine in single user mode > when doing upgrades, but I see no notice about it in the announcement. The announcement explicitly points to the FreeBSD Handbook for the procedure for doing source upgrades, which does indeed including booting the new kernel into single-user mode before doing the installworld. > So my question is: Is it ok to do this binary upgrade without start > single user mode first? Sure. It's riskier; if the new kernel doesn't boot, but you already have the new userland installed, you're stuck. You'll need to recover from some other bootable media, which may well take quite a while. Just how risky it is depends on how big a version jump you're making. > If no, must I reboot my machine to enter single user mode? Rebooting is at least as important as getting into single-user mode. You want to know your kernel is good. Single-user mode is good, too, because you don't want to change utilities out from under running processes if you can help it. All of that said, though, I do it all the time on lightly loaded machines. I always reboot after completing the upgrade, and usually also in between the installkernel and installworld. Trying the upgrade on a test machine first helps reduce the risk as well. Unfortunately, machines that you want to avoid downtime on are usually the same ones that you really can't afford to fail an upgrade... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
