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.
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.32.10-90.lincor_3.fc12.i686 ([email protected]) (gcc 
version 4.4.4 20100630 (Red Hat 4.4.4-10) (GCC) ) #1 SMP Fri Aug 13 11:59:33 
IST 2010
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  NSC Geode by NSC
  Cyrix CyrixInstead
  Centaur CentaurHauls
  Transmeta GenuineTMx86
  Transmeta TransmetaCPU
  UMC UMC UMC UMC
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
 BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001f6e0000 (usable)
 BIOS-e820: 000000001f6e0000 - 000000001f6e3000 (ACPI NVS)
 BIOS-e820: 000000001f6e3000 - 000000001f6f0000 (ACPI data)
 BIOS-e820: 000000001f6f0000 - 000000001f700000 (reserved)
 BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
DMI 2.4 present.
Phoenix BIOS detected: BIOS may corrupt low RAM, working around it.
e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
last_pfn = 0x1f6e0 max_arch_pfn = 0x100000
MTRR default type: uncachable
MTRR fixed ranges enabled:
  00000-9FFFF write-back
  A0000-BFFFF uncachable
  C0000-CDFFF write-protect
  CE000-EFFFF uncachable
  F0000-FFFFF write-through
MTRR variable ranges enabled:
  0 base 000000000 mask 0E0000000 write-back
  1 base 01F800000 mask 0FF800000 uncachable
  2 base 01F700000 mask 0FFF00000 uncachable
  3 disabled
  4 disabled
  5 disabled
  6 disabled
  7 disabled
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
original variable MTRRs
reg 0, base: 0GB, range: 512MB, type WB
reg 1, base: 504MB, range: 8MB, type UC
reg 2, base: 503MB, range: 1MB, type UC
total RAM covered: 503M
Found optimal setting for mtrr clean up
 gran_size: 64K         chunk_size: 16M         num_reg: 3      lose cover RAM: 
0G
New variable MTRRs
reg 0, base: 0GB, range: 512MB, type WB
reg 1, base: 503MB, range: 1MB, type UC
reg 2, base: 504MB, range: 8MB, type UC
initial memory mapped : 0 - 01000000
init_memory_mapping: 0000000000000000-000000001f6e0000
Using x86 segment limits to approximate NX protection
 0000000000 - 0000400000 page 4k
 0000400000 - 001f400000 page 2M
 001f400000 - 001f6e0000 page 4k
kernel direct mapping tables up to 1f6e0000 @ 10000-16000
RAMDISK: 1e6b6000 - 1f6bf3e3
ACPI: RSDP 000f7b50 00014 (v00 IntelR)
ACPI: RSDT 1f6e3000 0003C (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
ACPI: FACP 1f6e3080 00074 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
ACPI: DSDT 1f6e3100 04C76 (v01 INTELR AWRDACPI 00001000 MSFT 03000000)
ACPI: FACS 1f6e0000 00040
ACPI: _HPT 1f6e7e00 00038 (v01 IntelR AWRDACPI 42302E31 AWRD 00000098)
ACPI: _WDT 1f6e7e40 00047 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
ACPI: MCFG 1f6e7ec0 0003C (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
ACPI: APIC 1f6e7d80 00068 (v01 IntelR AWRDACPI 42302E31 AWRD 00000000)
ACPI: SSDT 1f6e8560 00482 (v01  PmRef    CpuPm 00003000 INTL 20050228)
ACPI: Local APIC address 0xfee00000
0MB HIGHMEM available.
502MB LOWMEM available.
  mapped low ram: 0 - 1f6e0000
  low ram: 0 - 1f6e0000
  node 0 low ram: 00000000 - 1f6e0000
  node 0 bootmap 00013000 - 00016edc
(9 early reservations) ==> bootmem [0000000000 - 001f6e0000]
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
  #1 [0000001000 - 0000002000]    EX TRAMPOLINE ==> [0000001000 - 0000002000]
  #2 [0000006000 - 0000007000]       TRAMPOLINE ==> [0000006000 - 0000007000]
  #3 [0000400000 - 0000b318d8]    TEXT DATA BSS ==> [0000400000 - 0000b318d8]
  #4 [001e6b6000 - 001f6bf3e3]          RAMDISK ==> [001e6b6000 - 001f6bf3e3]
  #5 [000009dc00 - 0000100000]    BIOS reserved ==> [000009dc00 - 0000100000]
  #6 [0000b32000 - 0000b3606a]              BRK ==> [0000b32000 - 0000b3606a]
  #7 [0000010000 - 0000013000]          PGTABLE ==> [0000010000 - 0000013000]
  #8 [0000013000 - 0000017000]          BOOTMAP ==> [0000013000 - 0000017000]
found SMP MP-table at [c00f3860] f3860
Zone PFN ranges:
  DMA      0x00000010 -> 0x00001000
  Normal   0x00001000 -> 0x0001f6e0
  HighMem  0x0001f6e0 -> 0x0001f6e0
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x0001f6e0
On node 0 totalpages: 128623
free_area_init_node: node 0, pgdat c09b9260, node_mem_map c1001200
00000000-0000ffff : reserved
00010000-0009efff : System RAM
0009f000-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000d0000-000d0fff : Adapter ROM
000e0000-000effff : pnp 00:0d
000f0000-000fffff : reserved
  000f0000-000fffff : System ROM
00100000-1f6dffff : System RAM
  00400000-0079856f : Kernel code
  00798570-009d970f : Kernel data
  00a6a000-00b318d7 : Kernel bss
1f6e0000-1f6e2fff : ACPI Non-volatile Storage
1f6e3000-1f6effff : ACPI Tables
1f6f0000-1f6fffff : reserved
1f700000-1fffffff : RAM buffer
d0000000-dfffffff : 0000:00:02.0
e0000000-efffffff : PCI MMCONFIG 0 [00-ff]
  e0000000-efffffff : reserved
    e0000000-efffffff : pnp 00:0c
fd800000-fd8fffff : PCI Bus 0000:01
fd900000-fd9fffff : PCI Bus 0000:03
fda00000-fdafffff : PCI Bus 0000:03
fdb00000-fdbfffff : PCI Bus 0000:01
fdc00000-fdcfffff : PCI Bus 0000:02
  fdc00000-fdc1ffff : 0000:02:00.0
  fdcf0000-fdcfffff : 0000:02:00.0
    fdcf0000-fdcfffff : r8169
fdd00000-fddfffff : PCI Bus 0000:02
  fddff000-fddfffff : 0000:02:00.0
    fddff000-fddfffff : r8169
fde80000-fdefffff : 0000:00:02.0
fdf00000-fdf7ffff : 0000:00:02.1
fdf80000-fdfbffff : 0000:00:02.0
fdff8000-fdffbfff : 0000:00:1b.0
  fdff8000-fdffbfff : ICH HD audio
fdffe000-fdffe3ff : 0000:00:1f.2
fdfff000-fdfff3ff : 0000:00:1d.7
  fdfff000-fdfff3ff : ehci_hcd
fec00000-ffffffff : reserved
  fec00000-fec00fff : IOAPIC 0
  fed00000-fed000ff : pnp 00:0d
  fed13000-fed1dfff : pnp 00:0d
  fed20000-fed8ffff : pnp 00:0d
  fee00000-fee00fff : Local APIC
    fee00000-fee00fff : pnp 00:0d
  ffb00000-ffb7ffff : pnp 00:0d
  fff00000-ffffffff : pnp 00:0d
_______________________________________________
flashrom mailing list
[email protected]
http://www.flashrom.org/mailman/listinfo/flashrom

Reply via email to