On Sun, Nov 06, 2005 at 10:18:12AM +0100, Ales wrote:
snip
Well, it looks like the nvidia driver doesn't support 6-STABLE (yet).
Did you guys managed to recompile the driver?
After trying to recompile nvidia driver:
snip
In file included from nvidia_ctl.c:14:
./nv-freebsd.h:25:2: #error
Roland Smith wrote:
On Sun, Nov 06, 2005 at 10:18:12AM +0100, Ales wrote:
snip
Well, it looks like the nvidia driver doesn't support 6-STABLE (yet).
Did you guys managed to recompile the driver?
After trying to recompile nvidia driver:
snip
In file included from nvidia_ctl.c:14:
Hello.
After upgrade to RELENG_6, buildworld, buildkernel, installkernel,
reboot I got this error. With 5.4 there was no problem. Can anyone see
what is going on with this hw?
Aleš
You should recompile the nvidia port with the new kernel.
Boot with the driver disabled in the meantime.
On 11/5/05, Ales [EMAIL PROTECTED] wrote:
Hello.
After upgrade to RELENG_6, buildworld, buildkernel, installkernel,
reboot I got this error. With 5.4 there was no problem. Can anyone see
Joao Barros wrote:
You should recompile the nvidia port with the new kernel.
Boot with the driver disabled in the meantime.
On 11/5/05, Ales [EMAIL PROTECTED] wrote:
Hello.
After upgrade to RELENG_6, buildworld, buildkernel, installkernel,
reboot I got this error. With 5.4 there was no
Ales wrote:
Joao Barros wrote:
You should recompile the nvidia port with the new kernel.
Boot with the driver disabled in the meantime.
On 11/5/05, Ales [EMAIL PROTECTED] wrote:
Hello.
After upgrade to RELENG_6, buildworld, buildkernel, installkernel,
reboot I got this error. With 5.4
On 11/5/05, Ales [EMAIL PROTECTED] wrote:
Joao Barros wrote:
You should recompile the nvidia port with the new kernel.
Boot with the driver disabled in the meantime.
On 11/5/05, Ales [EMAIL PROTECTED] wrote:
Hello.
After upgrade to RELENG_6, buildworld, buildkernel, installkernel,
On Sat, 18 Jun 2005 07:17:52 +0200
Zoran Kolic [EMAIL PROTECTED] wrote:
After moving to amd64 system (64-bit),
I have problem writing cd with cdrecord.
This is just a me too follow-up. I have been using growisofs to write
DVDs on this machine before, so I haven't noticed this problem before.
On Mon, 20 Jun 2005 19:03:23 +0400
Igor Robul [EMAIL PROTECTED] wrote:
If you just wish write CD-R/RW then you can try burncd (8) which is in
burncd fails while fixating cd's.
--
regards,
Torfinn Ingolfsen,
Norway
___
freebsd-stable@freebsd.org
On Sat, 05 Nov 2005 18:42:04 +0100
Torfinn Ingolfsen [EMAIL PROTECTED] wrote:
On Mon, 20 Jun 2005 19:03:23 +0400
Igor Robul [EMAIL PROTECTED] wrote:
If you just wish write CD-R/RW then you can try burncd (8) which is
in
burncd fails while fixating cd's.
--
I agree. Happened to me as
On Sat, 5 Nov 2005, Joao Barros wrote:
On 11/5/05, Ales [EMAIL PROTECTED] wrote:
Joao Barros wrote:
You should recompile the nvidia port with the new kernel.
Boot with the driver disabled in the meantime.
On 11/5/05, Ales [EMAIL PROTECTED] wrote:
Hello.
After upgrade to RELENG_6,
On Thu, Oct 06, 2005 at 01:41:38PM -0700, Vinod Kashyap wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jung-uk Kim
Sent: Thursday, October 06, 2005 1:30 PM
To: freebsd-stable@FreeBSD.org
Cc: Dan Rue
Subject: Re: twa kernel panic
On Mon, 2005-10-24 at 11:13 -0500, Dan Rue wrote:
At one point, I received the following error message just before the
machine locked up:
Oct 12 11:36:13 leopard kernel: initiate_write_filepage: already started
I grepped for that error message in the freebsd kernel source, and found
it in
On Mon, Oct 24, 2005 at 11:07:28AM -0700, Vinod Kashyap wrote:
After going around with 3ware web support, this issue has
been concluded, but not resolved. I tried my 3ware 9500 on
FreeBSD 5.3, 5.4, and 5-STABLE. With all of these versions
of OS and driver (i never changed the driver
-Original Message-
From: Dan Rue [mailto:[EMAIL PROTECTED]
Sent: Monday, October 24, 2005 11:23 AM
To: Vinod Kashyap
Cc: freebsd-stable@FreeBSD.org
Subject: Re: twa kernel panic under heavy IO
On Mon, Oct 24, 2005 at 11:07:28AM -0700, Vinod Kashyap wrote:
After going around
Vinod Kashyap wrote:
Going by the dmesg, you have a 9.1.5.2 driver and 9.2 firmware. The
driver in 5 -STABLE is from the 9.2 release. So, you might not have
the driver upgrade done properly. Try using the driver and firmware
from the same release. If you still see problems, please contact
-Original Message-
From: Brandon Fosdick [mailto:[EMAIL PROTECTED]
Sent: Friday, October 07, 2005 6:06 PM
To: Vinod Kashyap
Cc: Jung-uk Kim; freebsd-stable@freebsd.org; Dan Rue
Subject: Re: twa kernel panic under heavy IO
Vinod Kashyap wrote:
Going by the dmesg, you have
Vinod Kashyap wrote:
How did you figure out the versions? I'm looking at his
dmesg, and my own, and I'm not seeing the version info in a
recognizable form. I must admit that I haven't been able to
grok the 3ware version numbers at all, so maybe I'm dense.
What am I missing?
9.1.5.2 and
-Original Message-
From: Brandon Fosdick [mailto:[EMAIL PROTECTED]
Sent: Friday, October 07, 2005 6:26 PM
To: Vinod Kashyap
Cc: freebsd-stable@freebsd.org; Jung-uk Kim; Dan Rue
Subject: Re: twa kernel panic under heavy IO
Vinod Kashyap wrote:
How did you figure out the versions
Vinod Kashyap wrote:
Under 'Release Notes to View', select 'release_Release_Notes_Web',
and you will get to a page which lists the version of each individual
component that's part of the release, among other things.
:) I would have known that if Firefox wasn't barfing on PDF's right now, or if
-Original Message-
From: Brandon Fosdick [mailto:[EMAIL PROTECTED]
Sent: Friday, October 07, 2005 6:50 PM
To: Vinod Kashyap
Cc: freebsd-stable@freebsd.org; Jung-uk Kim; Dan Rue
Subject: Re: twa kernel panic under heavy IO
Vinod Kashyap wrote:
Under 'Release Notes to View
Greetings,
I am running a 3ware 9500 SATA raid card in a 12x300GB raid 50
configuration.
Here is dmesg identifying the controller:
3ware device driver for 9000 series storage controllers, version: 2.50.02.012
twa0: 3ware 9000 series Storage Controller port 0xb800-0xb8ff mem
On Thursday 06 October 2005 04:07 pm, Dan Rue wrote:
Greetings,
I am running a 3ware 9500 SATA raid card in a 12x300GB raid 50
configuration.
Here is dmesg identifying the controller:
3ware device driver for 9000 series storage controllers, version:
2.50.02.012 twa0: 3ware 9000 series
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jung-uk Kim
Sent: Thursday, October 06, 2005 1:30 PM
To: freebsd-stable@FreeBSD.org
Cc: Dan Rue
Subject: Re: twa kernel panic under heavy IO
On Thursday 06 October 2005 04:07 pm, Dan Rue wrote
On Sun, Aug 07, 2005 at 06:51:09PM +0200, Petr Holub wrote:
Hi all,
I've encoutnered the follwing kernel panic on 5.4-RELEASE-p6. However,
as the machine is production and not development one, I don't have
debugger analysis. The panic might *theoretically* be due to problems
accessing
You need to follow the instructions in the chapter on kernel debugging
in the developers handbook in order for anyone to be able to begin
investigating this.
I though that - alas at the time of the panic, that machine didn't have
dump partition configured. :(( Anyway, I've configured that
On Tue, Aug 09, 2005 at 07:22:39PM +0200, Petr Holub wrote:
You need to follow the instructions in the chapter on kernel debugging
in the developers handbook in order for anyone to be able to begin
investigating this.
I though that - alas at the time of the panic, that machine didn't have
On Sat, Aug 06, 2005 at 12:06:39PM -0700, Jason C. Wells wrote:
While compiling bash for my new 6.0-BETA2 system, I received this error:
ad4: detached
panic: vm_fault
I don't have a dump for you and I really must be going to work now. More
later if I can get myself trained up on crash
Hi all,
I've encoutnered the follwing kernel panic on 5.4-RELEASE-p6. However,
as the machine is production and not development one, I don't have
debugger analysis. The panic might *theoretically* be due to problems
accessing faulty CD-R media in the ATAPI DVD/CD-RW drive (that was the
only
While compiling bash for my new 6.0-BETA2 system, I received this error:
ad4: detached
panic: vm_fault
I don't have a dump for you and I really must be going to work now. More
later if I can get myself trained up on crash dumps.
Later,
Jason C. Wells
Hello all,
Maybe you have problems with 5.4-stable (2*CPU 2.8GHz Xeon, SMP enabled) and
IPFW/DUMMYNET too?
With 75% probability i am geting kernel panic when i try to delete configured
ipfw pipe :(
best regards,
Ramunas M.
___
freebsd-stable
Zoran Kolic wrote:
Dear all!
After moving to amd64 system (64-bit),
I have problem writing cd with cdrecord.
Release 5.4
Nec 3520a (dvd writer)
If you wish to write DVDs, then you can try
/usr/ports/sysutils/dvd+rw-tools
If you just wish write CD-R/RW then you can try burncd (8) which is
Dear all!
After moving to amd64 system (64-bit),
I have problem writing cd with cdrecord.
Release 5.4
Nec 3520a (dvd writer)
CDrtools-2.01
Whatever I do with cdrecord, it panics with
fatal trap 9 message. First few lines, not
from kernel say that it is not the right
cdrecord and I need pro-dvd
Hello,
if your Vonage linksys RT31P2 talks H323 try /usr/ports/net/gatekeeper
in proxy mode.
Cheers,
Vladimir Botka
On Sun, 12 Jun 2005, Damon Hopkins wrote:
I can reproduce this very easily.. I pick up my phone and make a call
Current Setup
Cable Modem---FreeBSD 5.4 Stable---HUB--Machines
The Vonage RT31P2 does not talk H.323, and it's not necessary to do
anything other than plain vanilla NAT to have it work through a
firewall. That is, no port forwarding, no SIP payload re-writing, etc.
Just plain vanilla NAT for both the SIP signaling and the RTP payload
will be all that's
I can reproduce this very easily.. I pick up my phone and make a call
Current Setup
Cable Modem---FreeBSD 5.4 Stable---HUB--Machines
\--Vonage Linksys RT31P2
I've tried various nap rules and ipf filter settings.. here are the
current mappings and
Hi Damon,
Am 12.06.2005 um 23:02 schrieb Damon Hopkins:
Tracing pid 27 tid 100021 td 0xc15a4180
mcopydata(c17fa400,0,38,c193abc0,0) at m_copydata+0x28
ipllog(0,d3d46bc8,d3d46b50,d3d46b48,d3d46b40) at ipllog+0x1f1
ipflog(105819,c17fa450,d3d46bc8,c17fa400,0) at ipflog+0x18f
Hello Robert.
Today i install new freebsd box with freebsd 5-stable, sources from are
over Jun 6 09:28 EEST.
when i tried to work I got are full repeatable panic.
#2 0xc04aafb0 in panic (fmt=0xc0610e42 sbflush_locked: cc %u || mb %p
|| mbcnt %u)
at /usr/src/sys/kern/kern_shutdown.c:566
Sorry I can't really help. I get the same thing after setting up my
vonage VOIP adapter. I did a tcpdump on the interface and saw that I was
getting a lot of UDP traffic. I updated my box as of last night and now
I don't get a panic anymore but the box just locks up instead w/out
panicing.
Hi all,
It is possible to configure OS for rebooting when kernel panic?
--
WBR, Andrey V. Elsukov
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Fri, Jun 10, 2005 at 11:04:17AM +0400, Andrey V. Elsukov wrote:
Hi all,
It is possible to configure OS for rebooting when kernel panic?
That should be the default condition as long as you don't specify
debugger support (or do and use DDB_UNATTENDED)
Kris
pgpzKShPybVZI.pgp
Description
Kris Kennaway wrote:
That should be the default condition as long as you don't specify
debugger support (or do and use DDB_UNATTENDED)
Thanks.
I have RELENG_5 server with ATA RAID promise controller and 4 ATA disks
in two RAID0 stripes.
Today one RAID0 has BROKEN (ar0). I have tried umount -f
Andrew McNaughton wrote:
You can't unmount your root file system.
Because of this it's possibly a good idea to have as minimal a root
partition system as possible, off the raid system, and very rarely
changed, so it's unlikely to get screwed up.
Yes, i know. Root FS, and othser system FS's
On 2005.06.10 03:06:46 -0400, Kris Kennaway wrote:
On Fri, Jun 10, 2005 at 11:04:17AM +0400, Andrey V. Elsukov wrote:
Hi all,
It is possible to configure OS for rebooting when kernel panic?
That should be the default condition as long as you don't specify
debugger support (or do
On Fri, 10 Jun 2005, Andrey V. Elsukov wrote:
Andrew McNaughton wrote:
You can't unmount your root file system.
Because of this it's possibly a good idea to have as minimal a root
partition system as possible, off the raid system, and very rarely changed,
so it's unlikely to get screwed
libthr is experimental and unmaintained..it was removed in 6.0 (well,
Bugger. There goes my only workaround for PR threads/80992!
-pcf.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To
On Thu, May 26, 2005 at 02:41:05PM +0100, Pete French wrote:
libthr is experimental and unmaintained..it was removed in 6.0 (well,
Bugger. There goes my only workaround for PR threads/80992!
Um, what about use libthr in 6.0 as well? Did you try it and find
that it doesn't work?
Kris
On Wed, May 25, 2005 at 04:00:22PM -0700, Robert Faulds wrote:
Tomcat5.0.30
libthr.so.1 via /etc/libmap.conf
libthr is experimental and unmaintained..it was removed in 6.0 (well,
replaced by David Xu's threading library). Try using the standard
library instead.
Kris
pgpEJL2E0p45X.pgp
Hi,
I have reported kernel panic on Dell 1600SC with 5.4-RELEASE but it is
related to ipnat from IPFILTER V3.4.35. Without SMP everything seems to
work fine. But when I turn on SMP and do ping -f one of ip addresses that
is maped to outside interface produces kernel panic or lock hard
uname -v
FreeBSD 5.3-RELEASE-p9
panic message:
savecore: reboot after panic: kmem_malloc(45056): kmem
_map too small: 334680064 total allocated
when i try to do kgdb i get this:
kgdb: cannot read PTD
Panic after 31 days of uptime.
I will gladly show more data if needed.
--
How fortunate the man
On Fri, 6 May 2005, Piotr Gnyp [EMAIL PROTECTED] wrote:
panic message:
savecore: reboot after panic: kmem_malloc(45056): kmem
_map too small: 334680064 total allocated
Ok, I`ve found:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#KMEM-MAP-TOO-SMALL
when i try to do kgdb i get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Jason,
Am 25.04.2005 um 16:19 schrieb Jason Andresen:
[...]
Is there maybe a special place on each drive I could dd /dev/zero to
clear out all of the vinum information? I tried clobbering the vinum
slices on every drive and newfsing them as
I have a machine that I tried upgrading from 4-STABLE to 5-STABLE. In
the process I lost one of the disks and had to replace it. The problem
is, that gvinum knows about the disk, but I can't seem to either
create the media volume (kernel panic) nor erase that entry from the
vinum list
On Sat, 23 Apr 2005, Viktor Rosendahl wrote:
Hi,
Last night when I was asleep my FreeBSD workstation suffered a kernel panic
and did a coredump. The panic occurred at 3.02 AM, that is one minute after
the start of the daily script (coincidence?).
The only unusual thing I have been doing
Hi,
Last night when I was asleep my FreeBSD workstation suffered a kernel panic
and did a coredump. The panic occurred at 3.02 AM, that is one minute after
the start of the daily script (coincidence?).
The only unusual thing I have been doing before the panic was that I was
playing with a 1GB
On Tue, 5 Apr 2005, Mars Trading wrote:
Got a kernel panic starting mgetty on ucom devices from 5.4-STABLE
as of 5-APR-0400 UTC. Wasn't able to copy the panic message though.
Here's the kgdb backtrace:
#0 doadump () at pcpu.h:159
#1 0xc04bd35e in boot (howto=260)
at /usr/src/sys/kern
At 12:55 PM 08/04/2005, Doug White wrote:
This is a known bug. ucom does some funky USB gyrations to force the port
to flush and it trips over itself. I don't have the PR handy but there's
one filed with a description of the underlying issue from bde.
kern/79420
The patch that Ian Dowse provided
Got a kernel panic starting mgetty on ucom devices from 5.4-STABLE
as of 5-APR-0400 UTC. Wasn't able to copy the panic message though.
Here's the kgdb backtrace:
#0 doadump () at pcpu.h:159
#1 0xc04bd35e in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:410
#2 0xc04bd686 in panic
On Fri, 01 Apr 2005 08:05:47 -0500 Mike Tancsa [EMAIL PROTECTED] wrote
about Re: USB device causes kernel panic:
MT I have a XS-Drive Pro VP300 (Vosonic) here which runs fine as USB1
MT device, but completely screws up my system when pluggeg into a USB2
MT port.
MT Try updating to the latest
Hello
First, sorry for the lack of details, but given that 5.4 is in
prerelease I though it could be interesting to rapport the problem
anyway, in hope that somebody else has seen something similar.
I don't haave the actual panic message since the serial cable wasn't
connected at the time and I
at scbus1 target 0 lun 1 (probe0)
Somehow probing/attachment of the device doesn't succeed. In this state
also bgfsck is blocked (waiting for interrupts or whatever). When
unplugging the device I get the following kernel panic (handwritten):
fatal trap 12: page fault while in kernel mode
At 07:39 AM 01/04/2005, Gerrit Kühn wrote:
Hi folks,
I have a XS-Drive Pro VP300 (Vosonic) here which runs fine as USB1
device, but completely screws up my system when pluggeg into a USB2 port.
I'm running
(%:~)- uname -a
FreeBSD arc.pmp.uni-hannover.de 5.3-STABLE FreeBSD 5.3-STABLE #2: Thu Dec
9
On Fri, 01 Apr 2005 08:05:47 -0500 Mike Tancsa [EMAIL PROTECTED] wrote
about Re: USB device causes kernel panic:
MT (%:~)- uname -a
MT FreeBSD arc.pmp.uni-hannover.de 5.3-STABLE FreeBSD 5.3-STABLE #2: Thu
MT Dec 9 12:00:08 CET 2004
MT Try updating to the latest RELENG_5. There have been a lot
Hi,
I was experimenting with PF and ALTQ on a netbooted Soekris 4801 when I
got this after pfctl -f /etc/pf.conf.
altq assertion ifq-ifq_len == 0 failed: file
/usr/src/sys/contrib/altq/altq/altq_subr.c, line 256
Sadly I can't reproduce it, and I don't recall what the previous
iterations of
Hi,
Firstly thank you for your help with my other problem on 5.3. This one
is slightly more distressing to me and concerns 4.11-STABLE.
I was trying to install FreeBSD 4.11 on the server mentioned in
theother article because of some stability advice about 5.3, and I
started getting odd probelms.
Admin @ InterCorner wrote:
Hi there!
I have sent this message before (Wed, 19 Jan 2005 04:11:40 +0100), but
without respons. So I'll try again.
---
I have gladly installed FreeBSD5 on my laptop to be free from M$ !! :D
And soon I will install it on my worksation aswell.
Here is (in my
= 0
Jan 19 03:05:38 laptop kernel: current process = 0 (swapper)
Jan 19 03:05:38 laptop kernel: trap number = 12
Jan 19 03:05:38 laptop kernel: panic: page fault
Jan 19 03:05:38 laptop kernel: Uptime: 1s
Jan 19 03:05:38 laptop kernel: Automatic reboot in 15 seconds - press a key on
the console
* Admin @ InterCorner [EMAIL PROTECTED] [20050129 20:09]:
I have sent this message before (Wed, 19 Jan 2005 04:11:40 +0100), but
without respons. So I'll try again.
You didn't provide enough info to help with ACPI debugging
# [EMAIL PROTECTED] / 2005-01-19 23:10:53 +0100:
Hello, this is what I got after running buildkernel on 5.3-RELEASE with
GENERIC on an MSI FIS2R (VIA K8T800-based board), AMD64 2800+, 1.5GB RAM
(transcribed as I didn't have the opportunity to set up crashdumps; does
it work in 5.3-REL?):
Hello, this is what I got after running buildkernel on 5.3-RELEASE with
GENERIC on an MSI FIS2R (VIA K8T800-based board), AMD64 2800+, 1.5GB RAM
(transcribed as I didn't have the opportunity to set up crashdumps; does
it work in 5.3-REL?):
page fault while in kernel mode
fault virtual address =
On Wed, Jan 19, 2005 at 11:10:53PM +0100, Roman Neuhauser wrote:
Hello, this is what I got after running buildkernel on 5.3-RELEASE with
GENERIC on an MSI FIS2R (VIA K8T800-based board), AMD64 2800+, 1.5GB RAM
(transcribed as I didn't have the opportunity to set up crashdumps; does
it work in
# [EMAIL PROTECTED] / 2005-01-19 14:21:20 -0800:
On Wed, Jan 19, 2005 at 11:10:53PM +0100, Roman Neuhauser wrote:
Hello, this is what I got after running buildkernel on 5.3-RELEASE with
GENERIC on an MSI FIS2R (VIA K8T800-based board), AMD64 2800+, 1.5GB RAM
(transcribed as I didn't have
= 0 (swapper)
Jan 19 03:05:38 laptop kernel: trap number = 12
Jan 19 03:05:38 laptop kernel: panic: page fault
Jan 19 03:05:38 laptop kernel: Uptime: 1s
Jan 19 03:05:38 laptop kernel: Automatic reboot in 15 seconds - press a key on
the console to abort
Jan 19 03:05:38 laptop kernel
On Wed, Dec 15, 2004 at 12:42:25PM -0800, Scott Sewall wrote:
I'm running FreeBSD 4.10-RELEASE-p3 that occasionally panics. The panic
occurs seems to happen when I'm running rsync of large directories
possibly in combination with reading or writing to a compact flash
attached to USB.
In message [EMAIL PROTECTED], Peter Jeremy wri
tes:
On Wed, Dec 15, 2004 at 12:42:25PM -0800, Scott Sewall wrote:
I'm running FreeBSD 4.10-RELEASE-p3 that occasionally panics. The panic
occurs seems to happen when I'm running rsync of large directories
possibly in combination with reading
I'm running FreeBSD 4.10-RELEASE-p3 that occasionally panics. The panic
occurs seems to happen when I'm running rsync of large directories
possibly in combination with reading or writing to a compact flash
attached to USB.
I've attached the panic message, dmesg output, and gdb output.
If
On Wed, Dec 15, 2004 at 12:42:25PM -0800, Scott Sewall wrote:
I'm running FreeBSD 4.10-RELEASE-p3 that occasionally panics. The panic
occurs seems to happen when I'm running rsync of large directories
possibly in combination with reading or writing to a compact flash
attached to USB.
On Mon, 06 Dec 2004 15:48:02 -0800, Paul Saab [EMAIL PROTECTED] wrote:
Arjan Van Leeuwen wrote:
I had a panic that looked a lot like this (panic in swi, came up when
I had some network traffic), and it's also been reported by other
people than me. Turning of SACK seems to work for most
Arjan Van Leeuwen wrote:
Please read the original thread:
http://lists.freebsd.org/mailman/htdig/freebsd-stable/2004-November/009307.html
I couldn't get a crashdump on this machine, but I provided a lot of
information (traces) in that thread.
Since no one replied to my last post in that thread, I
I'm getting a kernel panic every time I start getting traffic (~ 20Mb/s
total) to two squid processes. This was not happening with -RELEASE. I
upgraded on the advice that STABLE would decrease the %cpu spent in
system, which was much higher than that spent in user. The machine's
only
On Mon, Dec 06, 2004 at 01:19:54PM -0800, Jeff Behl wrote:
I'm getting a kernel panic every time I start getting traffic (~ 20Mb/s
total) to two squid processes. This was not happening with -RELEASE. I
upgraded on the advice that STABLE would decrease the %cpu spent in
system, which
Kris Kennaway wrote:
On Mon, Dec 06, 2004 at 01:19:54PM -0800, Jeff Behl wrote:
I'm getting a kernel panic every time I start getting traffic (~ 20Mb/s
total) to two squid processes. This was not happening with -RELEASE. I
upgraded on the advice that STABLE would decrease the %cpu spent
On Mon, 06 Dec 2004 13:19:54 -0800, Jeff Behl [EMAIL PROTECTED] wrote:
I'm getting a kernel panic every time I start getting traffic (~ 20Mb/s
total) to two squid processes. This was not happening with -RELEASE. I
upgraded on the advice that STABLE would decrease the %cpu spent in
system
Arjan Van Leeuwen wrote:
I had a panic that looked a lot like this (panic in swi, came up when
I had some network traffic), and it's also been reported by other
people than me. Turning of SACK seems to work for most people (at
least it worked for me). Put net.inet.tcp.sack.enable=0 in
You're helpful reply doesn't seem to include any information on where to
upload a crash dump, if that's what is being asked. I haven't dealt
with them before. Perhaps you'd be so kind as to direct?
A reply that helps work around a problem is always welcome, especially
when it keeps a
On Mon, Dec 06, 2004 at 07:27:32PM -0800, Jeff Behl wrote:
You're helpful reply doesn't seem to include any information on where to
upload a crash dump, if that's what is being asked. I haven't dealt
with them before. Perhaps you'd be so kind as to direct?
A reply that helps work around
Jeff Behl wrote:
You're helpful reply doesn't seem to include any information on where
to upload a crash dump, if that's what is being asked. I haven't
dealt with them before. Perhaps you'd be so kind as to direct?
A reply that helps work around a problem is always welcome, especially
when
Ok finally got a serial console setup to catch the panic.
I was getting the dumps with 5.2.1-rc2. Upgraded to
CURRENT and got same dumps when doing
ncplist s, doing a mount_nwfs, o r when system is
shutdown with IPXrouted being the process mentioned.
Panic message following and a trace and ps
Dave McCammon wrote:
I'm getting a kernel panic when attempting
to mount an nwfs fs or when doing a
ncplist s.
When I run 'ncplist s' or 'ncplist c' I get interesting error message:
ncp_initlib: kernel module is old, please recompile it.
And my 5.2.1-RC2 isn't panicing after that commands
I'm getting a kernel panic when attempting
to mount an nwfs fs or when doing a
ncplist s. I believe it also panics on shutdown
with IPXrouted but not 100 percent sure. I will verify
soon if someone need the info.
getting a kernel panic 12
with instruction pointer at
c051ccb6.
nm /boot/kernel
On Fri, 13 Feb 2004, Dave McCammon wrote:
I'm getting a kernel panic when attempting to mount an nwfs fs or when
doing a ncplist s. I believe it also panics on shutdown with IPXrouted
but not 100 percent sure. I will verify soon if someone need the info.
getting a kernel panic 12
This is a serious question and not intended as a troll.
I have a dying IDE hard drive that I want to try and recover some file from -
the problem is that with it connected to my box, both FreeBSD 4.9-RELEASE and
5.2-RC2 kernel panic.
This can be reliably duplicated by booting the machine
But now after some minutes the same crash. I made some other
dump:
1: one nullfs-mounted jail at init 6: reboot after panic: null_checkvp
http://turando.felvi.hu/crash/crash_2.tgz (~430M)
http://turando.felvi.hu/crash/gdb.out.2
2: simply nullfs mounted jails: 2xbind9
This patch does apear to prevent the panic as described in PR kern/57369.
However the system still falls back to PIO4 when it should be capable of
UDMA33 (at least)
On October 30, 2003 09:32 pm, Juan Manuel Sanchez wrote:
The ata raid code in STABLE allows 15 seconds for reading the disk
Anyone knows howt to solve this prob?
Keith.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
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
: interrupt mask = none
/kernel: trap number= 12
/kernel: panic: page fault
/kernel: syncing disks... 27 1
Regards,
Vitor Carvalho
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
At 08:51 PM 29/08/2003 -0300, wrote:
Hi all,
recently i ordered an email here for list speaking that my server had given
crash.
Hi,
There is a more extensive patch by [EMAIL PROTECTED] that fixes a
few more bugs. See the message
...so I can test my debugging kernel?
Thanks,
Mike H.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Hi,
I have a machine Athlon XP2000+ with 512MB DDR, and a HD SCSI to be serving of proxy,
running only squid. It was functioning normally, when he gave the following message to
me of error in/var/log/messages:
Aug 26 11:31:03 kern.crit bolter/kernel: panic: vm_page_remove(): page not found
501 - 600 of 649 matches
Mail list logo
