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
kern.cor
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 approva
> 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 site
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 in
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 "freebsd-stable
Bezüglich Harry Schmalzbauer's Nachricht vom 01.08.2016 08:41 (localtime):
> Hello,
>
> unfortunately my upgrade from 10.3 to 11-BETA3 caused machine outage.
> ESP encrypted IPv6-traffic acauses a immediate crash.
Andrey V. Elsukov rapidly analysed and corrected that in HEAD with r303657.
This s
0x80ca6c2f at crypto_dispatch+0x7f
#14 0x80c9605a at esp_input+0x4fa
#15 0x80c8179b at ipsec_common_input+0x40b
#16 0x80c8222d at ipsec6_common_input+0xcd
#17 0x80c64070 at ip6_input+0xc70
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
On 23.09.2012 23:41, Andriy Gapon wrote:
on 23/09/2012 23:10 Barbara said the following:
After updating src on RELENG_9 from r240236 to r240821 I have rebuilt
my world+kernel.
On reboot I had a kernel panic, "supervisor read, page not present"
for process swapper.
Trying to reboot in Single User
on 23/09/2012 23:10 Barbara said the following:
> After updating src on RELENG_9 from r240236 to r240821 I have rebuilt
> my world+kernel.
> On reboot I had a kernel panic, "supervisor read, page not present"
> for process swapper.
> Trying to reboot in Single User Mode I accidentally disabled ACPI
After updating src on RELENG_9 from r240236 to r240821 I have rebuilt
my world+kernel.
On reboot I had a kernel panic, "supervisor read, page not present"
for process swapper.
Trying to reboot in Single User Mode I accidentally disabled ACPI.
Luckily the machine booted succesfully but there was not
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
> > > wrote:
> > > > On Tuesday, April 26, 2011 01:09:42
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
> > wrote:
> > > On Tuesday, April 26, 2011 01:09:42 Gardner Bell wrote:
> > >> Downloading a torrent with many peers o
On Tuesday, April 26, 2011 15:15:45 Gardner Bell wrote:
> On Tue, Apr 26, 2011 at 4:12 AM, Bernhard Schmidt
> 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 cau
On Tue, Apr 26, 2011 at 4:12 AM, Bernhard Schmidt 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 running 8.2-STA
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 a
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 Ga
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
Hi!
Just tried to rebuild FreeNAS 7 from svn with FreeBSD 8.1p2 and after
iso image rebuild I tried to start it in VMware Player 3.1.3.
--
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
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 the kernel core?
We had a problem a while ago at Isilon that I can't tell if it's
related.
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
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
> 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
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
Hello,
I recently upgraded a server from RELENG_6_4 to RELENG_7_2 (both i386). Since
then, the box has started crashing regularly. The longest uptime since the
upgrade is 1d5h, the shortest is 2m35s. The backtrace is always similar:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic
From: Richard Mahlerwein
Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a
To: "FreeBSD-Stable"
Date: Tuesday, September 1, 2009, 2:58 PM
> From: Gavin Atkinson
> Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a
> To:
From: Richard Mahlerwein
Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a
To: "FreeBSD-Stable"
Date: Tuesday, September 1, 2009, 2:58 PM
> From: Gavin Atkinson
> Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a
> To:
> From: Gavin Atkinson
> Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a
> To: "Richard Mahlerwein"
> Cc: "FreeBSD-Stable"
> Date: Sunday, August 30, 2009, 3:47 PM
> On Sat, 29 Aug 2009, Richard
> Mahlerwein wrote:
>
&g
--- On Sun, 8/30/09, Gavin Atkinson wrote:
> From: Gavin Atkinson
> Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a
> To: "Richard Mahlerwein"
> Cc: "FreeBSD-Stable"
> Date: Sunday, August 30, 2009, 3:47 PM
> On Sat, 2
got a core dump, apparently
triggered by devd.
Fatal trap 12: page fault while in kernel mode.
cpu id = 0; apic id = 00
fault virtual address = 0x3030313a
fault code = supervisor write, page not present
[snip]
current process = 355 (devd)
[snip]
Does anyone have a further recommendation
Richard Mahlerwein wrote:
--- On Sat, 8/29/09, Marat N.Afanasyev wrote:
From: Marat N.Afanasyev
Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a
To: mahle...@yahoo.com
Cc: "FreeBSD-Stable"
Date: Saturday, August 29, 2009, 6:59 PM
such trap could be tr
near the
> end of the boot sequence I got a core dump, apparently
> triggered by devd.
>
>
> Fatal trap 12: page fault while in kernel mode.
> cpu id = 0; apic id = 00
> fault virtual address = 0x3030313a
> fault code = supervisor write, page not present
> [snip]
&
--- On Sat, 8/29/09, Marat N.Afanasyev wrote:
> From: Marat N.Afanasyev
> Subject: Re: Fatal Trap 12 in various processes always at address 0x3030313a
> To: mahle...@yahoo.com
> Cc: "FreeBSD-Stable"
> Date: Saturday, August 29, 2009, 6:59 PM
> Richard Mahlerwein
, apparently
triggered by devd.
Fatal trap 12: page fault while in kernel mode.
cpu id = 0; apic id = 00
fault virtual address = 0x3030313a
fault code = supervisor write, page not present
[snip]
current process = 355 (devd)
I redid the *whole* process in single user mode, yet no
difference. I
.
Fatal trap 12: page fault while in kernel mode.
cpu id = 0; apic id = 00
fault virtual address = 0x3030313a
fault code = supervisor write, page not present
[snip]
current process = 355 (devd)
I redid the *whole* process in single user mode, yet no
difference. I was out of town for 2.5
On May 10, 2009, Norbert Papke wrote:
> Inserting a USB thumb drive into a running sytem result in a "Fatal trap
> 12: page fault while in kernel mode".
After repeating the crash a few times with INVARIANTS enabled, it becomes
apparent that EHCI transfer queue is getting corru
pth. I will spend some more time trying to learn
this code but would appreciate pointers.
Cheers,
-- Norbert Papke.
On May 10, 2009, Norbert Papke wrote:
> On May 10, 2009, Norbert Papke wrote:
> > Inserting a USB thumb drive into a running sytem result in a "Fatal trap
> >
On May 10, 2009, Norbert Papke wrote:
> Inserting a USB thumb drive into a running sytem result in a "Fatal trap
> 12: page fault while in kernel mode".
>
> Unfortunately, I was not able to save a core (not entirely sure why, I'll
> investigate separately). I have
Inserting a USB thumb drive into a running sytem result in a "Fatal trap 12:
page fault while in kernel mode".
Unfortunately, I was not able to save a core (not entirely sure why, I'll
investigate separately). I have manually copied the backtrace:
usb_transfer_complete
sd.org/mailman/listinfo/freebsd-stable
> >To unsubscribe, send any 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
ble-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 = 0x30
fault code
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 alway
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" i
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 act
message buffer:
acd0: WARNING - PREVENT_ALLOW read data overrun 18>0
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
On Thu, Sep 11, 2008 at 11:56 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 11, 2008 at 12:08:47PM +0200, Michael Grant wrote:
>> On Thu, Sep 11, 2008 at 11:20 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
>> > On Thu, Sep 11, 2008 at 10:38:36AM +0200, Michael Grant wrote:
>> >> My
s different.
Having no clue, I've restored the not enabled state of powerd for the moment.
# kgdb kernel.debug /var/crash/vmcore.3
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it
> barbara wrote:
> > Hello,
> > I'm running 6.4-PRELEASE, last built on 2008-10-05 with /usr/src updated on
> > the same day.
> > I had a panic that looks to me very similiar to the one described here
> > (hence the subject):
> > http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/0
tions.
>
> 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 buffe
as configured as "i386-marcel-freebsd"...
Unread portion of the kernel message buffer:
acd0: WARNING - TEST_UNIT_READY read data overrun 18>0
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual addres
On Saturday 27 September 2008 02:37:55 pm John L. Templer wrote:
> I'm running 7.1-PRERELEASE, with /usr/src and /usr/ports last csup-ed
> just a few days ago. After being up for about a day or so the system
> will panic because of a page fault. I'm not completely sure, but it
> seems that the
e copies 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:
acd1: WARN
On Thu, Sep 11, 2008 at 12:08:47PM +0200, Michael Grant wrote:
> On Thu, Sep 11, 2008 at 11:20 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> > On Thu, Sep 11, 2008 at 10:38:36AM +0200, Michael Grant wrote:
> >> My box crashed again:
> >>
> >> panic: kmem_malloc(4096): kmem_map too small: 1073741
On Thu, Sep 11, 2008 at 11:20 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 11, 2008 at 10:38:36AM +0200, Michael Grant wrote:
>> My box crashed again:
>>
>> panic: kmem_malloc(4096): kmem_map too small: 1073741824 total allocated
>> cpuid = 0
>> Uptime: 33d11h12m58s
>> Dumping 3327
On Thu, Sep 11, 2008 at 10:38:36AM +0200, Michael Grant wrote:
> My box crashed again:
>
> panic: kmem_malloc(4096): kmem_map too small: 1073741824 total allocated
> cpuid = 0
> Uptime: 33d11h12m58s
> Dumping 3327 MB (2 chunks)
> chunk 0: 1MB (151 pages) ... ok
> chunk 1: 3327MB (851568 pages)
My box crashed again:
panic: kmem_malloc(4096): kmem_map too small: 1073741824 total allocated
cpuid = 0
Uptime: 33d11h12m58s
Dumping 3327 MB (2 chunks)
chunk 0: 1MB (151 pages) ... ok
chunk 1: 3327MB (851568 pages) <---hung here
Still no valid dump.
There is 4gig of physical memory in the
el message buffer:
ad1: TIMEOUT - READ_DMA retrying (1 retry left) LBA=67332091
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x188
fault code = supervisor read, page not present
instruction pointe
> I feel for you John, I've lost many nights sleep in the last couple
weeks trying to understand why this production box was crashing. I
was really surprised to see this start happening, normally my freebsd
boxes have uptimes in terms of years, not hours.
Thanks for the sentiment, at las
Michael Grant wrote:
I have been having what seems like similar panics. I too cannot
manage to get a crash dump, neither classic style nor minidump. Nor
can I get it to work with DDB, there seems to be a problem with DDB
and my Geom mirror.
They're not at all similar, please don't confuse the
I have been having what seems like similar panics. I too cannot
manage to get a crash dump, neither classic style nor minidump. Nor
can I get it to work with DDB, there seems to be a problem with DDB
and my Geom mirror.
Kris recommended I up kmem_size which I have done (twice now) and
since the
On Jul 24, 2008, at 9:15 AM, John Sullivan wrote:
Right, after trying for a number of days the system still just hung
without letting me get either a dump or to interactively debug
in the failed state, I reverted back to the Generic kernel, removed
half the memory (2 of the 4 1GB sticks) and t
reebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address= 0xb0
fault code= supervisor read data, page not present
instruction pointer= 0x8:0x8068d4bd
stack pointer
ured as "amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address= 0xb0
fault code= supervisor read data, page not present
instruction pointer= 0x8:0xff
> OK, the first thing to do is disable bg fsck, then force a full fsck of
all filesystems. bg fsck does a poor job of fixing arbitrary
filesystem corruption (it's not designed to do so, in fact), and you
can get into a situation where corrupted filesystems cause further
panics.
Done, not
> From: "John Sullivan" <[EMAIL PROTECTED]>
> Date: Wed, 16 Jul 2008 09:38:26 +0100
>
>
> > Could be memory, but I'd also suggest looking at
> > temperatures. I've had overheating systems produce lots of
> > such errors.
>
> Temperature is fine - it never get's that hot here in the UK ;-)
> Se
m running
6.3 patch 2.
Unless you have information you haven't yet shared, no it doesn't :)
"Fatal trap 12" is an effect, not a cause. We still need your backtrace
to make progress understanding the cause of your panic.
Kris
_
On Wed, Jul 16, 2008 at 10:38 AM, John Sullivan <[EMAIL PROTECTED]> wrote:
>
>> Could be memory, but I'd also suggest looking at
>> temperatures. I've had overheating systems produce lots of
>> such errors.
>
> Temperature is fine - it never get's that hot here in the UK ;-) Seriously,
> I put my
John Sullivan wrote:
John, a question, how is swap set up on your system? I was
swapping to a file (a memory disk device /dev/md0). I was
doing this because for some reason lost in ancient history,
this machine was not set up with a real swap partition.
Hence, no crash dump.
Swap is a p
> John, a question, how is swap set up on your system? I was
> swapping to a file (a memory disk device /dev/md0). I was
> doing this because for some reason lost in ancient history,
> this machine was not set up with a real swap partition.
> Hence, no crash dump.
Swap is a partition on t
> Could be memory, but I'd also suggest looking at
> temperatures. I've had overheating systems produce lots of
> such errors.
Temperature is fine - it never get's that hot here in the UK ;-) Seriously, I
put my hand in the box, touched a few heat sync's, it
is not running hot enough to cause
software installed.
>
> Although I have been using FreeBSD for a number of years this is the first
> time I have experienced regular panics and am at a
> complete loss trying to work out what is wrong. I would be grateful for any
> advice anyone is willing to give to help me
>
[EMAIL PROTECTED] wrote:
>> #9 0x8067d3ee in uma_zalloc_arg (zone=0xff00bfed07e0,
udata=0x0,
flags=-256) at /usr/src/sys/vm/uma_core.c:1835
From the frame #9, please do
p *zone
I am esp. interested in the value of the uz_ctor member.
It seems that it becomes corrupted, it valu
> Do the "frame 9" before "p *zone".
It's obvious now you say it ;-)
You are indeed right:
(kgdb) frame 9
#9 0x8067d3ee in uma_zalloc_arg (zone=0xff00bfed07e0, udata=0x0,
flags=-256) at /usr/src/sys/vm/uma_core.c:1835
1835 uma_dbg_alloc(zone
On Tue, Jul 15, 2008 at 08:47:03PM +0100, [EMAIL PROTECTED] wrote:
>
>
> >> #9 0x8067d3ee in uma_zalloc_arg (zone=0xff00bfed07e0,
> >>udata=0x0,
> >>flags=-256) at /usr/src/sys/vm/uma_core.c:1835
> >From the frame #9, please do
> >p *zone
> >I am esp. interested in the value of the
how warranty" for details.
> This GDB was configured as "amd64-marcel-freebsd".
>
> Unread portion of the kernel message buffer:
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address = 0x64
>
>> #9 0x8067d3ee in uma_zalloc_arg (zone=0xff00bfed07e0,
udata=0x0,
flags=-256) at /usr/src/sys/vm/uma_core.c:1835
From the frame #9, please do
p *zone
I am esp. interested in the value of the uz_ctor member.
It seems that it becomes corrupted, it value should be 0, as this see
[EMAIL PROTECTED] wrote:
(kgdb) backtrace
#0 doadump () at pcpu.h:194
#1 0xff0004742440 in ?? ()
#2 0x80477699 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:409
#3 0x80477a9d in panic (fmt=0x104 )
at /usr/src/sys/kern/kern_shutdown.c:563
#4 0x8
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 "amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault wh
John Sullivan wrote:
Can the system in question run memtest86+ successfully (no
errors) for an hour? It would help diminish (but not
entirely rule out) hardware (memory or chipset) issues.
Sorry, forgot to mention, I ran memtest over night without any problem
reported. I ran Fedora 9 for
> Can the system in question run memtest86+ successfully (no
> errors) for an hour? It would help diminish (but not
> entirely rule out) hardware (memory or chipset) issues.
Sorry, forgot to mention, I ran memtest over night without any problem
reported. I ran Fedora 9 for a month without a
On Tue, Jul 15, 2008 at 10:58:19AM +0100, John Sullivan wrote:
> I am experiencing 'random' reboots interspersed with panics whenever I put a
> newly installed system under load (make index in
> /usr/ports is enough). A sample panic is at the end of this email.
>
> I have updated to 7.0-RELEASE
be grateful for any
advice anyone is willing to give to help me
troubleshoot this issue.
Thanks in advance
John
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x80b0
fault code - supervisor write data, page not present
instructio
Jim Pingle wrote:
Jim Pingle wrote:
I'm having some trouble with a SuperMicro SuperServer 6022L-6 that
previously ran 7.0-BETA4 without problems. Today, I updated this
machine to 7.0-PRERELEASE and now it will not fully boot unless I
disable ACPI. A quick search of the PR database didn't turn
Jim Pingle wrote:
I'm having some trouble with a SuperMicro SuperServer 6022L-6 that
previously ran 7.0-BETA4 without problems. Today, I updated this machine
to 7.0-PRERELEASE and now it will not fully boot unless I disable ACPI.
A quick search of the PR database didn't turn up anything simil
/usr/obj/usr/src/sys/TEST i386
=
[EMAIL PROTECTED] /usr/obj/usr/src/sys/TEST]# kgdb kernel.debug
/var/crash/vmcore.1
Fatal trap 12: page fault while in kernel mode
cpuid = 3; apic id = 03
fault virtual address = 0
bsd".
Unread portion of the kernel message 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
nodes remaining...3 0 0 0 0 done
All buffers synced.
Uptime: 42s
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x20:0xc0440b3d
stack pointer = 0x
r' to stop...
Syncing disks, vnodes remaining...1 1 1 1 0 0 0 done
All buffers synced.
Uptime: 50m27s
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x0
fault code = supervisor write, page not present
instruction pointer = 0x20:0
On Thu, Oct 25, 2007 at 08:11:56PM +0200, Kris Kennaway wrote:
> Doug Poland wrote:
> >On Thu, Oct 25, 2007 at 01:17:38AM +0200, Kris Kennaway wrote:
> >>Doug Poland wrote:
> >>>
> >>>I just had a kernel panic using BETA1. According to the Developer
> >>>Handbook Kernel Debugging, I'm supplying th
o 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 = 1; apic id = 01
fault virtual address = 0x9006004
fault code
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 wh
you
are
welcome to change it and/or distribute copies 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 o
to change it and/or distribute copies 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 me
On Tue, Oct 02, 2007 at 02:55:08PM -0500, Natham wrote:
> Hi:
>
> Im getting a Fatal trap 12 from a freebsd 6.2 release p7, how can i
> report it and get help??
Check
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
on how to obtain needed
Hi:
Im getting a Fatal trap 12 from a freebsd 6.2 release p7, how can i
report it and get help??
Oct 2 02:39:37 freebsd kernel:
Oct 2 02:39:37 freebsd kernel:
Oct 2 02:39:37 freebsd kernel: Fatal trap 12: page fault while in kernel mode
Oct 2 02:39:37 freebsd kernel: cpuid = 0; apic id = 00
Hi list,
We have a backup server Dell Power Edge 1850, One Xeon 3.6 Ghz, 2GB Ram,
attached to one storage PowerVault 220 and one LTO tape drive, running
STABLE from start of June.
This machine basically runs FTP Server, NFS Server, compress directories
using tar and gzip and run some perl script
uot; for
> details.
> This GDB was configured as "i386-marcel-freebsd".
>
> Unread portion of the kernel message buffer:
> kernel trap 12 with interrupts disabled
>
>
> Fatal trap 12: page fault while in kernel mode
> cpuid = 2; apic id = 06
> fault virtua
rap 12 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
ue 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 panic
1 - 100 of 209 matches
Mail list logo
