I came across an interesting problem trying to pxeboot a diskless
machine over a wireless network.
The sequence of events goes like this:
network bios:
network bios issues DHCP request from 0.0.0.0 (via wireless bridge)
my dhcp server replies
network bios
Ok. A few panics later, I brought the box back from the dead, with the
help of a 5.0-rel mini-iso. :)
I have put the gory details (a script record of the session) on
http://anarcat.ath.cx/scrapped.log
(warning: it's big and ugly as the rest of this mail).
A few things about the final setup: my /
Howdy,
Excellent!
For regression tools, look at the /usr/src/tools/regression
directory in the -current source tree. There are regression tests
for sysv there.
Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61
unsubscribe freebsd-hackers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Mike Tancsa <[EMAIL PROTECTED]> writes:
> Thank you very much, I will do so as soon as I get the dump. BTW,
> could the act of giving the wrong params to dumpon cause the crash ?
No, it wouldn't.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
At 08:39 PM 17/02/2003 +0100, Dag-Erling Smorgrav wrote:
If / when you get a dump, show me the backtrace and the value of x, y
and udev (as reported by gdb operating on the recovered core)
Thank you very much, I will do so as soon as I get the dump. BTW, could
the act of giving the wrong para
Mike Tancsa <[EMAIL PROTECTED]> writes:
> ns4# nm /kernel | grep \^c0174 | sort
> [...]
> c01747d4 T makedev
> c01748f4 T freedev
This is it (makedev)
> Does this actually show the location ?
> ns4# gdb -k kernel.debug
> [...]
> (kgdb) list *0xc0174830
> 0xc0174830 is in makedev (/usr/src/sys/ker
At 07:50 PM 17/02/2003 +0100, Dag-Erling Smorgrav wrote:
Mike Tancsa <[EMAIL PROTECTED]> writes:
> I am seeing a repeatable panic with a 4.x SMP machine (not when in uni
> mode). It never produces a crash dump, but always panics when periodic
> runs.
Hmm, it doesn't even seem to *try* to dump...
Mike Tancsa <[EMAIL PROTECTED]> writes:
> I am seeing a repeatable panic with a 4.x SMP machine (not when in uni
> mode). It never produces a crash dump, but always panics when periodic
> runs.
Hmm, it doesn't even seem to *try* to dump... are you sure you have
configured a dump device?
> instru
Hello,
PostGreSQL (see the ports) is one (big) program which is difficult to set up
in a pure jail, as it uses shared memory : it could be a good candidate for
your test.
you may want to have first a patch against -Current, as this is the "One True
Way" to introduce a new functionality to Free
Hello,
PostgreSQL might be a good test, since it uses IPC to an extent. I also have
some
code for 5.0 that adds a struct prison pointer to the IPC primitives for
tracking purposes.
Although it doesn't give each jail its own IPC cache, it does ensure they
don't step on each
other. For the purpose o
Hello hackers.
I'm preparing a patch against FreeBSD 4.7 (for now) which splits IPC zones
between jails and main host. Every entity will have his own IPC memory
not shared with others (jails or main host). Message queues are already
patched, but it need to be tested - that's why I'm writing.
Does
At 2003-02-17T07:05:54Z, Pawel Jakub Dawidek <[EMAIL PROTECTED]> writes:
> I have prepared patch for jail functionality against FreeBSD 5.0-CURRENT.
> It provides multi-level jailing and multiple ips for jails.
That's awesome. I have no idea what I'd do with it, but it's a solution
that's beggin
I am seeing a repeatable panic with a 4.x SMP machine (not when in uni
mode). It never produces a crash dump, but always panics when periodic
runs. (started with a Jan 28th stable.
e.g.
Fatal trap 12: page fault while in kernel mode
mp_lock = 0102; cpuid = 1; lapic.id =
fault vir
Hello Daniel,
Sunday, February 16, 2003, 1:51:22 PM, you wrote:
DE> Does FreeBSD work with the Tyan i7500 (S2720UGN) motherboard? I'm
DE> particularly interested in whether the on-board gigabit NIC (using the
DE> intel 82545GC chip) works with the em driver, and whether the on-board
DE> SCSI con
15 matches
Mail list logo
