linux-kernel - Re: Memory at xxxxxx [disabled]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 10 Oct 2011 07:42:59 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Manu Abraham <abraham.manu@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-pci <linux-pci@...r.kernel.org>
Subject: Re: Memory at xxxxxx [disabled]

On Sat, Oct 8, 2011 at 12:14 PM, Manu Abraham <abraham.manu@...il.com> wrote:
> On 10/8/11, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
>> On Sat, Oct 8, 2011 at 9:51 AM, Manu Abraham <abraham.manu@...il.com> wrote:
>>> Hi,
>>>
>>> Any Idea why I am seeing the [disabled] for the specified memory
>>> region as described below ?
>>>
>>> 04:07.0 Multimedia controller [0480]: Twinhan Technology Co. Ltd
>>> Device [1822:4e31] (rev 01)
>>>        Subsystem: Twinhan Technology Co. Ltd Device [1822:0010]
>>>        Flags: medium devsel, IRQ 11
>>>        Memory at fd900000 (32-bit, prefetchable) [disabled] [size=4K]
>>
>> The complete dmesg log should have some clues.  Normally we use the
>> resources assignments done by BIOS.
>
>
> While waiting for a reply, I did a few reboots down the lane, no
> changes made by me, except that I plugged the card into the next PCI
> slot ..
>
> I am abit more perplexed now .. The device doesn't show "disabled" but
> shows a different device ID which is the correct one, as you can see,
> compared to earlier ..

The device ID issue is beyond my knowledge.  My guess is that your
device is flaky.

I might be able to help with the resource problem if you collect the
entire dmesg log.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/