'm aware of is the policy of not trying to break compatibility in
-STABLE, although that isn't strictly adhered to in practise.
Kris
pgp0.pgp
Description: PGP signature
in a minute.
>
> Mathew will soon be starting a work to merge his driver.
Please coordinate with re@ since the freeze will be beginning shortly.
kris
pgp0.pgp
Description: PGP signature
On Thu, Nov 13, 2003 at 06:44:25PM +1100, Peter Jeremy wrote:
> On Wed, Nov 12, 2003 at 06:04:00PM -0800, Kris Kennaway wrote:
> >...my sparc machine reports that my i386 nfs server has 15 exabytes of
> >free space!
> >
> >enigma# df -k
> >Filesystem 1K-blocks
/da0e 7957764 713336818777697%/usr
rot13:/mnt2 56595176 54032286 18014398507517260 0%/rot13/mnt2
Kris "Now accepting payment for data hosting" Kennaway
pgp0.pgp
Description: PGP signature
ocess is running? What state is it in? What else is running on the system?
Kris
pgp0.pgp
Description: PGP signature
On Tue, Nov 11, 2003 at 03:08:55PM -0500, David Hill wrote:
> Hello -
>
>
> I seem to not be able to get the IP address of a site. I am
> guessing its an issue with gethostbyname() and have a - at the end of
> the hostname...
...which is illegal.
Kris
pgp0.pgp
Description: PGP signature
On Fri, Nov 07, 2003 at 08:36:28PM -0800, Andrew P. Lentvorski, Jr. wrote:
> On Fri, 7 Nov 2003, John Baldwin wrote:
>
> > On 07-Nov-2003 Kris Kennaway wrote:
> > > So far this has happened (well, the panic above was new) on 5 separate
> > > machines that were all w
dn't post.
Kris
pgp0.pgp
Description: PGP signature
gt; experience?
> Thanks,
> Jason
Don't use -j when posting buildworld errors, because they are obscured
amongst other output. Please retry without -j and post the actual
error.
Kris
pgp0.pgp
Description: PGP signature
cannot continue
> *** Error code 1
> ~~~~
>
> I cannot figure out what is wrong. Please let me know.
This is a FAQ..read UPDATING.
Kris
pgp0.pgp
Description: PGP signature
On Sun, Nov 09, 2003 at 03:40:59PM -0500, Michael L. Squires wrote:
> The internal compiler error compiling R-letter (R-1.8.0) under 5-CURRENT went
> away when gcc was updated to 3.3.3.
Cool, it's good to know they're fixing bugs with those version updates :-)
Kris
pgp0
On Sun, Nov 09, 2003 at 06:05:06PM +0100, Lukas Ertl wrote:
> ---
> panic: Most recently used by mount
I reported this the other day..tjr has a fix in his p4 branch.
Kris
pgp0.pgp
Description: PGP signature
/sys/KERNSRV01 i386
Compile your rpc.lockd with -ggdb in the usual way (see the
developer's handbook for more help on debugging application crashes).
Is this repeatable?
Kris
pgp0.pgp
Description: PGP signature
On Fri, Nov 07, 2003 at 08:36:28PM -0800, Andrew P. Lentvorski, Jr. wrote:
> On Fri, 7 Nov 2003, John Baldwin wrote:
>
> > On 07-Nov-2003 Kris Kennaway wrote:
> > > So far this has happened (well, the panic above was new) on 5 separate
> > > machines that were all w
On Fri, Nov 07, 2003 at 10:10:07AM -0800, Kris Kennaway wrote:
> ad0: FAILURE - READ_DMA status=51 error=40
> ad0: FAILURE - READ_DMA status=51 error=40
> ad0: TIMEOUT - READ_DMA retrying (2 retries left)
> ata0: resetting devices ..
> ad0: FAILURE - already active DMA on th
t; Is this on a brand new -current ? lots of things that could
> cause this has been fixed...
Yes, it was updated last night.
Kris
pgp0.pgp
Description: PGP signature
M: Configure ad0c, start 0 length 30738677760 end 30738677759
GEOM: Configure ad0e, start 1073741824 length 2147483648 end 3221225471
GEOM: Configure ad0f, start 3221225472 length 27517452288 end 30738677759
Kris
pgp0.pgp
Description: PGP signature
aren't many possibilities here:
1) Environment
2) The makefile or something included by the makefile.
g++ doesn't come up with the command line it is executed with; gmake
executes g++ with the arguments specified in the makefile.
Kris
pgp0.pgp
Description: PGP signature
fwd_listener: cannot listen to port: 8000
> Could not request local forwarding.
>
> and I can't see any reason why the binding would fail:
Is something else (e.g. another ssh session) already bound to that port?
Kris
pgp0.pgp
Description: PGP signature
On Thu, Nov 06, 2003 at 03:10:49PM +1030, Alex Wilkinson wrote:
> CVSup'd today [Thu Nov 6 15:09:02 CST 2003].
>
> buildkernel fails on a warning.
Wasn't this fixed this morning?
Kris
pgp0.pgp
Description: PGP signature
On Thu, Oct 30, 2003 at 10:18:43AM -0800, Kris Kennaway wrote:
> One of the amd64 machines died with the following. The kernel is a
> few weeks old, so this might already be fixed.
>
> Kris
>
> malloc() of "64" with the following non-sleepable locks held:
> exclu
usr/obj/usr/src/i386/legacy/usr/games
> ===> gnu/usr.bin/gperf
> make: don't know how to make bsd.README. Stop
> *** Error code 2
>
> Did I miss something in my cvsup or is there a problem.
How do we know unless you show us your cvsupfile? :-)
Kris
pgp0.pgp
Description: PGP signature
eee754_scalbf'
> e_scalbf.So(.text+0x0): first defined here
> *** Error code 1
Apart from your libm problem (which I didn't see when I did this
locally), the fix to the java ports are not yet committed.
Kris
pgp0.pgp
Description: PGP signature
blem, and it still hints that the
> : native libc is being linked in.
>
> You might want to enable debugging of ld.so to confirm.
This was understood already (java is doing a dlopen of /usr/lib/libc.so).
Kris
pgp0.pgp
Description: PGP signature
relevant to you.
Sure, but..
> > > a good choice. I read the handbook and it advises to add the ... CFLAGS
> > > -0 -pipe and NOPROFILE= YES to /etc/make.conf.
> > ^^
> > No it doesn't ;-)
..it doesn't say anything about "-0 -pipe", which is a syntax error.
Kris
pgp0.pgp
Description: PGP signature
On Thu, Oct 30, 2003 at 05:03:38PM -0800, SteAltH FanThoM wrote:
> I am running 5-current the last cvs i did " 12.30 pm. today CST "
> failed on buildworld with this.
>
> ===> gnu/usr.bin/cvs/doc
> makeinfo --no-split -I /usr/src/gnu/usr.bin/cvs/doc -I
> /usr/src/gnu/usr.bin/cvs/doc/../../../.
5.1-current client.
>
> Me too!!
I've reported NFS corruption on certain p4 machines running 5.x, which
may or may not be related. No lockups though.
Kris
pgp0.pgp
Description: PGP signature
One of the amd64 machines died with the following. The kernel is a
few weeks old, so this might already be fixed.
Kris
malloc() of "64" with the following non-sleepable locks held:
exclusive sleep mutex mntvnode r = 0 (0x80758220) locked @
/a/asami/portbuild/amd64/src-clie
Is anyone else able to reproduce this?
- Forwarded message from pecquetj <[EMAIL PROTECTED]> -
>Number: 58581
>Category: kern
>Synopsis: System call hang 5.x triggered by gnunetd
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible:free
On Wed, Oct 29, 2003 at 10:40:29PM -0700, Greg Lewis wrote:
> On Wed, Oct 29, 2003 at 06:07:11PM -0800, Kris Kennaway wrote:
> > On Wed, Oct 29, 2003 at 03:28:32PM -0700, Scott Long wrote:
> >
> > > I just tried running the Diablo JDK under -current from yesterday (with
&
ewhere and SSLSessionCache is set to
> dbm:/some/dbm lockup does not accour.
>
> Linux 2.4.22 is not affected by this issue.
>
> Details:
What kernel configuration? What hardware?
Kris
pgp0.pgp
Description: PGP signature
me please
It sounds like you've made a mistake in upgrading - perhaps you didn't
follow the upgrade directions in the handbook?
Kris
pgp0.pgp
Description: PGP signature
es:+dlMain = dlopen("/usr/lib/libc.so", RTLD_LAZY);
./jdk131.patches:+void *dlMain = dlopen("/usr/lib/libc.so", RTLD_LAZY);
Java people, this is the cause of the binary incompatibility of 4.x
java binaries on 5.x. Can someone please fix?
Kris
pgp0.pgp
Description: PGP signature
running
> 5.1-R and others 4.8-R
I didn't see you do 'boot -h' in the log you posted.
Kris
pgp0.pgp
Description: PGP signature
installs properly. This is what I get on my serial console
> when I try to boot on 5.1-C (similar to 5.1-R) seems to hang after the vga0 shows
> up during boot.
>
> Is there anything I can do or provide to resolve my install problem?
Don't you have to tell the kernel
: the source of the libm problems was that libc.so.5 was *not*
linked in). I'm not sure why gdb says otherwise - perhaps it's
confused about the library paths.
Perhaps there's some kind of ABI problem here that java is choking on.
Kris
pgp0.pgp
Description: PGP signature
o part of the -sound list). So
> now I don't know what's going in with sound and -current.
Thanks very much for looking into this - it has been an outstanding
issue for too long. Hopefully some of the people who have reported
this can test your patches.
Kris
pgp0.pgp
Description: PGP signature
so the $65,000 question is:
> >
> >Does this make the Diablo JDKs work? :)
> >
>
>
> I could test, should I just get those files from current, integrate with
> 5.1-p10 and recompile?
That should work.
Kris
pgp0.pgp
Description: PGP signature
On Tue, Oct 28, 2003 at 12:21:09PM +0100, Karl M. Joch wrote:
> Kris Kennaway wrote:
>
> >On Tue, Oct 28, 2003 at 08:11:33AM +0100, Karl M. Joch wrote:
> >
> >>i added a stallion easy i/o to a 5.1 box. compiling the kernel fails
> >>with a lot of errors in s
On Tue, Oct 28, 2003 at 08:11:33AM +0100, Karl M. Joch wrote:
> i added a stallion easy i/o to a 5.1 box. compiling the kernel fails
> with a lot of errors in stallion.c. any chance that this gets corrected
> soon?
Post the errors you're seeing so we don't have to guess.
0.log
http://bento.freebsd.org/errorlogs/i386-5-latest/libesmtp-1.0_1,1.log
http://bento.freebsd.org/errorlogs/i386-5-latest/nc6-0.5_2.log
http://bento.freebsd.org/errorlogs/i386-5-latest/ninja-1.5.8.1.log
Can you please take a look?
Kris
pgp0.pgp
Description: PGP signature
gt; piece of code using "-O2" rather than "-O", and then execute "make" again.
>
> The gcc folks tend to be interested in this sort of thing. You might want
> to follow the instructions given and report the bug.
Try gcc 3.3.2 (e.g. install the port) first.
Kris
pgp0.pgp
Description: PGP signature
tendra
> actually
> ported to FreeBSD-current.
Is this a completely up-to-date system? I've been seeing this with
gcc, but I haven't verified if any of the subsequent commits to that
header fix the problem.
Kris
pgp0.pgp
Description: PGP signature
On Mon, Oct 27, 2003 at 07:29:17PM +0100, Kirill Ponomarew wrote:
> Hi,
>
> On Mon, Oct 27, 2003 at 10:22:33AM -0800, Kris Kennaway wrote:
> > I've been getting this since yesterday when trying to installworld:
> >
> > install: /var/chroot/usr/share/examples/net
trying to get a world built for about 3
days now, and it's been broken by one poorly-tested change or another.
That's very annoying.
Kris
pgp0.pgp
Description: PGP signature
50m30s
> panic: sleeping thread (pid 25) owns a mutex
> Uptime: 50m30s
This one is interesting..did you get a DDB trace or core?
Kris
pgp0.pgp
Description: PGP signature
/lib/libfetch/common.c on lines 58-63. See the following links for
> relevent information:
This has been discussed here in about half a dozen emails today. Are
you reading the mailing list as you are expected to when tracking
-current?
Kris
pgp0.pgp
Description: PGP signature
tch/common.c
> /usr/src/lib/libfetch/common.c:58: error: `EAINONAME' undeclared here (not
> in a
> function)
This was fixed yesterday.
Kris
pgp0.pgp
Description: PGP signature
On Fri, Oct 24, 2003 at 10:13:34AM -0700, Janet Sullivan wrote:
>
> Kris Kennaway wrote:
> >On Fri, Oct 24, 2003 at 04:39:14PM +0400, Sergey A. Osokin wrote:
> >>
> >>Fatal trap 12: page fault while in kernel mode
>
> >Looks like it might be related to t
ff40c) at syscall+0x310
> Xint0x80_syscall() at Xint0x80_syscall+0x1d
> --- syscall (202, FreeBSD ELF32, __sysctl), eip = 0x280bed2f, esp = 0xbfbff38c, ebp
> = 0xbfbff3b8 ---
>
> Any idea?
Looks like it might be related to the DRM import from yesterday.
You're not using any modules, are you?
Kris
pgp0.pgp
Description: PGP signature
ilure, with
> the additional error message
>
> /usr/src/lib/libfetch/common.c:58: error: 'EAINONAME' undeclared here (not in a
> function)
>
> Other error messages are similar or the same.
>
> I have re-cvsup'd and am trying again.
This was fixe
On Fri, Oct 24, 2003 at 09:44:45AM +0200, Pawel Jakub Dawidek wrote:
> Hello.
>
> It was reported already?
Yes, n times.
Kris
pgp0.pgp
Description: PGP signature
On Thu, Oct 23, 2003 at 12:07:14PM -0700, Kris Kennaway wrote:
> Updated to HEAD, booted with WITNESS enabled, and the boot dies here:
>
> ipfw2 initialized, divert disabled, rule-based forwarding enabled, default to
> accept, logging unlimited
> malloc() of "16" with th
up() at mi_startup+0xb5
begin() at begin+0x2c
Can you please investigate?
Kris
pgp0.pgp
Description: PGP signature
> tr
> panic() at panic+0x174
> trap() at trap+0x394
> -- fast data access mmu miss tar=0 %o7=0xc018b820 --
> quotactl() at quotactl+0x98
> syscall() at syscall+0x308
It looks like you have quotas enabled. Can you please provide more
details of your setup and how to reproduce this problem?
Kris
pgp0.pgp
Description: PGP signature
On Tue, Oct 21, 2003 at 11:47:32PM +0200, Jeroen Ruigrok/asmodai wrote:
> -On [20031021 20:52], Kris Kennaway ([EMAIL PROTECTED]) wrote:
> >On Tue, Oct 21, 2003 at 07:10:30PM +0200, Jeroen Ruigrok/asmodai wrote:
> >> You cannot set the root password as passwd dumps core on a sign
t;
> p.s.: you have *way* more issues here than locking- you've a bad disk.
I know, but the system shouldn't blow up with a lock assertion in this
failure mode.
> Anyway, isn't alpha desupported?
No.
Kris
pgp0.pgp
Description: PGP signature
> boot disk was totally zapped, filled with seemingly random characters.
This is a known bug in the ATA driver. Tor Egge provided a workaround
patch here a few weeks ago. I didn't try it because I can't afford to
trash my disks like that again.
Kris
pgp0.pgp
Description: PGP signature
to satisfy the installer, they both fail with a file not found error,
> most likely a device node.
This could also be because you're not running the right kernel.
Kris
pgp0.pgp
Description: PGP signature
showing how to tell whether these are real or not.
Kris
pgp0.pgp
Description: PGP signature
col, or if they're purely an artifact of the client.
>
> Also, can you confirm the Linux and FreeBSD clients are both using the
> same version of NFS with similar protocol settings (i.e., NFSv3 over UDP).
Does Linux do NFSv3 yet? I thought that at least until recently there
were sta
g_disk_start+0x1ec
g_io_schedule_down() at g_io_schedule_down+0x234
g_down_procbody() at g_down_procbody+0x5c
fork_exit() at fork_exit+0x100
exception_return() at exception_return
--- root of call graph ---
Kris
pgp0.pgp
Description: PGP signature
an we run ddb over the
> ethercon to debug a wedged machine?
No..that was addressd in Robert's mail.
Kris
pgp0.pgp
Description: PGP signature
> 1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:195
> 2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:195
> Stack backtrace:
>
> with no backtrace at all.
FWIW, the backtrace would have been reported on the system console.
Kris
pgp0.pgp
Description: PGP signature
On Mon, Oct 20, 2003 at 10:51:50AM +0200, John Angelmo wrote:
> Are there any hints how to solve my problem, I'm willing to give it a
> shot ;)
We're discussing it, please be patient.
kris
pgp0.pgp
Description: PGP signature
patibility breakage we're seeing here by comparing the symbols in
4.x and 5.x versions of libraries with the same major revision. We
can then run this once a day/week/whatever somewhere to catch these
problems as soon as they occur in future.
Kris
pgp0.pgp
Description: PGP signature
g with your system (i.e. stale headers in
/usr/include) that were causing your compilation failures?
Kris
pgp0.pgp
Description: PGP signature
ber in 5.x but is not
binary compatible. So the 4.x binary links to libc.so.4 and
libm.so.2, and the latter is actually a 5.x library that expects to
have __fpclassifyd resolved by linking with libc.so.5. Is it the case
on your system that you have old 4.x binaries installed?
Kris
pgp0.pgp
Description: PGP signature
528ff,68c) at slab_zalloc+0xb7
> uma_zone_slab(c103a3c0,1,c08528ff,68c,0) at uma_zone_slab+0xe6
> uma_zalloc_internal(c103a3c0,0,1,0,c101f470) at uma_zalloc_internal+0x3e
> bucket_alloc(80,1,c08528ff,70b,0) at bucket_alloc+0x5e
> uma_zfree_arg(c101f3c0,d278be04,0,778,60) at uma_zfree_arg+
ue as to why -march athlon breaks my networking?
That's a syntax error - can you please confirm you meant
-march=athlon?
Kernels aren't usually built without optimization (-O0). Is there
some reason you chose to do that?
Kris
pgp0.pgp
Description: PGP signature
On Tue, Oct 14, 2003 at 08:17:27PM -0700, Kris Kennaway wrote:
> On Wed, Oct 15, 2003 at 11:10:43AM +0800, David Xu wrote:
>
> > The change you made to ucontext.h breaks libkse. :-(
>
> Speaking of libkse breakage:
>
> 10427 root 200 10500K 8380K kserel 6:44
On Sat, Oct 18, 2003 at 10:25:20AM +0100, Lawrence Farr wrote:
> I had a similar problem with Samba-Devel that was down to me building
> over NFS.
Without rpc.lockd on both client and server?
Kris
pgp0.pgp
Description: PGP signature
given to you :-) (you didn't CC the
maintainer and you didn't attach config.log).
Kris
pgp0.pgp
Description: PGP signature
On Fri, Oct 17, 2003 at 06:19:55PM -0700, Janet Sullivan wrote:
> Is anyone able to successfully compile the newest
> /usr/ports/net/samba-libsmbclient under CURRENT?
http://bento.freebsd.org says yes.
Kris
pgp0.pgp
Description: PGP signature
cls -Wshadow -Wstrict-prototypes -Wwrite-strings
> -march=pentiumpro -DIN_GCC -DHAVE_LD_EH_FRAME_HDR
> -finhibit-size-directive -fno-inline-functions -fno-exceptions
> -fno-zero-initialized-in-bss -fno-omit-frame-pointer
It looks like you have highly non-standard CFLAGS.
Kris
pgp
On Thu, Oct 16, 2003 at 09:06:18AM -0400, Paul Mather wrote:
> Does anyone know whether the IBCS2 emulation functionality regressed
> going from FreeBSD 4 to FreeBSD 5?
It's quite possible, because that code is unmaintained.
Kris
pgp0.pgp
Description: PGP signature
On Thu, Oct 16, 2003 at 09:12:12AM +1100, Nigel Weeks wrote:
> Can someone give me the supfile tag for the latest 5.2 release candidate?
No such thing.
Kris
pgp0.pgp
Description: PGP signature
jndael-api-fst.c
>
> Thanks!
Yes, and it was claimed by someone else that this approach doesn't
actually fix the alignment problem.
Kris
pgp0.pgp
Description: PGP signature
%xcc, 1
> db> trace
> panic() at panic+0xf0
> trap() at trap+0x394
> -- memory address not aligned sfar=0xc037e7c1 sfsr=0x40029 %o7=0xc00d2740 --
> rijndael_blockEncrypt() at rijndael_blockEncrypt+0xe4
I think that's due to a recent commit of ume. It might not yet be
fixed.
Kris
pgp0.pgp
Description: PGP signature
rages: 0.00, 0.00, 0.00
at which point that package build machine was taken offline for
administrative reasons.
Kris
pgp0.pgp
Description: PGP signature
On Wed, Oct 15, 2003 at 01:23:42AM -0400, Daniel Eischen wrote:
> On Tue, 14 Oct 2003, Kris Kennaway wrote:
>
> > On Wed, Oct 15, 2003 at 11:10:43AM +0800, David Xu wrote:
> >
> > > The change you made to ucontext.h breaks libkse. :-(
> >
> > Speaking o
2.3
3523 kris 200 50924K 40996K kserel 2:32 0.00% 0.00% MozillaFirebird-bin
Those are threaded processes using libkse via libmap.conf, which are
using CPU but do not have any CPU% listed. Scheduler is 4BSD, kernel
was built yesterday.
Kris
pgp0.pgp
Description: PGP signature
-clients port fails saying:
> >
> > make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports
> /lib/libfntstubs.a. Stop
>
> I ran into this on my amd64 box too. Is yours an i386?
The port is broken on all architectures. anholt is looking into it.
Kris
pgp0.pgp
Description: PGP signature
On Sun, Oct 12, 2003 at 09:49:59PM -0700, John Reynolds wrote:
>
> [ On Sunday, October 12, Kris Kennaway wrote: ]
> >
> > Thanks..Alan made a commit which he thought might have fixed this, but
> > someone else also claimed it did not.
> >
> > See also
&
caring too much about it until now, but it seems it's
> still there in the kernel from Oct 11th, and I figured I might as well try to
> provide somebody some information ..
Thanks..Alan made a commit which he thought might have fixed this, but
someone else also claimed it did not.
See als
One of the package machines died with this, running -current from a
few days ago.
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x1c
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc055ea8e
stack pointer = 0x10:0xd9c0
III and CPU_ENABLE_SSE. I was able to get a traceback,
but I didn't bother to write it down. I can do so if necessary.
CPU: Pentium III/Pentium III Xeon/Celeron (497.44-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x673 Stepping = 3
Features=0x383f9ff
Kris
pgp0.pgp
Description: PGP signature
On Fri, Oct 10, 2003 at 08:33:01PM -0700, Kris Kennaway wrote:
> Since upgrading to -CURRENT last night I have been getting a lot of
> watchdog timeouts on my xl0 device every time I put it under load:
>
> citusc17# grep "watchdog timeout" messages | wc -l
> 44
>
ess except for the log warning when you have verbose
logging enabled.
Kris
pgp0.pgp
Description: PGP signature
itusc17 kernel: xlphy0: 10baseT, 10baseT-FDX, 100baseTX,
100baseTX-FDX, auto
Is anyone else seeing this?
Kris
pgp0.pgp
Description: PGP signature
t woudl be funny since the problem boards were replaced with Tyan
> S2518s, which have a PDC20267 onboard as well as the ROSB4. The disks
> were attached to the Promise, and never had any data corruption issues
> with them, at least under linnex.
This is a FreeBSD bug that was introduc
On Wed, Oct 08, 2003 at 02:16:52AM -0500, Alan Cox wrote:
> On Mon, Oct 06, 2003 at 02:30:30AM -0700, Kris Kennaway wrote:
> > I got this upon attempting to burn a CD with cdrecord on my
> > freshly-updated current machine:
> >
> > panic: mutex vm object not owned a
evice back to PIO.
I also had problems dumping onto a UDMA66 disk on a promise PDC20267
controller - it seemed to dump OK (dump was readable after I recovered
the disk), but it (or maybe the crash itself) trashed the partition
table.
Kris
pgp0.pgp
Description: PGP signature
eeds to know details of the
kernel which are not the same between the two versions.
Kris
pgp0.pgp
Description: PGP signature
p partition - I had to
recreate it by hand before I could bring the system back up, although
it then came back up without further problems.
Kris
pgp0.pgp
Description: PGP signature
I don't think I've seen this one before (i386, kernel built Sep 17).
Is it already fixed?
Kris
recursed on non-recursive lock (sleep mutex) vm page queue mutex @
/a/asami/portbuild/i386/src-client/sys/kern/vfs_bio.c:3630
first acquired @ /a/asami/portbuild/i386/src-client/sys/vm/vm
On Fri, Oct 03, 2003 at 10:10:20AM -0700, Lars Eggert wrote:
> Kris,
>
> Kris Kennaway wrote:
>
> >For some months now I have been experiencing NFS corruption on the
> >three machines in the dosirak.kr package cluster - these are SMP
> >pentium 4 machines that run
255H 63S/T 4462C)
SMP: AP CPU #3 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #2 Launched!
Kris
pgp0.pgp
Description: PGP signature
h cannot run on the 4.x kernel you are running.
The solution is to first boot into the 5.x kernel found at
/boot/kernel/kernel instead of letting your 4.x loader load the old
4.x kernel from the old default location.
Kris
pgp0.pgp
Description: PGP signature
even kill -HUP. The problems went away
when I reverted to libc_r.
Kris
pgp0.pgp
Description: PGP signature
101 - 200 of 1614 matches
Mail list logo
