Ron,
I really have no idea what's happening on his board. It seems
that his DRAM is working properly. The only possiblity is his linuxbios
does not handle 0xf0000 shadow properly. Did he change any thing in
730/southbridge.c or mtrr.c ??
Ollie
> This is a tough one.
>
> ron
>
> ---------- Forwarded message ----------
> Date: Mon, 25 Feb 2002 01:08:04 +0800
> From: Andrew Ip <[EMAIL PROTECTED]>
> To: Ronald G Minnich <[EMAIL PROTECTED]>
> Subject: Re: K7SEM FIXED
>
> Hi Ron,
>
> Looks like I have found out why does it happened. The following is the
> email which I just send to Ollie. It descripts why my LAN interface gets IRQ
> 0. I didn't send to the list, since no one seems to be getting this kind of
> problem. BTW, sorry for my privous senseless bug report. Thanks.
>
> -Andrew
>
> Here is the message
> ===================
> For the last several days, I have been debugging the problem where the
> m810lmr LAN interface somtimes gets IRQ 0. Finally I have found out that the
> irq table is not copied correctly. Looks like my system has problem to write
> into the memory when it is started from cold(leave the system for several
> minutes). The following is part of my log file which also contains some of my
> debugging message.
>
> Before copy_pirq_routing_table
> rom_table_start = 0xf0000
> rom_table_end = 0xf0000
> Copying IRQ routing tables...
> addr = 000f0000
> intel_irq_routing_table = 00009b40
> size = 0x60
> before addr 0x000f0000
> clearing 0x000f0000 size = 96
> hex
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> done.
> dump intel_irq_routing_table 0x00009b40
> hex
> 24 50 49 52 00 01 60 00 00 08 00 00 39 10 08 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14
> 00 08 41 b8 dc 42 b8 dc 43 b8 dc 44 b8 dc 00 00
> 00 10 41 b8 dc 42 b8 dc 43 b8 dc 44 b8 dc 00 00
> 00 48 41 b8 dc 42 b8 dc 43 b8 dc 44 b8 dc 01 00
> 00 58 43 b8 dc 44 b8 dc 41 b8 dc 42 b8 dc 02 00
> dump addr 0x000f0000
> hex
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> After copy_pirq_routing_table
> rom_table_start = 0xf0000
> rom_table_end = 0xf0060
>
> In source code, I added code to clear the memory f0000 to zero before copying
> the irq routing table. However, the log shows that the memory still contains
> ff's instead of 0's after copy. And it also shows copy_pirq_routing_table
> couldn't copy the irq routing table neither. Since irq routing table cannot be
> copied, LAN can't irq. Looks like this problem only occurs when it is started
> from cold. If the system is up for a while, this problem doesn't not occur.
> The following log shows everything works fine when the system is up for a while.
> Before copy_pirq_routing_table
> rom_table_start = 0xf0000
> rom_table_end = 0xf0000
> Copying IRQ routing tables...
> addr = 000f0000
> intel_irq_routing_table = 00009b40
> size = 0x60
> before addr 0x000f0000
> clearing 0x000f0000 size = 96
> hex
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> done.
> dump intel_irq_routing_table 0x00009b40
> hex
> 24 50 49 52 00 01 60 00 00 08 00 00 39 10 08 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14
> 00 08 41 b8 dc 42 b8 dc 43 b8 dc 44 b8 dc 00 00
> 00 10 41 b8 dc 42 b8 dc 43 b8 dc 44 b8 dc 00 00
> 00 48 41 b8 dc 42 b8 dc 43 b8 dc 44 b8 dc 01 00
> 00 58 43 b8 dc 44 b8 dc 41 b8 dc 42 b8 dc 02 00
> dump addr 0x000f0000
> hex
> 24 50 49 52 00 01 60 00 00 08 00 00 39 10 08 00
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 14
> 00 08 41 b8 dc 42 b8 dc 43 b8 dc 44 b8 dc 00 00
> 00 10 41 b8 dc 42 b8 dc 43 b8 dc 44 b8 dc 00 00
> 00 48 41 b8 dc 42 b8 dc 43 b8 dc 44 b8 dc 01 00
> 00 58 43 b8 dc 44 b8 dc 41 b8 dc 42 b8 dc 02 00
> After copy_pirq_routing_table
> rom_table_start = 0xf0000
> rom_table_end = 0xf0060
>
> Is there any reason why does it happen? Ollie, I really want to solve this
> problem. Would you give some suggestions of how to fix this strange problem?
> Ihave ask this on the list, but looks like no one has this problem. However, it
> happens on my K7SEM and M810LMR boards. Thank you very much.
>
> =====================================
>
> On Tue, Feb 05, 2002 at 09:14:55AM -0700, Ronald G Minnich wrote:
>
>>oh no!
>>
>>you mean if you have no keyboard connected the IRQ for eth0 is 0?
>>
>>SHIT!
>>
>>I'll try to figure this one out.
>>
>>I really hate these cheap mainboards.
>>
>>ron
>>
>>
>
>
