matthias
=>> Building x11/kde-workspace-kde4
build started at Fri Sep 21 05:23:49 CEST 2018
port directory: /usr/ports/x11/kde-workspace-kde4
package name: kde-workspace-kde4-4.11.22_26
building for: FreeBSD freebsd-r338641-ports-20180920-job-03 12.0-ALPHA5 FreeBSD
12.0-ALPHA5 1
The sources listed here are from head -r338675 .
/usr/src/sys/dev/fxp/if_fxpreg.h:297 is in:
struct fxp_cb_tx {
uint16_t cb_status;
uint16_t cb_command;
uint32_t link_addr;
uint32_t tbd_array_addr;
uint16_t byte_count;
uint8_t tx_threshold;
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
> 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
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
> 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
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
> 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 0x80b96297 rsp 0xfe00be241bb0 rbp
I removed SCTP from kernel and updated from r338797 to r338827
and the problem seems to be gone.
Michael
On 20.09.2018 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
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 0x80b9620b
On 9/17/18 4:17 AM, Andrey V. Elsukov wrote:
> On 16.09.2018 03:04, Larry Rosenman wrote:
>> vpanic() at vpanic+0x1a3/frame 0xfe00ca17c150
>> panic() at panic+0x43/frame 0xfe00ca17c1b0
>> trap_fatal() at trap_fatal+0x35f/frame 0xfe00ca17c200
>> trap_pfault() at trap_pfault+0x49/frame
On Thu, Sep 20, 2018 at 12:24 AM, Rebecca Cran
wrote:
On 9/19/18 3:53 AM, Greg V wrote:
Yes, of course it was 64-bit.
I don't think I ever downloaded the 32-bit one...
And are you sure it was booted via EFI and not the BIOS emulation CSM
(Compatibility Support Module)? I'm fairly
12 matches
Mail list logo
