: 20/09/2018 07:41
To: Michael Schmiedgen
Cc: freebsd-current@FreeBSD.org
Subject: Re: 12.0-ALPHA6 dumps with 'Fatal double fault'
> On 20. Sep 2018, at 14:18, Michael Schmiedgen wrote:
>
> Hi List,
>
> if compiling ports and configure script checks for SCTP with
>
Port is devel/apr1 and platform is amd64.
Works fine on my side. It would be helpful if you could build a kernel with
debug symbols, reproduce the problem and provide a stack strace.
Unfortunately I cannot. It is a production machine without debug that does not
like to run on 11.1 OR 11.2 fo
> On 20. Sep 2018, at 19:11, Michael Schmiedgen wrote:
>
> Hi Michael,
>
> many thanks for your help.
>
>
> On 20.09.2018 18:15, Michael Tuexen wrote:
>>> On 20. Sep 2018, at 17:12, Michael Schmiedgen wrote:
>>>
>>>
Can you elaborate which port was triggering the fault and which platfo
Hi Michael,
many thanks for your help.
On 20.09.2018 18:15, Michael Tuexen wrote:
On 20. Sep 2018, at 17:12, Michael Schmiedgen wrote:
Can you elaborate which port was triggering the fault and which platform you
are using?
I would like to reproduce the issue and fix it.
Port is devel/ap
> On 20. Sep 2018, at 17:12, Michael Schmiedgen wrote:
>
>
>> Can you elaborate which port was triggering the fault and which platform you
>> are using?
>> I would like to reproduce the issue and fix it.
>
> Port is devel/apr1 and platform is amd64.
Works fine on my side. It would be helpful i
Can you elaborate which port was triggering the fault and which platform you
are using?
I would like to reproduce the issue and fix it.
Port is devel/apr1 and platform is amd64.
CPU: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (3300.10-MHz K8-class CPU)
Origin="GenuineIntel" Id=0x206a7 Family
> On 20. Sep 2018, at 14:18, Michael Schmiedgen wrote:
>
> Hi List,
>
> if compiling ports and configure script checks for SCTP with
>
> 'checking whether SCTP is supported...'
>
> 12.0-ALPHA6 dumps core with message:
>
> Fatal double fault
> rip
core with message:
Fatal double fault
rip 0x80b96297 rsp 0xfe00be241bb0 rbp 0xfe00be245490
rax 0x1 rdx 0x3 rbx 0x7fffd198
rcx 0x80b9620b rsi 0xf8029eeb0368 rdi 0x4
r8 0xf801c925c580 r9 0xfe00be2456d4 r10 0x4
r11 0xfe00be245b80 r12 0x7fffd190 r13 0
r
Hi List,
if compiling ports and configure script checks for SCTP with
'checking whether SCTP is supported...'
12.0-ALPHA6 dumps core with message:
Fatal double fault
rip 0x80b96297 rsp 0xfe00be241bb0 rbp 0xfe00be245490
rax 0x1 rdx 0x3 rbx 0x7fffd198
rcx 0xff
"Steven Hartland" wrote:
> Thanks for your help testing this Fabian, I've now committed the fix for
> this for this:
> http://svnweb.freebsd.org/changeset/base/265321
Thanks a lot, Steve.
Fabian
signature.asc
Description: PGP signature
- Original Message -
From: "Fabian Keil"
Thanks for your help testing this Fabian, I've now committed the fix for
this for this:
http://svnweb.freebsd.org/changeset/base/265321
Regards
Steve
___
freebsd-current@freebsd.org mailing lis
"Steven Hartland" wrote:
> > "Steven Hartland" wrote:
> >
> > > From: "Fabian Keil"
> > >
> > > > After updating my laptop to yesterday's CURRENT (r265216),
> > > > I got the following fatal d
"Steven Hartland" wrote:
> From: "Fabian Keil"
>
> > After updating my laptop to yesterday's CURRENT (r265216),
> > I got the following fatal double fault on boot:
> > http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r265216/
> >
&g
"Steven Hartland" wrote:
> From: "Fabian Keil"
>
> > After updating my laptop to yesterday's CURRENT (r265216),
> > I got the following fatal double fault on boot:
> > http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r265216/
> >
&
- Original Message -
From: "Fabian Keil"
After updating my laptop to yesterday's CURRENT (r265216),
I got the following fatal double fault on boot:
http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r265216/
My previous kernel was based on r264721.
I'm usin
After updating my laptop to yesterday's CURRENT (r265216),
I got the following fatal double fault on boot:
http://www.fabiankeil.de/bilder/freebsd/kernel-panic-r265216/
My previous kernel was based on r264721.
I'm using a couple of custom patches, some of them are ZFS-related
and t
(Re-sending, my original post was accepted by mx1.freebsd.org, but seems to
have been lost somewhere.)
Thus spake Damian Gerow ([EMAIL PROTECTED]) [29/11/03 17:04]:
> But this is a little OT. I'll find some way to update my system, and
> respond back if the problem's fixed or not in a later -CURR
Thus spake Kris Kennaway ([EMAIL PROTECTED]) [29/11/03 17:18]:
> Can't you boot from the install floppy and then do a network install?
Don't have any floppies handy right now. I /could/ go out and get some...
But this is a little OT. I'll find some way to update my system, and
respond back if th
On Sat, Nov 29, 2003 at 04:43:44PM -0500, Damian Gerow wrote:
> Thus spake Kris Kennaway ([EMAIL PROTECTED]) [29/11/03 16:23]:
> > > over and over and over -- it makes the console essentially unusable.
> >
> > I think you're running into problems that have been fixed in
> > subsequent weeks. Is t
Thus spake Kris Kennaway ([EMAIL PROTECTED]) [29/11/03 16:23]:
> > over and over and over -- it makes the console essentially unusable.
>
> I think you're running into problems that have been fixed in
> subsequent weeks. Is there a reason you can't install the 5.2-BETA
> image?
Well, that's good
On Sat, Nov 29, 2003 at 04:07:44PM -0500, Damian Gerow wrote:
> A couple days ago, I downloaded 20031116-JPSNAP to install on a new system
> -- this box had been running 5.1-R without issues for some time, but wasn't
> doing anything particular, and I had mucked up the 5.1 -> 5.2 upgrade
> (statfs
nking an update might fix it, I booted into single user mode, cvsup'ed,
and started building. However, six buildworlds later, it appears that I'm
constantly getting a fatal double fault, but in differing places. This
looks like the turnstile double-panic outlined in 5.2R-TODO -- I ho
from ddb, type 'ps'
On Sun, 7 Jul 2002, Dirk Engling wrote:
>
> Fatal double fault:
> eip = 0xc01f75ba
> esp = 0xcdcecff8
> ebp = 0xcdced03c
> panic: double fault
> Debugger("panic")
> Stopped atDebugger+0x45:xchgl %ebx,in_Debugger.0
&
Fatal double fault:
eip = 0xc01f75ba
esp = 0xcdcecff8
ebp = 0xcdced03c
panic: double fault
Debugger("panic")
Stopped atDebugger+0x45:xchgl %ebx,in_Debugger.0
db> trace
Debugger(c02324bfc) at Debugger+0x45
panic(c034cf19,c034d445,cdced03c,0,0) at panic+0x74
dblfault_han
Hackers,
for the last couple of days i was able to crash my -current
laptop with "Fatal double fault" panic whenever i wanted.
i have created a small "spherical cow" :) to demonstrate
the problem (see attached). this is pretty much what my code
does. just compile and loa
Hello all,
I was in X today and the computer spontaneously restarted so I didn't see and
panic. After a restart fsck started in the background (I'm using soft updates
on all of my filesystems). While trying to determing what caused the crash by
looking in the system logs the computer crashed ag
I have searched the mailing lists, to no avail (hope I
did not miss the answer).
I am getting the following output on make world (FreeBSD
5.0-2820-CURRENT installed, cvsup current source at
11:00AM Eastern Time)..
Fatal double fault:
eip = 0xc030343c
esp = 0xcd025000
ebp = 0xcd025074
panic
So a double-fault is always a kernel stack problem?
I find it suspicious that this same machine
also had trouble with the 3c905B flaking out --
dropping packets during an ifconfig alias, and
sometimes never reactivating the interface
according to what tcpdump shows.
The 3c905B problem repeates it
On Mon, 8 Feb 1999, Mike Smith wrote:
> > The machine is running a custom kernel, but nothing
> > very unusual. My instinct is that it may be related to
> > something with the 3c905B 3COM cards that I reported
> > earlier, I'm trying with Intel EtherExpresses right now
> > and getting no fault p
> The machine is running a custom kernel, but nothing
> very unusual. My instinct is that it may be related to
> something with the 3c905B 3COM cards that I reported
> earlier, I'm trying with Intel EtherExpresses right now
> and getting no fault problems.
>
> The double-fault does not occur con
h [mailto:m...@smith.net.au]
> Sent: Monday, February 08, 1999 6:55 PM
> To: tc...@staff.circle.net
> Cc: curr...@freebsd.org
> Subject: Re: Tracking a Fatal Double Fault
>
>
> > Can someone please give me a short guide
> > on how to track down a fatal double fault?
> Can someone please give me a short guide
> on how to track down a fatal double fault?
> System is 3.0-19990205-STABLE, and I've written
> down the fault info.
Ack. It's actually pretty difficult. You can start by trying to
locate the PC for the fault in the kernel
Can someone please give me a short guide
on how to track down a fatal double fault?
System is 3.0-19990205-STABLE, and I've written
down the fault info.
Thanks,
-Troy Cobb
Circle Net, Inc.
http://www.circle.net
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscri
33 matches
Mail list logo
