Can't build amd64 version from 9.0-p3 host
Hello all, I have some problem with building amd64 version of current, while having 9 host. # svn status ? kernel.log ? world.log ? kernel2.log # svn info Path: . Working Copy Root Path: /zstorage/testenv/sources/10-kms URL: http://svn.freebsd.org/base/head Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 237169 Node Kind: directory Schedule: normal Last Changed Author: alc Last Changed Rev: 237168 Last Changed Date: 2012-06-16 21:56:19 +0300 (sat, 16 jun 2012) end of world.log: -- World build completed on Sat Jun 16 21:50:03 EEST 2012 -- end of kernel.log: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions cc1: warnings being treated as errors /zstorage/testenv/sources/10-kms/sys/modules/ath/../../dev/ath/if_ath.c: In function 'ath_attach': /zstorage/testenv/sources/10-kms/sys/modules/ath/../../dev/ath/if_ath.c:666: warning: format '%d' expects type 'int', but argument 4 has type 'long unsigned int' [-Wformat] *** Error code 1 Any help? -- Regards, Alexander Yerenkow ___ 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: Can't build amd64 version from 9.0-p3 host
On Mon, Jun 18, 2012 at 12:28 AM, Alexander Yerenkow yeren...@gmail.com wrote: Hello all, I have some problem with building amd64 version of current, while having 9 host. # svn status ? kernel.log ? world.log ? kernel2.log # svn info Path: . Working Copy Root Path: /zstorage/testenv/sources/10-kms URL: http://svn.freebsd.org/base/head Repository Root: http://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 237169 Node Kind: directory Schedule: normal Last Changed Author: alc Last Changed Rev: 237168 Last Changed Date: 2012-06-16 21:56:19 +0300 (sat, 16 jun 2012) end of world.log: -- World build completed on Sat Jun 16 21:50:03 EEST 2012 -- end of kernel.log: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions cc1: warnings being treated as errors /zstorage/testenv/sources/10-kms/sys/modules/ath/../../dev/ath/if_ath.c: In function 'ath_attach': /zstorage/testenv/sources/10-kms/sys/modules/ath/../../dev/ath/if_ath.c:666: warning: format '%d' expects type 'int', but argument 4 has type 'long unsigned int' [-Wformat] *** Error code 1 Any help? Update and try again (these warnings were fixed between the checkout date and now). Cheers, -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: PORTS_MODULES
Howdy, This is an FYI to let people know about a really nice feature for those that have ports installed which include kernel modules. You can place a list in /etc/src.conf like this: PORTS_MODULES= emulators/virtualbox-ose-kmod sysutils/fusefs-kmod x11/nvidia-driver which will cause those modules to be built and installed with all the proper matching stuff at the same time as buildkernel and installkernel. This feature has existed for a while, but has had issues. Thanks to a team effort it's a lot more robust now, and ready for prime time (in HEAD, and the -STABLE branches for now, soon to be in 9.1-RELEASE). Enjoy, Doug nice! does it also work when cross-compiling? ie, using an amd64-freebsd-8.3 kernel to compile for i386-freebsd-8.2 thanks, danny ___ 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: PORTS_MODULES
On Mon, Jun 18, 2012 at 12:40 AM, Daniel Braniss da...@cs.huji.ac.il wrote: Howdy, This is an FYI to let people know about a really nice feature for those that have ports installed which include kernel modules. You can place a list in /etc/src.conf like this: PORTS_MODULES= emulators/virtualbox-ose-kmod sysutils/fusefs-kmod x11/nvidia-driver which will cause those modules to be built and installed with all the proper matching stuff at the same time as buildkernel and installkernel. This feature has existed for a while, but has had issues. Thanks to a team effort it's a lot more robust now, and ready for prime time (in HEAD, and the -STABLE branches for now, soon to be in 9.1-RELEASE). Enjoy, Doug nice! does it also work when cross-compiling? ie, using an amd64-freebsd-8.3 kernel to compile for i386-freebsd-8.2 In theory, yes, however some of the environment required to bootstrap some ports might be missing, depending on how the ports module pokes around for data in /usr/src, etc. 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: ath(4) now defaults to 802.11n on GENERIC/i386 and GENERIC/amd64
On Fri, Jun 15, 2012 at 4:57 PM, Adrian Chadd adr...@freebsd.org wrote: On 15 June 2012 05:23, Monthadar Al Jaberi montha...@gmail.com wrote: But I am having a problem with athsurvey which is just reporting: min avg max tx% rx% bc% ec% tx% rx% bc% ec% tx% rx% bc% ec% (100.0 100.0 100.0 100.0) ( 0.0 0.0 0.0 0.0) ( 0.0 0.0 0.0 0.0) (100.0 100.0 100.0 100.0) ( 0.0 0.0 0.0 0.0) ( 0.0 0.0 0.0 0.0) Ah. AR5416 and later only. :) so sad :( is it a limitation of 5414? (Yes FreeBSD thinks its 5413, but on the chip it says 5414A-001 :P) athdebug is returning with: athdebug: sysctl-get(dev.ath.0.debug): Cannot allocate memory No ATH_DEBUG? Are you building a module? No its built in in the kernel, This is my kernel: # # AR71XX -- Kernel configuration file for FreeBSD/MIPS for Atheros 71xx systems # # This includes all the common drivers for the AR71XX boards along with # the usb, net80211 and atheros driver code. # # $FreeBSD$ # machine mips mips ident AR71XX_BASE cpu CPU_MIPS4KC makeoptions KERNLOADADDR=0x8005 options HZ=1000 options HWPMC_HOOKS files ../atheros/files.ar71xx # For now, hints are per-board. hints AR71XX_BASE.hints makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols # Build these as modules so small platform builds will have the # modules already built. makeoptions MODULES_OVERRIDE=random gpio ar71xx if_gif if_gre if_bridge bridgestp usb wlan wlan_xauth wlan_acl wlan_wep wlan_tkip wlan_ccmp wlan_rssadapt wlan_amrr ath ath_pci options DDB options KDB options SCHED_4BSD #4BSD scheduler options INET#InterNETworking options INET6 # IPv6 # options NFS_CL #Network Filesystem Client options PSEUDOFS#Pseudo-filesystem framework options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions # options NFS_LEGACYRPC # Debugging for use in -current options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_SKIPSPIN options DEBUG_REDZONE options DEBUG_MEMGUARD options FFS #Berkeley Fast Filesystem # options SOFTUPDATES #Enable FFS soft updates support # options UFS_ACL #Support for access control lists # options UFS_DIRHASH #Improve performance on big directories # options MSDOSFS # Read MSDOS filesystems; useful for USB/CF device pci device ar71xx_pci # 802.11 framework options IEEE80211_DEBUG options IEEE80211_ALQ options IEEE80211_SUPPORT_MESH # This option is currently broken for if_ath_tx. options IEEE80211_SUPPORT_TDMA options IEEE80211_AMPDU_AGE device wlan# 802.11 support device wlan_wep# 802.11 WEP support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support device wlan_xauth # 802.11 hostap support # Atheros wireless NICs device ath # Atheros interface support device ath_pci # Atheros PCI/Cardbus bus options ATH_DEBUG options ATH_DIAGAPI options ATH_ENABLE_11N options AH_DEBUG options AH_DEBUG_ALQ options ALQ device ath_hal option AH_SUPPORT_AR5416 device ath_rate_sample option AH_RXCFG_SDMAMW_4BYTES option AH_AR5416_INTERRUPT_MITIGATION # There's no DFS radar detection support yet so this won't actually # detect radars. It however does enable the rest of the channel change # machinery so DFS can be debugged. option ATH_ENABLE_DFS device mii device arge device usb options USB_EHCI_BIG_ENDIAN_DESC# handle big-endian byte order options USB_DEBUG options USB_HOST_ALIGN=32 # AR71XX (MIPS in general?) requires this device ehci device scbus device umass device da # On-board SPI flash device spibus device ar71xx_spi device mx25l device ar71xx_wdog device uart device loop device ether device md device bpf device random device if_bridge device gif # ip[46] in ip[46] tunneling protocol device gre # generic encapsulation - only for IPv4 in IPv4 though atm options ARGE_DEBUG # Enable if_arge debugging for now # Enable GPIO device gpio device gpioled adrian -- Monthadar Al Jaberi ___ freebsd-current@freebsd.org mailing
Re: ath(4) now defaults to 802.11n on GENERIC/i386 and GENERIC/amd64
Hi, The AR5414 should support it. I just havent implemented the same changes in the ar5212 HAL. Look at ar5416_ani.c and ar5212_ani.c. adrian ___ 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
drm2 and the kernel messages on shutdown
Good day, since switching to new drm code (starting at April if I recall correctly) I'm experiencing sporadic laptop hangs when choose the shutdown command in UI (gnome) environment. The hdd led isn't blinking but the laptop is still up. In such cases I forced to shutdown it by pressing power off button, but at the next system start it running filesystem checks (yes, with journal but some time only full fsck is able to fix that). What I'm asking for is - when there some sysctl or boot loader option will be available to turn on kernel messages on shutdown? I really want to know on what it hanging on. I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. PS. I'm now subscribed to current@. So do not need to approve my previous message, that's waiting for moderator approval. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: csup ends up in sigwai after Shutting down connection to server, never exits
On Thu, Jun 14, 2012 at 12:15:05PM +0100, Anton Shterenlikht wrote:
On Thu, Jun 14, 2012 at 11:57:38AM +0100, Anton Shterenlikht wrote:
On ia64 r235474 and r235163 I get:
# csup -L2 /root/ports-supfile
Parsing supfile /root/ports-supfile
Connecting to cvsup.uk.FreeBSD.org
Connected to 131.111.8.41
Server software version: SNAP_16_1h
MD5 authentication started
MD5 authentication successful
Negotiating file attribute support
Exchanging collection information
Establishing multiplexed-mode data connection
Running
Updating collection ports-all/cvs
Shutting down connection to server
csup never exits.
From top:
PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND
33822 root 2 200 37496K 23352K sigwai 1 0:32 0.00% csup
On amd64 r236740M I don't see this problem.
Just to update - I don't see this problem on ia64 r231193M.
It seems the only relevant change in usr.bin/csup since then was:
Index: usr.bin/csup/auth.c
===
--- usr.bin/csup/auth.c (revision 231193)
+++ usr.bin/csup/auth.c (working copy)
@@ -293,7 +293,7 @@
gettimeofday(tv, NULL);
pid = getpid();
ppid = getppid();
- srand(tv.tv_usec ^ tv.tv_sec ^ pid);
+ srandom(tv.tv_usec ^ tv.tv_sec ^ pid);
addrlen = sizeof(laddr);
error = getsockname(config-socket, (struct sockaddr *)laddr,
addrlen);
if (error 0) {
I was thinking of doing a binary search for this,
but realised that I'd have to build/install world,
not just kernel, right? This will take a *long* time.
Shall I submit a PR for this?
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
___
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: drm2 and the kernel messages on shutdown
В Mon, 18 Jun 2012 12:35:33 +0400 Ruslan Mahmatkhanov cvs-...@yandex.ru пишет: Good day, since switching to new drm code (starting at April if I recall correctly) I'm experiencing sporadic laptop hangs when choose the shutdown command in UI (gnome) environment. The hdd led isn't blinking but the laptop is still up. In such cases I forced to shutdown it by pressing power off button, but at the next system start it running filesystem checks (yes, with journal but some time only full fsck is able to fix that). What I'm asking for is - when there some sysctl or boot loader option will be available to turn on kernel messages on shutdown? I really want to know on what it hanging on. I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. PS. I'm now subscribed to current@. So do not need to approve my previous message, that's waiting for moderator approval. Dear Ruslan. Your problems hang your laptop is not associated with the transition to drm2. And you can see this - when the downgrade to the SVN revision r236313 Your problems are now committing to this http://svnweb.freebsd.org/base?view=revisionrevision=236317 You can check it and make sure my right. Good luck ___ 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: drm2 and the kernel messages on shutdown
Ruslan Mahmatkhanov cvs-...@yandex.ru writes: Hi, I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. As stated in the wiki page, syscons is not integrated with kms atm, so you need a serial console to get system messages. http://wiki.freebsd.org/Intel_GPU Éric Masson -- AB Pourquoi proposer une réforme si c'est pour affirmer qu'elle ne AB changera rien ? Pour mettre un frein définitif à l'immobilisme. -+-SP in http://www.le-gnu.net - Tout changer pour que rien ne bouge-+- ___ 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: drm2 and the kernel messages on shutdown
Ivan Klymenko wrote on 18.06.2012 13:02: В Mon, 18 Jun 2012 12:35:33 +0400 Ruslan Mahmatkhanov cvs-...@yandex.ru пишет: Good day, since switching to new drm code (starting at April if I recall correctly) I'm experiencing sporadic laptop hangs when choose the shutdown command in UI (gnome) environment. The hdd led isn't blinking but the laptop is still up. In such cases I forced to shutdown it by pressing power off button, but at the next system start it running filesystem checks (yes, with journal but some time only full fsck is able to fix that). What I'm asking for is - when there some sysctl or boot loader option will be available to turn on kernel messages on shutdown? I really want to know on what it hanging on. I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. PS. I'm now subscribed to current@. So do not need to approve my previous message, that's waiting for moderator approval. Dear Ruslan. Your problems hang your laptop is not associated with the transition to drm2. And you can see this - when the downgrade to the SVN revision r236313 Your problems are now committing to this http://svnweb.freebsd.org/base?view=revisionrevision=236317 You can check it and make sure my right. Good luck Thanks Ivan, I'll check it out. But the request in subject line is still valid for me, because the current state make me feels like.. uhmm.. a blind kitten :) -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: drm2 and the kernel messages on shutdown
Eric Masson wrote on 18.06.2012 13:08: Ruslan Mahmatkhanov cvs-...@yandex.ru writes: Hi, I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. As stated in the wiki page, syscons is not integrated with kms atm, so you need a serial console to get system messages. http://wiki.freebsd.org/Intel_GPU Éric Masson Ok, but in the earlier revision of this page or in some heads-up message in mailing list there was a note about that, that kernel messages are disabled just for development convenience, so this is main reason why I ever asked that. So, since there is some technical restriction about that, I would to shut up and wait. Thanks. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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
drm2 and the kernel messages on shutdown
Good day, since switching to new drm code (starting at April if I recall correctly) I'm experiencing sporadic laptop hangs when choose the shutdown command in UI (gnome) environment. The hdd led isn't blinking but the laptop is still up. In such cases I forced to shutdown it by pressing power off button, but at the next system start it running filesystem checks (yes, with journal but some time only full fsck is able to fix that). What I'm asking for is - when there some sysctl or boot loader option will be available to turn on kernel messages on shutdown? I really want to know on what it hanging on. I didn't bothered with this while it was available as third-party patch, but since it is now in -current and enabled by default, I think this feature should be available. Thanks. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: est man page
On Wed, 2012-06-13 at 11:06 -0700, Sean Bruno wrote: se http://people.freebsd.org/~sbruno/est_man.txt Looks good. Attached a diff for some small fixes. Updated again with feedback that I've gotten. I changed the Note that est interface is automatically loaded to Note that est capabilities are automatically loaded Sean Committed at svn r237245 ... Sean ___ 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: ath(4) now defaults to 802.11n on GENERIC/i386 and GENERIC/amd64
Hi,
On Fri, 15 Jun 2012 01:17:31 -0700
Adrian Chadd adr...@freebsd.org wrote:
Hi,
I've flipped on ATH_ENABLE_11N and the interrupt mitigation in i386
and amd64 GENERIC.
I'll flip it on on PPC when someone (chmee?) verifies that 802.11n
works on PPC.
I did my duty as PPC guinea pig, and can happily say that unlike other
cards *cough*bw{i,n},wi*cough* I can actually use ath on my PowerBook.
AR5416, about as stable as I've seen so far. I think you can flip it
on PPC now.
It's still delicate. I still don't know if RTS/CTS HT frame protection
is working quite right on all chips. But all the basics are there
(software TX aggregation, RX AMPDU reordering in net80211, BAR
transmission, software queue pause and unpause, frame retransmission.)
Don't be surprised if your 802.11n mobile devices perform poorly as
the power queue handling is very broken and will result in all kinds
of weird traffic stalls if things are too aggressive. I'll look into
fixing that soon.
If you have problems, please read the wiki article:
http://wiki.freebsd.org/dev/ath(4) - specifically the bits where I
tell you to compile with the debugging and diagnostic stuff in your
-HEAD kernel, including the HAL/driver diagnostic APIs and tools.
Enjoy,
Adrian
If I can reproduce that crash I mentioned on IRC, I'll post what I can
about it.
- Justin
___
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
