Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Cesare Leonardi Newsgroups: linux.debian.bugs.dist,linux.debian.kernel Subject: Bug#913119: linux-image-4.18.0-2-amd64: Hangs on lvm raid1 Date: Sat, 24 Nov 2018 00:50:01 +0100 Message-ID: References: X-Original-To: 913119@bugs.debian.org X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Fri Nov 23 23:45:11 2018 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -2.848 Reply-To: Cesare Leonardi , 913119@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: Debian Kernel Team X-Debian-Pr-Message: followup 913119 X-Debian-Pr-Package: src:linux X-Debian-Pr-Source: linux X-Spam-Bayes: score:0.0000 Tokens: new, 12; hammy, 150; neutral, 48; spammy, 0. spammytokens: hammytokens:0.000-+--H*u:60.0, 0.000-+--H*u:x86_64, 0.000-+--H*u:60.3.0, 0.000-+--H*UA:60.3.0, 0.000-+--H*UA:x86_64 Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:references:subject:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=V7RzzEdFQeWuDIIQ2k26ej2WC1SXlzthFjek4oIzy7M=; b=BqZFPJDs/Dr++oWZVNslBDa93V+4tQMUGSBrG+YMz9ydBOwoyX1nz9ri1GO0//EjV1 vPiCow82m/MatOftlzH/SCo2ufF5TdDvEo0L+RB12WmmfYr6RTtN3WSK1/YO1AsDxiD0 LDOGz9T0Q3PSfgC0JGGMul3FnFZKgfrQ3Vd15k6WN5uiKXO453M4ZiRER5RGbDHaUFtw BV1QaB5OBdNjgkED4enORiVk4NkuwDOoHZG4VS0jPK4n2NTimK2DAp0XOg/qc8f2NIjH fRN/gRE8UocXFDYom8A2aBdmvdSRwB2RiOiTsZx6456U7StZkkylvMAUQJGOS8RYrSxt 9irw== X-Google-Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:references:subject:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=V7RzzEdFQeWuDIIQ2k26ej2WC1SXlzthFjek4oIzy7M=; b=nT3pODWWeB5vjZr39tX6aOsy7fH8oLQF2HiualcflNvdNSVlfwTh79MJiYVTPCTXDc V14YKIS4bVtM1bR30Bw6OdCO8CDu7BrEVcp/4/AZPwJms0XJ4Rq+n+063DiNcgrfgt1t 4/RGTsWpIAijLJEsqm24PQK08dhqT59Cpo6JGbnpRIMqaIfaljG05jg2X3teoCokx/qX QJRdmRovYtheB6PAjLav87ly1a9JitqLCOpvoMD+h2ZLvNaK49mQcJNxOJh77FIUi3BB xpvhL/iNHWnhGVqNzWRnTmP6sfTTMAJoAwQaoN3e4O+T4o1zLOBY1ktRDnOTAlfiIn3w zWXQ== X-Gm-Message-State: AA+aEWa/rZXS1w7ljXSe+sHKVg9kFZVrVQbU7rLzaeC6TzIlNR44uVIO ukbx1NTZlWpD7/DgNsrADdwbtv2I X-Google-SMTP-Source: AFSGD/Vf9oOzT2KS8BxtF3Ird+dctkOYNjcwnaO+shJ0/PBKDElKnLlmiHZOU03ryKB3XP0XCkRIpw== X-Received: by 2002:a1c:6d3:: with SMTP id 202-v6mr15133336wmg.7.1543016572048; Fri, 23 Nov 2018 15:42:52 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: it-IT Content-Transfer-Encoding: 7bit X-Crossassassin-Score: 2 X-Debian-Message: from BTS X-Mailing-List: archive/latest/1500541 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 18 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: 913138@bugs.debian.org X-Original-Date: Sat, 24 Nov 2018 00:42:43 +0100 X-Original-Message-ID: X-Original-References: <154157498789.2411.17799566398451178693.reportbug@barone.internal.bernispa.com> <154157498789.2411.17799566398451178693.reportbug@barone.internal.bernispa.com> <9e001502-a297-0a3a-703e-bbf5630623f6@gmail.com> <9e001502-a297-0a3a-703e-bbf5630623f6@gmail.com> <154157498789.2411.17799566398451178693.reportbug@barone.internal.bernispa.com> <9e001502-a297-0a3a-703e-bbf5630623f6@gmail.com> Xref: csiph.com linux.debian.bugs.dist:929549 linux.debian.kernel:62543 Bug still present with the new 4.18.0-3-amd64 (4.18.20-1). This morning I've tryed to boot this new kernel version, removing the workaround given by the following kernel parameters: scsi_mod.use_blk_mq=0 dm_mod.use_blk_mq=0 The system showed disk hangs in less than 5 hours, and, as in previous 4.17 and 4.18, normal disk activities was restored after some minutes, without apparent data loss. I experienced two hangs before rebooting, but one of them didn't produce an oops in dmesg. It was not the first time I saw an hang without oops: maybe those that can recover in less than 120 seconds, doesn't produce oopses in dmesg? And just to be clear, it doesn't seem a bug related to LVM but more precisely to various types (all?) of LVM RAID. In fact my notebook disk uses LVM linear volumes and never showed those hangs and oopses. Cesare.