Re: What would cause /proc/ioports do be zeroed out?

[Randy Dunlap]

On 06/05/17 02:08, David Kastrup wrote:
> 
> Hi,
> 
> I am trying to pinpoint a problem I am having with current Ubuntu
> Artful, likely after some recent attempts of getting rid of some package
> incompatibilities.  More likely than not the ultimate culprit is
> somewhere in the Debian package management, however I am really puzzled
> at figuring out where exactly things go wrong and since my current
> configuration is "valid" according to the package manager, it might help
> in other situations if I manage to get the problem located.
> 
> 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
>   0000-0000 : pic1
>   0000-0000 : timer0
>   0000-0000 : smapi
>   0000-0000 : timer1
>   0000-0000 : keyboard
>   0000-0000 : PNP0800:00
>   0000-0000 : PNP0C09:00
>     0000-0000 : EC data
>   0000-0000 : keyboard
>   0000-0000 : PNP0C09:00
>     0000-0000 : EC cmd
> 
> [...]
> 
>   0000-0000 : PCI Bus 0000:0d
>   0000-0000 : PCI Bus 0000:15
>     0000-0000 : PCI CardBus 0000:16
>     0000-0000 : PCI CardBus 0000:16

Hi,

Does /proc/iomem show the same thing (i.e., zeros)?

How about if you do the test while logged in as root?


-- 
~Randy