Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #64520

Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing

Path csiph.com!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder7.news.weretis.net!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From Terry Glanfield <terry@glanfield.net>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing
Date Tue, 23 Jul 2019 23:00:01 +0200
Message-ID <yna37-17f-3@gated-at.bofh.it> (permalink)
References <yllYJ-7Id-1@gated-at.bofh.it>
X-Mailbox-Line From debian-bugs-dist-request@lists.debian.org Tue Jul 23 20:57:14 2019
Old-Return-Path <debbugs@buxtehude.debian.org>
X-Spam-Flag NO
X-Spam-Score -3.751
Reply-To Terry Glanfield <terry@glanfield.net>, 932408@bugs.debian.org
Original-Sender Terry Glanfield <terry@fierybreadcrumbs.com>
Resent-To debian-bugs-dist@lists.debian.org
Resent-Cc Debian Kernel Team <debian-kernel@lists.debian.org>
X-Debian-Pr-Message followup 932408
X-Debian-Pr-Package src:linux
X-Debian-Pr-Keywords moreinfo
X-Debian-Pr-Source linux
X-Spam-Bayes score:0.0000 Tokens: new, 20; hammy, 108; neutral, 36; spammy, 0. spammytokens: hammytokens:0.000-+--H*r:sk:AEAD-AE, 0.000-+--H*r:TLS1_3, 0.000-+--UD:20150623.gappssmtp.com, 0.000-+--UD:gappssmtp.com, 0.000-+--H*r:209.85.166
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=fierybreadcrumbs-com.20150623.gappssmtp.com; s=20150623; h=sender:mime-version:from:date:message-id:subject:to; bh=nkAmBzdFUNbyT8P1GOWvYgCej5EmB7CVwNwDnmsnQBo=; b=VI7U9wOZmDA+KClkUhgg0lfhC2Htx9XEz7XxYzctIOGzNy5/w7olbwA8C04l91SCkb 0+dS1uYubTb3snqz8CFNJis6M7N8cD1Sxi1mLSwibJrB6WfhANaOvAnR6fL1h/RRaHMw k26L0f3Oog4QS/obdCC+3VFVoBB2yBd8zEwxXEArIe7uaoNc3fN27KEvlsJzAe2Z3eOf +2QfUskpWs9jp17r0WVKT334ysgllhKAT9NEh/3hlO+Fo8LoHZPR9wZh5s0Wr74Crdcm dPZ5UYWQ8cgX8qLSXHfmfDyQ04Zh7Z8jeIXks6xzQlM+e+NIyo7xUb8o3d8+zMlbxEvk g/DA==
X-Google-Dkim-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:mime-version:from:date:message-id:subject :to; bh=nkAmBzdFUNbyT8P1GOWvYgCej5EmB7CVwNwDnmsnQBo=; b=bOJo+ZgmhVR93VlPtp0l6wNzNEj0bXSnpJ9sZtQnivXPPW+qEkws81bJEK9NZPjvLZ aE/shLgFpF4+kQWXTFVB5bSA82dJpsmkwAKq6UsnkDFQBhYLKNS7yp1DpMTP8E1l/Qhy R0/XoHR20J3SVXS1AK7l7x9wZIfpPqFUvXNMJr7R46ogExaCCyU8rvR/6yBxkMmazkFW 89iedSQbn8jQMpMY7rRWDUyORIBKziqHOvL7wVI8qEpQH7p20+YbwUI0XhXP62Ykne04 apkYOfK3QIcVtK2ktCXAeQiJuyD0E0y+xl+aC1BRSKfpQfisWp+Or0Clf90FetGPNtlA dapA==
X-Gm-Message-State APjAAAUttSQh1NW08L18Q6HgyN7SzFhSz0kT5vAA2fSGEXQPKb1KIh3/ 2r7m7CZui6XIZRZESoSRHTafwbTe
X-Google-SMTP-Source APXvYqx5pSq4RSOqCsGWCnkj9TxRSrMS88V++jvDdu/kU2UiILAGDnG9DXsVqQh5jOAwqqzTrZWiKA==
X-Received by 2002:a02:a595:: with SMTP id b21mr28059691jam.28.1563915327947; Tue, 23 Jul 2019 13:55:27 -0700 (PDT)
Sender robomod@news.nic.it
X-Received by 2002:a5d:885a:: with SMTP id t26mr20147335ios.218.1563915326848; Tue, 23 Jul 2019 13:55:26 -0700 (PDT)
MIME-Version 1.0
X-Gmail-Original-Message-ID <CADzUR6v4KWaJpwZgZHNcF+RBy29f1BLLoqsrcHg9zrD2ZndbFw@mail.gmail.com>
Content-Type text/plain; charset="UTF-8"
X-Debian-Message from BTS
X-Mailing-List <debian-bugs-dist@lists.debian.org> archive/latest/1547350
List-ID <debian-bugs-dist.lists.debian.org>
List-URL <https://lists.debian.org/debian-bugs-dist/>
Approved robomod@news.nic.it
Lines 19
Organization linux.* mail to news gateway
X-Original-Date Tue, 23 Jul 2019 21:55:16 +0100
X-Original-Message-ID <CADzUR6v4KWaJpwZgZHNcF+RBy29f1BLLoqsrcHg9zrD2ZndbFw@mail.gmail.com>
X-Original-References <156348219690.1204.7683713096229835770.reportbug@xterm.glanfield.net>
X-Original-Sender Terry Glanfield <terry@fierybreadcrumbs.com>
Xref csiph.com linux.debian.bugs.dist:966127 linux.debian.kernel:64520

Cross-posted to 2 groups.

Show key headers only | View raw


Thank you for the suggestion.

I've installed 4.19.60 but that gives the same kernel panic.

Where do I start in getting some more information to track what's causing this?

On Tue, 23 Jul 2019 14:40:59 +0200 Kinky Nekoboi
<kinky_nekoboi@nekoboi.moe> wrote:
> i had and have several problems with 4.19.37-5  ... an selfbuild vanila
> kernel 4.19.60 with default options fixed most of them for me ...
>
> Debian should really push a newer 4.19.y kernel for buster
>
> Am 23.07.19 um 14:01 schrieb Terry Glanfield:
> > This is still failing after an update to 4.19.37-5+deb10u1
> >
> > Any clues on where to start tracking this down?
> >
>

Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing Terry <terry@glanfield.net> - 2019-07-18 23:20 +0200
  Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing Ben Hutchings <ben@decadent.org.uk> - 2019-07-19 01:20 +0200
  Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing Terry Glanfield <terry@glanfield.net> - 2019-07-23 14:10 +0200
  Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing Terry Glanfield <terry@glanfield.net> - 2019-07-23 23:00 +0200
  Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing Harald Dunkel <harald.dunkel@aixigo.com> - 2019-08-28 08:40 +0200
  Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing Vcs Ccs <vcs107@gmail.com> - 2019-10-27 21:40 +0100

csiph-web