From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751334AbdFEWCI (ORCPT ); Mon, 5 Jun 2017 18:02:08 -0400 Received: from eggs.gnu.org ([208.118.235.92]:41914 "EHLO eggs.gnu.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751180AbdFEWCH (ORCPT ); Mon, 5 Jun 2017 18:02:07 -0400 From: David Kastrup To: linux-kernel@vger.kernel.org Cc: Randy Dunlap Subject: Re: What would cause /proc/ioports do be zeroed out? Organization: Organization?!? References: <8737be3ipn.fsf@fencepost.gnu.org> <87mv9m1dh9.fsf@fencepost.gnu.org> X-Face: 2FEFf>]>q>2iw=B6,xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN;i";/yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw Date: Tue, 06 Jun 2017 00:01:26 +0200 In-Reply-To: <87mv9m1dh9.fsf@fencepost.gnu.org> (David Kastrup's message of "Mon, 05 Jun 2017 20:44:18 +0200") Message-ID: <87h8zuccw9.fsf@fencepost.gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org David Kastrup writes: > Randy Dunlap writes: > >> On 06/05/17 02:08, David Kastrup wrote: >>> >>> The current symptom is that I cannot load some ACPI modules (compiled >>> via DKMS for x86_64 architecture) without io_force option, with the >>> kernel stating: >>> >>> [ 248.145348] thinkpad_ec: cannot claim IO ports 0x1600-0x161f... >>> [ 248.145350] consider using force_io=1. >>> >>> Now here is the really fishy thing: >>> >>> cat /proc/ioports >>> 0000-0000 : PCI Bus 0000:00 >>> 0000-0000 : dma1 >> >> Does /proc/iomem show the same thing (i.e., zeros)? > > Yes. > >> How about if you do the test while logged in as root? > > Darn it. Everything looks normal then in either case. So the /proc > thing likely is a red herring: > I have another computer with a Mate 17.04 distribution that is > complete 64bit including userland. It also masks the ioports like > this as non-root user and does not have the thinkpad_ec loading > problem. Bah. Once I can see the assigned ports, the ports complained about are for the acceleration sensors. And once I install hdapsd (the daemon acting on acceleration sensors) on that second computer, the same error occurs. So it has nothing at all to do with package management or 64/32 bits. And uninstalling hdapsd on my primary computer also solves the problem (as does setting the force_io option in /etc/modprobe.d/thinkpad_ec.conf). So lots of red herrings here. I just don't know why I started seeing this problem recently. But I am not likely to find out. So I removed the hdapsd package. Not sure whether the thinkpad_ec module from tp-smapi-dkms replaces it: at least it accesses the same ports. So it's really some problem specific to modules and functionality tied into my hardware rather than some general kernel functionality. Sorry for the noise. -- David Kastrup