On Fri, 18 Nov 2005, Joerg Pernfuss wrote:
Hi,
While hunting down the panic described in the other mail, I got an LOR
I couldn't find on the lists so far.
lock order reversal:
1st 0xc50147ec vnode interlock (vnode interlock) @
/usr/src/sys/kern/vfs_subr.c:2185
2nd 0xc1060144 system map
Darlin! :)
Nasty redhead chick giving a head to two old farters huge indoors.
Generosity is giving more than you can, and pride is taking less than you need.
Never seen inside beefore fresh faces
http://www.ruzujigany.com/?mneyeqemooglo
To live alone is the fate of
Hi all!
I've spent about a week trying to accomplish a rather simple task: To
build kernel and world once for each architecture we have, and
distribute this precompiled src and obj tree via NFS to all the
systems that need updating. I have combined this with a locally
maintained CVS
Starting out trying to upgrade the amd64 hosts, I export the
two obj directories via NFS, and mount them as /usr/obj on the
amd64 hosts that need upgrading.
I done upgrades the other way, by having the build machine
mount the clients to-be-root partition and installing to it
using NFS.
--
On 19 nov 2005, at 02.35, Pawel Jakub Dawidek wrote:
On Sat, Nov 19, 2005 at 01:55:57AM +0100, Johan Ström wrote:
snip
+ I just noticed another thing... My disk performance... sucks! :P
+
+ Some examples (from an otherwise unloaded system):
+
+ [EMAIL PROTECTED]:/home/johan$ time dd
I've just upgraded my home server from 6-BETA4 (that was stable and
worked without reboots for months) to 6.0-release. And now my server
suddenly reboots under any load, i'm even unable to rebuild my system to
beta4 again. All the services are shuted down now (apache, mysql, smb,
nfs, ftp, ntp,
I would suggest re-cvs'ing your box.
Be sure to use RELANG_6 that will get you 6.0-STABLE. Then make cleanworld
make buildworld make installworld make buildkernel KERNCONF=yourkernname
make installworld KERNCONF=yourkernname
That should get you up to 6.0-STABLE unless your box reboots during
I've already tried this, but firsty i'm not sure that 6-stable will
solve the problem, and secondly, i can finish buildworld process.
As a partial help i've performed buildkernel and installkernel of
6-stable with no visible success.
Stepan Rakhimov
Kyle Hittle wrote:
I would suggest
Hi,
On 11/19/05, Kyle Hittle [EMAIL PROTECTED] wrote:
I would suggest re-cvs'ing your box.
Be sure to use RELANG_6 that will get you 6.0-STABLE. Then make cleanworld
make buildworld make installworld make buildkernel KERNCONF=yourkernname
make installworld KERNCONF=yourkernname
By using
Hi,
On 11/19/05, Stepan Rakhimov [EMAIL PROTECTED] wrote:
I've just upgraded my home server from 6-BETA4 (that was stable and
worked without reboots for months) to 6.0-release. And now my server
suddenly reboots under any load, i'm even unable to rebuild my system to
beta4 again. All the
I've just upgraded my home server from 6-BETA4 (that was
stable and worked without reboots for months) to 6.0-release.
- What kind of machine is this? Please show the output of
dmesg.
- Have you enabled DDB and kernel debugging support. Can
you take a crash dump.
- Are there any messages
Hi,
On 11/19/05, Stepan Rakhimov [EMAIL PROTECTED] wrote:
I've already tried this, but firsty i'm not sure that 6-stable will
solve the problem, and secondly, i can finish buildworld process.
As a partial help i've performed buildkernel and installkernel of
6-stable with no visible success.
Joseph Koshy wrote:
I've just upgraded my home server from 6-BETA4 (that was
stable and worked without reboots for months) to 6.0-release.
- What kind of machine is this? Please show the output of
dmesg.
dmesg in the P.S.
- Have you enabled DDB and kernel debugging support. Can
you
Stepan Rakhimov wrote:
Joseph Koshy wrote:
I've just upgraded my home server from 6-BETA4 (that was
stable and worked without reboots for months) to 6.0-release.
- What kind of machine is this? Please show the output of
dmesg.
dmesg in the P.S.
- Have you enabled DDB and kernel
Xin LI wrote:
Hi,
On 11/19/05, Stepan Rakhimov [EMAIL PROTECTED] wrote:
I've just upgraded my home server from 6-BETA4 (that was stable and
worked without reboots for months) to 6.0-release. And now my server
suddenly reboots under any load, i'm even unable to rebuild my system to
beta4
sr i have some kernel dumps only , the size is 288mb, should i
sr send one of them?
Just the backtrace please.
sr CPU: AMD-K6(tm) 3D processor (551.25-MHz 586-class CPU)
sr Origin = AuthenticAMD Id = 0x58c Stepping = 12
sr Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX
sr AMD
Hi, Stepan,
On 11/19/05, Stepan Rakhimov [EMAIL PROTECTED] wrote:
[snip]
i have some kernel dumps only , the size is 288mb, should i send one of
them?
Try gdb /usr/obj/usr/src/sys/[YOURKERNEL]/kernel.debug
/var/crash/vmcore.0 and send the output from bt full would be good
enough I think.
On Nov 19, 2005, at 13:28 , Joseph Koshy wrote:
Starting out trying to upgrade the amd64 hosts, I export the
two obj directories via NFS, and mount them as /usr/obj on the
amd64 hosts that need upgrading.
I done upgrades the other way, by having the build machine
mount the clients to-be-root
Would I have to export every filesystem mount point on the
hosts then? Or does an -alldirs option do the trick (in
exports)?
I use a self-contained '/' partition on the machines where I
need to cross-install.
Note that one still needs to run mergemaster or etcmerge after
the cross-install
On 11/9/05, Ingeborg Hellemo [EMAIL PROTECTED] wrote:
Fresh new ProLiant dl380 2 CPU/dual core
Fresh new FreeBSD 6.0-RELEASE
During boot I arrive at
da0 at ciss0 bus 0 target 0 lun 0
da0: COMPAQ RAID 1 VOLUME OK Fixed Direct Access SCSI-0 device
da0: 135.168MB/s transfers
da0: 34727MB
On Wed, 16 Nov 2005 06:51:34 +, Jayton Garnett wrote
Hi,
I presume all you want is to get the wheel working under X.
Adding a line to xorg.conf in the mouse section is all I need to add
no matter what mouse I use to get the wheel to work under X/Gnome.
Option ZAxisMapping 4 5
Hello all,
I've recently upgraded my AMD64 FreeBSD station from 5.4 to 6.0 using
the handbook method.
Everything seems to work OK but I have the message after repeating every
second on tty1 after I log on X :
kvm_open : kinfo_proc size mismatch (expected 912 got 1088).
After some search
Lukas Ertl wrote:
On 11/9/05, Ingeborg Hellemo [EMAIL PROTECTED] wrote:
Fresh new ProLiant dl380 2 CPU/dual core
Fresh new FreeBSD 6.0-RELEASE
During boot I arrive at
da0 at ciss0 bus 0 target 0 lun 0
da0: COMPAQ RAID 1 VOLUME OK Fixed Direct Access SCSI-0 device
da0: 135.168MB/s transfers
On Sat, 19 Nov 2005, Laurent wrote:
I've recently upgraded my AMD64 FreeBSD station from 5.4 to 6.0 using
the handbook method.
Everything seems to work OK but I have the message after repeating every
second on tty1 after I log on X :
kvm_open : kinfo_proc size mismatch (expected 912 got
I installed 6.0 on a system with two SATA drives in RAID-1. 5.4 is
installed on a standard IDE channel. All appeared to work well until
sometime after updating the system to 6-STABLE, installing the Nvidia
driver and copying a lot of data (mainly ogg files) from my old hard
drive onto it. I
Eirik Øverby wrote:
I've spent about a week trying to accomplish a rather simple task: To
build kernel and world once for each architecture we have, and
distribute this precompiled src and obj tree via NFS to all the systems
that need updating. I have combined this with a locally
AFAICT cross-compiling amd64 on a i386 machine isn't supported
yet. I ran into a similar problem when I upgraded an i386
machine to amd64. I thought I could just set CPUTYPE=athlon-64
and buildworld would do the right thing. Apparently not.
Bootstrapping a single machine is supported:
# make
On Sat, Nov 19, 2005 at 03:54:07PM +0300, Stepan Rakhimov wrote:
I've just upgraded my home server from 6-BETA4 (that was stable and
worked without reboots for months) to 6.0-release. And now my server
suddenly reboots under any load, i'm even unable to rebuild my system to
beta4 again. All
On Sat, Nov 19, 2005 at 06:38:29PM +0100, Laurent wrote:
Hello all,
I've recently upgraded my AMD64 FreeBSD station from 5.4 to 6.0 using
the handbook method.
Everything seems to work OK but I have the message after repeating every
second on tty1 after I log on X :
kvm_open :
On 11/19/05, Jim Pingle [EMAIL PROTECTED] wrote:
Lukas Ertl wrote:
On 11/9/05, Ingeborg Hellemo [EMAIL PROTECTED] wrote:
Fresh new ProLiant dl380 2 CPU/dual core
Fresh new FreeBSD 6.0-RELEASE
During boot I arrive at
da0 at ciss0 bus 0 target 0 lun 0
da0: COMPAQ RAID 1 VOLUME OK
hi,
I tried to build gnome2 on freebsd6 stable.
It fails when it tries to compile gnomeapllets2, here is the output:
--START SNIP-
12.1/drivemount/help'
if ! test -d es/; then mkdir es/; fi
if test -f C/drivemount.xml; then d=../; else d=.././; fi; \
(cd es/ \
`which
Hello, All!
After 14 days of uptime I ran sysctl -a and it triggered a panic.
In ddb:
=Beginning of the citation==
db bt
Tracing pid 15840 tid 100071 td 0xc1553600
dev2udev(c20bf300,88,0,0,0) at dev2udev+0x11
sysctl_kern_ttys(c08d4500,0,0,cc865c04,c08d4500) at
1. after my upgrade, my serial ports are not accessible
monsterjam# ls -al /dev/cuaa*
ls: No match.
monsterjam#
2. I get very little dmesg output after a fresh boot
monsterjam# dmesg
lpt0: switched to polled extended mode
fxp0: promiscuous mode enabled
monsterjam#
monsterjam# uname -a
FreeBSD
On Saturday 19 November 2005 23:37, Jason wrote:
1. after my upgrade, my serial ports are not accessible
monsterjam# ls -al /dev/cuaa*
ls: No match.
I got surprised by this too, when trying to use my camera through serial
cable. They've become /dev/cuad and /dev/ttyd for outgoing and incoming
On Thu, 17 Nov 2005, Oliver Fromme wrote:
Brian Candler [EMAIL PROTECTED] wrote:
However, when I insert a CF card with normal partioning I need /dev/da0s1,
and this is not present in the /dev filesystem because the partition table
has not been read.
# mount -t msdos /dev/da0s1
On Wed, 16 Nov 2005, Michael Voucko wrote:
Hi,
I'm trying to install the latest version of heartbeat (linux-ha), which
unfortunately is not available from the ports tree yet.
Setup is two boxes running (5.4-STABLE FreeBSD from Oct 17 2005) both
connected
to a hub with lnc NICs on a
On Fri, 18 Nov 2005, Ricardo A. Reis wrote:
Hi all,
Updating proxy server running 5.4, i resolve enable acpi,smp
kernel to use HTT.
You need to set
machdep.hyperthreading_enabled=1
in /boot/loader.conf, and make sure HyperThreading is enabled in your
BIOS.
The ACPI messages
I'm trying to install the latest version of heartbeat (linux-ha), which
unfortunately is not available from the ports tree yet.
Setup is two boxes running (5.4-STABLE FreeBSD from Oct 17 2005) both connected
to a hub with lnc NICs on a private 10.0.0.0/24 subnet (actually its only a
'simulated
On Fri, 18 Nov 2005, Tom Jensen wrote:
Hi
Seen this panic twice, there seems to be no pattern and I have no idea what
triggers this, is it failing hardware?
Its certainly possible. Or a bad cable, or a bad firmware interaction.
System: FreeBSD 5.4-STABLE FreeBSD 5.4-STABLE #10: Sat Nov 5
On Sun, Nov 20, 2005 at 12:43:06AM +, Danny Pansters wrote:
On Saturday 19 November 2005 23:37, Jason wrote:
1. after my upgrade, my serial ports are not accessible
monsterjam# ls -al /dev/cuaa*
ls: No match.
I got surprised by this too, when trying to use my camera through serial
On Sunday 20 November 2005 01:28, you wrote:
On Sun, Nov 20, 2005 at 12:43:06AM +, Danny Pansters wrote:
On Saturday 19 November 2005 23:37, Jason wrote:
1. after my upgrade, my serial ports are not accessible
monsterjam# ls -al /dev/cuaa*
ls: No match.
I got surprised by this
I recently upgraded from stable-6 of Nov 4 to stable-6 of today on my
Dell Latitude D800 Laptop, and suddenly the response of the touchpad
mouse and keyboard was bery bad. In particular, when I type about 1 in
10 key presses simply do not register. I ended up going back to the Nov
4
On 20/11/2005 7:32 AM, Lukas Ertl wrote:
It has nothing to do with the SCSI controller, it's all about the
floppy drive. It seems like the fdc driver doesn't recognize that
there's no disk in the drive and tries to access it on and on and on.
As I said, disable the floppy drive in the BIOS (or
43 matches
Mail list logo
