linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 216407] New: OF: unittest fails some tests on ppc and ppc64 (### dt-test ### end of unittest - 266 passed, 6 failed)
Date: Wed, 24 Aug 2022 17:56:18 +0000	[thread overview]
Message-ID: <bug-216407-206035@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=216407

            Bug ID: 216407
           Summary: OF: unittest fails some tests on ppc and ppc64 (###
                    dt-test ### end of unittest - 266 passed, 6 failed)
           Product: Platform Specific/Hardware
           Version: 2.5
    Kernel Version: 6.0-rc2
          Hardware: PPC-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: PPC-64
          Assignee: platform_ppc-64@kernel-bugs.osdl.org
          Reporter: erhard_f@mailbox.org
                CC: frank.rowand@am.sony.com
        Regression: No

Created attachment 301645
  --> https://bugzilla.kernel.org/attachment.cgi?id=301645&action=edit
dmesg (kernel 6.0-rc2, Talos II

[...]
### dt-test ### end of unittest - 266 passed, 6 failed

Failing tests on my Talos II are:
### dt-test ### FAIL of_unittest_dma_ranges_one():927 of_dma_get_range: wrong
phys addr 0x0000000000000000 (expecting 20000000) on node
/testcase-data/address-tests/device@70000000
### dt-test ### FAIL of_unittest_dma_ranges_one():930 of_dma_get_range: wrong
DMA addr 0x0000000020000000 (expecting 0) on node
/testcase-data/address-tests/device@70000000
### dt-test ### FAIL of_unittest_dma_ranges_one():927 of_dma_get_range: wrong
phys addr 0x0000000100000000 (expecting 20000000) on node
/testcase-data/address-tests/bus@80000000/device@1000
### dt-test ### FAIL of_unittest_dma_ranges_one():930 of_dma_get_range: wrong
DMA addr 0x0000000020000000 (expecting 100000000) on node
/testcase-data/address-tests/bus@80000000/device@1000
### dt-test ### FAIL of_unittest_dma_ranges_one():927 of_dma_get_range: wrong
phys addr 0x0000000080000000 (expecting 20000000) on node
/testcase-data/address-tests/pci@90000000
### dt-test ### FAIL of_unittest_dma_ranges_one():930 of_dma_get_range: wrong
DMA addr 0x0000000020000000 (expecting 80000000) on node
/testcase-data/address-tests/pci@90000000

Failing tests on my PowerMac G4 MDD are:
### dt-test ### FAIL of_unittest_dma_ranges_one():927 of_dma_get_range: wrong
phys addr 0x00000000 (expecting 20000000) on node
/testcase-data/address-tests/device@70000000
### dt-test ### FAIL of_unittest_dma_ranges_one():930 of_dma_get_range: wrong
DMA addr 0x20000000 (expecting 0) on node
/testcase-data/address-tests/device@70000000
### dt-test ### FAIL of_unittest_dma_ranges_one():927 of_dma_get_range: wrong
phys addr 0x80000000 (expecting 20000000) on node
/testcase-data/address-tests/pci@90000000
### dt-test ### FAIL of_unittest_dma_ranges_one():930 of_dma_get_range: wrong
DMA addr 0x20000000 (expecting 80000000) on node
/testcase-data/address-tests/pci@90000000

Devices on my Talos II:
 # lspci 
0000:00:00.0 PCI bridge: IBM POWER9 Host Bridge (PHB4)
0000:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Turks XT [Radeon HD 6670/7670]
0000:01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Turks HDMI
Audio [Radeon HD 6500/6600 / 6700M Series]
0001:00:00.0 PCI bridge: IBM POWER9 Host Bridge (PHB4)
0001:01:00.0 Non-Volatile memory controller: Phison Electronics Corporation
Device 5008 (rev 01)
0002:00:00.0 PCI bridge: IBM POWER9 Host Bridge (PHB4)
0003:00:00.0 PCI bridge: IBM POWER9 Host Bridge (PHB4)
0003:01:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI
Host Controller (rev 02)
0004:00:00.0 PCI bridge: IBM POWER9 Host Bridge (PHB4)
0004:01:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme
BCM5719 Gigabit Ethernet PCIe (rev 01)
0004:01:00.1 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme
BCM5719 Gigabit Ethernet PCIe (rev 01)
0005:00:00.0 PCI bridge: IBM POWER9 Host Bridge (PHB4)
0005:01:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev
04)
0005:02:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics
Family (rev 41)
0030:00:00.0 PCI bridge: IBM POWER9 Host Bridge (PHB4)
0031:00:00.0 PCI bridge: IBM POWER9 Host Bridge (PHB4)
0032:00:00.0 PCI bridge: IBM POWER9 Host Bridge (PHB4)
0033:00:00.0 PCI bridge: IBM POWER9 Host Bridge (PHB4)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2022-08-24 17:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 17:56 bugzilla-daemon [this message]
2022-08-24 17:58 ` [Bug 216407] OF: unittest fails some tests on ppc and ppc64 (### dt-test ### end of unittest - 266 passed, 6 failed) bugzilla-daemon
2022-08-24 18:00 ` bugzilla-daemon
2022-08-24 18:01 ` bugzilla-daemon
2022-11-03 23:44 ` bugzilla-daemon
2022-11-03 23:45 ` bugzilla-daemon
2022-11-20 20:00 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-216407-206035@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).