Tejun Heo wrote: >> One thing I still need to investigate is why Ubuntu 10.04 was showing >> the problem, but perhaps I never got as far as updating the kernel after >> installing it. (AFAIK as installed it is 2.6.31, whilst the current >> update is 2.6.32-28 which I think should have the patch) > > Most likely. I've just been googling and peeking and it seems there may be another possibility but I'm much less familiar with Ubuntu so I could easily be misinterpreting something. I have an Ubuntu box at work and I just installed the linux-source-2.6.32-28.55 package on it. When I look at sata_via.c I see that there's a different (earlier?) version of the patch there than what is in 2.6.37 (the test is pdev->device == 0x3249 versus one based on board_id) So it's conceivable that I did update my lucid installation at home but that this version of the patch doesn't fix the problem. I'll check exactly what's what tonight. > So, that leaves the problem sil was seeing. Are you > interested in digging that down too? Well I don't mind testing that card with the kernels I've now got, assuming I can borrow the card again. I'm a lot less enthusiastic about compiling more new versions though. Firstly, I've got to finish sorting out my machine - my backup system has stopped working for example and I've still got a bunch of data to migrate/integrate from the old disk. And I need to upgrade SUSE to 11.3 to see if that fixes this problem without introducing any new ones. Secondly, kernel compilation in my limited experience has been a big hassle. Every time I change anything in sata_via.c it seems to want to recompile absolutely everything and that takes over two hours. I thought make was supposed to do minimal recompilation? That plus a bug in the script, the unexpectedly large amount of space required and some finger trouble made it a less than smooth process. Since we don't yet know whether a recent kernel fixes my sil problem and if it does we don't have any idea of a particular patch, that suggests the strategy would be bisection, which probably involves more compiles than I'm up for. But first steps first. I'll see if I can test it with my existing kernels. Cheers, Dave -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
