On Tue, May 06, 2008 at 06:56:42AM -0700, Jeremy Chadwick wrote:
> On Tue, May 06, 2008 at 09:47:59AM -0400, Stephen Clark wrote:
...
> > but there is never one. It is like it hangs trying to dump the memory image.
> >
> > This mother board has both sata and pata controllers but I am using only
>
Jeremy Chadwick wrote:
On Tue, May 06, 2008 at 09:47:59AM -0400, Stephen Clark wrote:
Jeremy Chadwick wrote:
On Fri, May 02, 2008 at 09:40:20AM -0400, Stephen Clark wrote:
Mine is a nvidia 6300 mb with a dual core amd processor. I am causing the panic
while trying to develope a DD for a EVDO u
On Tue, May 06, 2008 at 09:47:59AM -0400, Stephen Clark wrote:
> Jeremy Chadwick wrote:
>> On Fri, May 02, 2008 at 09:40:20AM -0400, Stephen Clark wrote:
>>> Mine is a nvidia 6300 mb with a dual core amd processor. I am causing the
>>> panic
>>> while trying to develope a DD for a EVDO usb modem -
Jeremy Chadwick wrote:
On Fri, May 02, 2008 at 09:40:20AM -0400, Stephen Clark wrote:
Mine is a nvidia 6300 mb with a dual core amd processor. I am causing the panic
while trying to develope a DD for a EVDO usb modem - so it is not a great
problem - I was just surprised it wasn't rebooting. Thi
On Fri, May 02, 2008 at 09:40:20AM -0400, Stephen Clark wrote:
> Mine is a nvidia 6300 mb with a dual core amd processor. I am causing the
> panic
> while trying to develope a DD for a EVDO usb modem - so it is not a great
> problem - I was just surprised it wasn't rebooting. This is a 6.1 system
Stephen Clark wrote:
> Hello List
>
> How do I get my freebsd 6.1 box to automatically reboot after a panic?
>
> Thanks,
> Steve
According to the handbook this is the default behavior unless you have
KBD option enabled in your kernel, in which case adding KDB_UNATTENDED
would cause the machine not
I got a couple requests for the tuning settings I've been using; it
seems I'm not the only one who's had problems with FreeBSD 6.x
stability as compared to 4.x.
I don't understand the kernel well enough to say whether any of these
are to any extent "right", but despite being pure voodoo, they
Clifton Royston wrote:
On Thu, May 01, 2008 at 03:15:51PM -0400, Stephen Clark wrote:
Matthew X. Economou wrote:
Steve,
I recall having to set dumpdev in /etc/rc.conf before I could get
FreeBSD to reboot automatically after a panic. I have dumpdev=AUTO
set on all of my headless servers. If y
On Thu, May 01, 2008 at 03:15:51PM -0400, Stephen Clark wrote:
> Matthew X. Economou wrote:
> >Steve,
> >
> >I recall having to set dumpdev in /etc/rc.conf before I could get
> >FreeBSD to reboot automatically after a panic. I have dumpdev=AUTO
> >set on all of my headless servers. If you are fee
Matthew X. Economou wrote:
Steve,
I recall having to set dumpdev in /etc/rc.conf before I could get
FreeBSD to reboot automatically after a panic. I have dumpdev=AUTO
set on all of my headless servers. If you are feeling especially
brave, you can also set fsck_y_enable=YES and background_fsck=
Steve,
I recall having to set dumpdev in /etc/rc.conf before I could get
FreeBSD to reboot automatically after a panic. I have dumpdev=AUTO
set on all of my headless servers. If you are feeling especially
brave, you can also set fsck_y_enable=YES and background_fsck=NO.
Good luck! ;)
--
"I s
Quoting Stephen Clark, who wrote on Thu, May 01, 2008 at 08:44:42AM -0400 ..
> Hello List
>
> How do I get my freebsd 6.1 box to automatically reboot after a panic?
It should do that automatically?
> Thanks,
> Steve
> --
>
> "They that give up essential liberty to obtain temporary safety,
> de
On Fri, Apr 11, 2008 at 11:22:12AM +0200, Spil Oss wrote:
> Hi Bjoern,
>
> Was looking at that page, but my kernel doesn't have debug enabled.
Rebuild the kernel with debugging symbols, or do you not have the disk
space for it?
> Someone suggested getting a backtrace using the vanilla kernel, th
Hi Bjoern,
Was looking at that page, but my kernel doesn't have debug enabled.
Someone suggested getting a backtrace using the vanilla kernel, that
kernel should still be in /boot/kernel but I can't get it to fly!
/boot/kernel.old]# kgdb /boot/kernel.old/kernel /var/crash/vmcore.0
[GDB will not b
On Fri, 11 Apr 2008, Spil Oss wrote:
Yesterday my to-be server running FreeBSD 7.0 #0 has rebooted after a
kernel panic.
FreeBSD newserver.example.net 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Fri
Apr 4 07:22:22 CEST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/BEASTIE70 i386
Please find messages a
On Nov 14, 2007, at 10:13 AM, Vivek Khera wrote:
I'm running 6.2-REL. The old kernel was -p5, now without the zero
copy sockets, i'm running -p8. I'll know in a couple of days if
this is our solution.
For the archives:
Removing zero copy sockets seems to have fixed the issue. Not a
s
Vivek Khera wrote:
On Nov 13, 2007, at 7:49 PM, Kris Kennaway wrote:
notification.
In the meantime, your best bet is to disable ZERO_COPY_SOCKETS.
There is a chance this was a recent regression, previously in 7.0 they
were believed to work.
I'm running 6.2-REL. The old kernel was -p5,
On Nov 13, 2007, at 7:49 PM, Kris Kennaway wrote:
notification.
In the meantime, your best bet is to disable ZERO_COPY_SOCKETS.
There is a chance this was a recent regression, previously in 7.0
they were believed to work.
I'm running 6.2-REL. The old kernel was -p5, now without the zer
Various calls that downgrade permissions or virtually copy a pmap in
pmap.c now remove PG_W (and did not 6 months ago). This may be the
cause of the regression. It would probably be better (and faster) if
the pages were "held" instead of wired.
-Kip
On Nov 13, 2007 4:49 PM, Kris Kennaway <[EM
Kip Macy wrote:
Unfortunately, ZERO_COPY_SOCKETs have long been a known source of
problems. I think also, when a page is copied as part of COW the new
page is unwired (see pmap_copy et al.), this could lead to
socow_iodone unwiring after send a page that was not wired. An added
issue is that part
On Nov 13, 2007, at 5:13 PM, Kip Macy wrote:
In the meantime, your best bet is to disable ZERO_COPY_SOCKETS.
Thanks for the info. I'm putting the new kernel in place and will see
what happens and report back.
___
freebsd-stable@freebsd.org mail
Unfortunately, ZERO_COPY_SOCKETs have long been a known source of
problems. I think also, when a page is copied as part of COW the new
page is unwired (see pmap_copy et al.), this could lead to
socow_iodone unwiring after send a page that was not wired. An added
issue is that parts of the VM assume
On 11/13/07, Vivek Khera <[EMAIL PROTECTED]> wrote:
>
> On Nov 13, 2007, at 4:50 PM, Vlad GALU wrote:
>
> >>vmio = 1
> >>offset = Unhandled dwarf expression opcode 0x93
> >> (kgdb)
> >>
> >
> >Do you happen to have ZERO_COPY_SOCKETS in your kernel config?
> >
> >
>
> Yes, I do.
On Nov 13, 2007, at 4:50 PM, Vlad GALU wrote:
vmio = 1
offset = Unhandled dwarf expression opcode 0x93
(kgdb)
Do you happen to have ZERO_COPY_SOCKETS in your kernel config?
Yes, I do. Are they known to be bad under certain loads or just in
general. I don't have this
On 11/13/07, Vivek Khera <[EMAIL PROTECTED]> wrote:
> I've got a Dell 1750 box that was rock-solid stable running 4.11 for a
> couple of years now operating a pretty busy website backend. A month
> or so ago we wiped it clean and repurposed it to run a different
> website running Drupal with a Var
25 matches
Mail list logo
