From owner-freebsd-current@freebsd.org Wed Jun 6 10:21:15 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41FCBFEFB4F for ; Wed, 6 Jun 2018 10:21:15 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C672A6DBE4 for ; Wed, 6 Jun 2018 10:21:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x230.google.com with SMTP id t6-v6so6973492iob.10 for ; Wed, 06 Jun 2018 03:21:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ClCdjHEgVFZV3/WA32WnwHlDa6X1Ncb4kx4fYeEcBTQ=; b=krDzjVPbxBoIozYcsZF3k7TsBB6qSjz6C5wMG21xK/M8zaKQXA2cfSUp243cK2q1rD 9W3nva2ESEm9cgLYPZBhdTCnYE9WOMnF26uYBFvkzUJAd8gwah/2aj8NtApOyACDE+AW vRDRqQ5EebRhUd+XGgB5hXc9fZ8bWTAk32VP6Ltjsy3e4HLgsaZnqQEuanar4UWur/Kj Jw9Pi+ij1dqU5/pv9MxBn1hR+P7UXC4WrNZpIon51DwnWt+oxO6M6aS1dUM7X+hBeabm n974o+HqCqGRlOhHJjWBc+kkOtgvuzcGbqnTu3kiOgO2ur8jsSC8tVAGL00QreVKYkBd 2O/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ClCdjHEgVFZV3/WA32WnwHlDa6X1Ncb4kx4fYeEcBTQ=; b=dymBk0xc0je+BAiSLGeCaJcueQyU/sHh5THEMpxeRFXNxMBIAqf/2zQsv4d/espT3E dqFXBNlPKEC+EehMlDbHnoUMfmVhnVNUNJSbqAuTLAoU24Rs8Ll8TDuH291KnaIMMdmv p3foZwtRwhL68VNJ6JNw6lKXHYTAL23LL+l97S3lrcjHLLIYTQw25o5rmgo5kF+cuDBx o7MNLkeZ0yCBlx7CGSVIIVL58hiaqU2jLvnqraG5+sML1VY19ktsromP0tFFGlUlfSiV 2E67Uz7En/q7SPTYFzUvNqZ+2LdC36oSz+I0ZxRgiLwE7il8E6nZMy/s88sw7pG0r2DC k/Lg== X-Gm-Message-State: APt69E2gA+cWFl6Hs+ZCZjZH/bOBBtwm7k3hpjNyB+ad1knrhyeHtXTS wy2tbkhI7qwUNoqpHH6+3TbBzkC8lkCfl5PvkII+1g== X-Google-Smtp-Source: ADUXVKLK+EKMX215e/Vy7sYkNO9lXzRM1jwZ5s9xsT+t6DFWjuxRZ7ZLrNZDPKyzf6BzAEzag45KtAvAIarQE6vNkVU= X-Received: by 2002:a5e:9817:: with SMTP id s23-v6mr2233081ioj.117.1528280474053; Wed, 06 Jun 2018 03:21:14 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Wed, 6 Jun 2018 03:21:13 -0700 (PDT) X-Originating-IP: [38.64.177.126] In-Reply-To: <20180606065520.1b927cdf@freyja.zeit4.iv.bundesimmobilien.de> References: <20180606065520.1b927cdf@freyja.zeit4.iv.bundesimmobilien.de> From: Warner Losh Date: Wed, 6 Jun 2018 06:21:13 -0400 X-Google-Sender-Auth: ki_TJxb-wrxRkCc07s4F8uLF7qM Message-ID: Subject: Re: CAM/ growisofs: Segmentation fault, SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range) To: "O. Hartmann" Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2018 10:21:15 -0000 On Wed, Jun 6, 2018 at 12:55 AM, O. Hartmann wrote: > Hello, > > my desperate call for help is according to PR 225291, > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225291. > > On one of our Workstations (Fujitsu Celsius M740 with Haswell XEON 6-core > CPU) > I face the inability to burn larger DVDs, using the port > sysutils/dvd+rw-tools. > > The recent status of the OS is FreeBSD 12.0-CURRENT #38 r334651: Tue Jun 5 > 13:33:18 CEST 2018 amd64, but this problem has been present since January, > see > PR citet above. > > The fact is, that with several DVD burner (all older models), burning DVDs > of > larger sizes (> 4 GB) started to fail around December/January and I thought > that might be due to a defect of the hardware. After switching to other > exchange burner models, the same error occured. > > While I was able to finish the job in January after the Seg fault occured, > this > is now impossible, even with the DVD burner it worked prior. > > Please have a look at the PR cited above for more details. > Without more details, I'm at a loss. I took a quick look at the bug report. I'm thinking that a lot of this is 'effect' not cause. The drive is getting some kind of bad request (or is just nuts, but we'll hold hardware breaking in reserve for the moment) and we're reacting appropriately to it (though the userland growisofs program segment faulting is clearly bad -- likely an untested error path). So I'm unsure what to do next... Any chance at all you can bisect the revision where this started happening? Warner