http://bugzilla.kernel.org/show_bug.cgi?id=12748
--- Comment #24 from Henrique de Moraes Holschuh <h...@hmh.eng.br> 2009-06-22 03:15:31 --- No, it is not related. There are many defective PCI devices which cause severe problems when they are placed in D3 (the most common is that they cannot be resurrected back to D0 until the system power cycles). There are also devices which the kernel doesn't know how to initialize, so it can't place them on D3, because it doesn't know how to resurrect them later (some GPUs, for example). These devices sometimes are already in D0, but I can't say if they are always already in D0. But many devices that work well can be set to D0 by the BIOS, so this wouldn't help at all, anyway. Due to the D3 problem of some devices, PCI will *NOT* place any devices in D3 right now (which is bad). I hope they will fix it soon, so that only broken or problematic devices will not be put in D3. To me, it looks like splitting "put device in D3" from "unlink power resources" is the only way to fix this. Maybe use an API for the disable device call, that lets one to say "DEVICE_REMAIN_IN_D0", so that PCI can always call it? Either that, or you must change the way power resources keep track of devices, so that they can notice when a device has gone away. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
