hi,
We figured it out today - gcc + no-arch-specific builtin bug. :-)
cognet and I are sorting through that stuff at the moment and should
land a fix in -HEAD soon.
Thanks!
-adrian
On 28 March 2018 at 02:20, Andrey V. Elsukov wrote:
> On 23.03.2018 20:07, Adrian Chadd wrote:
>> Hi!
>>
>>
On 23.03.2018 20:07, Adrian Chadd wrote:
> Hi!
>
> Just to keep things up to date; I had a chat with people on IRC.
>
> * I got the regression suite in github compiling and running on amd64.
> I'm going to attempt to commit some makefile hilarity to get it to
> cross-compile against the copy in s
Hi!
Just to keep things up to date; I had a chat with people on IRC.
* I got the regression suite in github compiling and running on amd64.
I'm going to attempt to commit some makefile hilarity to get it to
cross-compile against the copy in sys/contrib/ck
* I'll go get more info when I next power
Hi Adrian,
On Fri, Mar 23, 2018 at 12:46:02AM -0700, Adrian Chadd wrote:
> Hi,
>
> The stack backtrace looks like a null pointer dereference.
>
"Stopped at 0". Does that mean the PC is at 0, or just that we tried to
load 0 ?
> The concurrencykit website mentions ARM and MIPS as future ports. I
Hi,
The stack backtrace looks like a null pointer dereference.
The concurrencykit website mentions ARM and MIPS as future ports. Is
this actually true? Is concurrencykit supposed to actually run on
ARM/MIPS? Did anyone test? Actual MIPS hardware that we run on is like
$50. It's not exactly spendy
On Thu, Mar 22, 2018 at 09:09:37AM -0700, Adrian Chadd wrote:
> oh and xcompiled with gcc-6.x .
>
>
I'm not very knowledgable with mips. Is it possible gcc wrongly
generated an instruction that is not supported by mips74k ?
I suppose not, or it wouldn't lead to a TLB miss.
Olivier
>
> On 22 M
I dunno yet; this is a very embedded mips74k box. :)
-a
On 22 March 2018 at 06:00, Olivier Houchard wrote:
> On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V. Elsukov wrote:
>> On 22.03.2018 10:31, Adrian Chadd wrote:
>> > Erk. I'll go see if I can figure out what's going on.
>> >
>> > Thanks
oh and xcompiled with gcc-6.x .
-a
On 22 March 2018 at 09:09, Adrian Chadd wrote:
> I dunno yet; this is a very embedded mips74k box. :)
>
>
> -a
>
> On 22 March 2018 at 06:00, Olivier Houchard wrote:
>> On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V. Elsukov wrote:
>>> On 22.03.2018 10:31
On Thu, Mar 22, 2018 at 03:52:39PM +0300, Andrey V. Elsukov wrote:
> On 22.03.2018 10:31, Adrian Chadd wrote:
> > Erk. I'll go see if I can figure out what's going on.
> >
> > Thanks! This is really quite grr-y.
> >>> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode)
> >>> [ thread pi
On 22.03.2018 10:31, Adrian Chadd wrote:
> Erk. I'll go see if I can figure out what's going on.
>
> Thanks! This is really quite grr-y.
>>> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode)
>>> [ thread pid 11 tid 100010 ]
>>> Stopped at 0
>>> db> bt
>>> Tracing pid 11 tid 10001
Erk. I'll go see if I can figure out what's going on.
Thanks! This is really quite grr-y.
-a
On 21 March 2018 at 23:35, Andrey V. Elsukov wrote:
> On 22.03.2018 09:23, Adrian Chadd wrote:
>> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode)
>> [ thread pid 11 tid 100010 ]
>>
On 22.03.2018 09:23, Adrian Chadd wrote:
> Trap cause = 2 (TLB miss (load or instr. fetch) - kernel mode)
> [ thread pid 11 tid 100010 ]
> Stopped at 0
> db> bt
> Tracing pid 11 tid 100010 td 0x80673b40
> dyn_expire_states+0x13c (?,?,?,?) ra c1d08f44 sp c1247c40 sz 144
> dyn_tick+0x238 (0,?,?,
12 matches
Mail list logo
