On 04-Nov-2003 Brian F. Feldman wrote:
Steve Ames [EMAIL PROTECTED] wrote:
For the past few weeks my -CURRENT system has been locking up. With a
recent kernel (from 11/2) the following appears:
Fault trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code =
While trying to murder Mozilla and gwenview alongside compiling world and
perl, something went wrong...
Unfortunately, I'd updated my sources just prior to the event, so any listing
is probably highly suspect. Most things should be using libthr via libmap.
Apologies for the lack of info, I'll see
Submitter-Id: current-users
Originator:Vyacheslav I. Ivanchenko
Confidential: no
Synopsis: Port emulators/vmware3 + FreeBSD 5.x = kernel panic
Severity: critical
Priority: high
Category: ports
Class: sw-bug
Release: FreeBSD 5.1-CURRENT i386
Environment
I'm getting crashes when trying to debug mozilla (under KSE).
The panic message is panic: absolutely cannot call smp_ipi_shootdown
with interrupts already disabled. Attached is the trace.
Any ideas?
--
Dan Eischen
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is
On Wed, 17 Sep 2003, Daniel Eischen wrote:
I'm getting crashes when trying to debug mozilla (under KSE).
The panic message is panic: absolutely cannot call smp_ipi_shootdown
with interrupts already disabled. Attached is the trace.
Any ideas?
% (kgdb) bt
% #0 doadump () at
On Thu, 18 Sep 2003, Bruce Evans wrote:
On Wed, 17 Sep 2003, Daniel Eischen wrote:
I'm getting crashes when trying to debug mozilla (under KSE).
The panic message is panic: absolutely cannot call smp_ipi_shootdown
with interrupts already disabled. Attached is the trace.
Any ideas?
On Thu, 18 Sep 2003, Bruce Evans wrote:
On Wed, 17 Sep 2003, Daniel Eischen wrote:
I'm getting crashes when trying to debug mozilla (under KSE).
The panic message is panic: absolutely cannot call smp_ipi_shootdown
with interrupts already disabled. Attached is the trace.
Any ideas?
I am experiences some difficulty upgrading from 5.1-RELEASE to -CURRENT. I
have a Sony VAIO GRX570(P4 1.6GHz, 512MB, DVDROM/CD-RW). I installed 5.1-R
and CVSup'd -CURRENT, did I make world, with no problems. On reboot I get:
Fatal trap 12: page fault while in kernel mode
Fault virtual address=
Hi Bosko,
Well a couple weeks ago I re-cvsup'd to current since I had missed one of your updates
it would seem by a day. I still had the panic occur... so I did as suggested and
upped my KVA. I did the following:
In the kernel
options KVA_PAGES=400
options NMBCLUSTERS=8192
Hi,
latest kernel causes a panic early during boot:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x68
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc02667cf
stack pointer = 0x10:0xc0641cf8
frame pointer
latest kernel causes a panic early during boot:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x68
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc02667cf
stack pointer = 0x10:0xc0641cf8
frame pointer
I am currently trying to upgrade from 5.1-RELEASE to current on my Sony VAIO
laptop, model number GRX-570. On first boot of CURRENT kernel a panic occurs
right after inphy:
Fatal trap 12: page fault while in kernel mode
Fault virtual address= 0xdeadc0de
Fault code=
On Wed, Aug 27, 2003 at 00:49:56 +0200, Martin wrote:
Hi,
I compiled world and kernel tonight (Aug 26th) on my Thinkpad
R40 with a CD/RW drive. I tried my old settings with cam
enabled so I can use cdrecord.
During boot I got a kernel panic about 10 seconds after the
kernel detected
On Wed, 2003-08-27 at 02:27, Kenneth D. Merry wrote:
There are known problems with atapicam.
Try enabling DDB in your kernel config, and get a stack trace. If you're
panicing in free_hcb(), disable atapicam and try again.
Yes. I did exactly as you said and I got panic in free_hcb(). I
On Wed, Aug 27, 2003 at 16:54:05 +0200, Martin wrote:
On Wed, 2003-08-27 at 02:27, Kenneth D. Merry wrote:
There are known problems with atapicam.
Try enabling DDB in your kernel config, and get a stack trace. If you're
panicing in free_hcb(), disable atapicam and try again.
Yes. I
Hi,
I compiled world and kernel tonight (Aug 26th) on my Thinkpad
R40 with a CD/RW drive. I tried my old settings with cam
enabled so I can use cdrecord.
During boot I got a kernel panic about 10 seconds after the
kernel detected the CD/RW drive. Here some info:
Fatal trap 12: page fault
On Thu, Aug 14, 2003 at 10:57:07AM -0600, Stephane Raimbault wrote:
Hi Bosko,
This is the output of sysctl vm.zone about 2 minutes before the crash
occured. let me know if there is anything else I can provide you for this
crashing problem.
H. I don't know, maybe you really do have
know if there is other data you need from me.
Thanks again,
Stephane.
- Original Message -
From: Stephane Raimbault [EMAIL PROTECTED]
To: Bosko Milekic [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 11:02 AM
Subject: Re: FreeBSD 5.1-R kernel panic
Hi Bosko
-R kernel panic
Hi Bosko,
Thank you for your suggestion. I am a little un-easy about upgrading
my
system from -RELEASE to -CURRENT. Did you mean, simply upgrading the
kernel
to -CURRENT, or the entire system?
I'll think of a way I can continue this testing with you so
, August 11, 2003 6:15 PM
Subject: Re: FreeBSD 5.1-R kernel panic
Please run 'sysctl vm.zone' periodically and capture the output.
Then wait for this to happen and feel free to send me the last captured
output before the crash.
Is this a re-occuring crash for you? I thought we fixed this already
PROTECTED]
To: Bosko Milekic [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, July 30, 2003 11:02 AM
Subject: Re: FreeBSD 5.1-R kernel panic
Hi Bosko,
Thank you for your suggestion. I am a little un-easy about upgrading my
system from -RELEASE to -CURRENT. Did you mean, simply
information to help analyze this
problem.
Thanks,
Stephane Raimbault.
- Original Message -
From: Bosko Milekic [EMAIL PROTECTED]
Newsgroups: mailing.freebsd.current
Sent: Sunday, July 27, 2003 8:56
Subject: Re: FreeBSD 5.1-R kernel panic
On Sat, Jul 26, 2003 at 10:48:21PM -0600, Stephane
On Wed, Jul 30, 2003 at 09:25:34AM -0600, Stephane Raimbault wrote:
Hi Bosko,
My kernel panic'd again this morning. I had removed all the USB devices
from my kernel and had set my /etc/rc.conf to usbd_enable=NO and the
kernel panic'd again.
I have attached both my kernel config file and
just the
kernel, or the entire /usr/src system you would like me to upgrade.
Thanks,
Stephane.
- Original Message -
From: Bosko Milekic [EMAIL PROTECTED]
Newsgroups: mailing.freebsd.current
Sent: Wednesday, July 30, 2003 9:35 AM
Subject: Re: FreeBSD 5.1-R kernel panic
On Wed, Jul 30
On Wed, Jul 30, 2003 at 11:02:05AM -0600, Stephane Raimbault wrote:
Hi Bosko,
Thank you for your suggestion. I am a little un-easy about upgrading my
system from -RELEASE to -CURRENT. Did you mean, simply upgrading the kernel
to -CURRENT, or the entire system?
Due to potential sync
On Sat, Jul 26, 2003 at 10:48:21PM -0600, Stephane Raimbault wrote:
Well, I had compiled options DDB into the kernel and today the kernel
panic'd... here is what I got. I ran the following in the db prompt.
trace, show reg, ps. Let me know if this is the kind of information
you need, and if
: mailing.freebsd.current
Sent: Sunday, July 27, 2003 8:56
Subject: Re: FreeBSD 5.1-R kernel panic
On Sat, Jul 26, 2003 at 10:48:21PM -0600, Stephane Raimbault wrote:
Well, I had compiled options DDB into the kernel and today the kernel
panic'd... here is what I got. I ran the following in the db prompt
.
- Original Message -
From: Bosko Milekic [EMAIL PROTECTED]
Newsgroups: mailing.freebsd.current
Sent: Wednesday, July 23, 2003 10:14
Subject: Re: FreeBSD 5.1-R kernel panic
On Wed, Jul 23, 2003 at 09:56:32AM -0600, Stephane Raimbault wrote:
Hi Bosko,
Looking at netstat -m, the value I'd
Stephane Raimbault wrote:
I recently realized that I was miss-understanding how much free memory I had
on the system, and I doubt I even need the full 4Gig's.
Perhaps I can re-confirm how to check how much free real memory is available
on the system.
For 4G of physical RAM, with 3G of KVA
Stephane Raimbault wrote:
Well I went to go change my /boot/loader.conf options to reflect the
following:
kern.vm.kmem.size=35
Assuming this is in pages, it is 1/3 of the total physical RAM in the
system. This is way too large, unless you have recompiled your kernel
to have 3G KVA vs.
vmware3-3.2.1-2237_1, rtc-2002.03.05.2_2, world built on 21-7, backtrace:
(kgdb) bt
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc02217d9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc0221bb8 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3
On Fri, 2003-07-25 at 07:54, Sawek ak wrote:
vmware3-3.2.1-2237_1, rtc-2002.03.05.2_2, world built on 21-7, backtrace:
snip trace
/S
I've been seeing these for a few days as well. I just did a quick
search for open PRs and found ports/54417 that says you should have
options VFS_AIO in your
On Fri, 2003-07-25 at 04:54, Sawek ak wrote:
vmware3-3.2.1-2237_1, rtc-2002.03.05.2_2, world built on 21-7, backtrace:
(kgdb) bt
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc02217d9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc0221bb8 in panic () at
+0xce
mi_startup() at mi_startup+0xb5
begin() at begin+0x2c
db
---
Thanks,
Stephane.
- Original Message -
From: Bosko Milekic [EMAIL PROTECTED]
Newsgroups: mailing.freebsd.current
Sent: Wednesday, July 23, 2003 10:14
Subject: Re: FreeBSD 5.1-R kernel panic
On Wed, Jul 23, 2003
kernel panic
Stephane Raimbault wrote:
Hi Thanks for your response,
I do not have PAE enabled... I've been hesitant of turning it on, I'm
not
sure if it's too stable, I noticed that the asr driver is in the
nodriver
list in the PAE kernel config file and I use the asr driver for my
handbook, I seem to remember seeing something about it in there.
Thanks,
Stephane.
- Original Message -
From: Stephane Raimbault [EMAIL PROTECTED]
Newsgroups: mailing.freebsd.current
Sent: Tuesday, July 22, 2003 0:33
Subject: Re: FreeBSD 5.1-R kernel panic
Hi Thanks for your response,
I
On Wed, Jul 23, 2003 at 09:08:18AM -0600, Stephane Raimbault wrote:
...
I was looking at uping the kern.vm.kmem.size as suggested to do as well, but
I cannot find that value in sysctl -a, so I'm not sure where to set that
specifically. I have found the value for nmbclusters and it is set to
]
Newsgroups: mailing.freebsd.current
Sent: Wednesday, July 23, 2003 9:14
Subject: Re: FreeBSD 5.1-R kernel panic
On Wed, Jul 23, 2003 at 09:08:18AM -0600, Stephane Raimbault wrote:
...
I was looking at uping the kern.vm.kmem.size as suggested to do as well,
but
I cannot find that value in sysctl
run GENERIC to see if continues to have the
problem? I can probably run on one CPU for a few days, especially over the
weekend.
At the very least, you need options DDB. This will drop you into
the debugger on a kernel panic, at which point you can just issue 'tr'
to get a stack trace
and get you the info as
soon as I can.
thanks again,
Stephane.
- Original Message -
From: Bosko Milekic [EMAIL PROTECTED]
Newsgroups: mailing.freebsd.current
Sent: Wednesday, July 23, 2003 9:28
Subject: Re: FreeBSD 5.1-R kernel panic
On Wed, Jul 23, 2003 at 09:24:24AM -0600, Stephane
On Wed, Jul 23, 2003 at 09:56:32AM -0600, Stephane Raimbault wrote:
Hi Bosko,
Looking at netstat -m, the value I'd probably be interested in is the
following:
3% of cluster map consumed
knowing that the Maximum possible is 25600 I can deduce that ~768 are being
used? Is that correct.
Stephane Raimbault wrote:
Hi Thanks for your response,
I do not have PAE enabled... I've been hesitant of turning it on, I'm not
sure if it's too stable, I noticed that the asr driver is in the nodriver
list in the PAE kernel config file and I use the asr driver for my Adaptec
2015S raid card.
: mailing.freebsd.current
Sent: Monday, July 21, 2003 16:36
Subject: Re: FreeBSD 5.1-R kernel panic
On Mon, Jul 21, 2003 at 03:01:24PM -0600, Stephane Raimbault wrote:
I'm running FreeBSD 5.1-RELEASE with the SMP kernel and ran across the
following kernel panic.
panic: kmem_malloc(4096): kmem_map too
On Tue, Jul 22, 2003 at 12:18:31AM +0100, Bruce Cran wrote:
It sounds like the same or similar problem reported in the 'USB crappiness'
thread - the system slows down, and then any command crashes the system with
the error about kmem. I posted a backtrace to the problem in usb_mem.c, and
I'm running FreeBSD 5.1-RELEASE with the SMP kernel and ran across the
following kernel panic.
panic: kmem_malloc(4096): kmem_map too small: 275251200 total allocated
I'm trying to figure out what could be causing this, what kind of
information that I could provide to this group (or other group
.
Mik
On Mon, Jul 21, 2003 at 03:01:24PM -0600, Stephane Raimbault wrote:
I'm running FreeBSD 5.1-RELEASE with the SMP kernel and ran across the
following kernel panic.
panic: kmem_malloc(4096): kmem_map too small: 275251200 total allocated
I'm trying to figure out what could be causing
On Mon, Jul 21, 2003 at 03:01:24PM -0600, Stephane Raimbault wrote:
I'm running FreeBSD 5.1-RELEASE with the SMP kernel and ran across the
following kernel panic.
panic: kmem_malloc(4096): kmem_map too small: 275251200 total allocated
I'm trying to figure out what could be causing
On Mon, Jul 21, 2003 at 06:24:07PM -0400, Mik Firestone wrote:
For what it is worth, I am having the exact same problem. I cvsup'd and
builtworld on Sunday, July 20, and my machine has been crashing about every
half-hour since. It starts slowing down, the load average begins to
climb
On Mon, Jul 21, 2003 at 06:43:11PM +, Bosko Milekic wrote:
On Mon, Jul 21, 2003 at 06:24:07PM -0400, Mik Firestone wrote:
For what it is worth, I am having the exact same problem. I cvsup'd and
builtworld on Sunday, July 20, and my machine has been crashing about every
half-hour
In message [EMAIL PROTECTED], Aaron Wohl writes:
I got a got this kernel panic:
geom/geom_dev.c:(Negative bio_offset (%jd) on bio %p,
Anyone seeing this also?
Please put DDB in your kernel and try to reproduce, then capture
traceback etc. (see handbook).
--
Poul-Henning Kamp
I got a got this kernel panic:
geom/geom_dev.c:(Negative bio_offset (%jd) on bio %p,
Anyone seeing this also?
This is on a 2 processor XEON intel motherboard / adaptec 5400S raid /
AMD g2 console card.
The AMI g2 console card provides via USB a keyboard virtual cdrom etc.
Most
Hello -
When I kldload nvidia, i receive a kernel panic.
options INVARIANTS
options INVARIANT_SUPPORT
options DDB
options WITNESS
panic: spin lock ctl.mtx_rm not in order list
panic messages:
---
Reading symbols from /usr/src/sys/i386/compile/WIND/modules/usr/src
Hi guys,
Attached is a gdb trace of a panic on a -current system from a few
days ago. It seems like it was caused by a select(2) in XFree86.
Although I was testing some unrelated changes in libthr kernel code,
I have seen this panic before (about 2 weeks ago) on a stock
kernel.
FreeBSD
Soeren Schmidt writes:
It seems Nicolai E M Plum wrote:
I noticed some ATA problems solved in -current recently, so I tried
compiling a kernel from sources about 2 days ago. Booting from that
(GENERIC) kernel, I do not get Mounting root.., instead I get
(approximately, can't cut/paste
Hi
I installed 5.1-RELEASE from the CD images, and have problems using DMA
on my ATA discs. I get the same problem on several discs, both several
years old and brand new, across several vendors. 4.6-RELEASE handles the
discs fine. Relevant excepts from the boot messages are below, the
entire
It seems Nicolai E M Plum wrote:
Hi
I installed 5.1-RELEASE from the CD images, and have problems using DMA
on my ATA discs. I get the same problem on several discs, both several
years old and brand new, across several vendors. 4.6-RELEASE handles the
discs fine. Relevant excepts from the
Tuesday, June 17, 2003, 11:24:53 PM, you wrote:
Hi
I installed 5.1-RELEASE from the CD images, and have problems using DMA
on my ATA discs. I get the same problem on several discs, both several
years old and brand new, across several vendors. 4.6-RELEASE handles the
discs fine. Relevant
I just got a panic. As I have never had one before, I don't know what to
do. It's on another system so I don't have to reboot immediately (that
would solve the problem temporarily, wouldn't it?) if someone would give
me some advice, I could try to help debug it; however, as I'm not a
coder
On Thu, Mar 27, 2003 at 11:24:44AM +1030, Greg 'groggy' Lehey wrote:
On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote:
I just got a panic. As I have never had one before, I don't know what to
do. It's on another system so I don't have to reboot immediately (that
would solve
On Wednesday 26 March 2003 07:54 pm, Greg 'groggy' Lehey wrote:
On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote:
I just got a panic. As I have never had one before, I don't know what to
do. It's on another system so I don't have to reboot immediately (that
would solve the
On Fri, Mar 28, 2003 at 12:54:16AM -0500, taxman wrote:
that gives an error that is similiar to:
WARNING: syntax error on file /boot/loader.conf
dumpdev=/dev/ad0s1b
^
Hi Tim,
Please do 'dumpdev=/dev/ad0s1b. The doube quotes is a must .
Jiawei
--
Without the userland, the
I just got a panic. As I have never had one before, I don't know what to
do. It's on another system so I don't have to reboot immediately (that
would solve the problem temporarily, wouldn't it?) if someone would give
me some advice, I could try to help debug it; however, as I'm not a
coder
On 2003.03.26 13:35:28 +, Jason Morgan wrote:
I just got a panic. As I have never had one before, I don't know what to
do. It's on another system so I don't have to reboot immediately (that
Have a look at
http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC
://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING
for information on how to get more information from a panic.
OK, so I'll set up my system to capture the crash dump for next time,
but is there anything I can do right now? I'm at the db debugging
prompt, but I
On Wednesday, 26 March 2003 at 13:35:28 +, Jason Morgan wrote:
I just got a panic. As I have never had one before, I don't know what to
do. It's on another system so I don't have to reboot immediately (that
would solve the problem temporarily, wouldn't it?) if someone would give
me some
)
Any suggestions?
-Original Message-
From: John Stockdale [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2003 11:41 AM
To: '[EMAIL PROTECTED]'
Subject: RE: mdconfig/mdmfs problems - kernel panic
Ahh, that explains why the multiple /dev/md* didn't help the problem.
I'm looking
Just had a kernel panic. This is the first time I've tried to give you
something useful to go on from a dump so if I haven't included all the
information you need let me know.
FreeBSD aftershock.xtaz.co.uk 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Mar 19
10:53:19 GMT 2003
[EMAIL PROTECTED
Ok asked somebody in the know and he suggested adding a backtrace so here we
go:
Incidently this occured as I was using an NFS mount from this server.
FreeBSD aftershock.xtaz.co.uk 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Mar 19
10:53:19 GMT 2003
[EMAIL
(4Front's SBLive/Audigy driver) causes a
kernel panic on load. If I don't load the driver the system boots fine,
and runs with no other problems.
This is the message I get from the debugger when I load the driver:
panic: Invalid major (-1030904368) in make_dev
I've posted this info to their support
rather than a straight kernel panic, I get several errors directly
attributed to units on ccd0)
I apologize for not having the kernel panic info, but I havn't been able
to record it as of yet, and I don't have time to cause another panic
right now.
If that will help I'll be glad to try it again
In message [EMAIL PROTECTED], John Stockdale writes:
OS: FreeBSD 5.0-CURRENT, JPSNAP20030314
I'm running a Dual Xeon system with 1GB DDRRAM, and trying to create a
ram disk to compile under, specifically to compile the kernel.
I've tried several methods, involving either creating one 512MB disk
Message-
From: Poul-Henning Kamp [mailto:[EMAIL PROTECTED]
Sent: Monday, March 17, 2003 11:27 AM
To: John Stockdale
Cc: [EMAIL PROTECTED]
Subject: Re: mdconfig/mdmfs problems - kernel panic
In message [EMAIL PROTECTED], John Stockdale
writes:
OS: FreeBSD 5.0-CURRENT, JPSNAP20030314
I'm running
On Fri, 7 Mar 2003, Jody Franklin wrote:
I'd been keeping up with current (world/kernel) every other week or so,
and until this week I had no real problems. But after the build I did on
March 3rd my soundcard driver (4Front's SBLive/Audigy driver) causes a
kernel panic on load. If I don't
/Audigy driver) causes a
kernel panic on load. If I don't load the driver the system boots fine,
and runs with no other problems.
This is the message I get from the debugger when I load the driver:
panic: Invalid major (-1030904368) in make_dev
I've posted this info to their support
On Wed, 12 Mar 2003, Tobias Reifenberger wrote:
Am Di, 2003-03-11 um 17.43 schrieb KT Sin:
Another panic in tcp_input while exiting gtk-gnutella.
Update your sources, and make sure that you have 1.202 of
sys/netinet/tcp_input.c. I had a 100% reproducable panic very similar to
yours, and hsu
On Thu, Mar 13, 2003 at 10:10:30AM -0800, Doug Barton wrote:
Update your sources, and make sure that you have 1.202 of
sys/netinet/tcp_input.c. I had a 100% reproducable panic very similar to
yours, and hsu fixed it.
Doug
The distributedfolding panic is also corrected.
Jiawei
--
Without
Am Di, 2003-03-11 um 17.43 schrieb KT Sin:
Another panic in tcp_input while exiting gtk-gnutella.
I just can say 'me too'. This kind of panic in tcp_input.c bites me
since some weeks. It seems to be triggered by massive opening/closing of
tcp connections (like gtk-gnutella does).
Any ideas how
leafy wrote:
On Tue, Mar 11, 2003 at 05:24:55PM -0800, Doug Barton wrote:
You didn't say when your most recent upgrade was. If you're using
5.0-Release, you should upgrade to 5-current, where this problem
should be
fixed already.
Doug
I buildworld/installworld daily. So it's not fixed.
On Wed, Mar 12, 2003 at 10:20:59AM -0300, Daniel C. Sobral wrote:
Well, yes, but are you cvsupping from releng=. or releng=RELENG_5_0 or
releng=RELENG_5_0_0_RELEASE (or similar stuff)? I did experience such
problems for a while, but they did get fixed a week or two ago for me.
--
Daniel C.
On Wed, Mar 12, 2003 at 10:40:56PM +0800, leafy wrote:
I run -current. period :)
Jiawei
As a side note, I've used both userland PPPoE and kernel PPPoE (mpd +ipfilter, which
is my current setup), both exhibit the same problem.
I'll try again tonight.
Jiawei
--
Without the userland, the
On Wed, Mar 12, 2003 at 10:42:30PM +0800, leafy wrote:
On Wed, Mar 12, 2003 at 10:40:56PM +0800, leafy wrote:
I run -current. period :)
Jiawei
As a side note, I've used both userland PPPoE and kernel PPPoE (mpd +ipfilter, which
is my current setup), both exhibit the same problem.
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x20
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01c5a96
stack pointer = 0x10:0xcd316a98
frame pointer = 0x10:0xcd316abc
code segment= base 0x0,
Another panic in tcp_input while exiting gtk-gnutella.
Script started on Wed Mar 12 00:38:24 2003
melati# gdb -k kernel.debug /var/crash/vmcore.1
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
You didn't say when your most recent upgrade was. If you're using
5.0-Release, you should upgrade to 5-current, where this problem should be
fixed already.
Doug
--
This .signature sanitized for your protection
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
On Tue, Mar 11, 2003 at 05:24:55PM -0800, Doug Barton wrote:
You didn't say when your most recent upgrade was. If you're using
5.0-Release, you should upgrade to 5-current, where this problem should be
fixed already.
Doug
I buildworld/installworld daily. So it's not fixed.
Jiawei
--
I'd been keeping up with current (world/kernel) every other week or so,
and until this week I had no real problems. But after the build I did on
March 3rd my soundcard driver (4Front's SBLive/Audigy driver) causes a
kernel panic on load. If I don't load the driver the system boots fine,
and runs
With my three days old 5.0-current I had a kernel panic this afternoon
while I had wi0 in promiscous mode (FWIW).
Message was:
panic: headlocked should be 0
--
Chris Christoph P. U. Kukulies [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
Date: Sat, 1 Mar 2003
With my three days old 5.0-current
panic: headlocked should be 0
Try updating to rev 1.198 of tcp_input.c which was committed on Feb 26,
around 3 days ago.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the
:
sleeping with process lock locked from /usr/src/sys/vm/vm_pageout.c:1184
Feb 26 21:33:20 portable-cur kernel: /usr/src/sys/kern/kern_synch.c:152:
sleeping with process lock locked from /usr/src/sys/vm/vm_pageout.c:1184
Feb 26 21:33:20 portable-cur kernel: panic: sleeping thread owns a mutex
Feb
This problem started about Feb 19 and continues thru today's updates.
Everything seems to work great until I shut down the X server
at which time I get a fatal 'page fault while in kernel mode.'
I have two -CURRENT machines at the moment and only the one
with the nVidia driver (and kernel module)
walt wrote:
This problem started about Feb 19 and continues thru today's updates.
Everything seems to work great until I shut down the X server
at which time I get a fatal 'page fault while in kernel mode.'
I have two -CURRENT machines at the moment and only the one
with the nVidia driver
Terry Lambert wrote:
walt wrote:
This problem started about Feb 19 and continues thru today's updates.
Everything seems to work great until I shut down the X server
at which time I get a fatal 'page fault while in kernel mode.'
I have two -CURRENT machines at the moment and only the one
with the
On 11:50-0800, Feb 23, 2003, walt wrote:
This problem started about Feb 19 and continues thru today's updates.
Everything seems to work great until I shut down the X server
at which time I get a fatal 'page fault while in kernel mode.'
I have two -CURRENT machines at the moment and only the
(kgdb) where
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239
#1 0xc01bcab9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:371
#2 0xc01bcd23 in panic () at /usr/src/sys/kern/kern_shutdown.c:542
#3 0xc0200cc2 in bwrite (bp=0xc785a060) at /usr/src/sys/kern/vfs_bio.c:842
#4
Panic message? A panic w/o the actual panic message is like taking your
car to the shop and saying it doesn't drive right.
On 22-Feb-2003 leafy wrote:
(kgdb) where
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:239
#1 0xc01bcab9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:371
On Fri, Feb 21, 2003 at 10:38:46PM -0500, John Baldwin wrote:
Panic message? A panic w/o the actual panic message is like taking your
car to the shop and saying it doesn't drive right.
I am sorry, here it is:
panic: bwrite: buffer is not busy???
panic messages:
---
Fatal trap 12: page fault
On Thu, 2003-01-23 at 23:56, Steve Kargl wrote:
On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote:
/boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0
syms=[0x4+0x5540+0x702d|]
snip
embedded 0 6 A 0x60 3 4 5 6 7 9 10 11 12 14 15
panic: pmap_mapdev: Couldn't
On Thu, 2003-01-23 at 23:56, Steve Kargl wrote:
Sorry if this is the second copy, I'm not sure if it went out the first
time or not
On Thu, Jan 23, 2003 at 05:40:16PM -1000, Vincent Poy wrote:
/boot/kernel/acpi.ko text=0x2fab4 data=-0x1a84+0x6e0
syms=[0x4+0x5540+0x702d|]
snip
On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
On Thu, 2003-01-23 at 23:56, Steve Kargl wrote:
Disable acpi. acpi is broken.
I had the same problem until today. If ACPI was enabled, I would get a
panic on boot. I removed MAXMEM from my kernel conf, recompiled, and
On Sun, 2003-01-26 at 19:08, walt wrote:
Steve Kargl wrote:
On Sun, Jan 26, 2003 at 05:08:40PM -0500, Eric Jones wrote:
Is there any reason, on newer motherboards, to need the MAXMEM option?
I don't know. I've always used MAXMEM. Guess it's
time to remove it from my kernel config
501 - 600 of 851 matches
Mail list logo
