[flashrom] flashrom: Can't mmap memory

[Pádraig Brady]

On 30/09/10 00:50, Carl-Daniel Hailfinger wrote:
> On 28.09.2010 15:43, Pádraig Brady wrote:
>> On 28/09/10 13:54, Pádraig Brady wrote:
>>   
>>> This issue looks similar to this:
>>> http://www.coreboot.org/pipermail/coreboot/2009-February/044672.html
>>>
>>> Any ideas?
>>>     
>>
>> Ah, when trying the same binary on an official fedora 13 live usb key it works.
>> So it's something specific to my system. Feel free to ignore this unless
>> you know off the top of your head what the issue might be on my read-only
>> root, custom F12 distro.
>>
>> The differences are summarised below:
>>
>> Broken...
>>
>> flashrom v0.9.2-r1182 on Linux 2.6.32.10-90.fc12.i686 (i686)
>> Probing for Winbond W25x80, 1024 KB: Error accessing flash chip,
>> 0x100000 bytes at 0xfff00000
>> /dev/mem mmap failed: Value too large for defined data type
>>
>> Working...
>>
>> flashrom v0.9.2-r1182 on Linux 2.6.33.3-85.fc13.i686 (i686)
>> Probing for Winbond W25x80, 1024 KB: probe_spi_rdid_generic: id1 0xef, id2 0x3014
>> Chip status register is 00
>> Found chip "Winbond W25x80" (1024 KB, SPI) at physical address 0xfff00000.
>>   
> 
> Mh. Could you please compare the following for both kernels?
> CONFIG_X86_PAT
> CONFIG_STRICT_DEVMEM

I had noticed the associated error message in the source,
which was not output as EOVERFLOW is returned rather than EINVAL,
and so had already confirmed that both systems had:

# grep -E "CONFIG_(X86_PAT|STRICT_DEVMEM)" /boot/config*
CONFIG_X86_PAT=y
CONFIG_STRICT_DEVMEM=y

> /proc/iomem
> The first 100 lines of dmesg

I've not access to the working system at the moment,
and realise that the comparison might highlight the issue,
but just in case, I've attached the above for the broken system.
I'll post a diff from the working system later.

> I believe there should be a clue somewhere.
> 
> Finally, I'd love to see if flashrom r1180 works on the broken machine.
> (Explanation: r1181 changed physical memory handling, and I want to be
> totally sure that this is not the reason you're seeing errors).

I had tried to bisect, but r709 behaves the same way at least.

cheers,
Pádraig.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: broken.dmesg
URL: <http://www.flashrom.org/pipermail/flashrom/attachments/20100930/579fa1c7/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: broken.iomem
URL: <http://www.flashrom.org/pipermail/flashrom/attachments/20100930/579fa1c7/attachment-0001.ksh>