From: Meelis Roos <mroos@linux.ee>
To: Anatoly Pugachev <matorola@gmail.com>
Cc: sparclinux@vger.kernel.org, linux-pci@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 4.6-rc*: Kernel unaligned access at pci_bus_read_config_dword+0x64/0x80
Date: Mon, 13 Jun 2016 15:49:20 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1606131548260.25241@math.ut.ee> (raw)
In-Reply-To: <CADxRZqwuOnz8Cyedjiamyxz1nE80HxmoFANPmtZy-svr8wKfvg@mail.gmail.com>
> > Between 4.5.0 and 4.6.0-rc3, my Spar Enterprise T5120 has started
> > showing the following messages during bootup:
[...]
>
> got the same messages on my t5120 with kernel 4.6.1 :
[...]
> but 4.7.0-rc2+ (from git), does not have it, probably fixed.
Nope, I still get them on 4.7-rc3:
[ 4742.646120] Kernel unaligned access at TPC[6a5724] pci_bus_read_config_dword+0x64/0x80
[ 4742.646197] Kernel unaligned access at TPC[6a5724] pci_bus_read_config_dword+0x64/0x80
[ 4742.646265] Kernel unaligned access at TPC[6a5724] pci_bus_read_config_dword+0x64/0x80
[ 4742.646333] Kernel unaligned access at TPC[6a5724] pci_bus_read_config_dword+0x64/0x80
[ 4742.646401] Kernel unaligned access at TPC[6a5724] pci_bus_read_config_dword+0x64/0x80
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2016-06-13 12:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 19:11 4.6-rc*: Kernel unaligned access at pci_bus_read_config_dword+0x64/0x80 Meelis Roos
2016-06-09 17:33 ` Anatoly Pugachev
2016-06-13 12:49 ` Meelis Roos [this message]
2016-06-14 13:02 ` Anatoly Pugachev
2016-06-14 22:38 ` Anatoly Pugachev
2016-06-16 10:02 ` Anatoly Pugachev
2016-06-19 4:04 ` David Miller
2016-06-19 6:49 ` David Miller
2016-06-19 11:42 ` mroos
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=alpine.LRH.2.20.1606131548260.25241@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matorola@gmail.com \
--cc=sparclinux@vger.kernel.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).