Oddly enough, this triggered my memory:
Didn't you (or someone else) observe something odd about my 537EP(G)
when I sent in an LSPCI -VVV to the list a while back? I have a vague
memory about someone mentioning that it was missing a memory range or
something like that from the normal 537... Could that be the cause? (Or
have I done so much modem work that I'm slowly going crazy and imagined
that?) For what it's worth, I've attached the LSPCI again below.
05:02.0 Modem [0703]: Intel Corporation FA82537EP 56K V.92 Data/Fax
Modem PCI [8086:1080] (rev 04) (prog-if 00 [Generic])
Subsystem: Dell Device [1028:1000]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping+ SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (250ns min, 15500ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 18
Region 0: Memory at fe7ff000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at e800 [size=256]
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: serial
Bjorn.
On 03/09/2010 02:49 PM, Philippe Vouters wrote:
>
> Chris,
>
> Your last trace gives more information. The problem occurs in si3052Init
> when it calls read8 which fails with a NULL pointer dereference. This is
> what is trapped by the kernel.
>
> The sequence is:
> <si3052>:
> ...
> 2b90: 89 34 24 mov %esi,(%esp)
> 2b93: c7 44 24 04 06 00 00 movl $0x6,0x4(%esp)
> 2b9a: 00
> 2b9b: e8 b0 1a 00 00 call 4650 <read8>
> 2ba0: 84 c0 test %al,%al
>
> ...
> <read8>:
> 4650: 55 push %ebp
> 4651: 89 e5 mov %esp,%ebp
> 4653: 8b 55 0c mov 0xc(%ebp),%edx
> 4656: 31 c0 xor %eax,%eax
> 4658: 83 fa 64 cmp $0x64,%edx
> 465b: 77 10 ja 466d <read8+0x1d>
> 465d: 8b 45 08 mov 0x8(%ebp),%eax
> 4660: 8b 40 0c mov 0xc(%eax),%eax
> 4663: 8b 80 8c 00 00 00 mov 0x8c(%eax),%eax
> 4669: 0f b6 04 02 movzbl (%edx,%eax,1),%eax
> 466d: 5d pop %ebp
> 466e: c3 ret
> 466f: 90 nop
>
> 00004670 <read32>:
>
> The Linux kernel bug report says problem is on read8+0x19/0x20, so this
> is this machine instruction movzbl (%edx,%eax,1),%eax, especially this
> (%edx,%eax,1) part of the instruction which is NULL in your case with
> your board. The read8 with the movzbl (%edx,%eax,1) implies the code is
> attempting to fetch a byte content from an address.
>
> Tours truly,
Attachment:
signature.asc
Description: OpenPGP digital signature
