From: Michael Ellerman <mpe@ellerman.id.au>
To: Damien Stewart <gvdecor@yahoo.com.au>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PowerPC] [PASEMI] Issue with the identification of ATA drives after the of/irq updates 2024-05-29
Date: Tue, 09 Jul 2024 22:48:23 +1000 [thread overview]
Message-ID: <87plrm68a0.fsf@mail.lhotse> (raw)
In-Reply-To: <bfb21f1c-0e8e-40a8-a977-56d40a017f30@yahoo.com.au>
Damien Stewart <gvdecor@yahoo.com.au> writes:
> Hello.
>
>> How does it fail? I've repeatedly asked for dmesg outputs
>> for working and non-working configurations.
>
> I am the alleged tester. Attached are two dmesg logs. First one fails.
> Second passes with 2nd IRQ patch. Also attached is device tree blob if
> I've followed the correct command.
>
> The good log is direct from dmesg. But the bad log is collected live
> over serial, since it ends up in kernel panic, with no where to save
> it.
Thanks.
Which kernel is the bad log from? Just plain rc6 with no patches?
What happened when you tried the patch from me? I think Christian called
it vmlinux-6.10-17. Did you get any different output?
Does anything appear before the "hash-mmu" lines? Those are from the
kernel, we'd really like to see the output from firmware which runs
before that.
cheers
next prev parent reply other threads:[~2024-07-09 12:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 10:21 [PowerPC] [PASEMI] Issue with the identification of ATA drives after the of/irq updates 2024-05-29 Christian Zigotzky
2024-07-02 15:19 ` Marc Zyngier
2024-07-02 17:55 ` Christian Zigotzky
2024-07-02 19:49 ` Marc Zyngier
2024-07-03 3:11 ` Christian Zigotzky
2024-07-03 6:40 ` Marc Zyngier
2024-07-03 10:26 ` Christian Zigotzky
2024-07-03 10:41 ` Marc Zyngier
2024-07-03 16:23 ` Christian Zigotzky
2024-07-02 16:54 ` Marc Zyngier
2024-07-02 20:48 ` Rob Herring
2024-07-02 21:42 ` Marc Zyngier
2024-07-03 11:30 ` Michael Ellerman
2024-07-03 12:09 ` Marc Zyngier
2024-07-03 3:27 ` Christian Zigotzky
2024-07-03 6:41 ` Marc Zyngier
2024-07-04 4:10 ` Christian Zigotzky
2024-07-04 8:28 ` Marc Zyngier
2024-07-04 18:54 ` Christian Zigotzky
2024-07-05 7:05 ` Christian Zigotzky
2024-07-05 8:05 ` Christian Zigotzky
2024-07-05 13:01 ` Marc Zyngier
2024-07-05 13:30 ` Trevor Dickinson
2024-07-09 3:46 ` Damien Stewart
2024-07-09 12:48 ` Michael Ellerman [this message]
2024-07-04 11:53 ` Michael Ellerman
2024-07-04 18:27 ` Christian Zigotzky
2024-07-04 18:59 ` Christian Zigotzky
2024-07-05 1:19 ` Michael Ellerman
2024-07-05 20:45 ` Segher Boessenkool
2024-07-06 3:51 ` Christian Zigotzky
2024-07-06 4:15 ` Christian Zigotzky
2024-07-06 15:54 ` Christian Zigotzky
2024-07-10 3:53 ` Christian Zigotzky
2024-07-10 15:05 ` Rob Herring
2024-07-10 15:53 ` Christian Zigotzky
2024-07-06 4:08 ` Christian Zigotzky
2024-07-05 6:59 ` Christian Zigotzky
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=87plrm68a0.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=gvdecor@yahoo.com.au \
--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).