Hi FreeBSD hackers and engineers,
I am experiencing a kernel panic that comes on when my new PowerEdge 1950
FreeBSD 6.2 setup is under a certain stress load. I've emailed a few people
on the list who have given me useful comments, some of which I am still
following up. But I wanted to send a
On 22 Sep 2007, at 00:26, Benjie Chen wrote:
FreeBSD 6.2 on PowerEdge 1950, RAID1 setup with mfi driver
(PERC5i). 4GB
RAM. I am currently running i386, and not amd64, due to various
reasons.
Kernel panic is at 0xC066C731, which from nm shows it's in
mtx_lock_spin
c066c7b4 T
Hi
# su hlds -c ktrace -i ./hlds_run -game cstrike +ip 0.0.0.0 +port 27015
+map de_dust -debug
Auto detecting CPU
Using Pentium II Optimised binary.
Enabling debug mode
Auto-restarting the server on crash
Console initialized.
scandir failed:/usr/home/hlds/1.6/./platform/SAVE
Protocol version
Borja Marcos wrote:
On 22 Sep 2007, at 00:26, Benjie Chen wrote:
FreeBSD 6.2 on PowerEdge 1950, RAID1 setup with mfi driver (PERC5i). 4GB
RAM. I am currently running i386, and not amd64, due to various reasons.
Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin
Benjie Chen wrote:
Hi FreeBSD hackers and engineers,
I am experiencing a kernel panic that comes on when my new PowerEdge 1950
FreeBSD 6.2 setup is under a certain stress load. I've emailed a few people
on the list who have given me useful comments, some of which I am still
following up. But I
On 24 Sep 2007, at 11:33, Kris Kennaway wrote:
Borja Marcos wrote:
I don't have the exact IP address involved, but we experienced
consistent panics in two heavily loaded mail servers (same
hardware models, Dell Powereedge) runnning Postfix and FreeBSD 6.2.
Suspecting an issue with the IP
Borja Marcos wrote:
On 24 Sep 2007, at 11:33, Kris Kennaway wrote:
Borja Marcos wrote:
I don't have the exact IP address involved, but we experienced
consistent panics in two heavily loaded mail servers (same hardware
models, Dell Powereedge) runnning Postfix and FreeBSD 6.2.
Suspecting an
Benjie Chen wrote:
Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin
c066c7b4 T _mtx_lock_spin
c066c85c T _mtx_unlock_sleep
So this could mean that independent stress tests will not result in panic if
there aren't enough concurrency to cause the problem.
When you get
hi, all
http://lists.freebsd.org/pipermail/freebsd-questions/2007-June/151686.html
my problem
# fsck /dev/aacd0s1f
** /dev/aacd0s1f (NO WRITE)
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
fsck_ufs: cannot alloc 2378019004 bytes for inoinfo
# cat /boot/loader.conf
After experiencing overheating problems, I purchased a new CPU and motherboard
(Intel D975XBX2) which has a built in Raid controller Marvell 88SE61xx
I connected my existing FreeBSD-STABLE SATA drive to port 0.
Upon boot, I receive the following error:
int=000d err= efl=00030086
On Monday 24 September 2007, sam wrote:
Hi
# su hlds -c ktrace -i ./hlds_run -game cstrike +ip 0.0.0.0 +port 27015
+map de_dust -debug
Auto detecting CPU
Using Pentium II Optimised binary.
Enabling debug mode
Auto-restarting the server on crash
Console initialized.
scandir
Ivan Voras wrote:
Benjie Chen wrote:
Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin
c066c7b4 T _mtx_lock_spin
c066c85c T _mtx_unlock_sleep
So this could mean that independent stress tests will not result in
panic if
there aren't enough concurrency to cause the
On 24/09/2007, Kris Kennaway [EMAIL PROTECTED] wrote:
Ivan Voras wrote:
http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.html
Surely it cannot be since it involves a different function ;-)
:)
When all you have is a hammer...
On 24/09/2007, Benjie Chen [EMAIL PROTECTED] wrote:
Ivan and Kris,
I will try to get a kernel trace -- it may not happen for awhile since I am
not in the office and working remotely for awhile so it may not be easy to
get a trace... but I will check.
It's fairly easy:
1) add lines like the
Hi, i have motherboard with integrated Marvell 88SE6141 controller. And i can't
boot from any drives attached to this controller. This controller family is not
yet
supported.
After experiencing overheating problems, I purchased a new CPU and
motherboard
(Intel D975XBX2) which has a built
Hello Ulrich,
* Ulrich Spoerlein [EMAIL PROTECTED] [23-09-07 17:19]:
I'm using a Makefile to drive our release and package building and for
the releases I'm using an install.cfg, which gets created on the fly,
since the names of the kernels change now and then, here is the release
target
thx
On 24 Sep, sam wrote:
hi, all
http://lists.freebsd.org/pipermail/freebsd-questions/2007-June/151686.html
my problem
# fsck /dev/aacd0s1f
** /dev/aacd0s1f (NO WRITE)
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
fsck_ufs: cannot alloc 2378019004 bytes for inoinfo
I'd be
On Mon, 2007-09-24 at 16:30 -0700, Don Lewis wrote:
On 24 Sep, sam wrote:
hi, all
http://lists.freebsd.org/pipermail/freebsd-questions/2007-June/151686.html
my problem
# fsck /dev/aacd0s1f
** /dev/aacd0s1f (NO WRITE)
** Last Mounted on /usr
** Phase 1 - Check Blocks and Sizes
Ian Smith wrote this message on Sat, Sep 22, 2007 at 13:16 +1000:
This drew a blank in -questions. I don't know where else to post it, so
I'm hoping someone here might be able to spare me a clue.
You should probably have posted this question to -hackers instead..
This is more low level
Pieter de Goeje wrote:
On Monday 24 September 2007, sam wrote:
# mount|grep linux
linprocfs on /usr/compat/linux/proc (linprocfs, local)
linsysfs on /usr/compat/linux/sys (linsysfs, local)
# pkg_info | grep linux
linux_base-fc6-6_3 Base set of packages needed in Linux mode (for
i386/amd64)
20 matches
Mail list logo
