All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatoly Pugachev <matorola@gmail.com>
To: sparclinux@vger.kernel.org
Subject: Re: Regression with 4.7.2 on sun4u
Date: Wed, 07 Sep 2016 10:01:15 +0000	[thread overview]
Message-ID: <CADxRZqxWUU9FxWPqkcTVzvDE2PMQWEfLCXvH86vX6cgQ8xVxSw@mail.gmail.com> (raw)
In-Reply-To: <3fc12066-505b-5f87-cbbe-88593a736162@physik.fu-berlin.de>

[-- Attachment #1: Type: text/plain, Size: 2811 bytes --]

On Wed, Sep 7, 2016 at 12:22 PM, John Paul Adrian Glaubitz
<glaubitz@physik.fu-berlin.de> wrote:
> Hello!
>
> After kernel 4.7.2 entered Debian unstable, I decided to upgrade the buildds and ran into an
> apparent regression with the 4.7.x kernels on sun4u machines:

It's not only with sun4u, we're getting kernel OOPS on sun4v as well:

landau login: [860301.509777]               \|/ ____ \|/
[860301.509777]               "@'/ .. \`@"
[860301.509777]               /_| \__/ |_\
[860301.509777]                  \__U_/
[860301.509801] systemd-journal(1059): Kernel illegal instruction [#1]
[860301.509807]               \|/ ____ \|/
[860301.509807]               "@'/ .. \`@"
[860301.509807]               /_| \__/ |_\
[860301.509807]                  \__U_/
[860301.509814] CPU: 88 PID: 1059 Comm: systemd-journal Not tainted
4.7.0-1-sparc64-smp #1 Debian 4.7.2-1
[860301.509817] task: fff800201eb3a4c0 ti: fff800201e83c000 task.ti:
fff800201e83c000
[860301.509819] TSTATE: 0000004411001600 TPC: 00000000005c27dc TNPC:
00000000005c27e0 Y: 00000004    Not tainted
[860301.509830] TPC: <__kmalloc_track_caller+0x13c/0x200>
[860301.509832] g0: 0000000231c55926 g1: 0000000000400000 g2:
0000000000000000 g3: 00000000c0000000
[860301.509834] g4: fff800201eb3a4c0 g5: fff800207cae6000 g6:
fff800201e83c000 g7: 0000000000006700
[860301.509837] o0: 0000000000000000 o1: 0000000003ffffff o2:
fff800201e83fd98 o3: 0000000000004040
[860301.509838] o4: 0000000000000000 o5: fff800201e83fbb8 sp:
fff800201e83edb1 ret_pc: 00000000005c27d4
[860301.509841] RPC: <__kmalloc_track_caller+0x134/0x200>
[860301.509843] l0: 0000000000000000 l1: fff80000804024a0 l2:
0000000000000000 l3: 0000000000000000
[860301.509845] l4: 0000000000000000 l5: 0000000000000000 l6:
0000000000000000 l7: fff80001009fc000
[860301.509847] i0: fff80000804024a0 i1: 00000000024106c0 i2:
000000000085333c i3: 00000000024106c0
[860301.509849] i4: 00000000000001c0 i5: 00000000024106c0 i6:
fff800201e83ee61 i7: 0000000000853280
[860301.509855] I7: <__kmalloc_reserve.isra.5+0x20/0x80>
[860301.509856] Call Trace:
[860301.509859]  [0000000000853280] __kmalloc_reserve.isra.5+0x20/0x80
[860301.509861]  [000000000085333c] __alloc_skb+0x5c/0x180
[860301.509864]  [00000000008534a4] alloc_skb_with_frags+0x44/0x1e0
[860301.509873]  [000000000084ddcc] sock_alloc_send_pskb+0x1ec/0x220
[860301.509883]  [00000000009219cc] unix_dgram_sendmsg+0x12c/0x600
[860301.509887]  [00000000008485dc] sock_sendmsg+0x3c/0x80
[860301.509890]  [0000000000849010] ___sys_sendmsg+0x250/0x260
[860301.509893]  [0000000000849f94] __sys_sendmsg+0x34/0x80
[860301.509895]  [000000000084a000] SyS_sendmsg+0x20/0x40
[860301.509904]  [00000000004061f4] linux_sparc_syscall+0x34/0x44
[860301.509906] Disabling lock debugging due to kernel taint

full boot log in attachment as well.

[-- Attachment #2: sun4v-4.7.2-boot.log.gz --]
[-- Type: application/x-gzip, Size: 20447 bytes --]

  reply	other threads:[~2016-09-07 10:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07  9:22 Regression with 4.7.2 on sun4u John Paul Adrian Glaubitz
2016-09-07 10:01 ` Anatoly Pugachev [this message]
2016-10-21  9:12 ` Anatoly Pugachev
2016-10-21 12:57 ` Anatoly Pugachev
2016-10-21 15:00 ` David Miller
2016-10-21 15:49 ` Rob Gardner
2016-10-21 16:35 ` James Clarke
2016-10-21 17:26 ` David Miller
2016-10-21 17:47 ` James Clarke
2016-10-21 21:52 ` James Clarke
2016-10-22  1:07 ` David Miller
2016-10-22  9:51 ` James Clarke
2016-10-24 18:11 ` David Miller
2016-10-25  0:10 ` James Clarke
2016-10-26  2:12 ` David Miller

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=CADxRZqxWUU9FxWPqkcTVzvDE2PMQWEfLCXvH86vX6cgQ8xVxSw@mail.gmail.com \
    --to=matorola@gmail.com \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.