From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 63A14CA9EC0 for ; Mon, 28 Oct 2019 19:44:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 36E3220873 for ; Mon, 28 Oct 2019 19:44:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="FLW3qv+a" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730274AbfJ1ToN (ORCPT ); Mon, 28 Oct 2019 15:44:13 -0400 Received: from mail-io1-f65.google.com ([209.85.166.65]:41430 "EHLO mail-io1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730286AbfJ1ToN (ORCPT ); Mon, 28 Oct 2019 15:44:13 -0400 Received: by mail-io1-f65.google.com with SMTP id r144so12072643iod.8 for ; Mon, 28 Oct 2019 12:44:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=F9yjJ4PFl32YvXwzODYyp252wDBRX1rheD8d1z4Ivvk=; b=FLW3qv+axbhaUOF5KRVjcLXa9JGxUy+9IycXLKL7ODOTLYlhILhziuly0fmS1JXB9B ckQkfiYzMr+3b8qfhcm9OvC8bFiXj7JktliGL/2W+svmhKKa7iFU0XsDlA3Nkrp08a1s tMh3VP8eANWWkI2rINNMzSFGlMGZVravPCleRmCkGmH7aCbRiL6U2xjX/jANLlu1Wgre 5JjGs89gEJ2f+45wZT9rH/WpaPyYzzzom4kQ9xVd1EXVzjeVAqBpm7wZrGJAQaHUTlJ2 de09puaNuKaezs/nWUB7i9VIKtb2i0GvyUFei4J+aMgBH9NcZKgn09BXvShM6ouvJ26f mpxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=F9yjJ4PFl32YvXwzODYyp252wDBRX1rheD8d1z4Ivvk=; b=WL7Ec5U6WZk2i4yGdPyttbd4U6MJm7XsQz8km607Lbznb41EOpncUSwSniDFOBUlDk mf3QekSYeJ98NEMrJgnXTrRrw7NTlTbPwr+HkwjGUDnOqK1vfi8Tb0Xih7BdaoUIflnf FV3G7oKZWVUB11PCARezArjcPWFJmN2vnw2bm6STk1b8UKJaei0S1s8Ps1fP1SkvT5lF q0aakRUzEh4ZqABr3TCsVFm5q3ZonXpWy+K/UypLO3gWM94jeHFw7OH8xvZrTtCF5G0L 7GTnJpwK4/f1zWthJrWNNUq0vebFRrpQfd1PQdaxSgJOSRllOtcQd8YknjMB2S9jQ9eo jxJw== X-Gm-Message-State: APjAAAV6lnhpvAaX7s7SkwynlcqVMkAvBFwuURWe7VCzFToqWq9CKczN iMJ+I2DHeZHhOVv/J+9az9vHPbVRSdwc35PlWIt7Ug== X-Google-Smtp-Source: APXvYqySbESYw0jrXv1RKys8KhfT2FtD5Li8WHbjCYkEkjMl311M8QHJqCW9S1vOTGU9U4QUeJxDWTYmJM6k3ZHQhSc= X-Received: by 2002:a02:740a:: with SMTP id o10mr17482478jac.106.1572291852235; Mon, 28 Oct 2019 12:44:12 -0700 (PDT) MIME-Version: 1.0 References: <20191028171329.GA104845@google.com> In-Reply-To: Reply-To: bjorn@helgaas.com From: Bjorn Helgaas Date: Mon, 28 Oct 2019 14:43:59 -0500 Message-ID: Subject: Re: Oxford Semiconductor Ltd OX16PCI954 - weird dmesg To: Carlo Pisani Cc: Bjorn Helgaas , Bjorn Helgaas , linux-pci@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Mon, Oct 28, 2019 at 2:06 PM Carlo Pisani wrote: > > > What's your .config file? The knowledge about the host bridge windows > > must be compiled in somewhere. > > here it is > > http://www.downthebunker.com/chunk_of/stuff/public/projects/sonoko-x11/router-board/kernel/k4.4.197-rb532.config > > too long to be attached to this email > > > The UARTs do not have DMA enabled (BusMaster-) in the lspci output, so > > they shouldn't be able to corrupt memory. The NICs *do* have DMA > > enabled. Does the problem still happen if you turn off the NIC > > drivers (via-rhine and ath9k, it looks like)? > > I will recompile the kernel and re-test the router. It's a 48 hours burn-in test It looks like you're using a v4.4-based kernel, which is 3 1/2 years old. In general people are not very interested in debugging kernels that old. It's better if you can reproduce the problem on a current kernel, then backport the fix if you need it in an older kernel. Bjorn