03.05.2013 22:33, John Baldwin пишет:
On Friday, May 03, 2013 1:53:35 pm Alex Keda wrote:
03.05.2013 20:41, John Baldwin пишет:
On Thursday, May 02, 2013 4:18:45 pm Alex Keda wrote:
see begin in:
http://lists.freebsd.org/pipermail/freebsd-current/2012-
November/038000.html
Hmm, what I see i
Peter Wemm wrote:
> >> > offending revision.
> >>
> >> I've started a binary search. I'll let you know what that turns up.
> >
> > Thanks, and sorry for getting my Ian's mixed up. :-/
> >
> > --
> > John Baldwin
>
> There's been two separate machines, at least twice each on this exact
> panic / t
On Fri, 03 May 2013 22:22:01 -0700, Sean Bruno wrote:
>
>On Fri, 2013-05-03 at 22:03 -0700, Waitman Gobble wrote:
>> what is the output of running the command 'mixer'?
>
>$ mixer
>Mixer vol is currently set to 95:95
>Mixer pcm is currently set to 100:100
>Mixer speaker is currently s
got this panic when network interfaces were being unconfigured during
system shutdown. has anyone seen this? should i file a PR?
thanks
kit
test.yahoo.com dumped core - see /home/crash/vmcore.2
Sat May 4 20:43:55 MYT 2013
FreeBSD test.yahoo.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r250229: Sat
Hi,
I don't think I've posted this yet, but there's now support for these
NICs in -HEAD:
* AR9380
* AR9390
* AR9580
* AR9590
* AR9562
* QCA9565
The AR933x / AR934x SoC wifi is in -HEAD but it's not yet tidied up
enough to actually work on those SoCs. But it's there.
* What have I tested:
* hos
I have panic like your but in sctp_add_addr_to_vrf. I think need PR. My panic
screenshoot http://vvtlan.ru/panic1.jpg and second one
http://vvtlan.ru/panic2.jpg
Суббота, 4 мая 2013, 20:55 +08:00 от kit :
>
got this panic when network interfaces were being unconfigured during
system shutdown
I can't use the SoundBlaster PCI card on the laptop. Also, I need to be
able to switch between the FreeBSD sound drivers and OSS drivers. What do I
need to do to the kernel configuration file to allow this? Some ports will
build with GCC and others with clang. What is the switch/command argument
in
On Fri, 3 May 2013, Rick Macklem wrote:
RM>Ok, if you succeed in isolating the commit, that would be great.
Hmm. I'm somewhat stuck. clang from yesterday can't compile clang from a
month ago...
harti
RM>
RM>rick
RM>
RM>> harti
RM>>
RM>> On Fri, 3 May 2013, Rick Macklem wrote:
RM>>
RM>> RM>Ha
Hartmut Brandt wrote:
> On Fri, 3 May 2013, Rick Macklem wrote:
>
> RM>Ok, if you succeed in isolating the commit, that would be great.
>
> Hmm. I'm somewhat stuck. clang from yesterday can't compile clang from
> a
> month ago...
>
> harti
>
Oh well. You could try this patch (which is the one t
On Sat, May 4, 2013 at 12:28 AM, Waitman Gobble wrote:
> On Fri, 03 May 2013 22:22:01 -0700, Sean Bruno
> wrote:
>
>
> >
> >On Fri, 2013-05-03 at 22:03 -0700, Waitman Gobble wrote:
> >> what is the output of running the command 'mixer'?
> >
> >$ mixer
> >Mixer vol is currently set to 95:95
Hartmut Brandt wrote:
> On Fri, 3 May 2013, Rick Macklem wrote:
>
> RM>Ok, if you succeed in isolating the commit, that would be great.
>
> Hmm. I'm somewhat stuck. clang from yesterday can't compile clang from
> a
> month ago...
>
> harti
>
Oh, and one other thing you can try is switching to t
Install Windows, OSS is not suitable for audio production, except maybe
at a push, OS X.
Super Bisquit wrote:
I can't use the SoundBlaster PCI card on the laptop. Also, I need to be
able to switch between the FreeBSD sound drivers and OSS drivers. What do I
need to do to the kernel configuratio
I really don't think he's going to be install windows on a powerpc machine.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
What is the performance of OSS when it comes to playback, streaming, and
recording?
On Sat, May 4, 2013 at 8:09 PM, Michael Copeland <
mich...@kryptos-security.com> wrote:
> I really don't think he's going to be install windows on a powerpc machine.
>
___
Hello !
This problems appears about 4-6 months ago after updating of -CURRENT host.
Unable to boot host with nvidia_load="YES" in loader.conf because panic.
But when nvidia driver loads manually via kldload, everything OK.
Nvidia driver version is 310.44 at this moment, but problem was an
On 05.05.2013 08:01 (UTC+2), de...@stasyan.com wrote:
> Hello !
>
> This problems appears about 4-6 months ago after updating of -CURRENT
> host.
> Unable to boot host with nvidia_load="YES" in loader.conf because panic.
> But when nvidia driver loads manually via kldload, everything OK.
>
16 matches
Mail list logo