Yes, reverting this commit makes my T1000 boot.
Does the patch attached to the last mail work as well?
Sorry for misreading your mail - tested now and yes, it works.
--
Meelis Roos
___
iommu mailing list
iommu@lists.linux-foundation.org
https
you try to revert the commit to check if
my theory was correct to start with?
Yes, reverting this commit makes my T1000 boot.
--
Meelis Roos
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo
e7 b %xcc, 448634
44869c: c6 76 60 10 stx %g3, [ %i1 + 0x10 ]
4486a0: 11 00 26 b3 sethi %hi(0x9acc00), %o0
4486a4: 13 00 22 e3 sethi %hi(0x8b8c00), %o1
.
--
Meelis Roos
___
iommu mailing list
iommu@lists.linu
17.611695] b9651003
[ 17.611728] 80a6a000
[ 17.611762]
[ 17.625496] 8330700d
[ 17.625529] 04400126
[ 17.625562] c277a79f
[ 17.649127] c25fa7df
[ 17.649161] 84103fff
[ 17.649193]
[ 17.664729] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x
17.611728] 80a6a000
[ 17.611762]
[ 17.625496] 8330700d
[ 17.625529] 04400126
[ 17.625562] c277a79f
[ 17.649127] c25fa7df
[ 17.649161] 84103fff
[ 17.649193]
[ 17.664729] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00
I tried latest Linux on HP A180C (32-bit pa-risc). It works but the Zalon SCSI
driver barfs warnings for GSC addon differential scsi board.
The warnings seem to be DMA API related. Packaged 4.19 and self-compiled
5.0.0-rc7 exhibit the same problem.
[0.00] Linux version
main of
type 4; falling back to IOMMU_DOMAIN_DMA
[0.324800] iommu: Adding device :02:00.0 to group 16
[0.324807] pci :09:00.0: failed to allocate default IOMMU domain of
type 4; falling back to IOMMU_DOMAIN_DMA
[0.324810] iommu: Adding device :09:00.0 to group 17
--
In 4.19-rc1, I found that to keep Intel integrated graphics working when
VT-d is on, I need to have IOMMU passthough on or GPU init would fail
with DMAR error and the screen would display static gibberish. So I
turned IOMMU PT on by default in kernel config. It worked, also in rc2.
Now with
in dmesg.
--
Meelis Roos (mr...@linux.ee)
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
s no
member named ‘dma_mask’
op->dma_mask = DMA_BIT_MASK(32);
^
cc1: all warnings being treated as errors
scripts/Makefile.build:307: recipe for target
'arch/sparc/kernel/of_device_64.o' failed
--
Meelis Roos (mr...@linux.ee)
___
iommu mai
> On Sun, Aug 26, 2018 at 10:48:44AM +0300, Meelis Roos wrote:
> > Tried yesterdays git 4.18.0-12789-gaa5b105 on a Sun Ultra 1 with SBus
> > and several SBus connected devicess give DMA mapping related warnings:
>
> This should have been around since the warning was added.
m read (512 bytes read)
[ 59.720440] eth0: Link is up using
[ 59.720459] internal
[ 59.760188] transceiver at
[ 59.787280] 100Mb/s, Full Duplex.
[ 64.259942] random: crng init done
--
Meelis Roos (mr...@linux.ee)
___
iommu mailing list
hdata.dma_mask;
> dev->ofdev.dev.parent = parent;
> dev->ofdev.dev.bus = _bus_type;
> dev->ofdev.dev.release = macio_release_dev;
Yes, it does - thank you!
Tested-by: Meelis Roos <mr...@linux.ee>
--
Meelis Roos (mr...@linux.ee)
___
412829] Instruction dump:
[1.418409] 939d 4bff6329 80010024 7fe3fb78 8361000c 83810010 7c0803a6
83a10014
[1.424201] 83c10018 83e1001c 38210020 4e800020 <0fe0> 4b84 7fa3eb78
3be0
[1.430020] ---[ end trace 89c0f4a91a110769 ]---
--
Meelis Roos (mr
ing 0 use gpu addr 0xc800 and
cpu addr 0x8800ce36a000
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
[drm] radeon: irq initialized.
[drm] Loading R100 Microcode
[drm] radeon: ring at 0x0000C8001000
--
Meelis Ro
ete
>
> I agree. I'd do the BIOS update and also make sure the iLO FW is current.
OK, updates to the latest BIOS, CPU microcode revison is now 0x1b
instead of 0x19. ILO2 fw is already the latest.
The NMI-s still happen.
Disabled hpwdt. Now most boots are
ar-fault2.png when playing with
BIOS settings (disabling NUMA). It is the first time I see at least some
info in NMI decode.
--
Meelis Roos (mr...@linux.ee)
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
s.
Will try but I do not know a working base yet - this was broken in both
4.6 and 4.7-rc.
--
Meelis Roos (mr...@linux.ee)
___
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
> > > > On HP Proliant DL360 G6, Debian unstable 4.6 kernel runs fine but
> > > > selfcompiled 4.7-rc6 and 4.7-rc7 sometimes crash with NMI from
> > > > intel_idle. Sometimes it boots fine. With intel_idle disabled, it has
> > > > booted successful so far in 2 tries, one with rc6 and one with
I have a computer where I had noticed that I must not turn on IOMMU in
the BIOS, or Linux would crash on boot. The computer is Sun Ultra 20
workstation with dual-core 1st gen Opteron (175) and Nvidia CK804
chipset and 4G RAM. So IOMMU never worked for me before.
I investigated it more today -
20 matches
Mail list logo
