On Mon, 2008-10-06 at 15:01 +0200, Marcel Holtmann wrote: > > I have a different interpretation of the original issue, since afaik the > > value it was doing a BUG_ON on is a value that is only passed in by the > > driver and copied by the ucode to the response, hence it shouldn't > > actually crash unless the driver is passing bogus stuff in or, as it > > seems to be the case here, the DMA programming is completely fucked and > > the ucode just goes to write to random memory locations. > > that patch wasn't enough, but neverless we shouldn't crash the whole > kernel based on this. Well, I am undecided on yet; it appears that when the issue happens then the ucode may have written to arbitrary memory locations, if you don't have an iommu catching it then it may have corrupted anything in your kernel, so just crashing may be the only way to reasonably recover... I actually wrote the patch though to make it not crash, so I can hardly claim I didn't think it was a good idea to change that. But I think I've changed my mind based on further debugging of the issue. > In addition they were working on some IOMMU stuff and that explains what > you are seeing. I never got that far at all. My machine just dies on me. Well, yes, without the patch my machine dies when loading iwlagn. > > > However there seems to be some other issues with me > > > running a 64-bit OS and connecting to an N-capable access point. > > > > Strange. My test AP isn't N capable though. > > We had some discussion about the fact the different firmware versions > might be causing this. Don't have my X61 handy at the moment. I don't even know which one I'm using, I think it's some firmware Tomas gave me. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
