Page 1 of 1

Where to kernel bug report

Posted: Tue May 14, 2019 6:30 am
by pmatos
Hi,
I have attempted for the first time a build on a set of 7 rpi with distcc. Not long after the start, the master fell apart with a kernel bug:

Code: Select all

May 14 06:25:10 rpi-master kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
May 14 06:25:10 rpi-master kernel: pgd = a8a00000
May 14 06:25:10 rpi-master kernel: [00000000] *pgd=266fd835, *pte=00000000, *ppte=00000000
May 14 06:25:10 rpi-master kernel: Internal error: Oops: 17 [#1] SMP ARM
May 14 06:25:10 rpi-master kernel: Modules linked in: ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc overla
May 14 06:25:10 rpi-master kernel: CPU: 0 PID: 3672 Comm: racketcgc Not tainted 4.9.35-v7+ #1014
May 14 06:25:10 rpi-master kernel: Hardware name: BCM2835
May 14 06:25:10 rpi-master kernel: task: 867f3b00 task.stack: a660a000
May 14 06:25:10 rpi-master kernel: PC is at __schedule+0xac/0x7bc
May 14 06:25:10 rpi-master kernel: LR is at __schedule+0x94/0x7bc
May 14 06:25:10 rpi-master kernel: pc : [<80714474>]    lr : [<8071445c>]    psr: 60000193
                                   sp : a660bc40  ip : a660bc40  fp : a660bca4
May 14 06:25:10 rpi-master kernel: r10: 80b7e940  r9 : 00000000  r8 : 80c0442c
May 14 06:25:10 rpi-master kernel: r7 : 80b7e940  r6 : 00000428  r5 : 00000000  r4 : b9f29940
May 14 06:25:10 rpi-master kernel: r3 : 00000000  r2 : 00000000  r1 : 00000000  r0 : b9f29940
May 14 06:25:10 rpi-master kernel: Flags: nZCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user
May 14 06:25:10 rpi-master kernel: Control: 10c5383d  Table: 28a0006a  DAC: 00000055
May 14 06:25:10 rpi-master kernel: Process racketcgc (pid: 3672, stack limit = 0xa660a210)
May 14 06:25:10 rpi-master kernel: Stack: (0xa660bc40 to 0xa660c000)
May 14 06:25:10 rpi-master kernel: bc40: b91d8000 a5d683a0 00000000 00000003 a660bc74 b91d8000 393ab000 00000000
May 14 06:25:10 rpi-master kernel: bc60: 00000003 80714bd4 b9f29940 a660bc78 8042c51c 801e3474 02400000 a660a000
May 14 06:25:10 rpi-master kernel: bc80: 00000000 7fffffff b9f69e20 80714350 b0d0a1c0 ba6132e8 a660bcbc a660bca8
May 14 06:25:10 rpi-master kernel: bca0: 80714bd4 807143d4 00000001 7fffffff a660bd2c a660bcc0 80717e44 80714b90
May 14 06:25:10 rpi-master kernel: bcc0: a660bd0c a660bcd0 8018cc4c 805da53c a6395fce 0028df45 227e7ecd 0034c500
May 14 06:25:10 rpi-master kernel: bce0: ffffffff 00ffffff b926c040 00000000 7fffffff 807154c0 a660bd90 b0d0a1c0
May 14 06:25:10 rpi-master kernel: bd00: a660bd2c b9f69940 00000000 7fffffff b9f69e20 a660bd90 b0d0a1c0 ba6132e8
May 14 06:25:10 rpi-master kernel: bd20: a660bd4c a660bd30 80714350 80717c30 00000082 a660bd9c 80c02b44 807154c0
May 14 06:25:10 rpi-master kernel: bd40: a660bd64 a660bd50 807154e0 8071429c 00048001 00000082 a660bd8c a660bd68
May 14 06:25:10 rpi-master kernel: bd60: 80715108 807154cc 00000004 00000000 b0d0a1c0 00772e80 a88d6160 b0d0a1c0
May 14 06:25:10 rpi-master kernel: bd80: a660bdc4 a660bd90 8020db0c 80715080 ba6132e8 00000000 00000000 00000000
May 14 06:25:10 rpi-master kernel: bda0: 867f3b00 801614e0 80c02b48 80c02b48 00000004 ba6132e8 a660bdec a660bdc8
May 14 06:25:10 rpi-master kernel: bdc0: 8020e520 8020da84 a660be5c 00000054 00772e80 0000ee5d a660be5c 00000004
May 14 06:25:10 rpi-master kernel: bde0: a660be3c a660bdf0 80241388 8020e46c 00000000 00000001 80c06984 80d04818
May 14 06:25:10 rpi-master kernel: be00: 80c06984 00000054 a660be3c b8028000 8024faf8 a88d6160 00772e80 00000054
May 14 06:25:10 rpi-master kernel: be20: 00000040 b0d0a1c0 b0d0a1f8 00000054 a660bea4 a660be40 80241c84 80240f30
May 14 06:25:10 rpi-master kernel: be40: 00000000 80129a4c a660be64 a660be58 80129a4c 80129884 a660be84 a88d6160
May 14 06:25:10 rpi-master kernel: be60: 758a0000 00000054 a8a01d60 a5fce280 00000000 00000000 a660bea4 a660bfb0
May 14 06:25:10 rpi-master kernel: be80: 867f3b00 00000017 758a000c b0d0a1c0 b0d0a1f8 00000054 a660befc a660bea8
May 14 06:25:10 rpi-master kernel: bea0: 8071a134 8024187c 04000000 00000000 00000000 a660bec8 a660bf8c 80716c04
May 14 06:25:10 rpi-master kernel: bec0: a660bee4 00000000 00000000 00000008 a660a0f8 80c093f4 00000017 80719df8
May 14 06:25:10 rpi-master kernel: bee0: 758a000c a660bfb0 75aa0001 75a9ffff a660bfac a660bf00 801011e8 80719e04
May 14 06:25:10 rpi-master kernel: bf00: 00001fa8 00000000 a660bf34 a660a000 7ebc8c78 7ebc8b70 41034034 00000000
May 14 06:25:10 rpi-master kernel: bf20: a660a000 00000000 a660bf44 a660bf38 80461de4 80461b3c a660bf64 a660bf48
May 14 06:25:10 rpi-master kernel: bf40: 80103088 80461dd0 7ebc8a80 a660bfb0 00000000 00000077 a660bf8c a660bf68
May 14 06:25:10 rpi-master kernel: bf60: 8010af50 80103050 00000000 00000000 a660bfb0 a660bfb0 0029b30c 75eeffff
May 14 06:25:10 rpi-master kernel: bf80: a660bfa4 001894a0 60000010 001894a0 60000010 ffffffff 10c5383d 10c5387d
May 14 06:25:10 rpi-master kernel: bfa0: 00000000 a660bfb0 80719964 801011ac 00000000 00000007 758a0000 ffffffff
May 14 06:25:10 rpi-master kernel: bfc0: ffffffff 0029b81c 75a9ffff 00000001 00000001 75aa0001 75a9ffff 76c80000
May 14 06:25:10 rpi-master kernel: bfe0: 00000000 7ebc8d70 0029b7d8 001894a0 60000010 ffffffff 00000000 00000000
May 14 06:25:10 rpi-master kernel: [<80714474>] (__schedule) from [<80714bd4>] (schedule+0x50/0xa8)
May 14 06:25:10 rpi-master kernel: [<80714bd4>] (schedule) from [<80717e44>] (schedule_timeout+0x220/0x364)
May 14 06:25:10 rpi-master kernel: [<80717e44>] (schedule_timeout) from [<80714350>] (io_schedule_timeout+0xc0/0x138)
May 14 06:25:10 rpi-master kernel: [<80714350>] (io_schedule_timeout) from [<807154e0>] (bit_wait_io+0x20/0x6c)
May 14 06:25:11 rpi-master kernel: [<807154e0>] (bit_wait_io) from [<80715108>] (__wait_on_bit+0x94/0xd0)
May 14 06:25:11 rpi-master kernel: [<80715108>] (__wait_on_bit) from [<8020db0c>] (wait_on_page_bit_killable+0x94/0xa4)
May 14 06:25:11 rpi-master kernel: [<8020db0c>] (wait_on_page_bit_killable) from [<8020e520>] (__lock_page_or_retry+0xc0/0xfc)
May 14 06:25:11 rpi-master kernel: [<8020e520>] (__lock_page_or_retry) from [<80241388>] (do_swap_page+0x464/0x5fc)
May 14 06:25:11 rpi-master kernel: [<80241388>] (do_swap_page) from [<80241c84>] (handle_mm_fault+0x414/0xd80)
May 14 06:25:11 rpi-master kernel: [<80241c84>] (handle_mm_fault) from [<8071a134>] (do_page_fault+0x33c/0x3b0)
May 14 06:25:11 rpi-master kernel: [<8071a134>] (do_page_fault) from [<801011e8>] (do_DataAbort+0x48/0xc4)
May 14 06:25:11 rpi-master kernel: [<801011e8>] (do_DataAbort) from [<80719964>] (__dabt_usr+0x44/0x60)
May 14 06:25:11 rpi-master kernel: Exception stack(0xa660bfb0 to 0xa660bff8)
May 14 06:25:11 rpi-master kernel: bfa0:                                     00000000 00000007 758a0000 ffffffff
May 14 06:25:11 rpi-master kernel: bfc0: ffffffff 0029b81c 75a9ffff 00000001 00000001 75aa0001 75a9ffff 76c80000
May 14 06:25:11 rpi-master kernel: bfe0: 00000000 7ebc8d70 0029b7d8 001894a0 60000010 ffffffff
May 14 06:25:11 rpi-master kernel: Code: e2866008 e1a03083 e58434c8 1a000002 (e5953000) 
May 14 06:25:11 rpi-master kernel: ---[ end trace 7a8a05885d6d5f1a ]---
This is an up-to-date rpi

Code: Select all

Linux rpi-master 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
running stretch:

Code: Select all

Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 9.9 (stretch)
Release:        9.9
Codename:       stretch
Is there a place for specific kernel bugs on the rpi? Or should I just report upstream? In any case, has anyone experienced this before?

Re: Where to kernel bug report

Posted: Tue May 14, 2019 3:48 pm
by DougieLawson
You aren't even using the latest stable kernel. You won't find anyone willing to look at a bug in a 4.9 kernel as it would be a complete and total waste of time.

Recreate it on 4.14.98 or 4.19.40 and folks may take you more seriously.

Re: Where to kernel bug report

Posted: Tue May 14, 2019 4:01 pm
by jamesh
More politely, 4.9 is a very old kernel version and we don't do bug hunting on stuff that old. Not sure why you think your Pi is up to date because it isn't.

Update your kernel to the latest release (4.14) and see if the problem still happens.

You could even use rpi-update to get to 4.19 but that is not recomended until you have tried 4.14 as that is a very bleeding edge test kernel.