linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	senozhatsky@chromium.org, akpm@linux-foundation.org,
	minchan@kernel.org, terrelln@fb.com, sfr@canb.auug.org.au
Subject: Re: [Bug][Git-Bisect][6.11.0-next-20240917]BUG: Unable to handle kernel data access on read at 0xc00c020000013d88
Date: Mon, 23 Sep 2024 11:15:57 +0900	[thread overview]
Message-ID: <20240923021557.GA38742@google.com> (raw)
In-Reply-To: <57130e48-dbb6-4047-a8c7-ebf5aaea93f4@linux.vnet.ibm.com>

Hi,

On (24/09/22 22:23), Venkat Rao Bagalkote wrote:
> Greetings!!!
> 
> I am observing Kernel OOPs on PowerPC system, while running LTP Test case.
> 
> [11472.962838] BUG: Unable to handle kernel data access on read at
> 0xc00c020000013d88
> [11472.962846] Faulting instruction address: 0xc00000000055e2c0
[..]
> [11472.963005] NIP [c00000000055e2c0] kfree+0x60/0x468
> [11472.963013] LR [c008000004e02838] zram_destroy_comps+0x5c/0xa4 [zram]
> [11472.963020] Call Trace:
> [11472.963023] [c0000005da817b30] [c00000051f580440] 0xc00000051f580440
> (unreliable)
> [11472.963028] [c0000005da817ba0] [c008000004e02838]
> zram_destroy_comps+0x5c/0xa4 [zram]
> [11472.963034] [c0000005da817bd0] [c008000004e02d24]
> zram_reset_device+0x178/0x250 [zram]
> [11472.963040] [c0000005da817c20] [c008000004e031e0] reset_store+0xd0/0x174
> [zram]
> [11472.963046] [c0000005da817c80] [c000000000a85874]
> dev_attr_store+0x34/0x50
> [11472.963052] [c0000005da817ca0] [c00000000070e7a4]
> sysfs_kf_write+0x64/0x78
> [11472.963060] [c0000005da817cc0] [c00000000070d2a8]
> kernfs_fop_write_iter+0x1b0/0x290
> [11472.963066] [c0000005da817d10] [c000000000604868] vfs_write+0x38c/0x488
> [11472.963071] [c0000005da817dc0] [c000000000604c98] ksys_write+0x84/0x140

Can you post the script that you run?


  reply	other threads:[~2024-09-23  6:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-22 16:53 [Bug][Git-Bisect][6.11.0-next-20240917]BUG: Unable to handle kernel data access on read at 0xc00c020000013d88 Venkat Rao Bagalkote
2024-09-23  2:15 ` Sergey Senozhatsky [this message]
2024-09-23  5:36   ` Venkat Rao Bagalkote
2024-09-23 15:23     ` Sergey Senozhatsky
2024-09-24  8:09       ` Venkat Rao Bagalkote

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=20240923021557.GA38742@google.com \
    --to=senozhatsky@chromium.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=minchan@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=terrelln@fb.com \
    --cc=venkat88@linux.vnet.ibm.com \
    /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).