On Wed, Mar 20, 2013 at 10:08:57PM +0200, Konstantin Belousov wrote: > ... > I looked at the nvidia sources to check that the driver does not use > the interfaces which KBI was changed, and this is indeed the case, as > expected. > > I must admit that I have no idea why buffer cache changes could affect > nvidia driver, and with no input on the panic (I hope that it is panic, > and not a reset) have no idea even to speculate. So firewire cable is > probably the must. > > Note that I split that import of the work into the series of commits. > The split was done to ease the reading of the chunks, and individual > commits were not functionally tested. Still, you might try to do the > bisect. I elected to go ahead and try the bisection; here are my results: r248493M/248493: OK r248550M/248551: resets on X startup with nvidia.ko r248521M/248521: resets on X startup with nvidia.ko r248507M/248507: OK r248508M/248508: resets on X startup with nvidia.ko r248493M/248493 was my last working point (built yesterday morning). r248550M/248551 was what failed for me this morning. r248521M/248521 was a convenient mid-point between the above two. r248507M/248507 was the next natural test-point. r248508M/248508 was a guess on my part -- I would normally have gone to r248514, but since I had previously noted that r248508 touched some things that nvidia-driver uses, I thought that test might be worthwhile. I am, however, mildly concerned that no one else appears to be reporting similar symptoms (though I have it on good authority that someone is about to test). Peace, david -- David H. Wolfskill david_at_catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:35 UTC