Hi,
are you running which version of CURRENT?
E.g. Some snapshot or did you compile from source?
-Tommi
On Sun, 22 Apr 2018 at 13.47, Mariusz Zaborski wrote:
> Hello,
>
> I upgraded my FreeBSD to CURRENT and nvidia-drvier-390.48. But it's
> stop working.
> I tried also
Hello,
I upgraded my FreeBSD to CURRENT and nvidia-drvier-390.48. But it's
stop working.
I tried also nvidia-driver-390.25 without luck as well.
I have loaded nvidia-modeset.ko .
While I'm rebooting my machine its also core dumping:
https://people.freebsd.org/~oshogbo/nvidia-mail.png .
I'm
On Sat, Apr 21, 2018 at 11:30:55PM +, Rick Macklem wrote:
> Konstantin Belousov wrote:
> >On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote:
> >> I decided to start a new thread on current related to SCHED_ULE, since I
> >> see
> >> more than just performance degradation and on a
On Sat, Apr 21, 2018 at 11:49:34PM +0200, Tijl Coosemans wrote:
> On Sat, 21 Apr 2018 21:09:09 + Rick Macklem wrote:
> > With a recent head/current kernel (doesn't happen when running a Dec.
> > 2017 one), when I do a halt, it gets as far as:
> >
> > vnodes remaining...
Hi,
Normally I build my CURRENT by myself from Xorg - r332861.
But I also tried latest SNAPSHOT.
Thanks,
Mariusz
On 22 April 2018 at 14:24, Tommi Pernila wrote:
> Hi,
>
> are you running which version of CURRENT?
> E.g. Some snapshot or did you compile from source?
>
>
On Sunday, 22 April 2018 at 12:42:37 +0200, Mariusz Zaborski wrote:
> Hello,
>
> I upgraded my FreeBSD to CURRENT and nvidia-drvier-390.48. But it's
> stop working.
> I tried also nvidia-driver-390.25 without luck as well.
Yes, I've had this trouble as well with -STABLE. It happened some
time in
On Sun, Apr 22, 2018 at 6:40 PM, Greg 'groggy' Lehey
wrote:
> On Sunday, 22 April 2018 at 12:42:37 +0200, Mariusz Zaborski wrote:
>
> > I'm attaching also Xorg log.
>
> This seems to have got lost.
>
> Greg
Please be sure that attachments are typed "text/plain". I believe all
Konstantin Belousov wrote:
>On Sat, Apr 21, 2018 at 11:49:34PM +0200, Tijl Coosemans wrote:
>> On Sat, 21 Apr 2018 21:09:09 + Rick Macklem wrote:
>> > With a recent head/current kernel (doesn't happen when running a Dec.
>> > 2017 one), when I do a halt, it gets as far
On Sun, Apr 22, 2018 at 03:15:00PM +0200, Tijl Coosemans wrote:
> On Sun, 22 Apr 2018 15:05:21 +0300 Konstantin Belousov
> wrote:
> > On Sat, Apr 21, 2018 at 11:49:34PM +0200, Tijl Coosemans wrote:
> >> On Sat, 21 Apr 2018 21:09:09 + Rick Macklem
> Konstantin Belousov wrote:
> >On Sat, Apr 21, 2018 at 11:30:55PM +, Rick Macklem wrote:
> >> Konstantin Belousov wrote:
> >> >On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote:
> >> >> I decided to start a new thread on current related to SCHED_ULE, since
> >> >> I see
> >> >>
On Sun, 22 Apr 2018 15:05:21 +0300 Konstantin Belousov
wrote:
> On Sat, Apr 21, 2018 at 11:49:34PM +0200, Tijl Coosemans wrote:
>> On Sat, 21 Apr 2018 21:09:09 + Rick Macklem
>> wrote:
>>> With a recent head/current kernel (doesn't happen when
Konstantin Belousov wrote:
>On Sat, Apr 21, 2018 at 11:30:55PM +, Rick Macklem wrote:
>> Konstantin Belousov wrote:
>> >On Sat, Apr 21, 2018 at 07:21:58PM +, Rick Macklem wrote:
>> >> I decided to start a new thread on current related to SCHED_ULE, since I
>> >> see
>> >> more than just
On Sun, 22 Apr 2018 16:28:55 +0300 Konstantin Belousov
wrote:
> On Sun, Apr 22, 2018 at 03:15:00PM +0200, Tijl Coosemans wrote:
>> Thanks for the review. There's just one concern I have. With this patch
>> the bufspace_daemon threads appear to shutdown after the buf_daemon
On Sun, Apr 22, 2018 at 04:55:13PM +0200, Tijl Coosemans wrote:
> On Sun, 22 Apr 2018 16:28:55 +0300 Konstantin Belousov
> wrote:
> > On Sun, Apr 22, 2018 at 03:15:00PM +0200, Tijl Coosemans wrote:
> >> Thanks for the review. There's just one concern I have. With this
14 matches
Mail list logo