On Mon, 9 Apr 2018 12:48:13 -0400, Jason Andryuk wrote: > I made some progress by zeroing out ioport values. I booted up with > Host Notify active and then removed i2c-i801.ko > > isadump looked like: > efa0: 40 00 08 75 a7 00 00 00 00 44 00 00 1c 00 07 07 > efb0: 00 01 00 00 58 00 00 00 00 00 00 00 00 00 00 00 > > Then I used `isaset` to zero out fields to: > efa0: 40 00 00 00 00 00 00 00 00 44 00 00 1c 00 07 07 > efb0: 00 00 00 00 58 00 00 00 00 00 00 00 00 00 00 00 > > Power off. Bug not observed - no hang on subsequent boot! > > Note, 0xefb4 would not let me write 0. Something about data mismatch > and 0x58 was read back. Not too surprising. 0xefb4 contains the I2C address of the device which triggered the Host Notify. While the datasheet says it is RW, in practice you are only supposed to read from it. Writing makes no sense. Probably an error in the datasheet and the register is actually RO. Most likely the key is to zero out 0xefb1. The driver is supposed to do so, but for some reason it doesn't work for you. I'll check how my own systems behave in this respect when I have a moment. -- Jean Delvare SUSE L3 Support
