From: Erhard Furtner <erhard_f@mailbox.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, willy@infradead.org
Subject: Re: [Bisected] PowerMac G5 fails booting kernel 6.6-rc3 (BUG: Unable to handle kernel data access at 0xfeffbb62ffec65fe)
Date: Wed, 18 Oct 2023 01:01:08 +0200 [thread overview]
Message-ID: <20231018010108.22dc1211@yea> (raw)
In-Reply-To: <875y35zzjy.fsf@mail.lhotse>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
On Tue, 17 Oct 2023 14:40:49 +1100
Michael Ellerman <mpe@ellerman.id.au> wrote:
> I think I've reproduced the crash on my Quad G5 by using your config
> with some things tweaked, but I don't get any output on the screen :/
You could try PPC_EARLY_DEBUG=y with PPC_EARLY_DEBUG_BOOTX or PPC_EARLY_DEBUG_G5. It helped me on the G4 to get some output for the KASAN bug Christophe had a look at.
> Do you mind booting the commit above and taking a photo of the oops and
> attach it here. The oops you transcribed didn't entirely make sense,
> probably due to a typo here or there, so a photo would be best.
>
> cheers
No problem. Just thought transcribing the photo would make more sense for a mailing list. ;) But maybe some subtle errors slept crept in. Attached are 2 photos from the issue on current v6.6-rc6.
Regards,
Erhard
[-- Attachment #2: screenshot01.webp --]
[-- Type: image/webp, Size: 1097138 bytes --]
[-- Attachment #3: screenshot02.webp --]
[-- Type: image/webp, Size: 814274 bytes --]
next prev parent reply other threads:[~2023-10-17 23:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 11:27 [Bisected] PowerMac G5 fails booting kernel 6.6-rc3 (BUG: Unable to handle kernel data access at 0xfeffbb62ffec65fe) Erhard Furtner
2023-09-29 12:34 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-29 12:34 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-06 1:11 ` Bagas Sanjaya
2023-10-06 1:11 ` Bagas Sanjaya
2023-10-06 1:19 ` Matthew Wilcox
2023-10-06 1:19 ` Matthew Wilcox
2023-10-06 6:57 ` Bagas Sanjaya
2023-10-06 6:57 ` Bagas Sanjaya
2023-10-06 5:34 ` Aneesh Kumar K.V
2023-10-06 10:45 ` Erhard Furtner
2023-10-06 12:08 ` Aneesh Kumar K.V
2023-10-06 14:12 ` Erhard Furtner
2023-10-11 23:47 ` Michael Ellerman
2023-10-12 14:20 ` Erhard Furtner
2023-10-12 11:41 ` Michael Ellerman
2023-10-12 14:49 ` Erhard Furtner
2023-10-17 3:40 ` Michael Ellerman
2023-10-17 23:01 ` Erhard Furtner [this message]
2023-10-18 5:45 ` Michael Ellerman
2023-10-18 10:34 ` Erhard Furtner
2025-04-08 5:55 ` Christophe Leroy
2025-04-11 9:24 ` Erhard Furtner
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=20231018010108.22dc1211@yea \
--to=erhard_f@mailbox.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.