On 21.03.2013 09:04, Konstantin Belousov wrote: > On Wed, Mar 20, 2013 at 06:36:10PM -0700, David Wolfskill wrote: >> 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). > > This gives me an idea. The only so to say 'vm' change in r248508 was an > addition of the bio_transient_map submap. The vfs.unmapped_buf_allowed > tunable did not eliminated the submap creation. Please try r248569 > with vfs.unmapped_buf_allowed set to 0. > > If this combination allows the nvidia driver to start, please revert > the setting of vfs.unmapped_buf_allowed, and instead set > kern.bio_transient_maxcnt e.g. to 256 or even 128. > > Also, on the machine without the tunables customization, please show > the output of sysctl kern.nbuf, kern.bio_transient_maxcnt. Also show > the output of pciconf -lvb.
To be able to have kernel core dumps while X.Org is running, I need to set the "debug.debugger_on_panic=0" sysctl. Otherwise, the computer only reboots (it doesn't honor the ddb script). Maybe it can help here? -- Jean-Sébastien Pédron
signature.asc
Description: OpenPGP digital signature
