Re: More "issues" with -current - i2c problems

[Paul Goyette <paul%whooppee.com@localhost>]

On Sat, 12 Oct 2013, Matthew Orgass wrote:

> On 2013-10-12 paul%whooppee.com@localhost wrote:
>
> > But then I noticed that Soren had also modified the piixpm(4) driver to 
> > attach multiple iic* on SB800 hardware.  Some investigation shows that 
> > accessing iic[123] using i2cscan(8) causes all sorts of problems, and 
> > actually locks up the i2c bus on iic0!
>
>  This could easily be kern/47179 related (iic_acquire_bus return values 
> inconsistent and often ignored), since if some device is trying to write bus 
> 0 and ignores or misinterprets the return value of iic_acquire_bus then it 
> will interfere with whatever bus is selected (there could be something else 
> going on too if it reliably fails immediately).  Fixing this requires 
> changing all iic code, so keeping numbusses = 1 for now is the easiest 
> solution if that works (although I'm not sure why this issue
> doesn't cause more problems even with a single bus).

Indeed, your PR could be the problem, or at least part of it.

Let me know when you've got your patch ready to try!  :)


-------------------------------------------------------------------------
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer |                          | pgoyette at netbsd.org  |
-------------------------------------------------------------------------