Re: USB Keyboard not worked on current (r251681)
In attach file with dmesg log and usb debug enabled. Maybe it's help? Ryan Stone wrote: RS I am able to reproduce this on a Supermicro X8-something that I have. A RS git bisect took me down a strange path into a /projects branch. It is RS possible the branch got a bad merge from -CURRENT at one point; I'm still RS trying to narrow down where things went wrong (and even whether the branch RS is actually responsible or whether git got confused by the svn-git export RS process). RS ___ RS freebsd-current@freebsd.org mailing list RS http://lists.freebsd.org/mailman/listinfo/freebsd-current RS To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #2 r251990: Wed Jun 19 12:27:14 EEST 2013 r...@fmst-test.ukr.net:/usr/obj/usr/src/sys/ZEBRA amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz (2400.06-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206d7 Family = 0x6 Model = 0x2d Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x1fbee3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX AMD Features=0x2c100800SYSCALL,NX,Page1GB,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 137438953472 (131072 MB) avail memory = 128714944512 (122752 MB) Event timer LAPIC quality 600 ACPI APIC Table: ALASKA A M I FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 cpu4 (AP): APIC ID: 32 cpu5 (AP): APIC ID: 34 cpu6 (AP): APIC ID: 36 cpu7 (AP): APIC ID: 38 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: WIPRO8 WIPROSVR on motherboard acpi0: Power Button (fixed) acpi0: reservation of 400, 100 (3) failed cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 cpu4: ACPI CPU on acpi0 cpu5: ACPI CPU on acpi0 cpu6: ACPI CPU on acpi0 cpu7: ACPI CPU on acpi0 attimer0: AT timer port 0x40-0x43 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 Event timer RTC frequency 32768 Hz quality 0 hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 950 Event timer HPET frequency 14318180 Hz quality 550 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 26 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 26 at device 1.1 on pci0 pci2: ACPI PCI bus on pcib2 igb0: Intel(R) PRO/1000 Network Connection version - 2.3.10 port 0x8020-0x803f mem 0xdfa2-0xdfa3,0xdfa44000-0xdfa47fff irq 27 at device 0.0 on pci2 igb0: Using MSIX interrupts with 9 vectors igb0: Ethernet address: 00:25:90:91:e6:44 igb0: Bound queue 0 to cpu 0 igb0: Bound queue 1 to cpu 1 igb0: Bound queue 2 to cpu 2 igb0: Bound queue 3 to cpu 3 igb0: Bound queue 4 to cpu 4 igb0: Bound queue 5 to cpu 5 igb0: Bound queue 6 to cpu 6 igb0: Bound queue 7 to cpu 7 igb1: Intel(R) PRO/1000 Network Connection version - 2.3.10 port 0x8000-0x801f mem 0xdfa0-0xdfa1,0xdfa4-0xdfa43fff irq 30 at device 0.1 on pci2 igb1: Using MSIX interrupts with 9 vectors igb1: Ethernet address: 00:25:90:91:e6:45 igb1: Bound queue 0 to cpu 0 igb1: Bound queue 1 to cpu 1 igb1: Bound queue 2 to cpu 2 igb1: Bound queue 3 to cpu 3 igb1: Bound queue 4 to cpu 4 igb1: Bound queue 5 to cpu 5 igb1: Bound queue 6 to cpu 6 igb1: Bound queue 7 to cpu 7 pcib3: ACPI PCI-PCI bridge irq 32 at device 2.0 on pci0 pci4: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge irq 40 at device 3.0 on pci0 pci5: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 40 at device 3.2 on pci0 pci6: ACPI PCI bus on pcib5 pci0: base peripheral at device 4.0 (no driver attached) pci0: base peripheral at device 4.1 (no driver attached) pci0: base peripheral at device 4.2 (no driver attached) pci0: base peripheral at device 4.3 (no driver attached) pci0: base peripheral at device 4.4 (no driver attached) pci0: base peripheral at device 4.5 (no driver attached) pci0: base peripheral at device 4.6
Re: Atom N450 + C3 + HPET == bad timer behaviour
On 21.06.2013 04:02, Adrian Chadd wrote: On 20 June 2013 16:45, Adrian Chadd adr...@freebsd.org wrote: Hi, I'm having issues with HPET + C3 state on this Atom N450 based netbook. This is (shocking, I know!) running -HEAD (r251605.) If I use C2, HPET is fine. If I use RTC, i8254, LAPIC, C3 is also fine. LAPIC use probably disables C3 usage automatically there. RTC and i8254 use only periodic modes and so system will wakeup with at least HZ rate, so it is hard to say whether C3 will be used. But C3 + HPET results in multi-second pauses where it should be 1 second. What timecounter are you using? Have you tried to check what is going on in that moment: timecounter stoped, eventttimer interrupt losd or system is completely stuck somehow? I've disabled powerd and verified that dev.cpu.0.freq=1667; so it's not CPU frequency related. Doug found this: apparently SMI + timer fondling doesn't quite work out? http://lkml.indiana.edu/hypermail/linux/kernel/1102.3/00842.html SMI is a black box that can give us any kind of unexpected surprises. Theoretically there could be number of scenarios: HPET counter or comparator values corrupted by SMI code (not sure we can protect), SMI code can open race window on HPET comparator programming (that should be handled now), SMI code can have own bugs triggered by some specific HPET usage pattern (not our area). .. and the resolution: http://lkml.indiana.edu/hypermail/linux/kernel/1102.3/00957.html clockevents: Prevent oneshot mode when broadcast device is periodic When the per cpu timer is marked CLOCK_EVT_FEAT_C3STOP, then we only can switch into oneshot mode, when the backup broadcast device supports oneshot mode as well. Otherwise we would try to switch the broadcast device into an unsupported mode unconditionally. This went unnoticed so far as the current available broadcast devices support oneshot mode. Seth unearthed this problem while debugging and working around an hpet related BIOS wreckage. Add the necessary check to tick_is_oneshot_available(). does that help? That looks more like workaround for Linux-specific issue. Linux can use different timers hardware when CPU is active and when in deep sleep, and, as I understand from description, it tried to improperly use one of devices. Our code doesn't have that magic. Also I think this fix fixes not the original problem, but different one they've found during debugging. HPET always has ONESHOT capability, so this check is irrelevant when it is used as a broadcast device. -- Alexander Motin ___ 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: Compilation issue due to 251982
Hi,
Anyone got idea how to fix this compilation issue?
Regards,
Alie T
On Wed, Jun 19, 2013 at 12:08 PM, Alie Tan a...@affle.com wrote:
http://freshbsd.org/commit/freebsd/r251982
=== usr.bin (cleandir)
Makefile, line 370: Malformed conditional (${MK_SVN} == yes ||
${MK_SVNLITE} == yes)
Makefile, line 373: if-less endif
make: fatal errors encountered -- cannot continue
*** [usr.bin.cleandir__D] Error code 1
Stop in /usr/src.
*** [_cleanobj] Error code 1
Stop in /usr/src.
*** [kernel-toolchain] Error code 1
Stop in /usr/src.
___
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][panic] Running XOrg with SNA enabled causes system panic after few hours on G33
Unfortunately log is empty as a well as a lot of user files :( because of fsck. On Friday 21 June 2013 01:45:33 Oleg Sidorkin wrote: Check the logs for messages that can help to investigate the problem. If there is nothing helpful, I have no idea but to configure a serial console 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-current-unsubscr...@freebsd.org
Re: gpart: can not add MBR partitions with gpart add -t, mbr
Hi, When I refer to gpart(8) manpage (9.1 release, updated jan 25,2013), I find the description of partition types a bit confusing. Considering the case of a MoBo with old way Bios (non UEFI), the only scheme allowed to get a bootable system is MBR. (Note that after booting, your OS is able to manage gpt-scheme on different providers.) Then, if you speak bsd-ish, you are able to add on the MBR-scheme provider up to 4 freebsd-type slices, each of them containing up to 8 partitions with a BSD filesystem (or swap space). Or, if you speak msdos-ish, you would be able to add on the MBR provider up to 4 msdos-type partitions (or 3 + 1 extended ), each of them containing one filesystem. The manpage does'nt list explicitly the type for this second case; Oliver try to use mbr, decribed as A partition that is sub-partitioned by a Master Boot Record (MBR). This type is known as !024dee41-33e7-11d3-9d69-0008c781f39f by GPT.. Such definition is'nt very explicit. Let me show the example below on my provider ada0 : $ gpart show = 63 976773105 ada0 MBR (465G) 63 136314864 1 freebsd [active] (65G) 136314927 840458241- free - (400G) =0 136314864 ada0s1 BSD (65G) 08388608 1 freebsd-ufs (4.0G) 8388608 16777216 2 freebsd-swap (8.0G) 25165824 16777216 4 freebsd-ufs (8.0G) 419430408388608 5 freebsd-ufs (4.0G) 50331648 85983215 6 freebsd-ufs (41G) 136314863 1 - free - (512B) $ sudo gpart add -t mbr -i 2 -s 8G ada0 Password: gpart: Invalid argument $ sudo gpart add -t \!12 -i 2 -s 8G ada0 ada0s2 added $ $ sudo newfs_msdos ada0s2 /dev/ada0s2: 16773056 sectors in 262079 FAT32 clusters (32768 bytes/cluster) BytesPerSec=512 SecPerClust=64 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=63 Heads=16 HiddenSecs=0 HugeSectors=16777215 FATsecs=2048 RootCluster=2 FSInfo=1 Backup=2 $ sudo gpart add -t freebsd -i 3 -s 8G ada0 ada0s3 added $ gpart show ada0 = 63 976773105 ada0 MBR (465G) 63 136314864 1 freebsd [active] (65G) 136314927 16777215 2 !12 (8G) 153092142 16777215 3 freebsd (8G) 169869357 806903811- free - (384G) $ sudo newfs_msdos ada0s3 /dev/ada0s3: 16773056 sectors in 262079 FAT32 clusters (32768 bytes/cluster) BytesPerSec=512 SecPerClust=64 ResSectors=32 FATs=2 Media=0xf0 SecPerTrack=63 Heads=16 HiddenSecs=0 HugeSectors=16777215 FATsecs=2048 RootCluster=2 FSInfo=1 Backup=2 $ this example show that, if you want a msdos or fat32 partition, both the type \!12 or freebsd allows you to create a partition where you could install a msdos filesystem (but the mbr does not). Such behaviour is not surprising, (using freebsd-type to format as msdos means you don't use the space allowed for labeling); but what is really the purpose of the listed mbr-type in the gpart(8) manpage? Cheers Roger ___ 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: gpart: can not add MBR partitions with gpart add -t, mbr
On Fri, Jun 21, 2013 at 8:08 AM, Genre Roger genre.ro...@orange.fr wrote: Hi, When I refer to gpart(8) manpage (9.1 release, updated jan 25,2013), I find the description of partition types a bit confusing. Considering the case of a MoBo with old way Bios (non UEFI), the only scheme allowed to get a bootable system is MBR. (Note that after booting, your OS is able to manage gpt-scheme on different providers.) You can boot off GPT partitions using the PMBR bootcode (gpart -b /boot/pmbr ada0) on just about any system. I was booting my P4 running FreeBSD 8.something off a GPT-partitioned USB stick for over a year (maybe 2?) before converting it to PC-BSD 9.1 booting off a ZFS dual-mirror pool (also using GPT partitioned disks). Can't speak to the rest of your post. I only use gpart for GPT partitioned disks, and use fdisk/bsdlabel for non-GPT partitioned disks. -- Freddie Cash fjwc...@gmail.com ___ 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: gpart: can not add MBR partitions with gpart add -t, mbr
Hi, You're right on the ability to boot off a gpt partition, with a non-uefi bios. Sorry for the noise concerning that point. Cheers Roger ___ 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
usb ACM device doesn't work
Hi I bought a relay control board that has a USB interface. It presents a serial port to Linux on /dev/ttyACMx. However when I plug it into my FreeBSD host, it detects as follows: ugen0.2: KMT at usbus0 umodem0: KMT USB CDC COM, class 2/0, rev 1.10/1.00, addr 1 on usbus0 umodem0: data interface 1, has no CM over data, has no break and I cannot communicate with it. Any ideas how to communicate with it? This is the output of 'usbconfig -d ugen0.2 dump_curr_config_desc': ugen0.2: USB CDC COM KMT at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0043 bNumInterfaces = 0x0002 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00c0 bMaxPower = 0x Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0002 bInterfaceSubClass = 0x0002 bInterfaceProtocol = 0x0001 iInterface = 0x no string Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x05, 0x24, 0x00, 0x10, 0x01 Additional Descriptor bLength = 0x04 bDescriptorType = 0x24 bDescriptorSubType = 0x02 RAW dump: 0x00 | 0x04, 0x24, 0x02, 0x02 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x06 RAW dump: 0x00 | 0x05, 0x24, 0x06, 0x00, 0x01 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x01 RAW dump: 0x00 | 0x05, 0x24, 0x01, 0x00, 0x01 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 IN bmAttributes = 0x0003 INTERRUPT wMaxPacketSize = 0x0008 bInterval = 0x00fa bRefresh = 0x bSynchAddress = 0x Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x000a bInterfaceSubClass = 0x bInterfaceProtocol = 0x iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 OUT bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0040 bInterval = 0x0001 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0040 bInterval = 0x0001 bRefresh = 0x bSynchAddress = 0x Ian -- Ian Freislich ___ 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: Kernel build fails on ARM: Cannot fork: Cannot allocate memory
On 21.06.2013 01:56, Jeff Roberson wrote:
On Thu, 20 Jun 2013, Jeff Roberson wrote:
On Wed, 19 Jun 2013, Zbyszek Bodek wrote:
Hello,
I've been trying to compile the kernel on my ARMv7 platform using the
sources from the current FreeBSD HEAD.
make buildkernel . -j5
1/2 builds fails in the way described below:
--
ing-include-dirs -fdiagnostics-show-option -nostdinc -I.
-I/root/src/freebsd-arm-superpages/sys
-I/root/src/freebsd-arm-superpages/sys/contrib/altq
-I/root/src/freebsd-arm-superpages/sys/contrib/libfdt -D_KERNEL
-DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common
-finline-limit=8000 --param inline-unit-growth=100 --param
large-function-growth=1000 -mno-thumb-interwork -ffreestanding -Werror
/root/src/freebsd-arm-superpages/sys/ufs/ffs/ffs_snapshot.c
Cannot fork: Cannot allocate memory
*** [ffs_snapshot.o] Error code 2
1 error
*** [buildkernel] Error code 2
1 error
*** [buildkernel] Error code 2
1 error
5487.888u 481.569s 7:35.65 1310.0% 1443+167k 1741+5388io 221pf+0w
--
The warning from std err is:
--
vm_thread_new: kstack allocation failed
vm_thread_new: kstack allocation failed
--
I was trying to find out which commit is causing this (because I was
previously working on some older revision) and using bisect I got to:
--
Author: jeff j...@freebsd.org
Date: Tue Jun 18 04:50:20 2013 +
Refine UMA bucket allocation to reduce space consumption and improve
performance.
- Always free to the alloc bucket if there is space. This gives
LIFO
allocation order to improve hot-cache performance. This also
allows
for zones with a single bucket per-cpu rather than a pair if the
entire
working set fits in one bucket.
- Enable per-cpu caches of buckets. To prevent recursive bucket
allocation one bucket zone still has per-cpu caches disabled.
- Pick the initial bucket size based on a table driven maximum size
per-bucket rather than the number of items per-page. This gives
more sane initial sizes.
- Only grow the bucket size when we face contention on the zone
lock, this
causes bucket sizes to grow more slowly.
- Adjust the number of items per-bucket to account for the header
space.
This packs the buckets more efficiently per-page while making them
not quite powers of two.
- Eliminate the per-zone free bucket list. Always return buckets
back
to the bucket zone. This ensures that as zones grow into larger
bucket sizes they eventually discard the smaller sizes. It
persists
fewer buckets in the system. The locking is slightly trickier.
- Only switch buckets in zalloc, not zfree, this eliminates
pathological
cases where we ping-pong between two buckets.
- Ensure that the thread that fills a new bucket gets to allocate
from
it to give a better upper bound on allocation time.
Sponsored by:EMC / Isilon Storage Division
--
I checked this several times and this commits seems to be causing this.
Can you tell me how many cores and how much memory you have? And
paste the output of vmstat -z when you see this error.
You can try changing bucket_select() at line 339 in uma_core.c to read:
static int
bucket_select(int size)
{
return (MAX(PAGE_SIZE / size, 1));
}
This will approximate the old bucket sizing behavior.
Just to add some more information; On my machine with 16GB of ram the
handful of recent UMA commits save about 20MB of kmem on boot. There
are 30% fewer buckets allocated. And all of the malloc zones have
similar amounts of cached space. Actually the page size malloc bucket
is taking up much less space.
I don't know if the problem is unique to arm but I have tested x86
limited to 512MB of ram without trouble. I will need the stats I
mentioned before to understand what has happened.
Hello Jeff,
Thank you for your interest in my problem.
My system is a quad-core ARMv7 with 2048 MB of RAM on board.
Please see attachment for the output from vmstat -z when the error occurs.
Changing bucket_select() to
static int
bucket_select(int size)
{
return (MAX(PAGE_SIZE / size, 1));
}
as you suggested helps for the problem. I've performed numerous attempts
to build the kernel and none of them failed.
Best regards
Zbyszek Bodek
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
Re: conf/178611: [patch] daily_status_security_inline broken in 450.status-security
All, I'd like to add some additional detail for /etc/periodic/daily/450.status-security not working properly in all use cases in PR conf/178611. After looking a bit closer at other versions, I noticed that FreeBSD 10-CURRENT is also affected along with the 9.1-RELEASE that I use and mentioned in the PR. Both versions can be fixed up the the patch in the PR. The latest 8.4-RELEASE still uses the old way of doing things with an explict rc=3 statement at the end so that output never gets masked. Best regards, Jason Unovitch smime.p7s Description: S/MIME Cryptographic Signature
[panic] swi4 page fault (ip_slowtimo())
Hi, I have the following kgdb session from a page fault seemingly triggered in pf(4). I realize the -CURRENT is about a month old, but I cannot find any commits that seem relevant to this area of the code. I am happy to dig further and provide any information that is requested. Glen Script started on Fri Jun 21 19:57:21 2013 root@orion:/usr/obj/usr/src/sys/ORION # uname -a FreeBSD orion 10.0-CURRENT FreeBSD 10.0-CURRENT #10 r250476: Fri May 10 16:29:54 EDT 2013 root@orion:/usr/obj/usr/src/sys/ORION amd64 root@orion:/usr/obj/usr/src/sys/ORION # kgdb ./kernel.debug /var/crash/vmcore.8 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x11 fault code = supervisor read data, page not present instruction pointer = 0x20:0x80772688 stack pointer = 0x28:0xff800026da20 frame pointer = 0x28:0xff800026da40 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (swi4: clock) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0x80676a46 at kdb_backtrace+0x66 #1 0x8063ae6b at panic+0x13b #2 0x80918ba0 at trap_fatal+0x290 #3 0x80918f11 at trap_pfault+0x221 #4 0x809194c4 at trap+0x344 #5 0x80902c53 at calltrap+0x8 #6 0x806a29ce at pfslowtimo+0x2e #7 0x80651476 at softclock_call_cc+0x106 #8 0x80651b09 at softclock+0xa9 #9 0x8060c06d at intr_event_execute_handlers+0xfd #10 0x8060d81b at ithread_loop+0x9b #11 0x80608c1f at fork_exit+0x11f #12 0x8090317e at fork_trampoline+0xe Uptime: 42d1h53m40s (ada0:ahcich0:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00 (ada0:ahcich0:0:0:0): CAM status: CCB request is in progress (ada0:ahcich0:0:0:0): Error 5, Retries exhausted (ada0:ahcich0:0:0:0): Synchronize cache failed (ada1:ahcich1:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00 (ada1:ahcich1:0:0:0): CAM status: CCB request is in progress (ada1:ahcich1:0:0:0): Error 5, Retries exhausted (ada1:ahcich1:0:0:0): Synchronize cache failed (ada2:ahcich4:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00 (ada2:ahcich4:0:0:0): CAM status: CCB request is in progress (ada2:ahcich4:0:0:0): Error 5, Retries exhausted (ada2:ahcich4:0:0:0): Synchronize cache failed (ada3:ahcich5:0:0:0): FLUSHCACHE48. ACB: ea 00 00 00 00 40 00 00 00 00 00 00 (ada3:ahcich5:0:0:0): CAM status: CCB request is in progress (ada3:ahcich5:0:0:0): Error 5, Retries exhausted (ada3:ahcich5:0:0:0): Synchronize cache failed Dumping 2263 out of 6048 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91% Reading symbols from /boot/kernel/zfs.ko.symbols...done. Loaded symbols for /boot/kernel/zfs.ko.symbols Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. Loaded symbols for /boot/kernel/opensolaris.ko.symbols #0 doadump (textdump=value optimized out) at pcpu.h:231 231 __asm(movq %%gs:%1,%0 : =r (td) (kgdb) bt #0 doadump (textdump=value optimized out) at pcpu.h:231 #1 0x8063a9d6 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:447 #2 0x8063ae55 in panic (fmt=value optimized out) at /usr/src/sys/kern/kern_shutdown.c:754 #3 0x80918ba0 in trap_fatal (frame=0xc, eva=value optimized out) at /usr/src/sys/amd64/amd64/trap.c:872 #4 0x80918f11 in trap_pfault (frame=0xff800026d970, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:789 #5 0x809194c4 in trap (frame=0xff800026d970) at /usr/src/sys/amd64/amd64/trap.c:463 #6 0x80902c53 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0x80772688 in ip_slowtimo () at /usr/src/sys/netinet/ip_input.c:1237 #8 0x806a29ce in pfslowtimo (arg=0x0) at /usr/src/sys/kern/uipc_domain.c:508 #9 0x80651476 in softclock_call_cc (c=0x80e1ac60, cc=0x80dc6800, direct=0) at /usr/src/sys/kern/kern_timeout.c:674 #10 0x80651b09 in softclock (arg=value optimized out) at /usr/src/sys/kern/kern_timeout.c:802 #11 0x8060c06d in intr_event_execute_handlers (p=value optimized out, ie=0xfe0010811900) at /usr/src/sys/kern/kern_intr.c:1263 #12 0x8060d81b in ithread_loop (arg=0xfe0010819000) at /usr/src/sys/kern/kern_intr.c:1276 #13 0x80608c1f in fork_exit (callout=0x8060d780
Re: Cannot startx on FreeBSD10 Current
Mark Felder feld at feld.me writes: On Fri, 14 Jun 2013 12:05:13 -0500, Miguel Clara miguelmclara at gmail.com wrote: I wouldn't consider having no visual output from a laptop when you reboot/shutdown low priority... But that's not for me to decide... in any case is there any Bug Report/PR open about this that we can follow up? I would like to keep up to date with this. The driver is still in heavy development and considered incomplete, so there is no PR. Keep an eye on this Wiki page, and note the FAQ at the bottom: https://wiki.freebsd.org/Intel_GPU ___ freebsd-current at freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscribe at freebsd.org Sorry to get back to this, but I was testing other stuff in the meantime and had no time to reply. It seams that the issue is not just the black screen, the laptop won't trun off at all or reboot! If the other problem wasn't already a big issue this is indeed a major one! The only way to turn off is but force and this can cause damage to filesystems, this is indeed a very big issue, and I'm not sure if its specific to KMS or some freebsd-current problem cause I have no way to look into it! ___ 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 arm/arm
TB --- 2013-06-22 00:20:18 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-22 00:20:18 - 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-06-22 00:20:18 - starting HEAD tinderbox run for arm/arm TB --- 2013-06-22 00:20:18 - cleaning the object tree TB --- 2013-06-22 00:20:18 - /usr/local/bin/svn stat /src TB --- 2013-06-22 00:20:23 - At svn revision 252079 TB --- 2013-06-22 00:20:24 - building world TB --- 2013-06-22 00:20:24 - CROSS_BUILD_TESTING=YES TB --- 2013-06-22 00:20:24 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-22 00:20:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-22 00:20:24 - SRCCONF=/dev/null TB --- 2013-06-22 00:20:24 - TARGET=arm TB --- 2013-06-22 00:20:24 - TARGET_ARCH=arm TB --- 2013-06-22 00:20:24 - TZ=UTC TB --- 2013-06-22 00:20:24 - __MAKE_CONF=/dev/null TB --- 2013-06-22 00:20:24 - cd /src TB --- 2013-06-22 00:20:24 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sat Jun 22 00:20:30 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 [...] c++ -O2 -pipe -I/src/lib/clang/libclangparse/../../../contrib/llvm/include -I/src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/lib/Parse -I. -I/src/lib/clang/libclangparse/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\arm-unknown-freebsd10.0\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\/obj/arm.arm/src/tmp\ -I/obj/arm.arm/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/lib/Parse/ParseOpenMP.cpp -o ParseOpenMP.o c++ -O2 -pipe -I/src/lib/clang/libclangparse/../../../contrib/llvm/include -I/src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/lib/Parse -I. -I/src/lib/clang/libclangparse/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\arm-unknown-freebsd10.0\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\/obj/arm.arm/src/tmp\ -I/obj/arm.arm/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/lib/Parse/ParsePragma.cpp -o ParsePragma.o c++ -O2 -pipe -I/src/lib/clang/libclangparse/../../../contrib/llvm/include -I/src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/lib/Parse -I. -I/src/lib/clang/libclangparse/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\arm-unknown-freebsd10.0\ -DLLVM_HOST_TRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\/obj/arm.arm/src/tmp\ -I/obj/arm.arm/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/lib/Parse/ParseStmt.cpp -o ParseStmt.o /src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/lib/Parse/ParseStmt.cpp: In member function 'clang::StmtResult clang::Parser::ParseDoStatement()': /src/lib/clang/libclangparse/../../../contrib/llvm/tools/clang/lib/Parse/ParseStmt.cpp:1250: internal compiler error: Segmentation fault: 11 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 Stop. make: stopped in /src/lib/clang/libclangparse *** Error code 1 Stop. make: stopped in /src/lib/clang === lib/clang/include (install) sh /src/tools/install.sh -C -o root -g wheel -m 444 /src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/__wmmintrin_aes.h /src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/__wmmintrin_pclmul.h /src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/altivec.h /src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/ammintrin.h /src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avx2intrin.h /src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/avxintrin.h /src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/bmi2intrin.h /src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/bmiintrin.h /src/lib/clang/include/../../../contrib/llvm/tools/clang/lib/Headers/cpuid.h
[head tinderbox] failure on amd64/amd64
TB --- 2013-06-22 00:20:18 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-22 00:20:18 - 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-06-22 00:20:18 - starting HEAD tinderbox run for amd64/amd64 TB --- 2013-06-22 00:20:18 - cleaning the object tree TB --- 2013-06-22 00:20:18 - /usr/local/bin/svn stat /src TB --- 2013-06-22 00:20:23 - At svn revision 252079 TB --- 2013-06-22 00:20:24 - building world TB --- 2013-06-22 00:20:24 - CROSS_BUILD_TESTING=YES TB --- 2013-06-22 00:20:24 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-22 00:20:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-22 00:20:24 - SRCCONF=/dev/null TB --- 2013-06-22 00:20:24 - TARGET=amd64 TB --- 2013-06-22 00:20:24 - TARGET_ARCH=amd64 TB --- 2013-06-22 00:20:24 - TZ=UTC TB --- 2013-06-22 00:20:24 - __MAKE_CONF=/dev/null TB --- 2013-06-22 00:20:24 - cd /src TB --- 2013-06-22 00:20:24 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sat Jun 22 00:20:30 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 stage 5.1: building 32 bit shim libraries World build completed on Sat Jun 22 04:06:01 UTC 2013 TB --- 2013-06-22 04:06:01 - generating LINT kernel config TB --- 2013-06-22 04:06:01 - cd /src/sys/amd64/conf TB --- 2013-06-22 04:06:01 - /usr/bin/make -B LINT TB --- 2013-06-22 04:06:01 - cd /src/sys/amd64/conf TB --- 2013-06-22 04:06:01 - /usr/sbin/config -m LINT TB --- 2013-06-22 04:06:01 - building LINT kernel TB --- 2013-06-22 04:06:01 - CROSS_BUILD_TESTING=YES TB --- 2013-06-22 04:06:01 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-22 04:06:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-22 04:06:01 - SRCCONF=/dev/null TB --- 2013-06-22 04:06:01 - TARGET=amd64 TB --- 2013-06-22 04:06:01 - TARGET_ARCH=amd64 TB --- 2013-06-22 04:06:01 - TZ=UTC TB --- 2013-06-22 04:06:01 - __MAKE_CONF=/dev/null TB --- 2013-06-22 04:06:01 - cd /src TB --- 2013-06-22 04:06:01 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Sat Jun 22 04:06:01 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 stage 3.2: building everything [...] ^ /src/sys/fs/nfsclient/nfs_clstate.c:5161:8: error: format specifies type 'long long' but the argument has type 'uint64_t' (aka 'unsigned long') [-Werror,-Wformat] lyp-nfsly_lastbyte); ^~~ /src/sys/fs/nfs/nfscl.h:74:11: note: expanded from macro 'NFSCL_DEBUG' printf(__VA_ARGS__);\ ^ 3 errors generated. *** Error code 1 Stop. make: stopped in /obj/amd64.amd64/src/sys/LINT *** Error code 1 Stop. make: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-06-22 04:18:12 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-06-22 04:18:12 - ERROR: failed to build LINT kernel TB --- 2013-06-22 04:18:12 - 11333.01 user 2097.22 system 14273.70 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-amd64-amd64.full ___ 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: usb ACM device doesn't work
On 22/06/2013, at 4:10, Ian FREISLICH i...@clue.co.za wrote: I bought a relay control board that has a USB interface. It presents a serial port to Linux on /dev/ttyACMx. However when I plug it into my FreeBSD host, it detects as follows: ugen0.2: KMT at usbus0 umodem0: KMT USB CDC COM, class 2/0, rev 1.10/1.00, addr 1 on usbus0 umodem0: data interface 1, has no CM over data, has no break and I cannot communicate with it. Any ideas how to communicate with it? Have you tried anything? It should create /dev/cuaUx and /dev/ttyUx (where x is 0 in your case) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ 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: Cannot startx on FreeBSD10 Current
On Sat, Jun 22, 2013 at 12:29:49AM + I heard the voice of Miguel Clara, and lo! it spake thus: The only way to turn off is but force and this can cause damage to filesystems, this is indeed a very big issue, and I'm not sure if its specific to KMS or some freebsd-current problem cause I have no way to look into it! One little trick you might try is to login to a second VTY and run something like sleep 60 ; shutdown -r now before switching back and running startx; if it's just a UI crash/lockup rather than a whole-system such, that'll give you a clean reboot without FS damage. Of course, if it's a whole-system lockup, it won't, but that also means you can tell which it is, which may be diagnostically useful... (ssh'ing in from another machine is another way to track such things, but may be less convenient depending on your own setup...) -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ 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 ia64/ia64
TB --- 2013-06-22 04:02:48 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-22 04:02:48 - 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-06-22 04:02:48 - starting HEAD tinderbox run for ia64/ia64 TB --- 2013-06-22 04:02:48 - cleaning the object tree TB --- 2013-06-22 04:02:48 - /usr/local/bin/svn stat /src TB --- 2013-06-22 04:03:01 - At svn revision 252079 TB --- 2013-06-22 04:03:02 - building world TB --- 2013-06-22 04:03:02 - CROSS_BUILD_TESTING=YES TB --- 2013-06-22 04:03:02 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-22 04:03:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-22 04:03:02 - SRCCONF=/dev/null TB --- 2013-06-22 04:03:02 - TARGET=ia64 TB --- 2013-06-22 04:03:02 - TARGET_ARCH=ia64 TB --- 2013-06-22 04:03:02 - TZ=UTC TB --- 2013-06-22 04:03:02 - __MAKE_CONF=/dev/null TB --- 2013-06-22 04:03:02 - cd /src TB --- 2013-06-22 04:03:02 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sat Jun 22 04:03:09 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 Sat Jun 22 05:39:18 UTC 2013 TB --- 2013-06-22 05:39:18 - generating LINT kernel config TB --- 2013-06-22 05:39:18 - cd /src/sys/ia64/conf TB --- 2013-06-22 05:39:18 - /usr/bin/make -B LINT TB --- 2013-06-22 05:39:19 - cd /src/sys/ia64/conf TB --- 2013-06-22 05:39:19 - /usr/sbin/config -m LINT TB --- 2013-06-22 05:39:19 - building LINT kernel TB --- 2013-06-22 05:39:19 - CROSS_BUILD_TESTING=YES TB --- 2013-06-22 05:39:19 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-22 05:39:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-22 05:39:19 - SRCCONF=/dev/null TB --- 2013-06-22 05:39:19 - TARGET=ia64 TB --- 2013-06-22 05:39:19 - TARGET_ARCH=ia64 TB --- 2013-06-22 05:39:19 - TZ=UTC TB --- 2013-06-22 05:39:19 - __MAKE_CONF=/dev/null TB --- 2013-06-22 05:39:19 - cd /src TB --- 2013-06-22 05:39:19 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Sat Jun 22 05:39:19 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 stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/fs/nfsclient/nfs_clcomsubs.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/fs/nfsclient/nfs_clsubs.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/fs/nfsclient/nfs_clstate.c cc1: warnings being treated as errors /src/sys/fs/nfsclient/nfs_clstate.c: In function 'nfscl_dolayoutcommit': /src/sys/fs/nfsclient/nfs_clstate.c:5159: warning: format '%qd' expects type 'long long int', but argument 3 has type 'uint64_t' [-Wformat] /src/sys/fs/nfsclient/nfs_clstate.c:5159: warning: format '%qd' expects type 'long long int', but argument 4 has type 'uint64_t' [-Wformat]
[head tinderbox] failure on mips64/mips
TB --- 2013-06-22 04:53:04 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-06-22 04:53: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-06-22 04:53:04 - starting HEAD tinderbox run for mips64/mips TB --- 2013-06-22 04:53:04 - cleaning the object tree TB --- 2013-06-22 04:53:04 - /usr/local/bin/svn stat /src TB --- 2013-06-22 04:53:08 - At svn revision 252079 TB --- 2013-06-22 04:53:09 - building world TB --- 2013-06-22 04:53:09 - CROSS_BUILD_TESTING=YES TB --- 2013-06-22 04:53:09 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-22 04:53:09 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-22 04:53:09 - SRCCONF=/dev/null TB --- 2013-06-22 04:53:09 - TARGET=mips TB --- 2013-06-22 04:53:09 - TARGET_ARCH=mips64 TB --- 2013-06-22 04:53:09 - TZ=UTC TB --- 2013-06-22 04:53:09 - __MAKE_CONF=/dev/null TB --- 2013-06-22 04:53:09 - cd /src TB --- 2013-06-22 04:53:09 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sat Jun 22 04:53:16 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 Sat Jun 22 05:52:01 UTC 2013 TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m ADM5120 TB --- 2013-06-22 05:52:01 - skipping ADM5120 kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m ALCHEMY TB --- 2013-06-22 05:52:01 - skipping ALCHEMY kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m AP121 TB --- 2013-06-22 05:52:01 - skipping AP121 kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m AP91 TB --- 2013-06-22 05:52:01 - skipping AP91 kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m AP93 TB --- 2013-06-22 05:52:01 - skipping AP93 kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m AP94 TB --- 2013-06-22 05:52:01 - skipping AP94 kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m AP96 TB --- 2013-06-22 05:52:01 - skipping AP96 kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m AR71XX_BASE TB --- 2013-06-22 05:52:01 - skipping AR71XX_BASE kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m AR724X_BASE TB --- 2013-06-22 05:52:01 - skipping AR724X_BASE kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m AR91XX_BASE TB --- 2013-06-22 05:52:01 - skipping AR91XX_BASE kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m AR933X_BASE TB --- 2013-06-22 05:52:01 - skipping AR933X_BASE kernel TB --- 2013-06-22 05:52:01 - cd /src/sys/mips/conf TB --- 2013-06-22 05:52:01 - /usr/sbin/config -m BERI_DE4_MDROOT TB --- 2013-06-22 05:52:01 - building BERI_DE4_MDROOT kernel TB --- 2013-06-22 05:52:01 - CROSS_BUILD_TESTING=YES TB --- 2013-06-22 05:52:01 - MAKEOBJDIRPREFIX=/obj TB --- 2013-06-22 05:52:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-06-22 05:52:01 - SRCCONF=/dev/null TB --- 2013-06-22 05:52:01 - TARGET=mips TB --- 2013-06-22 05:52:01 - TARGET_ARCH=mips64 TB --- 2013-06-22 05:52:01 - TZ=UTC TB --- 2013-06-22 05:52:01 - __MAKE_CONF=/dev/null TB --- 2013-06-22 05:52:01 - cd /src TB --- 2013-06-22 05:52:01 - /usr/bin/make -B buildkernel KERNCONF=BERI_DE4_MDROOT Kernel build for BERI_DE4_MDROOT started on Sat Jun 22 05:52:01 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 stage 3.2: building everything [...] cc -c -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/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 -DKERNLOADADDR=0x8010 -march=mips64 -mabi=64 -msoft-float -ffreestanding -Werror /src/sys/fs/nfsclient/nfs_clcomsubs.c cc -c
