Peter Wemm [EMAIL PROTECTED] wrote:
For some reason, sysinstall or the kernel decided to += 64k on the
start address of the swap partition (to avoid swap clobbering the
fdisk, bootblocks, etc at the start of the disk), but neglected to
remove 64k from the size.
This could be undone.
SMAP type=01 base= len= 0009f800
SMAP type=02 base= 0009f800 len= 0800
SMAP type=02 base= 000e8400 len= 00017c00
SMAP type=01 base= 0010 len= 13ef
SMAP type=03 base= 13ff len=
Sat, May 26, 2001 at 22:03:34, barry (Barry Lustig) wrote about Re: Boot time memory
issue:
SMAP type=01 base= 0010 len= 13ef
[...]
Did that and got the same error. I put a printf just before the
pa_indx++ in machdep.c and watched it increment by 2's all the way
Check your disk label. I got burned a few months back on a fairly old
install where I created swap first, then root. This causes the swap
partition to start at sector 0, with root straight after. For some reason,
sysinstall or the kernel decided to += 64k on the start address of the swap
=== usr.bin/fetch
cc -O -pipe -Wall -pedantic -I/usr/obj/flat/src/i386/usr/include -c
/flat/src/usr.bin/fetch/fetch.c
gzip -cn /flat/src/usr.bin/fetch/fetch.1 fetch.1.gz
/flat/src/usr.bin/fetch/fetch.c: In function `stat_display':
/flat/src/usr.bin/fetch/fetch.c:131: warning: ANSI C does
is it possible to use the 5.0-current kernel with releases such as 4.3?
I would like to take advantage of the SMP optimizations that are in
5.0current.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On 27.05.2001 04:51:58 +, Matt Bedynek wrote:
is it possible to use the 5.0-current kernel with releases such as 4.3?
No.
I would like to take advantage of the SMP optimizations that are in
5.0current.
You would like to upgrade your whole system then.
On Sun, May 27, 2001 at 04:51:58AM -0500, Matt Bedynek wrote:
is it possible to use the 5.0-current kernel with releases such as 4.3?
I would like to take advantage of the SMP optimizations that are in
5.0current.
No.
Kris
PGP signature
Terry,
thanks a lot for taking the time to attack my DNS problem.
I think, however, that there's something fishy with either
my DNS setup or FreeBSD's new nsswitch configuration.
# Make your test program do a gethostbyname(), like it does.
#
# Then take the resulting IP address, and call
Hi,
I've got exactly the same with a 5.0-20010514-CURRENT snapshot from
current.freebsd.org.
BTW, it is running on a notebook, and the newcard kernel runs very well,
nice job !
--
---
-- [EMAIL PROTECTED]
---
- Original Message -
In the last episode (May 27), Matt Bedynek said:
is it possible to use the 5.0-current kernel with releases such as
4.3? I would like to take advantage of the SMP optimizations that are
in 5.0current.
-current is too unstable at the moment to try and use on a production
system, and I don't
I recently purchased a new Toshiba Satellite 2805 laptop, and I'm
trying to install -current on it =) When I tried to install from the
-current snapshots they all would lockup just after 'pcib0: ...' was
printed. So I tried a 4-stable snapshot and that worked
perfectly. However, I'm now
based on source code cvsup'd today:
panic+0xc8
fdrop+0x32
closef+0x9b
close+0x89
syscall+0x645
syscall_with_err_pushd+0x1b
Marc G. Fournier [EMAIL PROTECTED]
Systems Administrator @ hub.org
scrappy@{postgresql|isc}.org ICQ#7615664
To
On 27-May-2001 Mike Smith wrote:
| You could try disabling the PCI BIOS calls;
|
| set machdep.bios.pci=disable
|
| at the loader prompt. Let me know if this helps; I'd want to track this
| further if it does.
Yes, this works =)
Mike
--
Mike Heffner [EMAIL PROTECTED]
Just tried to do a buildworld with a May 24th kernel and it did it there
also ...
On Sun, 27 May 2001, Marc G. Fournier wrote:
based on source code cvsup'd today:
panic+0xc8
fdrop+0x32
closef+0x9b
close+0x89
syscall+0x645
syscall_with_err_pushd+0x1b
Marc G. Fournier
I am installing current on a new box and I need jkd. That basically means
linux emulation. I haven't been able to build it for some time on current.
I have used the submitted PR to upgrade it to 7.? and it has worked except
I have problems with all other ports that need linux_base. Right now
A make release failed here with:
#
touch release.8
Making fixit floppy.
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 6.
Warning: 1216 sector(s) in last cylinder unallocated
/dev/md0c: 2880
I am installing current on a new box and I need jkd. That basically means
linux emulation. I haven't been able to build it for some time on
current.
I have used the submitted PR to upgrade it to 7.? and it has worked except
I have problems with all other ports that need linux_base. Right
On Sun, May 27, 2001 at 10:45:59PM +0200, John Hay wrote:
This strongly smells like a side-effect of RELNOTESng that removed
the 'texts' subdir in favor of generated .txt from .sgml source
files
Wilko
A make release failed here with:
#
touch release.8
thank god for digital cameras ... current panic was while doing a simple
'make buildworld', no -j option ... based on most recent sources ...
cpid = 0; lapic.id =
instruction pointer = 0x8:0xc0179309
stack pointer = 0x10:0xcb350f60
frame pointer =
anyone having a problem with that with -current kernels? where the kernel
panics, on reboot the superblock is screwed ... I can do a 'mount -a' to
recalculate, then an umount -a and 'fsck -y' to clean the file systems ...
I have softupdates enabled on all file systems except for /, if that
In message [EMAIL PROTECTED] Matt Bedynek writes:
: is it possible to use the 5.0-current kernel with releases such as 4.3?
: I would like to take advantage of the SMP optimizations that are in
: 5.0current.
Yes and No. The 4.3 binaries run fine, but many kernel interfaces
have changed so
On 26-May-01 Michael Harnois wrote:
I finally got this much. I hope it helps.
lock order reversal
1st 0xc03af0a0 mntvnode @ ../../ufs/ffs/ffs_vnops.c:1007
2nd 0xc8b539cc vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:1016
recursed on non-recursive lock (sleep mutex) vm @
Please try
On Sun, 27 May 2001 17:32:15 -0700 (PDT), John Baldwin [EMAIL PROTECTED] said:
Please try http://www.FreeBSD.org/~jhb/patches/vm.patch it fixes
several places where we hold the vm lock across VOP's, etc.
Does that mean you've upgraded it? The last time I tried it (shortly
after you
On Sun, 27 May 2001 21:30:59 +0200, [EMAIL PROTECTED] said:
The ui_ref member in struct uidinfo is only 16 bits. This means
that a fatal wraparound due to a missing call to uifree() can
happen rather quickly.
Great! With your patch and the earlier one from Thomas I can build
dima@hornet% ls -1 share/man/man9/devfs*.9
share/man/man9/devfs_add_devswf.9
share/man/man9/devfs_link.9
share/man/man9/devfs_remove_dev.9
The above man pages are for the old DEVFS written by Julian, and don't
apply to the new one (the functions they describe
John Hay [EMAIL PROTECTED] writes:
A make release failed here with:
#
touch release.8
Making fixit floppy.
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 6.
Warning: 1216 sector(s) in
On 2001-May-27 20:36:54 -0700, Kris Kennaway [EMAIL PROTECTED] wrote:
I've been getting rather a lot of these tonight..any ideas?
May 27 18:52:06 xor /boot/kernel/kernel: Data modified on freelist: word 2 of object
0xc1a60100 size 64 previous type pagedep (0xd6adc0de != 0xdeadc0de)
If this
A make release failed here with:
#
touch release.8
Making fixit floppy.
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 6.
Warning: 1216 sector(s) in last cylinder unallocated
On Mon, May 28, 2001 at 01:48:33PM +1000, Peter Jeremy wrote:
On 2001-May-27 20:36:54 -0700, Kris Kennaway [EMAIL PROTECTED] wrote:
I've been getting rather a lot of these tonight..any ideas?
May 27 18:52:06 xor /boot/kernel/kernel: Data modified on freelist: word 2 of
object 0xc1a60100
John Hay [EMAIL PROTECTED] writes:
A make release failed here with:
#
touch release.8
Making fixit floppy.
disklabel: ioctl DIOCWLABEL: Operation not supported by device
Warning: Block size restricts cylinders per group to 6.
Warning: 1216
Peter Jeremy wrote:
On 2001-May-27 20:36:54 -0700, Kris Kennaway [EMAIL PROTECTED] wrote:
I've been getting rather a lot of these tonight..any ideas?
May 27 18:52:06 xor /boot/kernel/kernel: Data modified on freelist: word 2 of
object 0xc1a60100 size 64 previous type pagedep (0xd6adc0de
Gang,
I cvs'ed and built world/kernel shortly after jhb's all clear on
thursday, and things went fairly well. I did the same again after rwatson's
mutex commits on friday and things have gone downhill from there. Just
about any heavy system activity locks the system up. That includes
I'll add a 'me too'. I've been doing the same workaround with success, but
it's still very frustrating. I can also guarantee a softdep freelist panic
about 1/4 the way into a buildworld. I can provide a trace if anyone is
interested.
Scott
-Original Message-
From: Marc G. Fournier
Another problem I'm having in -current right now is with softupdates. When
the system panic'ed the first time, it came up ok and fsck'ed fine with no
apparent loss of data. However, during the fsck it complained bitterly
about my superblocks, and when it was done and the system booted,
35 matches
Mail list logo
