On Thursday 27 November 2003 06:35 pm, Leo Bicknell wrote:
Since applying your patch I'd have IPv4 stop working 4 times. No panic,
no console errors, just IPv4 traffic no longer does anything. Can't
forward through the box. Can't ping the box, can't do anything.
Logging in on console
Things are actually looking pretty good at this point; I'm probably going
to move from 4.9-STABLE to 5.2-RELEASE on my main home server, but I'm
seeing the following with 5.2-BETA at this point:
I'm running 5.2-BETA cvsup'd at about 9 PM 11/25 on two systems; one is
a Supermicro P6DGH, dual
Sam Leffler
On Wednesday 26 November 2003 06:51 am, Michael L. Squires wrote:
On my dual CPU P6DGH the 11/22 cvsup of 5.2-BETA and netatalk crashes
on boot. Stopping netatalk from starting stops the crash.
I wasn't able to catch any crash information, but am currently
Guy Van Sanden
I just ran nmap host...
Nessus has the same effect.
When running nmap host (nmap 2.53 on a 4.9-STABLE box)) against a 5.2-BETA
host on the host I see
Nove 27 13:06:24 mikes sm-mta[483]: NOQUEUE: SYSERR(root): getrequests: accept:
Software caused connection abort
Nove 27
On my dual CPU P6DGH the 11/22 cvsup of 5.2-BETA and netatalk crashes
on boot. Stopping netatalk from starting stops the crash.
I wasn't able to catch any crash information, but am currently recompiling
with sources from last night to see if it's repeatable.
Mike Squires
/usr/src/contrib/libstdc++/libsupc++/unwind-cxx.h:41:20: unwind.h: No such=
file or directory
mkdep: compile failed
*** Error code 1
=20
Stop in /usr/src/gnu/lib/libstdc++.
*** Error code 1
I'm running 5.1-CURRENT now, but I was able to build 5.1-RELEASE-p10. I
suspect you need to
The internal compiler error compiling R-letter (R-1.8.0) under 5-CURRENT went
away when gcc was updated to 3.3.3.
Mike Squires
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
I've gone ahead and made it a debug message again in -current. It's
Worked. I now get
kernel: info: [drm] Initialized rdeon 1.9.0 20020828 on minor 0
kernel: drm0: [MPSAFE]
Thanks!
Mike Squires
SM P6DGH/AiW 7200
___
[EMAIL PROTECTED] mailing list
On Sat, 25 Oct 2003 04:50:30 +0900, Shin-ichi Yoshimoto wrote:
I'm using a radeon DRM module.
Now DRM work fine. But some kernel messages found my log like this.
kernel: error: [drm:pid38523:radeon_ioctl] *ERROR* can't find
authenticator
Is this OK ?
Is there
System: FreeBSD 5.1-CURRENT i386
Relevant hardware config:
Mainboard : ASUS P4S533-E (SIS645DX north, SIS962/L south bridges)
Memory : PC2700 512MB DDR RAM (memtest86 tested)
VGA card : ATI RADEON 9000 PRO
I had similar lockups with a SuperMicro P6DGH (dual PIII/850)/ATI All-in
The R statistics port (ports/math/R-letter) is at version 1.7.0. Being
the impatient type I tried compiling the recently released 1.8.0 using
the same Makefile (with 1.7 changed to 1.8) and a new MD5 value, and
had no new problems compiling.
R v.1.7 and v 1.8 trigger a bug in GCC (internal
Since the drm updates to 5-CURRENT I'm getting multiple instances of the
following at boot (and not trap 12 :-) ):
from dmesg
drm0: ATI Radeon QD R100 port 0xc800-0xc8ff mem 0xff48-0xff4f,
0xe80-0xefff irq 11 at device 0.0 on pci1
info: [drm] AGP at 0xf800 64MB
info:
Janet Sullivan
Shin-ichi Yoshimoto wrote:
Now DRM work fine. But some kernel messages found my log like this.
kernel: error: [drm:pid38523:radeon_ioctl] *ERROR* can't find
authenticator
DRM is working again for me as well, but I'm also seeing a lot of these
error messages with my
Tinderbox
/vol/vol0/users/des/tinderbox/CURRENT/amd64/amd64/src/lib/libfetch/common.c:60:
error: initializer element is not constant
Under 5.1-CURRENT or i386 cvsuped on 10/23 I get the same failure, with
the additional error message
/usr/src/lib/libfetch/common.c:58: error:
-CURRENT as of 10/17 is not a problem, kernel just compiled with SMP
support today after cvsup at about 2 PM EST (10/24) panics.
Nothing shows up in the logs (of course?). I'm recompiling with no SMP
support and will report if that dies also.
Hardware is the oddball SM P6DGH dual PIII/850 with
Fatal trap 12: page fault while in kernel mode
I just committed a fix for this to CVS. Sorry for the trouble.
--
Eric Anholt[EMAIL PROTECTED]
This looks like the bug that was causing me trouble.
Mike Squires
16 matches
Mail list logo
