On Fri, 2006-03-10 at 00:26 -0500, Sanjoy Mahajan wrote: > [Re: bugme #5989, head no longer hanging in shame] > > From: "Yu, Luming" <luming.yu@xxxxxxxxx> > > I suggest you to retest, and post dmesg with UN-modified BIOS. > > I'm now running/testing an unmodified DSDT with 2.6.16-rc5. For a while > I had no S3 hangs, but I just noticed them again. The error is the same > as with the modified DSDT (with slightly different offsets): > > exregion-0185 [36] ex_system_memory_space: system_memory 0 (32 width) Address=0000000023FDFFC0 > exregion-0185 [36] ex_system_memory_space: system_memory 1 (32 width) Address=0000000023FDFFC0 > exregion-0290 [36] ex_system_io_space_han: system_iO 1 (8 width) Address=00000000000000B2 > > repeated endlessly. This sounds like the problem Daniel had on his Samsung P35 recently. He could fix it by getting rid of some asus_unhide_smbus stuff or the otherway around, adding asus_unhide_smbus quirks in the S3 resume code. This thread was recently posted on lkml: Re: [patch] smbus unhiding kills thermal management Here are some more details, for me that sounds related...: https://bugzilla.novell.com/show_bug.cgi?id=173420 Thomas - : 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