> Ok, that is how I understood it the first time. > > My question still stands: when it happened every time, did it happen > right away? >
Yes, it happened at once. Right after I booted Win7 and then booted into Linux again. It happened also, when I booted Win 7, shut down the computer, powered off (power supply and power cell), and then started Linux. Did I describe it now better? > If it did, and assuming you rebooted out of Windows 7 to try it, > there is no need to test 3.5.y any more. We already know it doesn't > reproduce the bug under the same circumstances as 3.2.y did. > So you know the reasons. That is really good news! I read about, that 3.5 changed several things in bus strategies. > Hoping that clarifies, > Jonathan Thank you very much! Hans -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201209111640.58551.hans.ullr...@loop.de
