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,
Hello,
I updated from an older CURRENT to a newer one and I am now getting a
dozen
kernel: devstat_end_transaction: HELP!! busy_count for da1 is < 0(-1)!
messages every seconds during disk activity.
Any ideas about what happening? da1 is on a sym adapter:
sym0: <1010-66> port 0x2000-0x20ff mem
0x
Added device bpf to my kernel config file, make a buildkenel&installkernel,
rebooted but there's not bpf in /dev:
[EMAIL PROTECTED] flag]$ grep bpf /usr/src/sys/i386/conf/SOUTHCROSS
device bpf # Berkeley packet filter
[EMAIL PROTECTED] flag]$ uname -a
FreeBSD southcross.skyne
Added device bpf to my kernel config file, make a buildkenel&installkernel,
rebooted but there's not bpf in /dev:
[EMAIL PROTECTED] flag]$ grep bpf /usr/src/sys/i386/conf/SOUTHCROSS
device bpf # Berkeley packet filter
[EMAIL PROTECTED] flag]$ uname -a
FreeBSD southcross.skyne
Added device bpf to my kernel config file, make a buildkenel&installkernel,
rebooted but there's not bpf in /dev:
[EMAIL PROTECTED] flag]$ grep bpf /usr/src/sys/i386/conf/SOUTHCROSS
device bpf # Berkeley packet filter
[EMAIL PROTECTED] flag]$ uname -a
FreeBSD southcross.skyne
On Tue, Mar 11, 2003 at 02:07:04PM +0100, Paolo Pisati wrote:
>
> Added device bpf to my kernel config file, make a buildkenel&installkernel,
> rebooted but there's not bpf in /dev:
>
> [EMAIL PROTECTED] flag]$ grep bpf /usr/src/sys/i386/conf/SOUTHCROSS
> device bpf # Berkele
Hello.
As I posted prior to this question, I have problems in getting diskless
started with 5.0-Current as cvsupdated today. The problem is still the same
and after a night of hairloosing work I think I got closer to the problem.
We use PXE as bootstrap environment, isc-dhcp and a read-only disk
After cvsup/rebuild today at about 14:00GMT I now get a
'page fault while in kernel mode' just after the system
tries to mount the rootfs.
Yesterday's kernel still works fine, and the filesystem
came up clean, so I guess the new kernel didn't get far
enough to write anything to disk.
To Unsubscribe
On Mon, Mar 10, 2003 at 10:44:34 -0500, Mike Barcroft wrote:
> Andrey A. Chernov <[EMAIL PROTECTED]> writes:
> > Many programs (from ports too) defines _ISOC99_SOURCE to get C99
> > functions, but we don't sense this define currently. Here is the fix for
> > review:
>
> Cool. I didn't realize t
On Tue, Mar 11, 2003 at 04:14:08PM +0200, Ruslan Ermilov wrote:
> Try "ls -l /dev/bpf0" instead, etc. Beware of DEVFS surprises. :-)
It works
But, why it works like this?!?!?
/me confused =P
--
Paolo
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
In message <[EMAIL PROTECTED]>, Attila Nagy wri
tes:
>Hello,
>
>I updated from an older CURRENT to a newer one and I am now getting a
>dozen
>kernel: devstat_end_transaction: HELP!! busy_count for da1 is < 0(-1)!
>messages every seconds during disk activity.
Yes, I just got this myself today. I o
On Tue, Mar 11, 2003 at 04:41:54PM +0100, Flag_reda wrote:
> On Tue, Mar 11, 2003 at 04:14:08PM +0200, Ruslan Ermilov wrote:
> > Try "ls -l /dev/bpf0" instead, etc. Beware of DEVFS surprises. :-)
>
> It works
>
> But, why it works like this?!?!?
>
> /me confused =P
>
Because of "devi
Andrey A. Chernov <[EMAIL PROTECTED]> writes:
> Hm, I don't quite understand, which one part you mean? My patch handles
> 2 following cases:
>
> 1) Any _POSIX_C_SOURCE with _ISOC99_SOURCE. It is from real life example
> (ImageMagick). It wants lower POSIX level, *but* wants _ISOC99_SOURCE in
> th
In message <[EMAIL PROTECTED]>, Ruslan Ermilov writes:
>Because of "device cloning"; devices are created on demand.
"device cloning" is really a wrong name for this, and I regret that
I every used that term. "On demand device creation" is closer,
but it doesn't have any sort of ring to it.
--
Hey All,
I've a -CURRENT box that was cvsup'd yesterday. It's a backup file server
with a RAID array attached. This was a -STABLE machine at one point that
I updated. The last few messages in /var/log/messages before the panic
looked like this:
Mar 10 15:44:34 alvin kernel: isp0: bad underrun
Hello,
> Yes, I just got this myself today. I overlooked that devstat is not
> locked when I moved the devstat to geom_disk. Expect a patch tonight.
Great, thanks!
--[ Free Software ISOs - http://www.fsn.hu/?f=download ]--
Attila Nagy e-mail: [
On 10-Mar-2003 Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Conrad Sabatier writes:
>>
>>diff <(cat file1) <(cat file2)
>>
>>errors out with:
>>
>>diff: /dev/fd/63: No such file or directory
>>diff: /dev/fd/62: No such file or directory
>>
>>Apparently, the nodes for the named pipes
On Tue, Mar 11, 2003 at 10:49:43 -0500, Mike Barcroft wrote:
> > 1) Any _POSIX_C_SOURCE with _ISOC99_SOURCE. It is from real life example
> > (ImageMagick). It wants lower POSIX level, *but* wants _ISOC99_SOURCE in
> > the same time.
>
> I don't like this at all. The meaning of _ANSI_SOURCE is t
On Tuesday 11 March 2003 17:06, Poul-Henning Kamp wrote:
[snip]
> "device cloning" is really a wrong name for this, and I regret that
> I every used that term. "On demand device creation" is closer,
> but it doesn't have any sort of ring to it.
... but "device on demand" does have a ring to it :)
Andrey A. Chernov <[EMAIL PROTECTED]> writes:
> On Tue, Mar 11, 2003 at 10:49:43 -0500, Mike Barcroft wrote:
> > > 1) Any _POSIX_C_SOURCE with _ISOC99_SOURCE. It is from real life example
> > > (ImageMagick). It wants lower POSIX level, *but* wants _ISOC99_SOURCE in
> > > the same time.
> >
> > I
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
welco
>
> As I posted prior to this question, I have problems in getting diskless
> started with 5.0-Current as cvsupdated today. The problem is still the same
> and after a night of hairloosing work I think I got closer to the problem.
>
> We use PXE as bootstrap environment, isc-dhcp and a read-only
< said:
> What to do, if, say, C99 program want to use some POSIX functions from
> lower (and not from higher) POSIX standard?
Programmer error. Either it's a C99 program or it's an old-POSIX
program; it cannot be both.
> #define _GNU_SOURCE 1
> #define _ISOC99_SOURCE 1
> #define _POSIX_C_SO
On Tue, 11 Mar 2003, John Hay wrote:
:>>
:>> As I posted prior to this question, I have problems in getting diskless
:>> started with 5.0-Current as cvsupdated today. The problem is still the same
:>> and after a night of hairloosing work I think I got closer to the problem.
:>>
:>> We use PXE as
-CURRENT as of this week-end on a Dell Inspiron 8200 laptop.
During desktop use :
panic: bremfree: removing a buffer not on a queue
panic messages:
---
panic: bwrite: buffer is not busy???
syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue
Uptime: 9h18m39s
Dumpi
Hi all,
I just cvsup updated my tree (this is FreeBSD CURRENT, 5.0), and make
buildworld breaks with:
...
cc -O -pipe -I. -I/usr/src/usr.bin/xlint/lint1
-I/usr/src/usr.bin/xlint/lint1/../arch/i386 -I/usr/src/usr.bin/xlint/lint1/../common
-c /usr/src/usr.bin/xlint/lint1/tree.c
cc -O -pipe -I.
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, Ruslan Ermilov writes:
Because of "device cloning"; devices are created on demand.
"device cloning" is really a wrong name for this, and I regret that
I every used that term. "On demand device creation" is closer,
but it doesn't have any
ds10# newfs /dev/md0c
fstab: /etc/fstab:0: No such file or directory
/dev/md0c: 1.4MB (2880 sectors) block size 4096, fragment size 512
using 4 cylinder groups of 0.36MB, 91 blks, 192 inodes.
super-block backups (for fsck -b #) at:
32, 760, 1488, 2216
ds10# fsck -n /dev/md0c
fstab: /etc/fs
This card isn't detected by default, so I added the vendor and dev IDs to if_wi_pci.c.
Now it's detected, but doesn't attach. Here's what I think are the relevant bits from
dmesg.
pci2: physical bus=2
map[14]: type 4, range 32, base dcf0, size 4, enabled
map[18]: type 4, ran
In message <[EMAIL PROTECTED]>, Attila Nagy wri
tes:
>Hello,
>
>> Yes, I just got this myself today. I overlooked that devstat is not
>> locked when I moved the devstat to geom_disk. Expect a patch tonight.
>Great, thanks!
There is a patch which can be tried at:
http://phk.freebsd.dk/patc
Hey, is anybody ever going to answer this email?
On Wed, Feb 26, 2003 at 02:48:10PM +0200, Ruslan Ermilov wrote:
> On Tue, Feb 25, 2003 at 09:52:02PM +0200, Ruslan Ermilov wrote:
> > On Tue, Feb 25, 2003 at 08:02:19PM +0200, John Hay wrote:
> [...]
> > > Ok, with the patches below I can get to whe
I see several instances of this in /var/log/messages after cvsup'ing
Monday evening and rebuilding world and kernel. I haven't seen any
messages about this, so I figured I'd ask here.
Message:
Mar 11 17:33:30 lorne kernel: malloc() of "64" with the following
non-sleepablelocks held:
Mar 11 17:33:
Hi,
I get the following error (or whatever) in my bootmessage:
agp0: mem 0xf000-0xf7ff at device 0.0 o
n pci0
pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.AGP_ - AE_NOT_F
OUND
I tried playing around in the bios but couldn't find anything that would fix this.
Could th
This morning's kernel. User PPP, "cvs up".
Regards,
Vladimir~> sudo gdb -k /usr/obj/usr/src/sys/KUSHNIR/kernel.debug /usr/crash/vmcore.0
GNU gdb 5.2.1 (FreeBSD)
panic: page fault
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x20
fault code
"Daniel C. Sobral" wrote:
> > "device cloning" is really a wrong name for this, and I regret that
> > I every used that term. "On demand device creation" is closer,
> > but it doesn't have any sort of ring to it.
>
> Worst of all, "device cloning" is one of Terry's buzzwords. :-)
Actually, it's
I'm getting what I think is substantial time drift on my -current boxes. My home
firewall in particular drifts about .42 seconds every hour. My desktop machine drifted
~350 seconds over the last 5 days.
Anyone else seeing this?
James.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubsc
On Tue, Mar 11, 2003 at 03:50:25PM -0800, James Satterfield wrote:
> I'm getting what I think is substantial time drift on my -current
> boxes. My home firewall in particular drifts about .42 seconds every
> hour. My desktop machine drifted ~350 seconds over the last 5 days.
>
> Anyone else seeing
On Tue, 11 Mar 2003, James Satterfield wrote:
> I'm getting what I think is substantial time drift on my -current boxes.
> My home firewall in particular drifts about .42 seconds every hour. My
> desktop machine drifted ~350 seconds over the last 5 days.
.42 s/ 1 hr is about 116 ppm stability
3
Derek Tattersall wrote:
> I see several instances of this in /var/log/messages after cvsup'ing
> Monday evening and rebuilding world and kernel. I haven't seen any
> messages about this, so I figured I'd ask here.
>
> Message:
> Mar 11 17:33:30 lorne kernel: malloc() of "64" with the following
>
I guess I've just never paid that much attention to the clock. I think it's time for
me to get a real clock and setup an NTP server.
Thanks.
James.
On Tue, 11 Mar 2003 16:24:57 -0800 (PST)
"Andrew P. Lentvorski, Jr." <[EMAIL PROTECTED]> wrote:
> On Tue, 11 Mar 2003, James Satterfield wrote:
>
>
Title: ±z¦³¤U¦C¯S½è¶Ü
«lÃz¡I¡I¾_¾Ù¡I¡I
±z¦³¤U¦C¯S½è¶Ü¡H
1.¨Æ·~¥ø¹Ï¤ß
2.¤£¥Ì¤ß¥¤Z
3.¤£º¡©ó²{ª¬
4.«i©ó±¹ï¥¼¨Ó
¥un±z¾Ö¦³¤W¦C¯S½è¡A§Ú̱N§K¶O°ö°V±z©Ò¦³¬ÛÃö§Þ¾¯à¤O¡A
In article you write:
>I see several instances of this in /var/log/messages after cvsup'ing
>Monday evening and rebuilding world and kernel. I haven't seen any
>messages about this, so I figured I'd ask here.
>
>Message:
>Mar 11 17:33:30 lorne kernel: malloc() of "64" with the following
>non-slee
FYI, -bugs is not a discussion list.
On Tue, 11 Mar 2003, Attila Nagy wrote:
> The following reply was made to PR kern/49079; it has been noted by GNATS.
>
> From: Attila Nagy <[EMAIL PROTECTED]>
> To: Martin Machacek <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: kern/49079: panic: b
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
* Jonathan Lemon ([EMAIL PROTECTED]) [030312 01:12]:
> Date: Tue, 11 Mar 2003 18:59:15 -0600 (CST)
> From: Jonathan Lemon <[EMAIL PROTECTED]>
> Message-Id: <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: exclusive sleep mutex netisr...
> Organization:
> Cc:
>
> In a
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
--
"W
You should send this information to the gcc folks. My understanding is
that they are interested in solving problems like this.
Doug
On Mon, 11 Mar 2003, Dan Naumov wrote:
> Hello list.
>
> Since my issues are related to 5.0, I though I'd rather ask here. I've
> noticed an interesting problem: I
James Satterfield wrote:
> I guess I've just never paid that much attention to the clock. I think it's t
> ime for me to get a real clock and setup an NTP server.
> Thanks.
> James.
One of my gate boxes drifts about 11.5 sec a day. I use rdist to
keep all my hosts at each site in sync - vital for
Francisco Solsona <[EMAIL PROTECTED]> writes:
> Hi all,
>
> I just cvsup updated my tree (this is FreeBSD CURRENT, 5.0), and make
> buildworld breaks with:
It doesn't sound like your tree is completely in-sync.
> shouldn't MB_LEN_MAX be defined in /limits.h?
It's in revision 1.15 of .
Best reg
Derek Tattersall wrote:
> Mar 10 20:55:09 lorne kernel: malloc() of "64" with the following non-sleepablelocks
> held:
The only malloc of 64 bytes in this code path should be the
transient template structure malloc (FWIW).
John: did you look at my patch for the locking?
-- Terry
To Unsubscribe
Terry Lambert wrote:
> Derek Tattersall wrote:
> > Mar 10 20:55:09 lorne kernel: malloc() of "64" with the following
> > non-sleepablelocks held:
>
> The only malloc of 64 bytes in this code path should be the
> transient template structure malloc (FWIW).
>
> John: did you look at my patch for t
I've trimmed to the relavent part of the stack.
On Tue, 11 Mar 2003, Thomas Quinot wrote:
> #11 0xc0232072 in bwrite (bp=0xce5313e0) at /usr/src/sys/kern/vfs_bio.c:795
> #12 0xc0232a7c in bawrite (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:1138
> #13 0xc023a02b in cluster_wbuild (vp=0xc4a21124, size=
Compile, run under gdb, then type "print test()" when the program receives
SIGABRT. Seems to work incorrectly on 4.7 too.
#include
#include
void
test(void)
{
puts("hello");
}
int
main(int argc, char *argv[])
{
abort();
exit(0);
}
Tim
To Unsubscribe: send mail to [E
04:00 GMT Mar 12:
Just cvsup'd and rebuilt with same result as 12 hours ago --
I see a kernel panic "page fault while in kernel mode" just
after attempting to mount the root filesystem.
The kernel from yesterday works fine and when I reboot the
filesystems come up clean, so the new kernel nevers w
In article <[EMAIL PROTECTED]>, Dan
Naumov <[EMAIL PROTECTED]> wrote:
>
> Since my issues are related to 5.0, I though I'd rather ask here.
> I've noticed an interesting problem: I am using FreeBSD 5.0-p4 and
> GCC 3.2.1 and if I use "CPUTYPE=athlon-tbird" and "CFLAGS= -O2
> -mmmx -m3dnow -fomit-
On Wed, 5 Mar 2003 19:37:35 +0100 (MET)
Marcin CIE LAK <[EMAIL PROTECTED]> wrote:
> See the patches enclosed to emulators/rtc
> and emulators/vmware2 ports.
> Tested only for -current with:
> #define __FreeBSD_version 500104
Hum.. This is not work in my environment. Because MOD_LOAD initi
Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
-
Running -current from March 11 on a dual cpu compaq 5100, there are some
warnings in the dmesg about the tl ethernet interface.
Here are the warnings:
malloc() of "128" with the following non-sleepablelocks held:
exclusive sleep mutex tl0 (network driver) r = 0 (0xc4017aa8) locked @
/usr/src/5-
Got this when booting a fresh kernel:
Bad malloc flags: 4
Stack backtrace:
backtrace(c03953d4,4,1,c035e443,c1b6e500) at backtrace+0x17
malloc(3c,c03dfe80,4,c1b85d00,dcd7bc78) at malloc+0x5b
m_tag_alloc(0,e,30,4,c5a5bcc0) at m_tag_alloc+0x2f
ip6_addaux(c1b85d00,dcd7bcbc,c02af378,c1b85d00,c5bab800)
In message <[EMAIL PROTECTED]>, "Andrew
P. Lentvorski, Jr." writes:
>An $8.00 wristwatch has much better time accuracy that your multi-$100 PC.
That's because the crystal in your wristwatch is cut specially so that it
has a flat temp-co at about 23-16 C, whereas the xtal in your computer
is has
On Tue, 11 Mar 2003, Kris Kennaway wrote:
> Got this when booting a fresh kernel:
>
> Bad malloc flags: 4
> Stack backtrace:
> backtrace(c03953d4,4,1,c035e443,c1b6e500) at backtrace+0x17
> malloc(3c,c03dfe80,4,c1b85d00,dcd7bc78) at malloc+0x5b
What does the output of ls -l /etc/malloc.conf look
In message <[EMAIL PROTECTED]>, Andre Guibert de
Bruet writes:
>
>On Tue, 11 Mar 2003, Kris Kennaway wrote:
>
>> Got this when booting a fresh kernel:
>>
>> Bad malloc flags: 4
>> Stack backtrace:
>> backtrace(c03953d4,4,1,c035e443,c1b6e500) at backtrace+0x17
>> malloc(3c,c03dfe80,4,c1b85d00,dcd7b
Is Qt expected to work on -CURRENT? Because on my system it won't
even build:
[EMAIL PROTECTED] /usr/ports/x11-toolkits/qt31% pcvs up
[EMAIL PROTECTED] /usr/ports/x11-toolkits/qt31% ident Makefile
Makefile:
$FreeBSD: ports/x11-toolkits/qt31/Makefile,v 1.134 2003/02/22 09:13:12 demon Exp $
[E
The port builds fine here on -CURRENT from 5 march. It is supposed to find the
freebsd-g++ platform.
If this doesn't work, try adding -platform=freebsd-g++ to the CONFIGURE_ARGS
in the ports' Makefile.
Best regards,
Arjan
On Tuesday 11 March 2003 23:47, Dag-Erling Smorgrav wrote:
> Is Qt exp
Arjan van Leeuwen <[EMAIL PROTECTED]> writes:
> The port builds fine here on -CURRENT from 5 march. It is supposed to find the
> freebsd-g++ platform.
>
> If this doesn't work, try adding -platform=freebsd-g++ to the CONFIGURE_ARGS
> in the ports' Makefile.
Thanks. Turned out to be pilot error
On Tuesday 11 March 2003 23:47, Dag-Erling Smorgrav wrote:
> Is Qt expected to work on -CURRENT? Because on my system it won't
> even build:
[snip]
>The specified system/compiler is not supported:
>
>
>/usr/ports/x11-toolkits/qt31/work/qt-x11-free-3.1.1/mkspecs//usr/X11R6/mkspecs/defa
In message: <[EMAIL PROTECTED]>
"Hartmann, O." <[EMAIL PROTECTED]> writes:
: Can anyone help? Has someone a runnng diskless FBSD 5.0-R/5-CURRENT
: environment?
I fixed a couple of bugs in the /etc/rc.d files that broke diskless
boots about a month or two so after 5.0-RELEASE. It would
67 matches
Mail list logo
