Torsten Kaiser wrote: > On 10/13/07, Torsten Kaiser wrote: >> Wait! >> >> I think I found the bug: Its a evil interaction between the above >> patch and the swncq patch that is applied later. >> The qc_defer patch removes the old ata_scmd_need_defer that was always >> called for all drivers and substitutes it for ata_std_qc_defer and >> adds it as aops->qc_defer to all drivers that support NCQ *at that >> point*. >> Then the swncq patch adds a new NCQ capable driver, but the nobody >> added the qc_defer-ops to the ops-structure that is added. So swncq >> will never defer any commands and the first command that would need to >> be defered (the SMART commands) blows up, if there is still another >> command in flight. >> >> I will only add the qc_defer and try this... > > 3 boots, all worked. So I'm very sure that was the bug, but I will now > do a little load testing... > > The only strange thing about 2.6.23-mm1 is, that it takes ~4 second > more to boot. So, you basically applied the attached patch? Yeah, absence of qc_defer for an NCQ-capable chip would do it. Jeff