On Wed, 2007-04-18 at 09:08 +0200, Stefan Reinauer wrote:
Can you try whether this patch helps?
Got the patch, will apply it after i break.
I have noticed modprobing l440gx will provoke this problem on this single cpu generic 440bx board. I don't think this hang occurs with my tyan 1832DL dual cpu board.
Also, the generic single cpu 440bx board, flashrom doesn't detect any flash chips. So I've loaded up uniflash and it tells me the flash chip is at the standard 0xfffc0000 -> (DA256C2D)
It's a STMicroelectronics M29F002(B)(T)/5V
XMSPos XMSLeft and sector map can also be provided, but I think what we want is just the memory location of the flash bios chip (0xfffc0000)?
I'm taking a quick break and will be back in 30 minutes and will apply the patch.
-- Roger http://www.eskimo.com/~roger/index.html Key fingerprint = 8977 A252 2623 F567 70CD 1261 640F C963 1005 1D61
Wed Apr 18 00:58:26 PDT 2007
* roger roger@eskimo.com [070418 10:05]:
On Wed, 2007-04-18 at 09:08 +0200, Stefan Reinauer wrote: I have noticed modprobing l440gx will provoke this problem on this single cpu generic 440bx board. I don't think this hang occurs with my tyan 1832DL dual cpu board.
Try without loading the module. The hang occurs in timer setup, which is long before any flash access is happening (and on the first thought a connection between that sounds very unlikely).
Also, when it still hangs, try waiting a longer time (up to 10min or so for a try). Maybe there's something weird going on with the system time. What kernel is this? What glibc?
Also, the generic single cpu 440bx board, flashrom doesn't detect any flash chips. So I've loaded up uniflash and it tells me the flash chip is at the standard 0xfffc0000 -> (DA256C2D)
The flash probing is really stupid -- it does not mention whether there is an unidentified chip or no chip at all.
XMSPos XMSLeft and sector map can also be provided, but I think what we want is just the memory location of the flash bios chip (0xfffc0000)?
And we want to switch it into a mode where it responds to memory writes to it's bus. That is the most tricky part. If the flash ID is known, the size and address is known as well.
The address of the system flash is always 4G-size on x86 based machines.
Stefan