After upgrading to 11.2-RELEASE-p2, the server constantly reboots instead of
hanging at the crash-dump.
Still, I don’t get a crash dump in /var/crash
kern.corefile: %N.core
kern.coredump_devctl: 0
kern.nodump_coredump: 0
kern.coredump: 1
kern.capmode_coredump: 0
kern.sugid_coredump: 0
On Sun, Sep 9, 2018 at 3:59 AM Rainer Duffner
wrote:
>
>
> > Am 09.09.2018 um 11:08 schrieb Eugene Grosbein :
> >
> > This list strips attachments, so you should upload it somewhere and post
> a link.
>
>
>
> Well actually, the text you get when you post one says it’s awaiting
> moderator
> Am 09.09.2018 um 11:08 schrieb Eugene Grosbein :
>
> This list strips attachments, so you should upload it somewhere and post a
> link.
Well actually, the text you get when you post one says it’s awaiting moderator
approval.
But I found a way to upload it without signing up for some
09.09.2018 5:35, Rainer Duffner wrote:
> Hi,
>
> I got a kernel panic
>
> This a a HP Gen10 system.
> It has this new Microsemi SAS HBA that only got the driver with 11.2.
>
> It’s running a syslog-server (syslog-ng)
>
> I have attached a screenshot of the panic, hopefully it comes through.
>
Hi,
I got a kernel panic
This a a HP Gen10 system.
It has this new Microsemi SAS HBA that only got the driver with 11.2.
It’s running a syslog-server (syslog-ng)
I have attached a screenshot of the panic, hopefully it comes through.
dumpdev is set to „AUTO“, but I don’t find any crashdumps
http://eis.bris.ac.uk/~mexas/core.txt.9
vmcore.9 is >450MB:
http://cmplx.uk/pic/vmcore.9
Thanks
Anton
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
On Tuesday, April 26, 2011 17:35:32 Gardner Bell wrote:
On Tue, Apr 26, 2011 at 04:25:26PM +0200, Bernhard Schmidt wrote:
On Tuesday, April 26, 2011 15:15:45 Gardner Bell wrote:
On Tue, Apr 26, 2011 at 4:12 AM, Bernhard Schmidt bschm...@freebsd.org
wrote:
On Tuesday, April 26, 2011
on 26/04/2011 02:09 Gardner Bell said the following:
#6 0xc0bcbebc in calltrap () at /usr/src/sys/i386/i386/exception.s:166
#7 0xc0999329 in ieee80211_tx_mgt_timeout (arg=0xc647a000)
at /usr/src/sys/net80211/ieee80211_output.c:2478
Looks like an issue in wireless code...
--
Andriy
On Tuesday, April 26, 2011 01:09:42 Gardner Bell wrote:
Downloading a torrent with many peers on a toshiba satellite notebook
using an Atheros AR5006 wireless nic caused the following panic. This
is an i386 system running 8.2-STABLE from around April 06.
Can you reproduce that?
A comment
On Tue, Apr 26, 2011 at 4:12 AM, Bernhard Schmidt bschm...@freebsd.org wrote:
On Tuesday, April 26, 2011 01:09:42 Gardner Bell wrote:
Downloading a torrent with many peers on a toshiba satellite notebook
using an Atheros AR5006 wireless nic caused the following panic. This
is an i386 system
On Tuesday, April 26, 2011 15:15:45 Gardner Bell wrote:
On Tue, Apr 26, 2011 at 4:12 AM, Bernhard Schmidt bschm...@freebsd.org
wrote:
On Tuesday, April 26, 2011 01:09:42 Gardner Bell wrote:
Downloading a torrent with many peers on a toshiba satellite notebook
using an Atheros AR5006
On Tue, Apr 26, 2011 at 04:25:26PM +0200, Bernhard Schmidt wrote:
On Tuesday, April 26, 2011 15:15:45 Gardner Bell wrote:
On Tue, Apr 26, 2011 at 4:12 AM, Bernhard Schmidt bschm...@freebsd.org
wrote:
On Tuesday, April 26, 2011 01:09:42 Gardner Bell wrote:
Downloading a torrent with
Downloading a torrent with many peers on a toshiba satellite notebook
using an Atheros AR5006 wireless nic caused the following panic. This
is an i386 system running 8.2-STABLE from around April 06.
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address
On Sun, 21 Mar 2010 00:39:01 -0400 jhell wrote:
DDB as I have heard can be configured AFAIR to textdump but I have no
knowledge of that.
ddb_enable=YES in /etc/rc.conf would be enough. But I also remove textdump
set in kdb.enter.panic script (/etc/ddb.conf) as I prefer normal dumps (with
(it is always the same core message),
saying something about
Fatal trap 12: page fault while in kernel mode [...] current process:
12
(swi2: cambio)
Can you show the stack traceback from the kernel core?
We had a problem a while ago at Isilon that I can't tell if it's
related. In our case
On 03/16/10 00:04, O. Hartmann wrote:
On 03/15/10 18:30, Matthew Fleming wrote:
Since the last update and make world on Friday, 12th March I get a
crash
on one of my FreeBSD SMP boxes (it is always the same core message),
saying something about
Fatal trap 12: page fault while in kernel mode
Since the last update and make world on Friday, 12th March I get a crash
on one of my FreeBSD SMP boxes (it is always the same core message),
saying something about
Fatal trap 12: page fault while in kernel mode
[...]
current process: 12 (swi2: cambio)
I'm sorry not providing more
Since the last update and make world on Friday, 12th March I get a
crash
on one of my FreeBSD SMP boxes (it is always the same core message),
saying something about
Fatal trap 12: page fault while in kernel mode [...] current process:
12
(swi2: cambio)
Can you show the stack traceback from
On 03/15/10 18:30, Matthew Fleming wrote:
Since the last update and make world on Friday, 12th March I get a
crash
on one of my FreeBSD SMP boxes (it is always the same core message),
saying something about
Fatal trap 12: page fault while in kernel mode [...] current process:
12
(swi2
mail to freebsd-stable-unsubscr...@freebsd.org
Here it is, with some additional information afterward:
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address
On Thu, Mar 05, 2009 at 07:55:30PM -0500, Boris Kochergin wrote:
Ahoy. I recently upgraded an amd64 machine to 7.1-RELEASE, and started
getting a bunch of these at a pretty high frequency (a few hours to a
day apart):
http://acm.poly.edu/~spawk/IMG00033.jpg
The current process is always
On Thu, 2009-03-05 at 19:55 -0500, Boris Kochergin wrote:
Ahoy. I recently upgraded an amd64 machine to 7.1-RELEASE, and started
getting a bunch of these at a pretty high frequency (a few hours to a
day apart):
http://acm.poly.edu/~spawk/IMG00033.jpg
The current process is always httpd.
afterward:
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x30
fault code = supervisor read data, page not present
instruction pointer = 0x8
Ahoy. I recently upgraded an amd64 machine to 7.1-RELEASE, and started
getting a bunch of these at a pretty high frequency (a few hours to a
day apart):
http://acm.poly.edu/~spawk/IMG00033.jpg
The current process is always httpd. They're particularly annoying
because the machine doesn't
read data overrun 180
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in
kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x104
fault code =
supervisor read, page not present
instruction pointer = 0x20:0xc0541da5
stack
pointer = 0x28
buffer:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x35000214
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc080c74f
stack pointer = 0x28:0xd7d25b4c
frame pointer = 0x28:0xd7d25b5c
code segment
with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 06
fault virtual address = 0x104E
fault code = supervisor read, page not presentx
instruction pointer = 0x20:0xc0668f3dp
stack pointer = 0x28:0xe8916c70e
frame pointer
: page fault while in kernel mode
cpuid = 2; apic id = 06
fault virtual address = 0x104E
fault code = supervisor read, page not presentx
instruction pointer = 0x20:0xc0668f3dp
stack pointer = 0x28:0xe8916c70e
frame pointer = 0x28:0xe8916c7cn
code segment
and write to 10 files on an NFS mounted
filesystem.
If I keep removing the files on one of the other machines in a while loop,
the first system panics:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x34
of the other machines in a while loop,
the first system panics:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x34
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06bdefa
stack
,
The panics keep happening, so I'm trying alternate kernel setups. This is a
trace of a panic on a default SMP kernel with debugging symbols.
I'm At a loss on how to progress at this point, perhaps someone can help me
please?
[snip]
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic
:
Hi Again,
The panics keep happening, so I'm trying alternate kernel setups. This is a
trace of a panic on a default SMP kernel with debugging symbols.
I'm At a loss on how to progress at this point, perhaps someone can help me
please?
[snip]
Fatal trap 12: page fault while
kernel setups. This is a
trace of a panic on a default SMP kernel with debugging symbols.
snip
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x34
^
fault code = supervisor read, page
that launches
40 threads to randomly append and write to 10 files on an NFS mounted
filesystem.
If I keep removing the files on one of the other machines in a while loop,
the first system panics:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x34
can help
me
please?
[snip]
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x34
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06bdefa
stack pointer = 0x28:0xeb9cf938
,
To continue this story, a colleague wrote a small program in C that launches
40 threads to randomly append and write to 10 files on an NFS mounted
filesystem.
If I keep removing the files on one of the other machines in a while loop,
the first system panics:
Fatal trap 12: page fault while
of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd.
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 0
of a panic on a default SMP kernel with debugging symbols.
I'm At a loss on how to progress at this point, perhaps someone can help me
please?
[snip]
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x34
fault code = supervisor read
.
Unread portion of the kernel message buffer:
6external: promiscuous mode enabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0596202
stack pointer = 0x28
.
Unread portion of the kernel message buffer:
6external: promiscuous mode enabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0596202
stack pointer = 0x28
On Sat, 6 Jan 2007, Marc G. Fournier wrote:
Just had the following happen on a FreeBSD 6.2-PRERELEASE #7: Sun Dec 17
01:28:52 AST 2006 system ... amd64, HP Proliant, 6G of RAM ... have core if
there is information that I can provide out of it ...
Fatal trap 12: page fault while in kernel
-PRERELEASE #7: Sun Dec 17
01:28:52 AST 2006 system ... amd64, HP Proliant, 6G of RAM ... have core if
there is information that I can provide out of it ...
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x18c
fault code
... have core
if
there is information that I can provide out of it ...
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x18c
fault code = supervisor read, page not present
instruction pointer = 0x8:0x801f9053
]
On Sat, 6 Jan 2007, Marc G. Fournier wrote:
Just had the following happen on a FreeBSD 6.2-PRERELEASE #7: Sun Dec 17
01:28:52 AST 2006 system ... amd64, HP Proliant, 6G of RAM ... have core
if there is information that I can provide out of it ...
Fatal trap 12: page fault while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just had the following happen on a FreeBSD 6.2-PRERELEASE #7: Sun Dec 17
01:28:52 AST 2006 system ... amd64, HP Proliant, 6G of RAM ... have core if
there is information that I can provide out of it ...
Fatal trap 12: page fault while in kernel
. :-{ (Well, there's something to be said for
consistency. :-})
It seems to run OK (albeit slowly) for a couple of minutes; then the
serial console reports:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 06
fault virtual address = 0x0
fault code
On Thu, 15 Jun 2006 16:22:40 -0700 David Wolfskill [EMAIL PROTECTED] wrote:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 06
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x20:0x0
stack pointer
).
* On machine A, I have installed the mail/postal port; I run postal,
directing it to send mail to the SMTP server on machine B (the machine
under test).
It seems to run OK (albeit slowly) for a couple of minutes; then the
serial console reports:
Fatal trap 12: page fault while in kernel mode
cpuid
/postfix.
The mount options is rw, quota (Yes, I used quota)
I have tried to replace my kernel, but GENERIC and custom kernels panic, too.
Please give me some advice :)
==
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x34
fault code = supervisor read, page
/postfix.
The mount options is rw, quota (Yes, I used quota)
I have tried to replace my kernel, but GENERIC and custom kernels panic, too.
Please give me some advice :)
==
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x34
fault code = supervisor read, page
so the application doesn't go
completely berserk. I note that running postal using the same
parameters against a similar box running Postfix just chugs along, no
problem at all.
Here's a typical complaint as extracted from /var/log/messages:
May 31 16:02:13 mx-out05 kernel: Fatal trap 12: page
kernel: Fatal trap 12: page fault while in kernel mode
May 31 16:02:13 mx-out05 kernel: cpuid = 0; apic id = 00
May 31 16:02:13 mx-out05 kernel: fault virtual address
May 31 16:02:13 mx-out05 kernel: = 0x0
May 31 16:02:13 mx-out05 kernel: fault code = supervisor read, page
not present
ithread_loop(c35260f0,d44c1d38,c07d220e,31d,dfff) at
ithread_loop+0x84
fork_exit(c0590a00,c35260f0,d44c1d38) at fork_exit+0xc1
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xd44c1d6c, ebp = 0 ---
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
Hi,
I had 6 crash in 3 hours with exactly the same messages
is my aac controler dead ?
aac0: COMMAND 0xc4c9d900 TIMEOUT AFTER 512 SECONDS
aac0: WARNING! Controller is no longer running! code= 0x100
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 01
fault virtual address
show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd.
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
in _mtx_lock_sleep (m=0x805710c0,
tid=18446742975234022368, opts=180,
file=0xfffe Address 0xfffe out of bounds,
My panic.
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x808080f4
fault code = supervisor read
Online 00:02 Online 00:03 Online
00:04 Online 00:05 Online 00:06 Online 00:07 Online 00:08 Online 00:09
Online 00:10 Online 00:11 Online 00:12 Online 00:13 Online 00:14
Online 00:15 Online 00:16 Online 00:17 Online 00:18 Online 00:19kernel
trap 12 with interrupts disabled
Fatal trap 12: page fault
On Fri, Mar 17, 2006 at 10:59:40AM -0600, Vlad wrote:
this is 6.0-STABLE as for Mar 17.
Are you using kernel mode ppp? If so, don't.
Kris
pgp3tycV8zjpL.pgp
Description: PGP signature
no, nothing like that. and it reboots several times a day.
also, I have my swap twice less than physical mem, so I can't get a
dump (btw, there was a patch for to gzip core before it stores it into
swap, so it can be fit in swap of smaller size - anyone has it?)
On 3/17/06, Kris Kennaway [EMAIL
On Fri, Mar 17, 2006 at 11:41:58AM -0600, Vlad wrote:
no, nothing like that. and it reboots several times a day.
Where do the online/offline messages come from?
Kris
pgptmL30y88dA.pgp
Description: PGP signature
I have Putty logging stuff and I guess it's either part of its
keepalive packets.
On 3/17/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Fri, Mar 17, 2006 at 11:41:58AM -0600, Vlad wrote:
no, nothing like that. and it reboots several times a day.
Where do the online/offline messages come
On Fri, Mar 17, 2006 at 11:46:03AM -0600, Vlad wrote:
I have Putty logging stuff and I guess it's either part of its
keepalive packets.
OK, thanks.
Kris
pgp9bQOumoHeI.pgp
Description: PGP signature
On Fri, Mar 17, 2006 at 11:41:58AM -0600, Vlad wrote:
no, nothing like that. and it reboots several times a day.
also, I have my swap twice less than physical mem, so I can't get a
dump (btw, there was a patch for to gzip core before it stores it into
swap, so it can be fit in swap of
-freebsd.
Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x48
fault code = supervisor read, page not present
instruction pointer = 0x8:0x8026d5f6
stack pointer
of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x48
fault code = supervisor read, page not present
instruction pointer = 0x8:0x80263071
stack pointer = 0x10
After a cvsup to RELENG_6 today I got the following trap while
encoding some videos with Avidemux. I'm going to leave the machine
at the ddb prompt since the following trace information doesn't seem
very helpful.
Fatal trap 12: page fault while in kernel mode
fault virtual address
Hello Peter,
Friday, February 10, 2006, 7:10:50 PM, you has on mind:
Please don't cross-post. A problem with 6-RELEASE is not appropriate
for [EMAIL PROTECTED]
I apologize.
On Fri, 2006-Feb-10 14:48:39 +0100, Daniel Gerzo wrote:
I've just got installed a brand new box, and I can say
with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xa9b2d30c
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc0810407
stack pointer = 0x28:0xe33b9b58
frame pointer = 0x28:0xe33b9be0
code segment
Please don't cross-post. A problem with 6-RELEASE is not appropriate
for [EMAIL PROTECTED]
On Fri, 2006-Feb-10 14:48:39 +0100, Daniel Gerzo wrote:
I've just got installed a brand new box, and I can say that it's
hanging on regular basis, around every 10 minutes.
Is the panic always at the
Hello.
While copying a few directories from one machine to my new notebook (tar
over ssh over wireless connection [if_iwi]), the notebook paniced with
the following:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x52535307
fault code = supervisor read
On Wednesday 07 December 2005 02:47 am, Yuri Khotyaintsev wrote:
On Friday 02 December 2005 14.54, John Baldwin wrote:
On Friday 02 December 2005 05:00 am, Yuri Khotyaintsev wrote:
I have the following panic occurring several times a week. The machine
is an NFS server, and it usually
On Friday 02 December 2005 14.54, John Baldwin wrote:
On Friday 02 December 2005 05:00 am, Yuri Khotyaintsev wrote:
I have the following panic occurring several times a week. The machine is
an NFS server, and it usually panics early in the morning, when first
people try to access it. After
of the kernel message buffer:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x74
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc053a426
stack pointer = 0x28:0xd56c0b88
frame
On Friday 02 December 2005 05:00 am, Yuri Khotyaintsev wrote:
I have the following panic occurring several times a week. The machine is
an NFS server, and it usually panics early in the morning, when first
people try to access it. After reboot it may work OK for 1-2 days, and then
panics
On Friday 02 December 2005 14.54, John Baldwin wrote:
On Friday 02 December 2005 05:00 am, Yuri Khotyaintsev wrote:
I have the following panic occurring several times a week. The machine is
an NFS server, and it usually panics early in the morning, when first
people try to access it. After
to be produce an
immediate and reproduceable panic (hand copied):
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc30f8000
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc05e9783
stack pointer = 0x10:0xd8030c38
frame pointer = 0x10:0xd8030c80
code
On Wed, Jun 29, 2005 at 04:42:49PM +0100, Dominic Marks wrote:
This may be because I compiled my debugging kernel after I had
installed the system, although it should have been an identical
source tree ... I'm currently rebuilding the system to
the freshest available -STABLE in the hope that
On Wednesday 29 June 2005 18:14, Kris Kennaway wrote:
On Wed, Jun 29, 2005 at 04:42:49PM +0100, Dominic Marks wrote:
This may be because I compiled my debugging kernel after I had
installed the system, although it should have been an identical
source tree ... I'm currently rebuilding the
this from over the
local network, unfortunately this seems to be produce an
immediate and reproduceable panic (hand copied):
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xc30f8000
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc05e9783
On Thu, 17 Feb 2005, Rong-En Fan wrote:
On Wed, 16 Feb 2005 15:36:25 -0800 (PST), Doug White
[EMAIL PROTECTED] wrote:
On Wed, 16 Feb 2005, Rong-En Fan wrote:
Hello,
This is a 5.3-RELEASE-p5/amd64 on IBM X236 (EM64T) with 2GB RAM
and a LSI 21320 rmpt(4) running at 160MB/s with a
On Wed, 16 Feb 2005 15:36:25 -0800 (PST), Doug White
[EMAIL PROTECTED] wrote:
On Wed, 16 Feb 2005, Rong-En Fan wrote:
Hello,
This is a 5.3-RELEASE-p5/amd64 on IBM X236 (EM64T) with 2GB RAM
and a LSI 21320 rmpt(4) running at 160MB/s with a hardware
RAID (da0, da1). HTT is enabled. When
to rebuild first, I'm getting the exiting from
__thread_start error...
any suggestions are welcome. :)
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 06
fault virtual address = 0x88
fault code = supervisor read, page not present
instruction pointer
)
kernel conf dmesg (boot -v) are at
http://rafan.infor.org/tmp/236/
any suggestions are welcome. :)
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 06
fault virtual address = 0x88
fault code = supervisor read, page not present
instruction pointer = 0x8
)
kernel conf dmesg (boot -v) are at
http://rafan.infor.org/tmp/236/
any suggestions are welcome. :)
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 06
fault virtual address = 0x88
fault code = supervisor read, page not present
instruction pointer = 0x8
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
14:36:28 CET 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/WRK i386
# burncd -f /dev/acd0 blank fixate
blanking CD - 100% done
fixating CD, please wait..
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xfffc
fault code
.
If there's any additional informtion I can provide to try and resolve
the problem, please ask. I'm willing to put some effort into fixing the
problem.
Any and all help is greatly appreciated.
-- Scott
Fatal trap 12: page fault while in kernel mode
mp_lock = 0102; cpuid = 1; lapic.id = 0100
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.
* Ernst de Haan ([EMAIL PROTECTED]):
The most obvious possibility seems to be 'maxusers 0'
No.
This just means to autoconfigure a value according to the amount of
memory present at configure time.
--Thomas
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Is there a possibility that a memory chip is dead (or should I say
deadish)?
As I said, the memory died. :)
The Memtest86 returned a lot of errors. I've replaced the memory module
and now it seems all right.
Mario Pranjic, dipl.ing.
sistem administrator
Knjiznica, Institut Rudjer Boskovic
On Wed, Feb 19, 2003 at 04:40:58PM +0100, Mario Pranjic wrote:
Is there a possibility that a memory chip is dead (or should I say
deadish)?
As I said, the memory died. :)
The Memtest86 returned a lot of errors. I've replaced the memory module
and now it seems all right.
It's so nice when
(adding the general list back in!)
:
:On Thu, 5 Sep 2002, Matthew Dillon wrote:
:
: Whew! These are big! :-). I've got jupiter's files downloaded, now
: it's working on venus.
:
:Ya, both are 4gig servers :) That was why netdump was so critical, cause
:they are also both
I think i have the same problem that described in other mails like
4.5-STABLE softupdates brokeness: repeated panics and lockups
and others on this mailing list.
It has come just after a software and hardware upgrade of my server
to 4.5-STABLE. I've tried diferent things to
94 matches
Mail list logo
