Linux-RISC-V Archive on lore.kernel.org
 help / Atom feed
* sbi_trap_error: hart4: trap handler failed (error -5)
@ 2019-02-11 14:13 Andreas Schwab
  2019-02-11 20:17 ` Atish Patra
  0 siblings, 1 reply; 3+ messages in thread
From: Andreas Schwab @ 2019-02-11 14:13 UTC (permalink / raw)
  To: linux-riscv

I have been getting this error:

sbi_trap_error: hart4: trap handler failed (error -5)
sbi_trap_error: hart4: mcause=0xd mtval=0x155574e000
sbi_trap_error: hart4: mepc=0x80003dba mstatus=0x8000000a00027822
sbi_trap_error: hart4: ra=0x80001eaa sp=0x8000dd60
sbi_trap_error: hart4: gp=0x2aaaccdd18 tp=0x155573cb20
sbi_trap_error: hart4: s0=0x8000ddc0 s1=0x5e
sbi_trap_error: hart4: a0=0x20000 a1=0x8000ddf0
sbi_trap_error: hart4: a2=0x15555eee96 a3=0x8000000a00006022
sbi_trap_error: hart4: a4=0x8000dd6b a5=0x155574e001
sbi_trap_error: hart4: a6=0x0 a7=0x155574e001
sbi_trap_error: hart4: s2=0xee s3=0x3
sbi_trap_error: hart4: s4=0x96 s5=0x20
sbi_trap_error: hart4: s6=0x0 s7=0x15555eee96
sbi_trap_error: hart4: s8=0x74 s9=0x14774
sbi_trap_error: hart4: s10=0x58782b5b s11=0x34fe3e52
sbi_trap_error: hart4: t0=0x4 t1=0x155574dffd
sbi_trap_error: hart4: t2=0x55 t3=0x85a303
sbi_trap_error: hart4: t4=0x0 t5=0x0
sbi_trap_error: hart4: t6=0x15

What does that mean?

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: sbi_trap_error: hart4: trap handler failed (error -5)
  2019-02-11 14:13 sbi_trap_error: hart4: trap handler failed (error -5) Andreas Schwab
@ 2019-02-11 20:17 ` Atish Patra
  2019-02-12  8:15   ` Andreas Schwab
  0 siblings, 1 reply; 3+ messages in thread
From: Atish Patra @ 2019-02-11 20:17 UTC (permalink / raw)
  To: Andreas Schwab, linux-riscv

On 2/11/19 6:16 AM, Andreas Schwab wrote:
> I have been getting this error:
> 
> sbi_trap_error: hart4: trap handler failed (error -5)
> sbi_trap_error: hart4: mcause=0xd mtval=0x155574e000

Looks like you are getting a CAUSE_LOAD_PAGE_FAULT (0xd) on hart4.

> sbi_trap_error: hart4: mepc=0x80003dba mstatus=0x8000000a00027822
> sbi_trap_error: hart4: ra=0x80001eaa sp=0x8000dd60
> sbi_trap_error: hart4: gp=0x2aaaccdd18 tp=0x155573cb20
> sbi_trap_error: hart4: s0=0x8000ddc0 s1=0x5e
> sbi_trap_error: hart4: a0=0x20000 a1=0x8000ddf0
> sbi_trap_error: hart4: a2=0x15555eee96 a3=0x8000000a00006022
> sbi_trap_error: hart4: a4=0x8000dd6b a5=0x155574e001
> sbi_trap_error: hart4: a6=0x0 a7=0x155574e001
> sbi_trap_error: hart4: s2=0xee s3=0x3
> sbi_trap_error: hart4: s4=0x96 s5=0x20
> sbi_trap_error: hart4: s6=0x0 s7=0x15555eee96
> sbi_trap_error: hart4: s8=0x74 s9=0x14774
> sbi_trap_error: hart4: s10=0x58782b5b s11=0x34fe3e52
> sbi_trap_error: hart4: t0=0x4 t1=0x155574dffd
> sbi_trap_error: hart4: t2=0x55 t3=0x85a303
> sbi_trap_error: hart4: t4=0x0 t5=0x0
> sbi_trap_error: hart4: t6=0x15
> 
> What does that mean?
> 

It would help if you also give some more details about the platform and 
boot flow you are testing. Are you testing OpenSBI + U-Boot + Linux or 
OpenSBI + Linux (kernel image as a direct payload to OpenSBI).

Are you getting this error on QEMU or Unleashed ?

FYI: This is a OpenSBI specific issue. You can always create a github
issue for a quick response.

Regards,
Atish
> Andreas.
> 

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: sbi_trap_error: hart4: trap handler failed (error -5)
  2019-02-11 20:17 ` Atish Patra
@ 2019-02-12  8:15   ` Andreas Schwab
  0 siblings, 0 replies; 3+ messages in thread
From: Andreas Schwab @ 2019-02-12  8:15 UTC (permalink / raw)
  To: Atish Patra; +Cc: linux-riscv

On Feb 11 2019, Atish Patra <atish.patra@wdc.com> wrote:

> It would help if you also give some more details about the platform and
> boot flow you are testing. Are you testing OpenSBI + U-Boot + Linux or
> OpenSBI + Linux (kernel image as a direct payload to OpenSBI).

The latter.

> Are you getting this error on QEMU or Unleashed ?

On the unleashed.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-11 14:13 sbi_trap_error: hart4: trap handler failed (error -5) Andreas Schwab
2019-02-11 20:17 ` Atish Patra
2019-02-12  8:15   ` Andreas Schwab

Linux-RISC-V Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-riscv/0 linux-riscv/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-riscv linux-riscv/ https://lore.kernel.org/linux-riscv \
		linux-riscv@lists.infradead.org infradead-linux-riscv@archiver.kernel.org
	public-inbox-index linux-riscv


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.infradead.lists.linux-riscv


AGPL code for this site: git clone https://public-inbox.org/ public-inbox