What is PR?
On Tuesday 09 September 2014 13:37:44 Adrian Chadd wrote:
> Hi,
>
> please file a PR.
>
> There's been some other issues with the BB hanging on the AR9287 so I
> think I have to hard-reset the chip to solve it.
>
>
> -a
>
>
> On 9
?
--
Artyom Mirgorodskiy
___
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"
ns/
> > > > > [2] -
> > > > >
> > > >
> > http://www.freebsd.org/news/status/report-2013-07-2013-09.html#Continuation-of-the-Newcons-Project
> > > > > [3] -
> > > > >
> > > >
> > http://raybsd.blogspot.com/2013/10/newcons-inter
Thank you. Work fine for me
On Tuesday 01 October 2013 13:45:21 Hans Petter Selasky wrote:
> On 10/01/13 13:11, Artyom Mirgorodskiy wrote:
> > I removed old libraries:
> >
> > ls /usr/lib/libusb*
> > /usr/lib/libusb.a/usr/lib/libusb_p.a /usr/lib/libusbhid.
? ()
#7 0x000800636000 in ?? ()
#8 0x in ?? ()
On Tuesday 01 October 2013 12:40:35 Hans Petter Selasky wrote:
> On 10/01/13 12:24, Artyom Mirgorodskiy wrote:
> > ls /usr/lib/libusb*
> > /usr/lib/libusb.a/usr/lib/libusb.so.3 /usr/lib/libusbhid.so@
>
you provide more information about your system?
>
> uname -a
>
> ls /usr/lib/libusb*
>
> ls /usr/local/libdata/pkgconfig/*usb*
>
--
Artyom Mirgorodskiy
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
gt; cd /usr/ports/graphics/libgphoto2
> make all reinstall clean
>
> cd /usr/ports/graphics/photo2
> make all reinstall clean
>
> --HPS
--
Artyom Mirgorodskiy
___
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"
ibthr.so.3
> > > > > #1 0x0008040083cd in libusb_free_device_list () from
> > > > > /usr/lib/libusb.so.3
> > > > > #2 0x000803801a2a in gp_port_usb_exit (port= > > > > out>)
> > > > > at libusb1.c:275
> > > > > #3 0x000801135763 in gp_port_free (po
0x000803801a2a in gp_port_usb_exit (port=)
> > > at libusb1.c:275
> > > #3 0x000801135763 in gp_port_free (port=0x80286d280) at
> > > gphoto2-port.c:124
> > > #4 0x000800ebc6a9 in gp_abilities_list_detect (list=0x80286
o_list=0x802869050, l=0x8028ec000, context=0x45)
> > at gphoto2-abilities-list.c:488
> > #5 0x0040e0f7 in ?? ()
> > #6 0x00404aef in ?? ()
> > #7 0x000800635000 in ?? ()
> > #8 0x in ?? ()
> >
> >
> > --
> > Art
=0x802869080,
info_list=0x802869050, l=0x8028ec000, context=0x45)
at gphoto2-abilities-list.c:488
#5 0x0040e0f7 in ?? ()
#6 0x00404aef in ?? ()
#7 0x000800635000 in ?? ()
#8 0x in ?? ()
--
Artyom Mirgorodskiy
e and see if there is
> something that helps to understand the problem.
--
Artyom Mirgorodskiy
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd
blem seems to be gone with the patch applied ?
> >
> > Now 48h are passed without panics. Fix definitely works. Thanks.
>
> Thank you.
>
> I tested it locally (without SNA) and committed the change a hour ago.
> It is required a
ote:
> > Thanks for the patch.
> > I've adapted the proposed patch for stable/9 and it is running with
> > SNA enabled now.
>
> In other words, your problem seems to be gone with the patch applied ?
>
> >
> > On Sat, Jun 15, 2013 at 11:54 PM, Artyom Mir
I can't apply patch
On Saturday 15 June 2013 21:48:08 Konstantin Belousov wrote:
> On Sat, Jun 15, 2013 at 09:46:02PM +0300, Artyom Mirgorodskiy wrote:
> > Can you please also create patch for -current?
> It is for current. Code in stable/9 should be identical though.
--
Ar
Can you please also create patch for -current?
On Saturday 15 June 2013 08:17:46 Konstantin Belousov wrote:
> On Fri, Jun 14, 2013 at 10:16:15AM +0300, Artyom Mirgorodskiy wrote:
> > Thank you! This patch also solve my issue (unable shutdown):
> > http://lists.freebsd.org/pi
y
> assigned page to the different object");
>}
> and it worked with SNA enabled for about a week with no problems. But
> I'm not sure that is a good solution.
>
> I can provide additional info if required.
>
> Thanks
> --
> Oleg Sidorkin
> __
Hi
More than a month I can not shutdown FreeBSD on my laptop correctly when
running Xorg with Intel GPU. However reboot work correctly. Shutdown work fine
if I choose Vesa driver in xorg.conf. So I can run with intel, then edit
xorg.conf, kill Xorg server and shutdown correctly. If I shut down i
ny of the other reporters of this use fuse?-- R. Kevin Oberman, Network
EngineerE-mail: rkober...@gmail.com[2]
--
Artyom Mirgorodskiy
[1] mailto:artyom.mirgorod...@gmail.com
[2] mailto:rkober...@gmail.com
___
freebsd-current@freebsd.org ma
__
> 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"
--
Artyom Mirgorodskiy
___
fr
ther or not
> > the 11n option is set.
> >
> > thanks!
> >
> >
> > adrian
> >
> > On 19 April 2013 04:08, Artyom Mirgorodskiy
> > wrote:
> >> Adrian, I found the problem.
> >>
> >> I'm use ath as module, so A
Adrian, I found the problem.
I'm use ath as module, so ATH_ENABLE_11N is not defined. When I define
ATH_ENABLE_11N - everything work.
Artyom Mirgorodskiy
On Friday 19 April 2013 13:27:21 wrote:
Updated. However I did not see chainmask information.
See attached
On Friday 19 April 20
Nothing :(
On Thursday 18 April 2013 15:22:49 Adrian Chadd wrote:
> Hm! I wonder..
>
> Edit if_athvar.h - change sc_rxchainmask and sc_txchainmask in
> ath_softc to be uint32_t, rather than int.
>
> See if that helps.
>
>
>
> Adrian
>
> On 18 April 2013
Did not work.
On Thursday 18 April 2013 13:58:23 Adrian Chadd wrote:
> On 18 April 2013 13:33, Artyom Mirgorodskiy
> wrote:
> > Yes. I tested 247287 and it breaks.
>
> Hm.
>
> Well, not much changed there.
>
> Try going to 247287 (ie, the broken revision),
Yes. I tested 247287 and it breaks.
On Thursday 18 April 2013 13:31:29 Adrian Chadd wrote:
> On 18 April 2013 11:58, Artyom Mirgorodskiy
> wrote:
> > Yes, HEAD everything else except the wifi code (ath).
> >
> > Last working revision is 247286. So problem in revision 24
g just to test the
> AR9287 for you and it was peachy!
>
>
> Adrian
>
> On 18 April 2013 10:36, Artyom Mirgorodskiy
> wrote:
> > Yes
> >
> >
> >
> > On Thursday 18 April 2013 10:30:33 Adrian Chadd wrote:
> >
> >
e 0.0 on pci10
> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
>
>
--
Artyom Mirgorodskiy
--
Artyom Mirgorodskiy
___
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"
slot 0 INTA hardwired to IRQ 18
> > ath0: mem 0xe050-0xe050 irq 18 at device 0.0 on pci10
> > ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 0 vector 60
>
>
--
Artyom Mirgorodskiy
___
freebsd-current@freebsd.org mailing
all all my ports now to see what will come
> out there.
>
> Erich
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send an
This patch work for me. Thanks.
On Friday 14 December 2012 00:30:52 Niclas Zeising wrote:
> Can you please try the attached patch, against x11-servers/xorg-server.
> Apply it and recompile xorg-server with normal flags (that is, no
> debugging) and let me and the list know the result when startin
I have recompile xorg-server with WITH_DEBUG=yes and did not get crash
On Thursday 13 December 2012 22:36:24 Dimitry Andric wrote:
> On 2012-12-13 21:49, Johannes Dieterich wrote:
> > I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and
> > WITH_KMS=yes. Interestingly, gdm loads fine
I have a similar problem when running firefox
On Thursday 13 December 2012 15:49:38 Johannes Dieterich wrote:
> Dear all,
>
> I lately see xorg segfault 11s with CURRENT, WITH_NEW_XORG=yes and
> WITH_KMS=yes. Interestingly, gdm loads fine but xfce4 at login directly
> causes the segfault (log att
Works fine
On Tuesday 11 December 2012 16:07:03 Gleb Smirnoff wrote:
> On Tue, Dec 11, 2012 at 12:21:20PM +0200, Artyom Mirgorodskiy wrote:
> A> Gleb, when I reset errno at the begin of fiboptlist_csv() everything work
> as expected.
>
> Artyom,
>
> can you pl
Gleb, when I reset errno at the begin of fiboptlist_csv() everything work as
expected.
On Tuesday 11 December 2012 12:16:13 Artyom Mirgorodskiy wrote:
> # route add default 192.168.1.1
> fiboptlist_csv: arg default, ret 846422615, str "0"
> route: fiboptlist_csv failed.
&g
# route add default 192.168.1.1
fiboptlist_csv: arg default, ret 846422615, str "0"
route: fiboptlist_csv failed.
On Tuesday 11 December 2012 11:13:34 Gleb Smirnoff wrote:
> Artyom,
>
> can you please run route with attached patch and show output?
>
>
--
This message is for the person(s)
Before calling fiboptlist_csv() the errno = EINVAL. I hope this help to solve
problem.
On Monday 10 December 2012 17:40:57 Gleb Smirnoff wrote:
> On Sat, Dec 08, 2012 at 01:00:57PM +0200, Artyom Mirgorodskiy wrote:
> A> I just upgraded to revision 244030. Unexpected route comma
sysctl net.my_fibnum
net.my_fibnum: 0
On Monday 10 December 2012 17:40:57 Gleb Smirnoff wrote:
> On Sat, Dec 08, 2012 at 01:00:57PM +0200, Artyom Mirgorodskiy wrote:
> A> I just upgraded to revision 244030. Unexpected route command is not
> working:
> A>
> A> #route add
I just upgraded to revision 244030. Unexpected route command is not working:
#route add default 192.168.1.1
route: fiboptlist_csv failed.
#netstat -rn
Routing tables
Internet:
DestinationGatewayFlagsRefs Use Netif Expire
127.0.0.1 link#2 UH
38 matches
Mail list logo