Re: NetBSD mtree committed
On Tue, Jan 1, 2013 at 7:11 PM, Garrett Cooper wrote: ... > Ran into this linker error when running make installworld going > from 10-CURRENT from a month ago to now: > > /tmp/install.9ten1vtn/mtree: Undefined symbol "strunvis" > *** Error code 1 > > And I'm running into similar issues with mergemaster. Is this a > known chicken and egg problem? Ugh, the environment is fubared. Let's put this question on hold until I've done enough digging to figure out why it's doing the wrong thing.. -Garrett ___ 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"
Re: NetBSD mtree committed
On Fri, Dec 21, 2012 at 1:02 PM, Brooks Davis wrote: > I have committed NetBSD's mtree to the tree and am building and > installing it as nmtree. I plan to replace our mtree with this version > after the following steps: > > - Add a WITH_NMTREE build option to install nmtree as mtree and the >old mtree as omtree. > - Switch the default to WITH_NMTREE. > - Remove the old mtree. > - Rename usr.sbin/nmtree to usr.sbin/mtree. > > During this process I will also commit patches to switch makefs > to use NetBSD's mtree which will make the -F specfile option more > useful. > > As a reminder we are doing this because, we will gain the -C option > which produces mtree files compatible with libarchive and makefs (one > line per file with full path) and the -N option which allows a stand > alone set of passwd and group files. When mated with the -U and -M > options to NetBSD's install we will have most of the pieces require to > allow installworld to run as a user and then build images containing > proper permissions. > > The new mtree does introduce some incompatibilities, but nearly all can > be overcome with small command line changes. With one exception, > FreeBSD 9 compatible behavior can be restored by adding the "-F > freebsd9" to the command line. In some cases new warnings are > generate to aid transition, but the output should otherwise be the same. > If you find cases where it is not, please let me know. > > Known incompatibilities are: > > - The -u and -U (update) options do not update the modification time or >set file flags unless the -t and -i options are passed respectively. > - Because the -i option as already take, FreeBSD's option to indent >4 spaces for each directory level is now -j. > - The -d (directories only) option does not omit blank lines when >entering a new directory or leaving one. The -b option now enables >this behavior independently. > - The handling of the uname and group keywords when the uid or gid can >not be resolved is changed. In the new code, when the uname or group >keyword is request and the name can not be found a uid or gid keyword >is emitted instead. Historically, mtree would report and error and >exit unless the -w option was passed. If that happened then a >warning was printed and no keyword was emitted. That resulted in >potentially dangerous /set statements. As a result I declined to >implement this behavior. > >Here is an example of the dangerous \set statements: > >$ ls -l >total 0 >-rwxr-xr-x 1 root wheel 0 Dec 21 14:13 a >-rwsr-xr-x 1 12345 wheel 0 Dec 21 14:13 b >$ mtree -c -p . -n -k uname,mode -w > ../mtree.out >mtree: Could not get uname for uid=12345 >$ cat ../mtree.out > >/set type=file uname=root mode=0755 >. type=dir uname=brooks >a >b mode=04755 >.. > >$ mtree -f ../mtree.out -u -p . >b: user (0, 12345, modified) >$ ll >total 0 >-rwxr-xr-x 1 root wheel 0 Dec 21 14:13 a >-rwsr-xr-x 1 root wheel 0 Dec 21 14:13 b >$ > > I have heard some requests to MFC the new mtree code. At this time I > have no concrete plans to do so. If it were done then I would modify > the code to run with -F freebsd9 and would implement full uname/group > compatibility. Ran into this linker error when running make installworld going from 10-CURRENT from a month ago to now: /tmp/install.9ten1vtn/mtree: Undefined symbol "strunvis" *** Error code 1 And I'm running into similar issues with mergemaster. Is this a known chicken and egg problem? Thanks, -Garrett ___ 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"
Re: Amd(8) Hangs at Boot
Cy Schubert wrote: > Just udated to the latest current and amd hangs at boot. Ideas? > I think I spoke too soon w.r.t. the bxe(4) device and UDP checksums. I thought I saw some email about UDP checksum offload for it being broken but I can't locate the email, so I probably have this wrong. Sorry about the noise, rick ps: The loopback configuration issue might still be the culprit. > NFS access cache time=0 > Starting amd. > [halt - sent] > KDB: enter: Break to debugger > [ thread pid 762 tid 100072 ] > Stopped at kdb_break+0x4e: movl $0,kdb_why > db> bt > Tracing pid 762 tid 100072 td 0x8a1675e0 > kdb_break(87641200,c7c8617c,807a9208,81ac6b54,81ac6b50,...) at > kdb_break+0x4e/frame 0xc7c86130 > uart_intr(87641200,0,8a1675e0,4,875f30d0,...) at uart_intr+0x8e/frame > 0xc7c8615c > intr_event_handle(8757fa80,c7c861c0,1,8a1675e0,8a22d6e4,...) at > intr_event_handle+0x85/frame 0xc7c8617c > intr_execute_handlers(875f30d0,c7c861c0,0) at > intr_execute_handlers+0x42/fra > me 0xc7c8619c > lapic_handle_intr(42,c7c861c0) at lapic_handle_intr+0x3d/frame > 0xc7c861b0 > Xapic_isr2() at Xapic_isr2+0x35/frame 0xc7c861b0 > --- interrupt, eip = 0x80929af4, esp = 0xc7c86200, ebp = 0xc7c86220 > --- > udp_bind(8a4b71a0,8a125380,8a1675e0,8a1675e0,8758b400,...) at > udp_bind+0x104/frame 0xc7c86220 > bindresvport(8a4b71a0,0,c7c86380,89fa8300,c7c86408,...) at > bindresvport+0x14a/frame 0xc7c86284 > clnt_reconnect_call(876e82e0,c7c86358,1,89fa8300,c7c86408,...) at > clnt_reconnect_call+0x2a0/frame 0xc7c862e8 > newnfs_request(c7c86408,8a229200,0,8a229310,0,...) at > newnfs_request+0x82a/frame 0xc7c863b0 > nfsrpc_getattrnovp(8a229200,8a22928c,20,1,8758be80,...) at > nfsrpc_getattrnovp+0xfa/frame 0xc7c864b0 > mountnfs(8a125b40,c7c86870,c7c8678c,0,c7c86728,...) at > mountnfs+0x883/frame > 0xc7c865a0 > nfs_mount(8a11c2a0,80d1e8e8,8a0fc400,8758be80,0,...) at > nfs_mount+0x169f/frame 0xc7c86960 > vfs_donmount(8a1675e0,80,0,c7c86b58,8a10b000,...) at > vfs_donmount+0xc94/frame 0xc7c86b40 > kernel_mount(87557a80,80,0,58,3,...) at kernel_mount+0x52/frame > 0xc7c86b80 > nfs_cmount(87557a80,7fbfd170,80,0,80b46c55,...) at > nfs_cmount+0x63/frame 0xc7c86c08 > sys_mount(8a1675e0,c7c86cc8,8a1675e0,88bb82f0,80d94a80,...) at > sys_mount+0x20b/frame 0xc7c86c40 > syscall(c7c86d08) at syscall+0x479/frame 0xc7c86cfc > Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xc7c86cfc > --- syscall (21, FreeBSD ELF32, sys_mount), eip = 0x280ebef7, esp = > 0x7fbfd09c, ebp = 0x7fbfd0c0 --- > db> > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: http://www.FreeBSD.org > > The need of the many outweighs the greed of the few. > > > ___ > 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" ___ 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"
Re: loopback interface broken on current
Am 01/01/13 21:42, schrieb Manfred Antar: > At 11:48 AM 1/1/2013, Gleb Smirnoff wrote: >> On Tue, Jan 01, 2013 at 02:39:58AM -0800, Manfred Antar wrote: >> M> >On Thu, Dec 27, 2012 at 09:05:26AM -0800, Manfred Antar wrote: >> M> >M> For the past few days the loopback interface 127.0.0.1 is broken on >> current. >> M> >M> The last good kernel that works for me is r244662: Mon Dec 24 >> 06:43:07 PST 2012 >> M> >M> Here are some of the errors from current today: >> M> > >> M> >Can you please track this down to the specific revision that made the >> M> >regression? The timeframe is samll, so binary search probably won't >> M> >take long time. >> M> Hi >> M> I'm not sure how to do this :( >> M> I just switched from CVS to SVN 2 weeks ago. >> M> I still have a current CVS tree on my machine. >> M> I guess i can try to check out a /usr/src/sys from the 25 on and see what >> changes were made. >> M> I'm just learning SVN so not sure how to do it with that. >> >> With SVN you don't need to care about dates, you just go through the >> sequential list of revisions. So you just seek between r244662 and the >> most recent revision tht didn't work for you. On first step you >> divide the bad revision (let it be 244768) and good one r244662: >> >> (244662 + 244768)/2 = 244715 >> >> Ok, it is 244715. Let's take it and test: >> >> svn up -r 244715 >> >> If it is fine, you check the one in the middle between 244715and >> 244768. Otherwise you chek in between 244715 and 244662. And so on... >> >> -- >> Totus tuus, Glebius. > > OK > I tracked it down to revision 244678 > 244677 works > the files involved are: > (src)5012}svn up -r 244678 > Updating '.': > Usys/netinet/in.c > Usys/netinet6/in6.c > Updated to revision 244678 > > It seems like the ip6 for localhost is configured but ip4 isn't: > Setting hostname: pozo.com. > ifa_del_loopback_route: deletion failed: 3 > ifconfig: ioctl (SIOCAIFADDR): File exists > bge0: link state changed to DOWN > ifa_del_loopback_route: deletion failed: 3 > > lo0: flags=8049 metric 0 mtu 16384 > options=63 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > nd6 options=21 > > From 244677: > Setting hostname: pozo.com. > > Starting Network: lo0 bge0. > lo0: flags=8049 metric 0 mtu 16384 > options=63 > inet 127.0.0.1 netmask 0xff00 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 > nd6 options=21 > > Manfred I have a similar issue here. It came out after a lot of problems with the amd automounter which rendered a server completeley useless and the very interesting issue is, that the loopback interface, lo0, has IPv6 configured, but it doesn't have IPv4 configured anymore. After a recompilation of the kernel on the 31.12.2012 and a reboot, the box is not responsive anymore (it a remote box I reach not before 07th Jan). NAGIOS is still reporting ICMP ping is good, but every other service is down. On another server I do not face this problem - or have faced that problem and I use the very same OS revisions on most of the CURRENT boxes. But all machines started suffering from some amd automounter issue before the problem got serious. This is strange ... oh signature.asc Description: OpenPGP digital signature
Re: Amd(8) Hangs at Boot
Cy Schubert wrote: > Just udated to the latest current and amd hangs at boot. Ideas? > It appears that r244678 broke the ip4 configuration of loopback for some network interfaces. I don't know, but it might explain why this is happening? Also, if you happen to have a bxe(4) interface, it looks like a recent commit broke UDP checksums, which could also explain it. rick > NFS access cache time=0 > Starting amd. > [halt - sent] > KDB: enter: Break to debugger > [ thread pid 762 tid 100072 ] > Stopped at kdb_break+0x4e: movl $0,kdb_why > db> bt > Tracing pid 762 tid 100072 td 0x8a1675e0 > kdb_break(87641200,c7c8617c,807a9208,81ac6b54,81ac6b50,...) at > kdb_break+0x4e/frame 0xc7c86130 > uart_intr(87641200,0,8a1675e0,4,875f30d0,...) at uart_intr+0x8e/frame > 0xc7c8615c > intr_event_handle(8757fa80,c7c861c0,1,8a1675e0,8a22d6e4,...) at > intr_event_handle+0x85/frame 0xc7c8617c > intr_execute_handlers(875f30d0,c7c861c0,0) at > intr_execute_handlers+0x42/fra > me 0xc7c8619c > lapic_handle_intr(42,c7c861c0) at lapic_handle_intr+0x3d/frame > 0xc7c861b0 > Xapic_isr2() at Xapic_isr2+0x35/frame 0xc7c861b0 > --- interrupt, eip = 0x80929af4, esp = 0xc7c86200, ebp = 0xc7c86220 > --- > udp_bind(8a4b71a0,8a125380,8a1675e0,8a1675e0,8758b400,...) at > udp_bind+0x104/frame 0xc7c86220 > bindresvport(8a4b71a0,0,c7c86380,89fa8300,c7c86408,...) at > bindresvport+0x14a/frame 0xc7c86284 > clnt_reconnect_call(876e82e0,c7c86358,1,89fa8300,c7c86408,...) at > clnt_reconnect_call+0x2a0/frame 0xc7c862e8 > newnfs_request(c7c86408,8a229200,0,8a229310,0,...) at > newnfs_request+0x82a/frame 0xc7c863b0 > nfsrpc_getattrnovp(8a229200,8a22928c,20,1,8758be80,...) at > nfsrpc_getattrnovp+0xfa/frame 0xc7c864b0 > mountnfs(8a125b40,c7c86870,c7c8678c,0,c7c86728,...) at > mountnfs+0x883/frame > 0xc7c865a0 > nfs_mount(8a11c2a0,80d1e8e8,8a0fc400,8758be80,0,...) at > nfs_mount+0x169f/frame 0xc7c86960 > vfs_donmount(8a1675e0,80,0,c7c86b58,8a10b000,...) at > vfs_donmount+0xc94/frame 0xc7c86b40 > kernel_mount(87557a80,80,0,58,3,...) at kernel_mount+0x52/frame > 0xc7c86b80 > nfs_cmount(87557a80,7fbfd170,80,0,80b46c55,...) at > nfs_cmount+0x63/frame 0xc7c86c08 > sys_mount(8a1675e0,c7c86cc8,8a1675e0,88bb82f0,80d94a80,...) at > sys_mount+0x20b/frame 0xc7c86c40 > syscall(c7c86d08) at syscall+0x479/frame 0xc7c86cfc > Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xc7c86cfc > --- syscall (21, FreeBSD ELF32, sys_mount), eip = 0x280ebef7, esp = > 0x7fbfd09c, ebp = 0x7fbfd0c0 --- > db> > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: http://www.FreeBSD.org > > The need of the many outweighs the greed of the few. > > > ___ > 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" ___ 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"
fsck problem
Starting file system checks: /dev/label/rootFS: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/label/rootFS: clean, 11916812 free (74068 frags, 1480343 blocks, 0.5% fragmentation) ** SU+J Recovering /dev/label/homeFS ** Reading 33554432 byte journal from inode 12. ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck_ufs: Directory 1136967 name not found THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: ufs: /dev/label/homeFS (/home) Unknown error; help! ERROR: ABORTING BOOT (sending SIGTERM to parent)! Jan 2 04:35:11 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode Enter full pathname of shell or RETURN for /bin/sh: # g\^H\^[[Kfsck -y .home fsck: cannot open `/dev/.home': No such file or directory # fsck -y .home\^H\^H\^H\^H\^Hhome\^[[K\^H\^H\^H\^H/home\^H\^H\^H\^H twa0: INFO: (0x04: 0x0029): Verify started: unit=0, subunit=1 twa0: INFO: (0x04: 0x0029): Verify started: unit=0, subunit=0 ** /dev/label/homeFS USE JOURNAL? yes ** SU+J Recovering /dev/label/homeFS ** Reading 33554432 byte journal from inode 12. RECOVER? yes ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck_ufs: Directory 1136967 name not found # tunefs -j disable .\^H\^[[K/home Clearing journal flags from inode 12 tunefs: soft updates journaling cleared but soft updates still set. tunefs: remove .sujournal to reclaim space # tunefs -j disable /home\^[[23D\^[[10Pfsck -y\^[[6C ** /dev/label/homeFS ** Last Mounted on /home ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts UNREF FILE I=48071192 OWNER=www MODE=100600 SIZE=5472256 MTIME=Jan 1 23:59 2013 CLEAR? yes UNREF FILE I=48071193 OWNER=www MODE=100600 SIZE=3538944 MTIME=Jan 2 00:01 2013 CLEAR? yes UNREF FILE I=53478932 OWNER=h40708 MODE=100644 SIZE=81 MTIME=Dec 29 00:24 2012 CLEAR? yes UNREF FILE I=53478934 OWNER=h40708 MODE=100644 SIZE=67 MTIME=Dec 27 17:24 2012 CLEAR? yes UNREF FILE I=53478935 OWNER=h40708 MODE=100644 SIZE=71 MTIME=Dec 28 12:34 2012 CLEAR? yes UNREF FILE I=53478947 OWNER=h40708 MODE=100644 SIZE=88 MTIME=Jan 1 18:10 2013 CLEAR? yes UNREF FILE I=53478953 OWNER=h40708 MODE=100644 SIZE=70 MTIME=Dec 28 00:42 2012 CLEAR? yes UNREF FILE I=53478954 OWNER=h40708 MODE=100644 SIZE=66 MTIME=Dec 31 08:20 2012 CLEAR? yes UNREF FILE I=53478956 OWNER=h40708 MODE=100644 SIZE=72 MTIME=Dec 28 00:48 2012 CLEAR? yes ** Phase 5 - Check Cyl groups FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? yes SUMMARY INFORMATION BAD SALVAGE? yes BLK(S) MISSING IN BIT MAPS SALVAGE? yes 2587656 files, 12137676 used, 212163011 free (637755 frags, 26440657 blocks, 0.3% fragmentation) * FILE SYSTEM MARKED CLEAN * * FILE SYSTEM WAS MODIFIED * # # # # # ^DSetting hostuuid: 564d258e-1ef7-b7a3-bde0-b6bca10c3382. Setting hostid: 0x88403a99. Entropy harvesting: interrupts ethernet point_to_point kickstart. Fast boot: skipping disk checks. Mounting local file systems:. === so, whats rason for use SUJ? about system: srv0$ uname -a FreeBSD srv0.host-food.ru 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Wed Dec 5 04:05:50 MSK 2012 t...@srv0.host-food.ru:/usr/obj/usr/src/sys/HOST-FOOD amd64 srv0$ mount /dev/label/rootFS on / (ufs, local) devfs on /dev (devfs, local, multilabel) /dev/label/homeFS on /home (ufs, local, noatime, nosuid, with quotas, soft-updates) linprocfs on /proc (linprocfs, local) tmpfs on /tmp (tmpfs, local, noexec, nosuid) devfs on /var/named/dev (devfs, local, multilabel) srv0$ df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/label/rootFS 59G 13G 40G25%/ devfs1.0k1.0k 0B 100%/dev /dev/label/homeFS855G 46G740G 6%/home linprocfs4.0k4.0k 0B 100%/proc tmpfs 14G4.0k 14G 0%/tmp devfs1.0k1.0k 0B 100%/var/named/dev srv0$ ___ 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"
Re: loopback interface broken on current
At 11:48 AM 1/1/2013, Gleb Smirnoff wrote: >On Tue, Jan 01, 2013 at 02:39:58AM -0800, Manfred Antar wrote: >M> >On Thu, Dec 27, 2012 at 09:05:26AM -0800, Manfred Antar wrote: >M> >M> For the past few days the loopback interface 127.0.0.1 is broken on >current. >M> >M> The last good kernel that works for me is r244662: Mon Dec 24 06:43:07 >PST 2012 >M> >M> Here are some of the errors from current today: >M> > >M> >Can you please track this down to the specific revision that made the >M> >regression? The timeframe is samll, so binary search probably won't >M> >take long time. >M> Hi >M> I'm not sure how to do this :( >M> I just switched from CVS to SVN 2 weeks ago. >M> I still have a current CVS tree on my machine. >M> I guess i can try to check out a /usr/src/sys from the 25 on and see what >changes were made. >M> I'm just learning SVN so not sure how to do it with that. > >With SVN you don't need to care about dates, you just go through the >sequential list of revisions. So you just seek between r244662 and the >most recent revision tht didn't work for you. On first step you >divide the bad revision (let it be 244768) and good one r244662: > >(244662 + 244768)/2 = 244715 > >Ok, it is 244715. Let's take it and test: > >svn up -r 244715 > >If it is fine, you check the one in the middle between 244715and >244768. Otherwise you chek in between 244715 and 244662. And so on... > >-- >Totus tuus, Glebius. OK I tracked it down to revision 244678 244677 works the files involved are: (src)5012}svn up -r 244678 Updating '.': Usys/netinet/in.c Usys/netinet6/in6.c Updated to revision 244678 It seems like the ip6 for localhost is configured but ip4 isn't: Setting hostname: pozo.com. ifa_del_loopback_route: deletion failed: 3 ifconfig: ioctl (SIOCAIFADDR): File exists bge0: link state changed to DOWN ifa_del_loopback_route: deletion failed: 3 lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 nd6 options=21 From 244677: Setting hostname: pozo.com. Starting Network: lo0 bge0. lo0: flags=8049 metric 0 mtu 16384 options=63 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 nd6 options=21 Manfred || n...@pozo.com || || Ph. (415) 681-6235 || -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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"
Re: CFT: Overhauled CPSW driver for BeagleBone
On Jan 1, 2013, at 8:12 AM, Brett Wynkoop wrote: > On Mon, 31 Dec 2012 15:25:15 -0800 > Tim Kientzle wrote: > >> I've made some progress reworking the CPSW driver for >> BeagleBone and would appreciate any feedback: >> >> https://github.com/kientzle/cpsw >> > Greeting- > > The driver is working much better than the driver currently in head. I > have maintained an ssh connection to the BeagleBone for more than 24 > hours! Just committed this to -CURRENT r244939. Tim ___ 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"
Re: loopback interface broken on current
Maybe it's this commit? HTH, -Garrett r244678 | glebius | 2012-12-25 05:01:58 -0800 (Tue, 25 Dec 2012) | 17 lines The SIOCSIFFLAGS ioctl handler runs if_up()/if_down() that notify all interested parties in case if interface flag IFF_UP has changed. However, not only SIOCSIFFLAGS can raise the flag, but SIOCAIFADDR and SIOCAIFADDR_IN6 can, too. The actual |= is done not in the protocol code, but in code of interface drivers. To fix this historical layering violation, we will check whether ifp->if_ioctl(SIOCSIFADDR) raised the IFF_UP flag, and if it did, run the if_up() handler. This fixes configuring an address under CARP control on an interface that was initially !IFF_UP. P.S. I intentionally omitted handling the IFF_SMART flag. This flag was never ever used in any driver since it was introduced, and since it means another layering violation, it should be garbage collected instead of pretended to be supported. ___ 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"
Re: CFT: Overhauled CPSW driver for BeagleBone
On Mon, 31 Dec 2012 15:25:15 -0800 Tim Kientzle wrote: > I've made some progress reworking the CPSW driver for > BeagleBone and would appreciate any feedback: > > https://github.com/kientzle/cpsw > Greeting- The driver is working much better than the driver currently in head. I have maintained an ssh connection to the BeagleBone for more than 24 hours! Thanks so much Tim! -Brett -- wynk...@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6924 718-717-5435 ___ 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"
Re: CFT: Overhauled CPSW driver for BeagleBone
Greeting- This is a follow up to my previous private message about how your driver is working on my BeagleBone. wynkoop@beaglebone:~ % w 8:15PM up 15:17, 2 users, load averages: 0.05, 0.01, 0.00 USER TTY FROM LOGIN@ IDLE WHAT root u0 - 5:00AM 3:36 -csh (csh) wynkooppts/0cherry.wynn.com 2:05PM - w wynkoop@beaglebone:~ % date Mon Dec 31 20:15:13 EST 2012 wynkoop@beaglebone:~ % As you can see I am logged in on pts/0 since 2:05PM. I was never able to keep an ssh connection alive more than 30-40 min with the driver that is in head. I think you should check it into head now so people setting up new BBs get the benefit. As discussed off list there is still room for improvement, but I think that can be better handled if this much more stable driver goes into the tree sooner rather than later. It will allow for more testing and feedback to assist with the next round of improvements. This thing is running so well now that I am about to put a web server on the box and give it a static IP address. Once we have USB I think the BB will become my primary mail and web server..Think of the power I will save! -Brett -- wynk...@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6924 718-717-5435 ___ 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"
Re: loopback interface broken on current
On 1/1/2013 2:22 AM, Gleb Smirnoff wrote: > Manfred, > > On Thu, Dec 27, 2012 at 09:05:26AM -0800, Manfred Antar wrote: > M> For the past few days the loopback interface 127.0.0.1 is broken on > current. > M> The last good kernel that works for me is r244662: Mon Dec 24 06:43:07 > PST 2012 > M> Here are some of the errors from current today: > > Can you please track this down to the specific revision that made the > regression? The timeframe is samll, so binary search probably won't > take long time. > > nc -l 127.0.0.1 works for me on r244911 ___ 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"
[head tinderbox] failure on mips64/mips
TB --- 2013-01-01 16:38:04 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-01-01 16:38:04 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-01-01 16:38:04 - starting HEAD tinderbox run for mips64/mips TB --- 2013-01-01 16:38:04 - cleaning the object tree TB --- 2013-01-01 16:39:20 - /usr/local/bin/svn stat /src TB --- 2013-01-01 16:39:23 - At svn revision 244923 TB --- 2013-01-01 16:39:24 - building world TB --- 2013-01-01 16:39:24 - CROSS_BUILD_TESTING=YES TB --- 2013-01-01 16:39:24 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-01 16:39:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-01 16:39:24 - SRCCONF=/dev/null TB --- 2013-01-01 16:39:24 - TARGET=mips TB --- 2013-01-01 16:39:24 - TARGET_ARCH=mips64 TB --- 2013-01-01 16:39:24 - TZ=UTC TB --- 2013-01-01 16:39:24 - __MAKE_CONF=/dev/null TB --- 2013-01-01 16:39:24 - cd /src TB --- 2013-01-01 16:39:24 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Tue Jan 1 16:39:28 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue Jan 1 17:39:15 UTC 2013 TB --- 2013-01-01 17:39:15 - cd /src/sys/mips/conf TB --- 2013-01-01 17:39:15 - /usr/sbin/config -m ADM5120 TB --- 2013-01-01 17:39:15 - skipping ADM5120 kernel TB --- 2013-01-01 17:39:15 - cd /src/sys/mips/conf TB --- 2013-01-01 17:39:15 - /usr/sbin/config -m ALCHEMY TB --- 2013-01-01 17:39:15 - skipping ALCHEMY kernel TB --- 2013-01-01 17:39:15 - cd /src/sys/mips/conf TB --- 2013-01-01 17:39:15 - /usr/sbin/config -m AP91 TB --- 2013-01-01 17:39:15 - skipping AP91 kernel TB --- 2013-01-01 17:39:15 - cd /src/sys/mips/conf TB --- 2013-01-01 17:39:15 - /usr/sbin/config -m AP93 TB --- 2013-01-01 17:39:15 - skipping AP93 kernel TB --- 2013-01-01 17:39:15 - cd /src/sys/mips/conf TB --- 2013-01-01 17:39:15 - /usr/sbin/config -m AP94 TB --- 2013-01-01 17:39:15 - skipping AP94 kernel TB --- 2013-01-01 17:39:15 - cd /src/sys/mips/conf TB --- 2013-01-01 17:39:15 - /usr/sbin/config -m AP96 TB --- 2013-01-01 17:39:15 - skipping AP96 kernel TB --- 2013-01-01 17:39:15 - cd /src/sys/mips/conf TB --- 2013-01-01 17:39:15 - /usr/sbin/config -m AR71XX_BASE TB --- 2013-01-01 17:39:15 - skipping AR71XX_BASE kernel TB --- 2013-01-01 17:39:15 - cd /src/sys/mips/conf TB --- 2013-01-01 17:39:15 - /usr/sbin/config -m AR724X_BASE TB --- 2013-01-01 17:39:15 - skipping AR724X_BASE kernel TB --- 2013-01-01 17:39:15 - cd /src/sys/mips/conf TB --- 2013-01-01 17:39:15 - /usr/sbin/config -m AR91XX_BASE TB --- 2013-01-01 17:39:15 - skipping AR91XX_BASE kernel TB --- 2013-01-01 17:39:15 - cd /src/sys/mips/conf TB --- 2013-01-01 17:39:15 - /usr/sbin/config -m BERI_DE4_MDROOT TB --- 2013-01-01 17:39:15 - building BERI_DE4_MDROOT kernel TB --- 2013-01-01 17:39:15 - CROSS_BUILD_TESTING=YES TB --- 2013-01-01 17:39:15 - MAKEOBJDIRPREFIX=/obj TB --- 2013-01-01 17:39:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-01-01 17:39:15 - SRCCONF=/dev/null TB --- 2013-01-01 17:39:15 - TARGET=mips TB --- 2013-01-01 17:39:15 - TARGET_ARCH=mips64 TB --- 2013-01-01 17:39:15 - TZ=UTC TB --- 2013-01-01 17:39:15 - __MAKE_CONF=/dev/null TB --- 2013-01-01 17:39:15 - cd /src TB --- 2013-01-01 17:39:15 - /usr/bin/make -B buildkernel KERNCONF=BERI_DE4_MDROOT >>> Kernel build for BERI_DE4_MDROOT started on Tue Jan 1 17:39:15 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] awk -f /src/sys/tools/makeobjops.awk /src/sys/kern/linker_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/kern/serdev_if.m -h rm -f .newdep /obj/src/make.amd64/make -V CFILES_NOZFS -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/dev/ath -I/src/sys/dev/ath/ath_hal -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -I/src/sys/dev/cxgb -I/src/sys/dev/cxgbe -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=1 --param large-function-growth=10 --param max-inline-insns-single=1 -fno-pic -mno-abicalls -G0 -DKERNLOAD
Re: loopback interface broken on current
Manfred, On Thu, Dec 27, 2012 at 09:05:26AM -0800, Manfred Antar wrote: M> For the past few days the loopback interface 127.0.0.1 is broken on current. M> The last good kernel that works for me is r244662: Mon Dec 24 06:43:07 PST 2012 M> Here are some of the errors from current today: Can you please track this down to the specific revision that made the regression? The timeframe is samll, so binary search probably won't take long time. -- Totus tuus, Glebius. ___ 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"
Re: svn commit: r244604 - head/usr.sbin/gssd
On 12/31/12, Rick Macklem wrote: > Rick Macklem wrote: >> Rick Macklem wrote: >> > Garrett Cooper wrote: >> > > On Sun, Dec 30, 2012 at 4:49 PM, Rick Macklem >> > > >> > > wrote: >> > > > bf1783 wrote: >> > > >> >Author: rmacklem >> > > >> >Date: Sat Dec 22 23:21:17 2012 >> > > >> >New Revision: 244604 >> > > >> >URL: http://svnweb.freebsd.org/changeset/base/244604 >> > > >> This breaks world built WITHOUT_KERBEROS and WITH_GSSAPI. >> > > > Could you please test the attached patch. > Oh, and I've attached the updated patch, rick Your patch fixes the build problem. I leave it to you to decide whether, if gssd is so dependent upon the Kerberos mechanism support, it should be built at all when base system Kerberos isn't available. And also, if it is to be built, whether your additions should depend upon MK_KERBEROS_SUPPORT or MK_KERBEROS (the former is implied by the latter, but the converse isn't true). Thanks and Happy New Year, b. ___ 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"
Re: svn commit: r244604 - head/usr.sbin/gssd
On 1/1/13, b.f. wrote: > On 12/31/12, Rick Macklem wrote: >> Rick Macklem wrote: >>> Rick Macklem wrote: >>> > Garrett Cooper wrote: >>> > > On Sun, Dec 30, 2012 at 4:49 PM, Rick Macklem >>> > > >>> > > wrote: >>> > > > bf1783 wrote: >>> > > >> >Author: rmacklem >>> > > >> >Date: Sat Dec 22 23:21:17 2012 >>> > > >> >New Revision: 244604 >>> > > >> >URL: http://svnweb.freebsd.org/changeset/base/244604 > >>> > > >> This breaks world built WITHOUT_KERBEROS and WITH_GSSAPI. > >>> > > > Could you please test the attached patch. > >> Oh, and I've attached the updated patch, rick > > Your patch fixes the build problem. I leave it to you to decide > whether, if gssd is so dependent upon the Kerberos mechanism support, > it should be built at all when base system Kerberos isn't available. > And also, if it is to be built, whether your additions should depend > upon MK_KERBEROS_SUPPORT or MK_KERBEROS (the former is implied by the > latter, but the converse isn't true). Of course, I meant above that WITHOUT_KERBEROS_SUPPORT is implied by WITHOUT_KERBEROS, and that the converse isn't true. b. ___ 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"
