4.9 Pre-Release build weirdness

2003-09-02 Thread T Kellers
After cvsupping, when I built world, it errored out with an error 134. I mv /usr/src /usr/src.old and cvsupped again... tried a buildworld, still an error 134 I "make kernel" and all went well After rebooting, I made world .. all went well I cp'd my custom kernel source to /usr/src/sys/i386/conf a

Re: How to force a kernel panic?

2003-09-02 Thread Archie Cobbs
Mike Harding wrote: > ...so I can test my debugging kernel? If you just need a debugger breakpoint, rather than a panic, then try one of these: sysctl debug.enter_debugger=ddb sysctl debug.enter_debugger=gdb -Archie ___

Re: testers needed for CAM INVARIANTS fix

2003-09-02 Thread Kenneth D. Merry
On Tue, Sep 02, 2003 at 12:46:16 +0400, Maxim Konovalov wrote: > Hi Ken, > > On Mon, 1 Sep 2003, 16:13-0600, Kenneth D. Merry wrote: > > > > > I've got a fix for the panic from the cd(4)/da(4) drivers when INVARIANTS > > is turned on in -stable. > > > > The fix is to create a task queue that runs

Re: Heads up: panics should be fixed!

2003-09-02 Thread Michael W. Oliver
+--- On Tuesday, September 02, 2003 20:10, | T.Suzuki proclaimed: | | Our -stable machine has been rebooting every 24hrs from upgrading | on "Jul 18". | | Then I did cvsup again on Aug 31 03:00JST (GMT +0900). But.. | | # gdb -k kernel.1 vmcore.1 | | IdlePTD at ph

Re: Heads up: panics should be fixed!

2003-09-02 Thread T.Suzuki
Our -stable machine has been rebooting every 24hrs from upgrading on "Jul 18". Then I did cvsup again on Aug 31 03:00JST (GMT +0900). But.. # gdb -k kernel.1 vmcore.1 IdlePTD at phsyical address 0x00367000 initial pcb at physical address 0x002c55c0 panicstr: page

RE: error in make installworld

2003-09-02 Thread Smux
The command works perfectly and the instalation goes with sucess tkx sorry for my english! =) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"

5.1-RELEASE-p2 daily panic

2003-09-02 Thread Brandon Weisz
(please CC as I'm not subscribed) Not sure if freebsd-stable@ is the correct list as this is 5.1-RELEASE-p2. Seems to have started after rebuild for -p2 patches. The box was quite stable before then. This is very easy to reproduce. It happens daily just before 24 hrs uptime. FreeBSD edge.int

Re: netinet/pim_var.h: No such file or directory

2003-09-02 Thread Steve Friedrich
netinet/pim_var.h: No such file or directory I saw this when I was searching thru the archives and I didn't notice a response. I had this problem and my workaround was to use "find" to find the file and copy it to /usr/include/netinet directory. Then the "depend" stage completed and the build

Re: netinet/pim_var.h: No such file or directory

2003-09-02 Thread Steve Friedrich
netinet/pim_var.h: No such file or directory I saw this when I was searching thru the archives and I didn't notice a response. I had this problem and my workaround was to use "find" to find the file and copy it to /usr/include/netinet directory. Then the "depend" stage completed and the build

Re: v6 in tonight's cvsup

2003-09-02 Thread Kirk Strauser
At 2003-09-02T03:04:16Z, Randy Bush <[EMAIL PROTECTED]> writes: > hosts with v6 enabled get lock-ups. Oh dear. My car and my wife's minivan both have v-6es. Should I be worried? > but two of them got very very net soggy. That's a new one. -- Kirk Strauser pgp0.pgp Description: PGP sign

Re: testers needed for CAM INVARIANTS fix

2003-09-02 Thread Maxim Konovalov
Hi Ken, On Mon, 1 Sep 2003, 16:13-0600, Kenneth D. Merry wrote: > > I've got a fix for the panic from the cd(4)/da(4) drivers when INVARIANTS > is turned on in -stable. > > The fix is to create a task queue that runs in a thread context and use > that to create the sysctl variables needed by cd(4

Re: kern/55727: rl(4) not working in recent 4.8-STABLE: watchdogtimeout

2003-09-02 Thread Eugene Grosbein
Bill Paul wrote: > > Ok. I went out and bought a D-Link 530+ card with the same chip you > have and used the latest (.18) driver, and it works fine for me. > I am really not sure what's broken. There are only two small things > that _might_ have bearing on the problem. To test my theory, download