On Thu, 21 Mar 2013 20:31:06 +0200
Konstantin Belousov wrote:
> On Thu, Mar 21, 2013 at 07:14:26PM +0100, Gary Jennejohn wrote:
> > I wonder whether there isn't some dependency on the graphics chip being
> > used.
> >
> > I'm running r248589 AMD64 and didn't have to touch a thing to get X
> > to
iI am @248554 on an AMD64 box with 8 gig of memory, and a 64 bit kernel.
The video is on the motherboard and is a Radeon chipset. I also
experienced the panic while starting XDM.
I found Shawn's suggested remedy of etting both vfs.unmapped_buf_allowed=0
and kern.bio_transient_maxcnt=512 in /boot/
On Thu, Mar 21, 2013 at 03:58:35PM +0200, Konstantin Belousov wrote:
> ...
> > Script started on Thu Mar 21 06:07:41 2013
> > g1-235(10.0-C)[1] uname -a
> > FreeBSD g1-235.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #845
> > r248575M/248575: Thu Mar 21 05:35:06 PDT 2013
> > r...@g1-235.
On Thu, Mar 21, 2013 at 07:14:26PM +0100, Gary Jennejohn wrote:
> I wonder whether there isn't some dependency on the graphics chip being
> used.
>
> I'm running r248589 AMD64 and didn't have to touch a thing to get X
> to start.
>
> But I'm using an older, presumably less demanding graphics chip
On Thu, Mar 21, 2013 at 12:12:07PM -0400, Shawn Webb wrote:
> Looks like setting both vfs.unmapped_buf_allowed=0 and
> kern.bio_transient_maxcnt=512 worked for me. I'm now up and running
> smoothly.
The vfs.unmapped_buf_allowed=0 setting turns off the unmapped support,
and kern.bio_transient_maxcn
On Thu, 21 Mar 2013 12:12:07 -0400
Shawn Webb wrote:
[snip lots of stuff]
> > I appear to be experiencing the same issue. I've been following this
> > thread. I have a coredump, but it's over 700mb in size. What would be the
> > best way to get that to you guys? The revision I'm at is r248583 on
On Thu, Mar 21, 2013 at 12:04 PM, Shawn Webb wrote:
> On Thu, Mar 21, 2013 at 9:58 AM, Konstantin Belousov
> wrote:
>
>> On Thu, Mar 21, 2013 at 06:34:46AM -0700, David Wolfskill wrote:
>> > On Thu, Mar 21, 2013 at 10:04:41AM +0200, Konstantin Belousov wrote:
>> > > ...
>> > > This gives me an i
On Thu, Mar 21, 2013 at 9:58 AM, Konstantin Belousov wrote:
> On Thu, Mar 21, 2013 at 06:34:46AM -0700, David Wolfskill wrote:
> > On Thu, Mar 21, 2013 at 10:04:41AM +0200, Konstantin Belousov wrote:
> > > ...
> > > This gives me an idea. The only so to say 'vm' change in r248508 was an
> > > addi
On Thu, Mar 21, 2013 at 06:34:46AM -0700, David Wolfskill wrote:
> On Thu, Mar 21, 2013 at 10:04:41AM +0200, Konstantin Belousov wrote:
> > ...
> > 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
> >
On Thu, Mar 21, 2013 at 10:04:41AM +0200, Konstantin Belousov wrote:
> ...
> 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 v
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 st
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/
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
I would advise that you try the following:
(1) On a machine which is not your laptop, build a CURRENT chroot
(2) Follow the instructions at:
http://www.freebsd.org/doc/handbook/network-pxe-nfs.html
to NFS export the chroot and set up a TFTP server.
(3) Set up your laptop to PXE boot using
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.
OK; thank you for checking & reporting.
> I must admit that I have
On Wed, Mar 20, 2013 at 11:02:39AM -0700, David Wolfskill wrote:
> On Wed, Mar 20, 2013 at 07:44:58PM +0200, Konstantin Belousov wrote:
> > ...
> > Ok. The best idea I have right now is to rebuild the nvidia.ko.
>
> OK; I did this: After rebooting (without attempting to either load
> nvidia.ko or
On Wed, Mar 20, 2013 at 07:44:58PM +0200, Konstantin Belousov wrote:
> ...
> Ok. The best idea I have right now is to rebuild the nvidia.ko.
OK; I did this: After rebooting (without attempting to either load
nvidia.ko or start X in any way), I issued:
sudo portmaster x11/nvidia-driver
wh
On Wed, Mar 20, 2013 at 07:44:58PM +0200, Konstantin Belousov wrote:
> ...
> > I then started xdm, and (as before), got an unclean reboot. (So: no
> > difference in behavior as far as I can tell.)
>
> Ok. The best idea I have right now is to rebuild the nvidia.ko.
Again? OK
> Do you have a
On Wed, Mar 20, 2013 at 07:24:30PM +0200, Andriy Gapon wrote:
> on 20/03/2013 19:18 David Wolfskill said the following:
> > Yes; src.conf includes the line:
> >
> > PORTS_MODULES=x11/nvidia-driver
>
> Have you double-checked that this actually works according to your intention?
> ...
Until I sta
On Wed, Mar 20, 2013 at 10:37:59AM -0700, David Wolfskill wrote:
> On Wed, Mar 20, 2013 at 07:13:41PM +0200, Konstantin Belousov wrote:
> > ...
> > Did you rebuild the nvidia driver after the update ?
> > Do you have a core dump partition configured ?
>
> (I note that I have, in the past, captured
On Wed, Mar 20, 2013 at 07:13:41PM +0200, Konstantin Belousov wrote:
> ...
> Did you rebuild the nvidia driver after the update ?
> Do you have a core dump partition configured ?
(I note that I have, in the past, captured crash dumps from head running
on this machine with this configuration.)
> T
on 20/03/2013 19:18 David Wolfskill said the following:
> Yes; src.conf includes the line:
>
> PORTS_MODULES=x11/nvidia-driver
Have you double-checked that this actually works according to your intention?
--
Andriy Gapon
___
freebsd-current@freebsd.or
On Wed, Mar 20, 2013 at 07:13:41PM +0200, Konstantin Belousov wrote:
> ...
> > I'm open to suggestions, and willing to hack and test (and report,
> > of course).
>
> Did you rebuild the nvidia driver after the update ?
Yes; src.conf includes the line:
PORTS_MODULES=x11/nvidia-driver
> Do you ha
On Wed, Mar 20, 2013 at 09:00:56AM -0700, David Wolfskill wrote:
> Yesterday, I built head & ran it without incident (as has been the
> daily norm for some time now):
>
> FreeBSD g1-235.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #843
> r248493M/248493: Tue Mar 19 05:57:09 PDT 2013
> r
I've been having random panics since the VM changes. I'm stuck
running r247527. If I try to install a newer kernel/world, I get random
panics (I really should enable crashdumps). Not a big deal, but I'm mostly
interested in epair fixes and bhyve enhancements.
On Wed, Mar 20, 2013 at 12:00 PM, Dav
Yesterday, I built head & ran it without incident (as has been the
daily norm for some time now):
FreeBSD g1-235.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #843
r248493M/248493: Tue Mar 19 05:57:09 PDT 2013
r...@g1-235.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386
Today, after upd
26 matches
Mail list logo
