On Sun, Sep 14, 2003 at 07:13:09PM -0700, Doug White wrote:
>Incidentally, if you are getting wrapping even without this, you can use a
>serial console to capture the output. I've had to do this for doing nasty
>ACPI debugging with lots of the options enabled.
For kernel spew, you can also increa
On Sun, 14 Sep 2003, masta wrote:
> I owe you a beer Doug (or a soda-pop)! ;)
hehe :)
> You were correct about the sysctl.conf being the root-cause of the kernel
> spew.
Mike Smith ran into it one day and we spent some time debugging it.
Someone made the observation that they were sysctl items
I owe you a beer Doug (or a soda-pop)! ;)
You were correct about the sysctl.conf being the root-cause of the kernel
spew.
My sysctl.conf is having these lines:
#security.bsd.see_other_uids=0
sysctl net.inet.tcp.blackhole=1
sysctl net.inet.udp.blackhole=1
See the fau paux? I must have decided to
On Sat, 13 Sep 2003, masta wrote:
> For some time now I've have an issue with a dell laptop I use. It spews a
> bunch of kernel junk after init is spawned, and the spew causes my dmesg
> to become too full to actually produce a file I can send to the list that
> is meaningfull.
I remember this :)
7;ve decided to proved the
info I have at hand. Hopefully somebody will understand what the mystery
kernel spew is and give me a clue. Later on I'll see if I can do the old
ctrl+alt+esc debuger trick while it spews to get a backtrace thingy. In
the mean time does anybody know how to increase the
