Re: i810 audio patch

Nathan Bryant
2001-12-04T05:19:08Z

Nathan Bryant wrote

> - I haven't seen those oopses again either; they may have been caused
> by i810_configure_clocking being called twice during the
> initialization due to a merging goof on my part...

Ok, I spoke too soon. That piece of code couldn't cause the problem,
because of the surrounding if (clocking==...

So there may be some VM/buffer related problem lurking under the covers
still. Originally the oops popped up in kswapd, for me, but I can't
trigger it again.