linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Erhard Furtner <erhard_f@mailbox.org>
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: Tue, 17 Oct 2023 14:40:49 +1100	[thread overview]
Message-ID: <875y35zzjy.fsf@mail.lhotse> (raw)
In-Reply-To: <20231012164903.0ee6c1e1@yea>

Erhard Furtner <erhard_f@mailbox.org> writes:
> On Thu, 12 Oct 2023 22:41:56 +1100
> Michael Ellerman <mpe@ellerman.id.au> wrote:
>
>> Can you checkout the exact commit that crash is from and do:
>> 
>>  $ make arch/powerpc/mm/book3s64/hash_utils.lst
>> 
>> And paste/attach the content of that file.
>> 
>> cheers
>
> Ok, attached the output from:
>
> git checkout 9fee28baa601f4dbf869b1373183b312d2d5ef3d
> make vmlinux -j16
> make arch/powerpc/mm/book3s64/hash_utils.lst
>
> Commit 9fee28baa601f4dbf869b1373183b312d2d5ef3d is the 1st bad commit of my bisect.

Thanks.

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 :/

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

  reply	other threads:[~2023-10-17  3:41 UTC|newest]

Thread overview: 19+ 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-10-06  1:11 ` Bagas Sanjaya
2023-10-06  1:19   ` Matthew Wilcox
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 [this message]
2023-10-17 23:01       ` Erhard Furtner
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=875y35zzjy.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=erhard_f@mailbox.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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 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).