> Anyway, I really don't care either way, but this seems like something > that the drivers should be doing. What suddenly changed that caused > this problem to occur that hasn't happened in the years prior to now > that drives this to be a stable-kernel issue? When this first went in I pointed out it was an utterly stupid idea. Since it went in lots of machines haven't rebooted properly or powered off right. There are two problems 1. Clearing the busmaster bit is not well defined behaviour. It even freezes some hardware. 2. Lots of PC class hardware has firmware which believes that it can access the hardware as it goes to reboot or poweroff and that someone won't have shut it down. Like it or not the firmware expected behaviour for such things is "what Windows did". The expected PC behaviour is subtle and magic - eg the fact D3 on some IDE disk controllers is terminal until power cycled because Windows didn't do that or that the BIOS goes off and chats to the disks in reboot without assuming the disk controller is completely uninitialized. kexec is a special cornercase and handling is as such (knowing it will bother to re-init appropriate devices) is very different to the current broken behaviour for PC systems. Alan
