On Sun, 2013-05-05 at 10:01 +0400, 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.
Nvidia
Hi Rick,
the patch doesn't help. So how can I help to fix that? Of course, I can use the
work-around with oldnfs, but ...
harti
-Original Message-
From: Rick Macklem [mailto:rmack...@uoguelph.ca]
Sent: Saturday, May 04, 2013 11:33 PM
To: Brandt, Hartmut
Cc: curr...@freebsd.org;
Any help is appreciated.
base r250200
ports r317168
=== Returning to build of nvidia-driver-173.14.35_2
=== nvidia-driver-173.14.35_2 depends on shared library: GL.1 - found
==
=== Cleaning for nvidia-driver-173.14.35_2
On 06.05.2013 05:43, Sean Bruno wrote:
On Mon, 2013-05-06 at 03:25 +0200, Michael Schmiedgen wrote:
On 04.05.2013 06:14, Sean Bruno wrote:
Speaker/headphones working great on Current.
Was trying to get the microphone working, but it seems to not quite be
working.
I got the same problem with
On Sun, May 05, 2013 at 10:01:00AM +0400, de...@stasyan.com wrote:
dHello !
d
dThis problems appears about 4-6 months ago after updating of -CURRENT
host.
d Unable to boot host with nvidia_load=YES in loader.conf because panic.
d But when nvidia driver loads manually via kldload,
On Sun, May 05, 2013 at 07:45:45PM -0700, Kevin Oberman wrote:
K I have a T520. It has an internal mic. Not USB. It also has a standard
K headphone/mic jack. It works with a headset with a mic. It's a four contact
K jack: Left, right, mic, and common. A cell-phone headset will work fine.
K
K Have
On Mon, May 06, 2013 at 11:27:33AM +0400, Gleb Smirnoff wrote:
T On Sun, May 05, 2013 at 10:01:00AM +0400, de...@stasyan.com wrote:
T dHello !
T d
T dThis problems appears about 4-6 months ago after updating of -CURRENT
host.
T d Unable to boot host with nvidia_load=YES in
After latest world / kernel update (r250260 Sun May 5, amd64) I cannot mount
root - message is:
Addditional ABI support: linux
Clearing /tmp
Updating motd
*Mounting late file systems:mount: illegal option -- L*
Mounting /etc/fstab filesystems failed, startup aborted
System then falls into
Is this startup error message related to the problem?
starting devd
devd: can't open devctl device /dev/devctl: device busy
/etc/rc: warning: failed to start devd
crw--- 1 root wheel May 6 /dev/devctl
-
10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3
xorg.devel
Is this startup error message related to the problem?
starting devd
devd: can't open devctl device /dev/devctl: device busy
/etc/rc: warning: failed to start devd
crw--- 1 root wheel May 6 /dev/devctl
-
10-Current-amd64-using ccache-portstree merged with marcuscom.gnome3
xorg.devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 5/6/13 12:56 AM, Beeblebrox wrote:
After latest world / kernel update (r250260 Sun May 5, amd64) I
cannot mount root - message is: Addditional ABI support: linux
Clearing /tmp Updating motd *Mounting late file systems:mount:
illegal option
[redirecting to ports@, where this belongs]
On 2013-05-06 08:19, sig6247 wrote:
...
cc -O2 -pipe -fno-strict-aliasing -DNV_VERSION_STRING=\173.14.35\
-D__KERNEL__ -DNVRM -UDEBUG -U_DEBUG -DNDEBUG -O -Werror -D_KERNEL -DKLD_MODULE -nostdinc
On Mon, 2013-05-06 at 11:31 +0400, Gleb Smirnoff wrote:
A very lame explanation then: may be Sean plugs simple 3-contact
minijack into
the socket, to get sound output via headset? But this jack plugged
disables
internal mic.
I haven't been using any headset to this point. So, its the
Hello !
dThis problems appears about 4-6 months ago after updating of
-CURRENT host.
d Unable to boot host with nvidia_load=YES in loader.conf because panic.
d But when nvidia driver loads manually via kldload, everything OK.
d Nvidia driver version is 310.44 at this moment, but
On Mon, May 06, 2013 at 04:16:28PM +0400, Stas Timokhin wrote:
S dThis problems appears about 4-6 months ago after updating of
S -CURRENT host.
S d Unable to boot host with nvidia_load=YES in loader.conf because panic.
S d But when nvidia driver loads manually via kldload, everything OK.
On Mon, 2013-05-06 at 09:27 +0300, Alexander Motin wrote:
From information provided by Sean I can't see why added quirk for
playback may affect recording in any way. More likely I would guess
that
change from two playback pcm/dsp devices to one, while still having
two
record ones, made
On 06.05.2013 15:12, Sean Bruno wrote:
On Mon, 2013-05-06 at 09:27 +0300, Alexander Motin wrote:
From information provided by Sean I can't see why added quirk for
playback may affect recording in any way. More likely I would guess
that
change from two playback pcm/dsp devices to one, while
Hartmut Brandt wrote:
Hi Rick,
the patch doesn't help. So how can I help to fix that? Of course, I
can use the work-around with oldnfs, but ...
Well, I plan on going through the readdir code and seeing if I can spot
a case that would break for small RPC replies. If I can find something,
Hi
We just experienced the following panic on r249172
It was coincident with a panic on our other router using carp+pfsync.
Unread portion of the kernel message buffer:
panic: pfsync_insert_state: st-sync_state == PFSYNC_S_NONE
cpuid = 12
KDB: stack backtrace:
db_trace_self_wrapper() at
provided by Kevin Oberman:
hint.hdac.0.cad0.nid35.config=as=2
hint.hdac.0.cad0.nid27.config=as=2 seq=15
No success with these settings. There is no change to my ability to
record with audacity.
Sorry, on your system hdac.0 is HDMI audio. Try hdac.1 instead.
Hrm ... I set:
Thank you for the answer. BOTH problems were indeed related to
/etc/rc.d/mountlate, as they both disappeared after deleting mountlate.
I then re-did an installworld mergemaster, rebooted and system is fine
now. I probably overlooked doing the installworld on host after having
updated the jail
Hello !
S Can you please try the attached patch to kernel?
S Test of patch with nvidia-driver-310.44_1 (builded by clang from
S -CURRENT) passed successfully - booting module from /boot/loader.conf
S is OK.
Sorry if I wasn't clear before.
Can you please test nvidia-driver-310.44_1 without
On Mon, May 06, 2013 at 06:16:34PM +0400, Stas Timokhin wrote:
S S Can you please try the attached patch to kernel?
S S Test of patch with nvidia-driver-310.44_1 (builded by clang from
S S -CURRENT) passed successfully - booting module from /boot/loader.conf
S S is OK.
S Sorry if I wasn't
On Fri, 2013-05-03 at 21:14 -0700, Sean Bruno wrote:
Speaker/headphones working great on Current.
Was trying to get the microphone working, but it seems to not quite be
working.
By not working, there is no audio detected when recording. Is there
something in here that looks like a
On Sun, 2013-05-05 at 13:31 -0500, rmt...@servalan.servalan.com wrote:
Tried upgrading one of my machines to -CURRENT yesterday and got the
following panic when the sbp code did its probing of all the firewire
devices:
sbp0: SBP-2/SCSI over FireWire on firewire0
sbp0:
On Mon, May 6, 2013 at 11:27 AM, Sean Bruno sean_br...@yahoo.com wrote:
Using a 4 position (combined headphone/mic) head set with the T520 and
*no* device hints WORKS for recording and playback.
Its the onboard microphone that is not working for me. No device hints
provided in this thread
On Mon, 2013-05-06 at 15:50 -0400, Zaphod Beeblebrox wrote:
On Mon, May 6, 2013 at 11:27 AM, Sean Bruno sean_br...@yahoo.com
wrote:
Using a 4 position (combined headphone/mic) head set with the
T520 and
*no* device hints WORKS for recording and playback.
What happens if you re-add the xpt_periph variable to sbp_do_attach() ?
ref:
http://svnweb.freebsd.org/base/head/sys/dev/firewire/sbp.c?r1=249468r2=249467pathrev=249468diff_format=f
see line 1089
Sean
Tried that. No change, still get the same panic: mutex sbp not owned
at
On 05/06/13 04:49, Kevin Oberman wrote:
On Sun, May 5, 2013 at 7:43 PM, Sean Bruno sean_br...@yahoo.com wrote:
On Mon, 2013-05-06 at 03:25 +0200, Michael Schmiedgen wrote:
Was trying to get the microphone working, but it seems to not quite be
working.
I got the same problem with my X220.
not sure why. for my case, padaligining one of the rwlocks solved it.
you may want to try the patch attached and see if it works for you.
anyway, i'm filing a PR if nobody has done so already.
thanks
kit
On Sat, May 04, 2013 at 09:22:23PM +0400, Andrey Smagin wrote:
I have panic like your
ah, it's should be fixed now as per r250300. changes that caused this panic
have been backed out.
kit
--- On Tue, 5/7/13, kit kt...@acm.org wrote:
From: kit kt...@acm.org
Subject: Re: panic in sctp_del_addr_from_vrf() ?
To: Andrey Smagin samsp...@mail.ru, freebsd-current@freebsd.org
Date:
31 matches
Mail list logo
