On 11/1/06, Vlad Galu [EMAIL PROTECTED] wrote:
On 10/31/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Tue, Oct 31, 2006 at 04:34:59PM +0200, Vlad Galu wrote:
Yes, but for objective reasons I can't publish it :(
The only
debugging option that I didn't use was INVARIANTS.
Which is
On Tue, Nov 14, 2006 at 05:10:23PM +0200, Vlad Galu wrote:
On 11/1/06, Vlad Galu [EMAIL PROTECTED] wrote:
On 10/31/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Tue, Oct 31, 2006 at 04:34:59PM +0200, Vlad Galu wrote:
Yes, but for objective reasons I can't publish it :(
The only
On 10/31/06, Kris Kennaway [EMAIL PROTECTED] wrote:
It now crashes in a different place. Unfortunately I don't have
physical access to the machine. A bt full is available at
http://night.rdslink.ro/dudu/freebsd/03_11_2006.txt. The stack was
corrupted though :(
--
If it's there, and you can
On 10/1/06, Cy Schubert [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED],
Vlad
GALU writes:
On 9/30/06, Martin Blapp [EMAIL PROTECTED] wrote:
Hi,
1.) Bad ram ? Have you run some memory tester ?
Yes, memtest86 didn't show anything weird.
2.) Have you background fsck running
On 10/31/06 08:03, Vlad Galu wrote:
On 10/1/06, Cy Schubert [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED],
Vlad
GALU writes:
On 9/30/06, Martin Blapp [EMAIL PROTECTED] wrote:
Hi,
1.) Bad ram ? Have you run some memory tester ?
Yes, memtest86 didn't show anything weird.
2.)
On 10/31/06, Eric Anderson [EMAIL PROTECTED] wrote:
On 10/31/06 08:03, Vlad Galu wrote:
On 10/1/06, Cy Schubert [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED],
Vlad
GALU writes:
On 9/30/06, Martin Blapp [EMAIL PROTECTED] wrote:
Hi,
1.) Bad ram ? Have you run some memory tester ?
On Tue, Oct 31, 2006 at 04:34:59PM +0200, Vlad Galu wrote:
Yes, but for objective reasons I can't publish it :(
The only
debugging option that I didn't use was INVARIANTS.
Which is coincidentally the most useful one ;-)
Also turn on DEBUG_LOCKS and DEBUG_VFS_LOCKS then report the output
On 10/31/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Tue, Oct 31, 2006 at 04:34:59PM +0200, Vlad Galu wrote:
Yes, but for objective reasons I can't publish it :(
The only
debugging option that I didn't use was INVARIANTS.
Which is coincidentally the most useful one ;-)
Also turn on
I've been getting random crashes like the one below, once or twice a
week, always in the same code path. The system is a RELENG_6 as of Wed
Sep 27 11:42:57 EEST 2006, running on amd64.
-- cut here --
#0 doadump () at pcpu.h:172
No locals.
#1 0x8022d033 in boot (howto=260) at
Hi,
1.) Bad ram ? Have you run some memory tester ?
2.) Have you background fsck running on this disk ? If
so try to boot into single user and do a full fsck on this
disk.
Martin
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
On 9/30/06, Martin Blapp [EMAIL PROTECTED] wrote:
Hi,
1.) Bad ram ? Have you run some memory tester ?
Yes, memtest86 didn't show anything weird.
2.) Have you background fsck running on this disk ? If
so try to boot into single user and do a full fsck on this
disk.
I have
In message [EMAIL PROTECTED],
Vlad
GALU writes:
On 9/30/06, Martin Blapp [EMAIL PROTECTED] wrote:
Hi,
1.) Bad ram ? Have you run some memory tester ?
Yes, memtest86 didn't show anything weird.
2.) Have you background fsck running on this disk ? If
so try to boot into single
12 matches
Mail list logo
