linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 205099] New: KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d
Date: Sun, 06 Oct 2019 17:49:07 +0000	[thread overview]
Message-ID: <bug-205099-206035@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=205099

            Bug ID: 205099
           Summary: KASAN hit at raid6_pq: BUG: Unable to handle kernel
                    data access at 0x00f0fd0d
           Product: Platform Specific/Hardware
           Version: 2.5
    Kernel Version: 5.4-rc1
          Hardware: PPC-32
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: PPC-32
          Assignee: platform_ppc-32@kernel-bugs.osdl.org
          Reporter: erhard_f@mailbox.org
        Regression: No

Created attachment 285367
  --> https://bugzilla.kernel.org/attachment.cgi?id=285367&action=edit
dmesg (kernel 5.4-rc1, PowerMac G4 DP)

With lots of KASAN ppc fixes included in kernel 5.4-rc1 now, I am revisiting
the issues of bug #204479.

raid6 pq still reliably oopses:

[...]
[   19.186966] BUG: Unable to handle kernel data access at 0x00f0fd0d
[   19.196913] Faulting instruction address: 0xf1692560
[   19.235490] ohci-pci: OHCI PCI platform driver
[   19.236988] Oops: Kernel access of bad area, sig: 11 [#1]
[   19.255518] BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
[   19.265311] Modules linked in: ohci_pci(+) raid6_pq(+) zlib_inflate sungem
hwmon sungem_phy i2c_algo_bit sr_mod drm_kms_helper cdrom syscopyarea
sysfillrect firewire_ohci sysimgblt ohci_hcd ehci_pci fb_sys_fops ttm
firewire_core snd_aoa_i2sbus ehci_hcd crc_itu_t snd_aoa_soundbus snd_pcm
snd_timer drm snd soundcore usbcore ssb uninorth_agp
drm_panel_orientation_quirks pcmcia usb_common pcmcia_core agpgart
[   19.287432] CPU: 0 PID: 127 Comm: modprobe Tainted: G        W        
5.4.0-rc1 #10
[   19.298613] NIP:  f1692560 LR: f16924e8 CTR: c023bcf4
[   19.309692] REGS: e8d13730 TRAP: 0300   Tainted: G        W         
(5.4.0-rc1)
[   19.320847] MSR:  02009032 <VEC,EE,ME,IR,DR,RI>  CR: 28228822  XER: 00000000
[   19.332102] DAR: 00f0fd0d DSISR: 40000000 
               GPR00: e8d13988 e8d137e8 ee01b4a0 f16a5070 00000010 00000000
f16924e8 00000000 
               GPR08: f16a5070 00f0fd0d e7171aea e8d13a70 c023bcf4 0050fff4
00000060 00000050 
               GPR16: 00000040 f16a5000 00000012 eb28d000 eb28c000 00000070
00000060 00000050 
               GPR24: 00000040 00000030 00000020 00000010 e8d13a38 eb28d010
eb28c010 00000000 
[   19.388060] NIP [f1692560] raid6_altivec8_gen_syndrome_real+0x3c8/0x488
[raid6_pq]
[   19.399417] LR [f16924e8] raid6_altivec8_gen_syndrome_real+0x350/0x488
[raid6_pq]
[   19.405058] usb 1-1: new high-speed USB device number 2 using ehci-pci
[   19.410774] Call Trace:
[   19.410786] [e8d137e8] [00001032] 0x1032 (unreliable)
[   19.410824] [e8d139d8] [f1692654] raid6_altivec8_gen_syndrome+0x34/0x58
[raid6_pq]
[   19.410857] [e8d13a08] [f15c83c0] init_module+0x3c0/0x518 [raid6_pq]
[   19.460942] Apple USB OHCI 0001:10:18.0 disabled by firmware
[   19.468239] [e8d13af8] [c0005820] do_one_initcall+0xb8/0x36c
[   19.468264] [e8d13bc8] [c0109480] do_init_module+0xa8/0x2c4
[   19.502777] [e8d13bf8] [c010c2e4] load_module+0x2b68/0x2d24
[   19.514192] [e8d13df8] [c010c704] sys_finit_module+0x100/0x140
[   19.525556] [e8d13f38] [c001a274] ret_from_syscall+0x0/0x34
[   19.536910] --- interrupt: c01 at 0x35e2c4
                   LR = 0x4e67c4
[   19.559299] Instruction dump:
[   19.570504] 1304c4c4 7d2048ce 39210090 1325ccc4 7d6048ce 1346d4c4 81210088
1367dcc4 
[   19.581997] 7d11a8ce 115f5b06 116b5800 8141008c <7c0048ce> 392100a0 7d8048ce
392100b0 
[   19.593571] ---[ end trace 5e7216580d039a39 ]---

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2019-10-06 17:52 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-06 17:49 bugzilla-daemon [this message]
2019-10-06 17:49 ` [Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d bugzilla-daemon
2019-10-09 21:19 ` bugzilla-daemon
2019-12-10 23:51 ` bugzilla-daemon
2019-12-10 23:52 ` bugzilla-daemon
2019-12-10 23:54 ` bugzilla-daemon
2019-12-11 19:22 ` bugzilla-daemon
2019-12-14 13:49 ` bugzilla-daemon
2019-12-15 16:01 ` bugzilla-daemon
2019-12-21 17:42 ` bugzilla-daemon
2019-12-21 17:43 ` bugzilla-daemon
2020-01-17 21:16 ` bugzilla-daemon
2020-01-17 21:19 ` bugzilla-daemon
2020-01-17 21:22 ` bugzilla-daemon
2020-01-17 21:25 ` bugzilla-daemon
2020-01-18  8:47 ` bugzilla-daemon
2020-01-18 20:06 ` bugzilla-daemon
2020-01-20 12:40 ` bugzilla-daemon
2020-01-20 22:56 ` bugzilla-daemon
2020-01-21  5:52 ` bugzilla-daemon
2020-01-21 12:20 ` bugzilla-daemon
2020-01-21 12:24 ` bugzilla-daemon
2020-01-21 13:00 ` bugzilla-daemon
2020-01-21 13:00 ` bugzilla-daemon
2020-01-21 13:31 ` bugzilla-daemon
2020-02-26 15:49 ` bugzilla-daemon
2020-02-26 15:52 ` bugzilla-daemon
2020-02-26 16:17 ` bugzilla-daemon
2020-04-13 14:12 ` bugzilla-daemon
2020-04-13 14:15 ` bugzilla-daemon
2020-09-04 22:50 ` bugzilla-daemon
2020-09-04 22:54 ` bugzilla-daemon
2021-06-19  6:27 ` bugzilla-daemon
2021-06-19  8:25 ` bugzilla-daemon
2021-11-26  1:47 ` bugzilla-daemon
2021-11-26  1:48 ` bugzilla-daemon
2021-11-26  1:49 ` bugzilla-daemon
2021-11-26  9:03 ` bugzilla-daemon
2021-11-26  9:14 ` bugzilla-daemon
2021-11-26  9:20 ` bugzilla-daemon
2021-11-26 11:33 ` bugzilla-daemon
2021-11-29  0:32 ` bugzilla-daemon
2021-11-29  0:32 ` bugzilla-daemon
2021-11-29  0:34 ` bugzilla-daemon
2021-11-29  6:51 ` bugzilla-daemon
2021-11-29 19:46 ` bugzilla-daemon
2021-11-29 19:46 ` bugzilla-daemon
2021-11-30 13:58 ` bugzilla-daemon
2021-11-30 13:58 ` bugzilla-daemon
2021-11-30 15:39 ` bugzilla-daemon

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=bug-205099-206035@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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).