From: <kkabe@vega.pgw.jp>
To: rostedt@goodmis.org
Cc: kkabe@vega.pgw.jp, regressions@lists.linux.dev,
bagasdotme@gmail.com, alexander.deucher@amd.com,
christian.koenig@amd.com, Xinhui.Pan@amd.com, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, linux-kernel@vger.kernel.org,
amd-gfx@lists.freedesktop.org
Subject: Re: radeon.ko/i586: BUG: kernel NULL pointer dereference,address:00000004
Date: Sat, 15 Jul 2023 11:39:11 +0900 [thread overview]
Message-ID: <230715113911.M0124687@vega.pgw.jp> (raw)
In-Reply-To: Your message of "Fri, 14 Jul 2023 10:00:19 -0400". <20230714100019.6bf9b1ab@gandalf.local.home>
rostedt@goodmis.org sed in <20230714100019.6bf9b1ab@gandalf.local.home>
>> On Fri, 14 Jul 2023 14:34:04 +0900
>> <kkabe@vega.pgw.jp> wrote:
>>
>> > >> > So I'm confused about why it's mentioned. Was it backported?
>> > >>
>> > >> Taketo Kabe, could you please help to clean this confusion up? Did you
>> > >> mean 5.19 in https://bugzilla.kernel.org/show_bug.cgi?id=217669#c5 ? And
>> > >> BTW: did you really use a vanilla kernel for your bisection?
>> >
>> >
>> > Reporter Me:
>> > I bisected using freedesktop.org kernel tree, which git commit ID is
>> > in sync with kernel.org
>> > but version number in ./Makefile could be slighty behind.
>> >
>> > Patch in
>> > https://bugzilla.kernel.org/show_bug.cgi?id=217669#c4
>> > fixed the problem in freedesktop.org kernel 5.18.0-rc2 .
>> > This may explain that in kernel.org tree, the said commit is in kernel-5.19.
>>
>> Even if the bisect did land on this commit, it doesn't make sense. I would
>> think that one of the results of the bisect was incorrect (a pass that
>> should have failed?), as that would lead the bisect down to the wrong
>> conclusion.
>>
>> Now if you you remove this commit and everything works fine, and add it
>> back again and it fails reliably, then I can't argue it is not the commit.
I agree with that it does not make sense.
But reverting that commit made the freedesktop.org kernel-5.18-0-rc2 not panic,
and adding it back made kernel panic
(actually, check for vblank->worker==NULL fires)
>>
>> But the commit in question kicks off a worker thread at boot up to search
>> for weak functions that were tagged to be traced by the function tracer and
>> sets them to "disabled" to never be traced.
>>
>> Is the function tracer used at all here? I really do not see how this
>> commit affects the code that is crashing. Unless there's something wrong
>> with the way the kworker was set up and it corrupted other kworkers :-/
>> -- Steve
Yes, this is puzzling. That's why I need other people's opinion on this.
Does it matter the DUT is a slow machine (Pentium 120MHz)?
--
kabe
next prev parent reply other threads:[~2023-07-15 2:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 2:50 Fwd: radeon.ko/i586: BUG: kernel NULL pointer dereference, address: 00000004 Bagas Sanjaya
2023-07-14 3:12 ` Steven Rostedt
2023-07-14 3:44 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-14 5:32 ` radeon.ko/i586: BUG: kernel NULL pointer dereference, address:00000004 kkabe
2023-07-14 5:34 ` kkabe
2023-07-14 14:00 ` Steven Rostedt
2023-07-15 2:39 ` kkabe [this message]
2023-07-17 15:21 ` radeon.ko/i586: BUG: kernel NULL pointer dereference,address:00000004 Steven Rostedt
2023-07-22 1:57 ` radeon.ko/i586: BUG: kernel NULL pointerdereference,address:00000004 kkabe
2023-07-17 15:36 ` radeon.ko/i586: BUG: kernel NULL pointer dereference, address:00000004 Steven Rostedt
2023-07-20 23:39 ` radeon.ko/i586: BUG: kernel NULL pointer dereference,address:00000004 kkabe
2023-07-22 2:30 ` kabe
2023-07-23 11:55 ` kkabe
2023-07-23 14:32 ` Steven Rostedt
2023-08-29 12:08 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-23 14:27 ` Steven Rostedt
2023-10-02 10:03 ` Fwd: radeon.ko/i586: BUG: kernel NULL pointer dereference, address: 00000004 Linux regression tracking #update (Thorsten Leemhuis)
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=230715113911.M0124687@vega.pgw.jp \
--to=kkabe@vega.pgw.jp \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=christian.koenig@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®