On Mon, Jun 04, 2001 at 09:37:36PM -0700, Matthew Jacob wrote:
>
> It's an easy fix except if it's your root fs- turn off softupdates.
Yeah that's the solution -- just keep disabling features. How far do we
go? Disable FFS, disable the VM system. Well, I might be left with
enough to get a pri
On Thu, 31 May 2001 16:31:21 +0900,
Seigo Tanimura said:
Seigo> Lock of struct filedesc, file, pgrp, session and sigio is now ready
Seigo> for testing.
Although the patch is still under test, a new task proposal comes to
my mind.
A new task: lock underlying objects of struct file, namely a
It's an easy fix except if it's your root fs- turn off softupdates.
On Mon, 4 Jun 2001, David O'Brien wrote:
> On Mon, Jun 04, 2001 at 02:25:41PM -0700, John Baldwin wrote:
> > Yes. Many, many, many, many times. Softupdates is broken in -current
> > right now and has been since Kirk's last c
On Mon, 4 Jun 2001, John Baldwin wrote:
>
> On 03-Jun-01 Tony Fleisher wrote:
> > I just tried to boot a -current kernel cvsupped
> > at Sat Jun 2 14:11:35 PDT 2001, and was thrown
> > the following error trying to boot to single-user
> > (transcribed by hand):
> >
> > src/sys/kern/kern_sync.
On Mon, Jun 04, 2001 at 02:25:41PM -0700, John Baldwin wrote:
> Yes. Many, many, many, many times. Softupdates is broken in -current
> right now and has been since Kirk's last commit. :-P
Why can't a filesystem hacker back it out until his return? Things are
not getting better and this is tri
I applied Tor's patch and while it helped, I still got a panic
("deallocate_dependencies: active_pagedep", which, btw, Tor's patch added)
partway into a buildworld. I've resigned to disabling softupdates on my
machine for now =-(
> -Original Message-
> From: Bruce A. Mah [mailto:[EMAIL P
If memory serves me right, David Wolfskill wrote:
> >Someone should test and commit Tor's patch. I didn't have time to
> >check whether it fixed the problems before I left (and I'm sure as
> >hell not going to update back to -current remotely to check myself :-)
>
> FWIW, I applied that patch t
>Date: Mon, 4 Jun 2001 15:02:00 -0700
>From: Kris Kennaway <[EMAIL PROTECTED]>
>Someone should test and commit Tor's patch. I didn't have time to
>check whether it fixed the problems before I left (and I'm sure as
>hell not going to update back to -current remotely to check myself :-)
FWIW, I a
On Mon, Jun 04, 2001 at 02:25:41PM -0700, John Baldwin wrote:
>
> On 04-Jun-01 Matthew Jacob wrote:
> >
> >
> > Data modified on freelist: word 2 of object 0xfe000190b780 size 72
> > previous type inodedep (0xd6adc0de != 0xdeadc0de)
> > ...
> > Data modified on freelist: word 2 of object 0x
consistently happens for me when i try to umount /tmp. A
normal umount doesn't work, not even in single-user mode (device
busy), and a forcible umount causes the panic. fstat doesn't show any
open descriptors on it though. It happens on a newfs'd /tmp, too.
It /only/ happens after a "mount -a
On 04-Jun-01 Matthew Jacob wrote:
>
>
> Data modified on freelist: word 2 of object 0xfe000190b780 size 72
> previous type inodedep (0xd6adc0de != 0xdeadc0de)
> ...
> Data modified on freelist: word 2 of object 0xfe0001806700 size 72
> previous type pagedep (0xd6adc0de != 0xdeadc0de)
>
Of course, Kris' message doesn't say "non-SMP" or "non-Alpha". I think I can
assume, though, that it was non-Alpha :-).
>
> Whoops- I *did* look, but didn't see that one... sorry
>
>
> > I believe so; see -current archives, such as
> >
> >
>http://docs.freebsd.org/cgi/getmsg.cgi?fetch=7339
Whoops- I *did* look, but didn't see that one... sorry
> I believe so; see -current archives, such as
>
>
>http://docs.freebsd.org/cgi/getmsg.cgi?fetch=73390+0+archive/2001/freebsd-current/20010603.freebsd-current
>
> Cheers,
> david
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
Data modified on freelist: word 2 of object 0xfe000190b780 size 72
previous type inodedep (0xd6adc0de != 0xdeadc0de)
...
Data modified on freelist: word 2 of object 0xfe0001806700 size 72
previous type pagedep (0xd6adc0de != 0xdeadc0de)
Anyone seen these on non-SMP? On i386?
-matt
On 03-Jun-01 Tony Fleisher wrote:
> I just tried to boot a -current kernel cvsupped
> at Sat Jun 2 14:11:35 PDT 2001, and was thrown
> the following error trying to boot to single-user
> (transcribed by hand):
>
> src/sys/kern/kern_sync.c:385 sleeping with "eventhandler"
> locked from src/sys
< said:
> We could make off_t a long long on the alpha. Otherwise the formats need:
> printf("%lld", (long long) pos); /* or %qd to shut up the ANSI warning */
They always need that, until printf learns about the `j' width
specifier (at which time they all change to `printf("%jd",
(intmax_t)
>I just put the patch for merging latest KAME into FreeBSD:
> http://www.imasy.or.jp/~ume/ipv6/test/freebsd5-kame20010528-20010604.diff.gz
thanks!
itojun
sys/kern/uipc_mbuf2.c
PULLDOWN_STAT cases are just for debugging and should be unnecessary
for FreeBSD-c
On Mon, Jun 04, 2001 at 04:48:30PM +0900, Seigo Tanimura wrote:
> >> Test of 2 weeks should be enough, followed by commit in 15 June.
>
> David> I request that this be on hold until we actually get -current Alphas
> David> usable again.
>
> OK, then we can test on pc98 and ia64 to wait for that.
-current, cvsup: date=2001.06.03.00.00.00
Normally worked, but after Ctrl-Alt-Del:
IdlePTD 4038656
initial pcb at 32f940
panicstr: from debugger
panic messages:
---
panic: free: multiple frees
panic: from debugger
Uptime: 25m49s
(kgdb) bt
#0 0xc0199a36 in dumpsys ()
#1 0xc0199823 in boot ()
#
Hi,
I just put the patch for merging latest KAME into FreeBSD:
http://www.imasy.or.jp/~ume/ipv6/test/freebsd5-kame20010528-20010604.diff.gz
This is based on KAME snap 20010528 and against 5-CURRENT of Jun 2.
There are many many changes since last KAME merge (2701).
Please review it
On Sat, 2 Jun 2001 12:52:23 -0700,
"David O'Brien" <[EMAIL PROTECTED]> said:
David> On Fri, Jun 01, 2001 at 09:28:57PM +0900, Seigo Tanimura wrote:
David> It would also be nice to get a timeline on the commit schedule for this.
>> Test of 2 weeks should be enough, followed by commit in 15 June.
[[ Thought too late to send the original to current, but my followup
can go to -current too ]]
It appears that you also need a new pccardd as well. Please let me
know if there are any problems.
Warner
In message <[EMAIL PROTECTED]> Warner Losh writes:
: I've added pci card support to OLDCAR
22 matches
Mail list logo
