Re: xorg build failed
On 6/5/06, Nikolas Britton <[EMAIL PROTECTED]> wrote: On 6/2/06, Manfred Lotz <[EMAIL PROTECTED]> wrote: > Hi there, > Trying to build xorg-server 6.9.3 I get Where did you get Xorg 6.9.3 from? He is probably referring to 6.9.0_3 Matty ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: new sk driver [was: nve timeout (and down) regression?]
On Sun, Jun 04, 2006 at 12:41:12PM +0200, Michael Gerhards wrote: > Pyun YongHyeon <[EMAIL PROTECTED]> wrote: > > > FYI: Fix committed to HEAD. > > This happened nearly three weeks ago. When might this fix get into 6-STABLE? Unfortunately sk(4) in HEAD has a known issue and I'm working on it. Since I couldn't reproduce the issue on my system and it takes a long time to regenerate the issue on reporter's system(normally one week), it's not easy to commit right fix. The last patch sent to a problem reporter seems to work around the issue so I'll commit it this week. > I have also problems on my system which might be related to the sk-trouble, > so this fix might also help me. Or should I try to compile the new driver > on my system (running 6-STABLE)? > Yes. I'd like to hear any issues related with sk(4) in HEAD. -- Regards, Pyun YongHyeon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: trying to sleep while sleeping is prohibited - USB network panic after ifconfig
On Wed, May 31, 2006 at 09:18:12PM -0600, Scott Long wrote:
> This looks like a pretty fundamental problem with the aue driver.
>
I have a patch attached that will hopefully fix it. I dont have the
hardware so anyone with an aue adapter please test.
> Scott Ullrich wrote:
>
> >Sleeping on "usbsyn" with the following non-sleepable locks held:
> >exclusive sleep mutex in_multi_mtx r = 0 (0xc0acfbc0) locked @
> >/usr/src/sys/neti
> >net/in.c:971
> >KDB: stack backtrace:
> >kdb_backtrace(1,c27e5418,c27e7000,1,ccfe3a50) at kdb_backtrace+0x29
> >witness_warn(5,0,c0993d00,c09846cb) at witness_warn+0x18e
> >msleep(c27ffb00,0,4c,c09846cb,0) at msleep+0x42
> >usbd_transfer(c27ffb00,ccfe3ab0,c0649b2d,c27ffb00,c24a1580) at
> >usbd_transfer+0x1
> >21
> >usbd_sync_transfer(c27ffb00,c24a1580,ccfe3acc,c06c6ea4,c25d0a00) at
> >usbd_sync_tr
> >ansfer+0x11
> >usbd_do_request_flags_pipe(c257d600,c257d280,ccfe3b0c,ccfe3b0b,0) at
> >usbd_do_req
> >uest_flags_pipe+0x5d
> >usbd_do_request_flags(c257d600,ccfe3b0c,ccfe3b0b,0,0) at
> >usbd_do_request_flags+0
> >x20
> >usbd_do_request(c257d600,ccfe3b0c,ccfe3b0b) at usbd_do_request+0x1a
> >aue_csr_read_1(c25d0a00,0) at aue_csr_read_1+0x50
> >aue_setmulti(c25d0a00,c280e280,c25d3000,ccfe3ba8,ccfe3b78) at
> >aue_setmulti+0x4a
> >aue_ioctl(c25d3000,80206931,0) at aue_ioctl+0x106
> >if_addmulti(c25d3000,ccfe3ba8,ccfe3ba4,ccfe3ba8,10,c0acfbc0,0,c09a3cd4,3cb)
> >at i
> >f_addmulti+0x1b8
> >in_addmulti(ccfe3bdc,c25d3000) at in_addmulti+0x69
> >in_ifinit(c25d3000,c27da500,c262dcd0,0,ccfe3c38) at in_ifinit+0x529
> >in_control(c28206f4,8040691a,c262dcc0,c25d3000,c27e7000) at
> >in_control+0x882
> >ifioctl(c28206f4,8040691a,c262dcc0,c27e7000,0) at ifioctl+0x198
> >soo_ioctl(c2678c60,8040691a,c262dcc0,c2480780,c27e7000) at soo_ioctl+0x2db
> >ioctl(c27e7000,ccfe3d04,3,2,286) at ioctl+0x370
> >syscall(3b,3b,3b,8056080,80583c0) at syscall+0x22f
> >Xint0x80_syscall() at Xint0x80_syscall+0x1f
> >--- syscall (54, FreeBSD ELF32, ioctl), eip = 0x28131603, esp =
> >0xbfbfe59c, ebp
> >= 0xbfbfede8 ---
> >panic: trying to sleep while sleeping is prohibited
> >cpuid = 0
> >KDB: enter: panic
> >[thread pid 13 tid 13 ]
> >Stopped at kdb_enter+0x2b: nop
> >
> >More information (bt, bt all, show alllocks) can be found at
> >http://www.pfsense.com/~sullrich/panics/usb_network_nic_panic.txt
> >
> >Let me know if you need any more information.
> >___
> >freebsd-stable@freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> >To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Index: if_aue.c
===
RCS file: /home/ncvs/src/sys/dev/usb/if_aue.c,v
retrieving revision 1.96
diff -u -p -r1.96 if_aue.c
--- if_aue.c14 Feb 2006 12:44:55 - 1.96
+++ if_aue.c4 Jun 2006 23:42:34 -
@@ -524,6 +524,7 @@ aue_setmulti(struct aue_softc *sc)
struct ifnet*ifp;
struct ifmultiaddr *ifma;
u_int32_t h = 0, i;
+ u_int8_thashtbl[8] = { 0, 0, 0, 0, 0, 0, 0, 0 };
ifp = sc->aue_ifp;
@@ -534,10 +535,6 @@ aue_setmulti(struct aue_softc *sc)
AUE_CLRBIT(sc, AUE_CTL0, AUE_CTL0_ALLMULTI);
- /* first, zot all the existing hash bits */
- for (i = 0; i < 8; i++)
- aue_csr_write_1(sc, AUE_MAR0 + i, 0);
-
/* now program new ones */
IF_ADDR_LOCK(ifp);
#if __FreeBSD_version >= 50
@@ -550,10 +547,14 @@ aue_setmulti(struct aue_softc *sc)
continue;
h = ether_crc32_le(LLADDR((struct sockaddr_dl *)
ifma->ifma_addr), ETHER_ADDR_LEN) & ((1 << AUE_BITS) - 1);
- AUE_SETBIT(sc, AUE_MAR + (h >> 3), 1 << (h & 0x7));
+ hashtbl[(h >> 3)] |= 1 << (h & 0x7);
}
IF_ADDR_UNLOCK(ifp);
+ /* write the hashtable */
+ for (i = 0; i < 8; i++)
+ aue_csr_write_1(sc, AUE_MAR0 + i, hashtbl[i]);
+
return;
}
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg build failed
On 6/2/06, Manfred Lotz <[EMAIL PROTECTED]> wrote: Hi there, Trying to build xorg-server 6.9.3 I get Where did you get Xorg 6.9.3 from? -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg build failed
On Sun, 04 Jun 2006 20:36:26 +0930 Wayne Sierke <[EMAIL PROTECTED]> wrote: ... > > Perhaps a more useful comment would by why you think /var/tmp could > be a "weird", or rather a problematic, location? > > For the OP: Is there anything significant about your /var/tmp? (Does > it have enough free space? Is it mounted noexec, etc.?) > There is enough free space, around 5 GB. The setting of /var/tmp/portswrk was no problem. Also when removing WRKDIRPREFIX in /etc/make.conf I got the same build error (now having directory ./work directly under x11-server). Manfred ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg build failed
On Sat, 3 Jun 2006 03:06:50 -0400 (EDT) doug <[EMAIL PROTECTED]> wrote: > Unless you have a reason to want to modify the source, why not use > the package: > > setenv PACKAGEROOT ftp://ftp.FreeBSD.org > pkg_add -r xorg > > will get you 6.9.0_1 in a few minutes > Yes, you are right. I just didn't think about when doing a portupgrade -R xorg-server. I finally did a pkg_add -r xorg which worked fine. Thanks, Manfred ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg build failed
On Sun, 2006-06-04 at 21:29 +1200, Kaiwai Gardiner wrote: > One would ask as to why xorg has failed to compile, and it appears no > one else here has experienced the same issue; hence the reason I > suggested a clean removal of installed ports and a vanilla compile of > it. > > I've updated my ports from the cvs, and haven't experienced an xorg > compilation issue - I compile from the standard /usr/ports/x11/xorg > location, and I don't see to suffer the same issues - co-incidence or > simply being boring with the locating of things has saved me from > compilation problems? > > Matty > If the OP's problem is merely a result of using WRKDIRPREFIX then something is buggy and needs attention. As mentioned in man ports, it can be useful if /usr/ports is on a read-only filesystem, e.g. cdrom. Another reason, for which I've used it, is if there is insufficient free space for the temporary work files in /usr/ports. Perhaps a more useful comment would by why you think /var/tmp could be a "weird", or rather a problematic, location? For the OP: Is there anything significant about your /var/tmp? (Does it have enough free space? Is it mounted noexec, etc.?) Wayne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: new sk driver [was: nve timeout (and down) regression?]
Pyun YongHyeon <[EMAIL PROTECTED]> wrote: > FYI: Fix committed to HEAD. This happened nearly three weeks ago. When might this fix get into 6-STABLE? I have also problems on my system which might be related to the sk-trouble, so this fix might also help me. Or should I try to compile the new driver on my system (running 6-STABLE)? Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg build failed
One would ask as to why xorg has failed to compile, and it appears no one else here has experienced the same issue; hence the reason I suggested a clean removal of installed ports and a vanilla compile of it. I've updated my ports from the cvs, and haven't experienced an xorg compilation issue - I compile from the standard /usr/ports/x11/xorg location, and I don't see to suffer the same issues - co-incidence or simply being boring with the locating of things has saved me from compilation problems? Matty On 6/4/06, Wolfgang Zenker <[EMAIL PROTECTED]> wrote: > On 6/3/06, doug <[EMAIL PROTECTED]> wrote: >> Unless you have a reason to want to modify the source, why not use the >> package: >> setenv PACKAGEROOT ftp://ftp.FreeBSD.org >> pkg_add -r xorg >> will get you 6.9.0_1 in a few minutes > There have been updates released after it was released - nothing wrong with > building from the source, the problem is when people compile from all weird > locations, with all weird settings, then complain that the shit hit the fan. In this case the OP just used WRKDIRPREFIX, which is the documented way of having your port build directories outside /usr/ports. I wouldn't call that "compile from all weird locations, with all weird settings". Wolfgang ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg build failed
> On 6/3/06, doug <[EMAIL PROTECTED]> wrote: >> Unless you have a reason to want to modify the source, why not use the >> package: >> setenv PACKAGEROOT ftp://ftp.FreeBSD.org >> pkg_add -r xorg >> will get you 6.9.0_1 in a few minutes > There have been updates released after it was released - nothing wrong with > building from the source, the problem is when people compile from all weird > locations, with all weird settings, then complain that the shit hit the fan. In this case the OP just used WRKDIRPREFIX, which is the documented way of having your port build directories outside /usr/ports. I wouldn't call that "compile from all weird locations, with all weird settings". Wolfgang ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
