Re: Device timeout from mfi(9) while booting 9.2-RELEASE
On 5 Oct 2013, at 2:32 am, Teske, Devin wrote:
>
> On Oct 4, 2013, at 8:59 AM, Sean Bruno wrote:
>
>> On Fri, 2013-10-04 at 18:27 +1000, Jan Mikkelsen wrote:
mfi0: 14299 (boot + 4s/0x0020/info) - Firmware version 3.190.05-1669
mfi0: 14300 (boot + 5s/0x0020/info) - Package version 23.7.0-0029
mfi0: 14301 (boot + 5s/0x0020/info) - Board Revision
>>
>> Does it make sense then, to take a survey and add a recommended minium
>> f/w for cards that we know about to the man page?
>>
>
> Sounds like a great idea.
>
> I can provide the following *good* firmware infos:
>
> ===
>
> In order:
>
> 1. (as root) mfiutil show adapter | grep Name
> 2. grep 'mfi[[:digit:]]\{1,\}:.*\(vers\|Board\)' /var/run/dmesg.boot
> 3. (as root) mfiutil show firmware | grep Pack # only required on older cards
>
> ===
The mfiutils instructions only work for the first card in the system.
I just went through a few running systems and found these combinations. Some of
these are looking a bit old and should be upgraded. All are running fine.
Product Name: LSI MegaRAID SAS 9261-8i
mfi0: 21552 (boot + 3s/0x0020/info) - Firmware version 2.130.383-2315
mfi0: 21554 (boot + 9s/0x0020/info) - Package version 12.13.0-0154
mfi0: 21555 (boot + 9s/0x0020/info) - Board Revision 15A
Product Name: LSI MegaRAID SAS 9240-4i
mfi1: 15228 (boot + 3s/0x0020/info) - Firmware version 2.130.384-2291
mfi1: 15229 (boot + 5s/0x0020/info) - Package version 20.11.1-0137
mfi1: 15230 (boot + 5s/0x0020/info) - Board Revision 03A
Product Name: LSI MegaRAID SAS 9261-8i
mfi0: 62632 (boot + 4s/0x0020/info) - Firmware version 2.120.243-1482
mfi0: 62634 (boot + 9s/0x0020/info) - Package version 12.12.0-0090
mfi0: 62635 (boot + 9s/0x0020/info) - Board Revision 15A
Product Name: LSI MegaRAID SAS 9240-8i
mfi0: 6559 (boot + 3s/0x0020/info) - Firmware version 2.130.374-2023
mfi0: 6560 (boot + 5s/0x0020/info) - Package version 20.10.1-0126
mfi0: 6561 (boot + 5s/0x0020/info) - Board Revision 04A
Product Name: LSI MegaRAID SAS 9261-8i
mfi0: 74819 (boot + 4s/0x0020/info) - Firmware version 2.120.183-1415
mfi0: 74822 (boot + 9s/0x0020/info) - Package version 12.12.0-0073
mfi0: 74823 (boot + 9s/0x0020/info) - Board Revision 15A
Product Name: LSI MegaRAID SAS 9261-8i
mfi0: 72049 (boot + 4s/0x0020/info) - Firmware version 2.120.63-1242
mfi0: 72051 (boot + 6s/0x0020/info) - Package version 12.12.0-0048
mfi0: 72052 (boot + 6s/0x0020/info) - Board Revision 15A
Product Name: LSI MegaRAID SAS 9240-8i
mfi0: 2463 (boot + 3s/0x0020/info) - Firmware version 2.130.354-1664
mfi0: 2464 (boot + 5s/0x0020/info) - Package version 20.10.1-0107
mfi0: 2465 (boot + 5s/0x0020/info) - Board Revision 04A
Regards,
Jan.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Device timeout from mfi(9) while booting 9.2-RELEASE
- Original Message -
From: "Jan Mikkelsen"
To: "Teske, Devin"
Cc: "Konstantin Belousov" ; "Steven Hartland" ; "Ryan Stone" ;
Sent: Monday, October 07, 2013 8:57 AM
Subject: Re: Device timeout from mfi(9) while booting 9.2-RELEASE
On 5 Oct 2013, at 2:32 am, Teske, Devin wrote:
On Oct 4, 2013, at 8:59 AM, Sean Bruno wrote:
On Fri, 2013-10-04 at 18:27 +1000, Jan Mikkelsen wrote:
mfi0: 14299 (boot + 4s/0x0020/info) - Firmware version 3.190.05-1669
mfi0: 14300 (boot + 5s/0x0020/info) - Package version 23.7.0-0029
mfi0: 14301 (boot + 5s/0x0020/info) - Board Revision
Does it make sense then, to take a survey and add a recommended minium
f/w for cards that we know about to the man page?
Sounds like a great idea.
I can provide the following *good* firmware infos:
===
In order:
1. (as root) mfiutil show adapter | grep Name
2. grep 'mfi[[:digit:]]\{1,\}:.*\(vers\|Board\)' /var/run/dmesg.boot
3. (as root) mfiutil show firmware | grep Pack # only required on older cards
===
The mfiutils instructions only work for the first card in the system.
I just went through a few running systems and found these combinations. Some of these are looking a bit old and should be
upgraded. All are running fine.
Product Name: LSI MegaRAID SAS 9261-8i
mfi0: 21552 (boot + 3s/0x0020/info) - Firmware version 2.130.383-2315
mfi0: 21554 (boot + 9s/0x0020/info) - Package version 12.13.0-0154
mfi0: 21555 (boot + 9s/0x0020/info) - Board Revision 15A
Product Name: LSI MegaRAID SAS 9240-4i
mfi1: 15228 (boot + 3s/0x0020/info) - Firmware version 2.130.384-2291
mfi1: 15229 (boot + 5s/0x0020/info) - Package version 20.11.1-0137
mfi1: 15230 (boot + 5s/0x0020/info) - Board Revision 03A
Product Name: LSI MegaRAID SAS 9261-8i
mfi0: 62632 (boot + 4s/0x0020/info) - Firmware version 2.120.243-1482
mfi0: 62634 (boot + 9s/0x0020/info) - Package version 12.12.0-0090
mfi0: 62635 (boot + 9s/0x0020/info) - Board Revision 15A
Product Name: LSI MegaRAID SAS 9240-8i
mfi0: 6559 (boot + 3s/0x0020/info) - Firmware version 2.130.374-2023
mfi0: 6560 (boot + 5s/0x0020/info) - Package version 20.10.1-0126
mfi0: 6561 (boot + 5s/0x0020/info) - Board Revision 04A
Product Name: LSI MegaRAID SAS 9261-8i
mfi0: 74819 (boot + 4s/0x0020/info) - Firmware version 2.120.183-1415
mfi0: 74822 (boot + 9s/0x0020/info) - Package version 12.12.0-0073
mfi0: 74823 (boot + 9s/0x0020/info) - Board Revision 15A
Product Name: LSI MegaRAID SAS 9261-8i
mfi0: 72049 (boot + 4s/0x0020/info) - Firmware version 2.120.63-1242
mfi0: 72051 (boot + 6s/0x0020/info) - Package version 12.12.0-0048
mfi0: 72052 (boot + 6s/0x0020/info) - Board Revision 15A
Product Name: LSI MegaRAID SAS 9240-8i
mfi0: 2463 (boot + 3s/0x0020/info) - Firmware version 2.130.354-1664
mfi0: 2464 (boot + 5s/0x0020/info) - Package version 20.10.1-0107
mfi0: 2465 (boot + 5s/0x0020/info) - Board Revision 04A
Just to confirm when you say fine, have you checked to ensure none
are reporting timeouts?
Regards
Steve
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Device timeout from mfi(9) while booting 9.2-RELEASE
On 7 Oct 2013, at 7:30 pm, Steven Hartland wrote:
>
> - Original Message - From: "Jan Mikkelsen"
> To: "Teske, Devin"
> Cc: "Konstantin Belousov" ; "Steven Hartland"
> ; "Ryan Stone" ;
>
> Sent: Monday, October 07, 2013 8:57 AM
> Subject: Re: Device timeout from mfi(9) while booting 9.2-RELEASE
>
>
>>
>> On 5 Oct 2013, at 2:32 am, Teske, Devin wrote:
>>
>>>
>>> On Oct 4, 2013, at 8:59 AM, Sean Bruno wrote:
>>>
On Fri, 2013-10-04 at 18:27 +1000, Jan Mikkelsen wrote:
>> mfi0: 14299 (boot + 4s/0x0020/info) - Firmware version 3.190.05-1669
>> mfi0: 14300 (boot + 5s/0x0020/info) - Package version 23.7.0-0029
>> mfi0: 14301 (boot + 5s/0x0020/info) - Board Revision
Does it make sense then, to take a survey and add a recommended minium
f/w for cards that we know about to the man page?
>>>
>>> Sounds like a great idea.
>>>
>>> I can provide the following *good* firmware infos:
>>>
>>> ===
>>>
>>> In order:
>>>
>>> 1. (as root) mfiutil show adapter | grep Name
>>> 2. grep 'mfi[[:digit:]]\{1,\}:.*\(vers\|Board\)' /var/run/dmesg.boot
>>> 3. (as root) mfiutil show firmware | grep Pack # only required on older
>>> cards
>>>
>>> ===
>>
>> The mfiutils instructions only work for the first card in the system.
>>
>> I just went through a few running systems and found these combinations. Some
>> of these are looking a bit old and should be upgraded. All are running fine.
>>
>> Product Name: LSI MegaRAID SAS 9261-8i
>> mfi0: 21552 (boot + 3s/0x0020/info) - Firmware version 2.130.383-2315
>> mfi0: 21554 (boot + 9s/0x0020/info) - Package version 12.13.0-0154
>> mfi0: 21555 (boot + 9s/0x0020/info) - Board Revision 15A
>>
>> Product Name: LSI MegaRAID SAS 9240-4i
>> mfi1: 15228 (boot + 3s/0x0020/info) - Firmware version 2.130.384-2291
>> mfi1: 15229 (boot + 5s/0x0020/info) - Package version 20.11.1-0137
>> mfi1: 15230 (boot + 5s/0x0020/info) - Board Revision 03A
>>
>> Product Name: LSI MegaRAID SAS 9261-8i
>> mfi0: 62632 (boot + 4s/0x0020/info) - Firmware version 2.120.243-1482
>> mfi0: 62634 (boot + 9s/0x0020/info) - Package version 12.12.0-0090
>> mfi0: 62635 (boot + 9s/0x0020/info) - Board Revision 15A
>>
>> Product Name: LSI MegaRAID SAS 9240-8i
>> mfi0: 6559 (boot + 3s/0x0020/info) - Firmware version 2.130.374-2023
>> mfi0: 6560 (boot + 5s/0x0020/info) - Package version 20.10.1-0126
>> mfi0: 6561 (boot + 5s/0x0020/info) - Board Revision 04A
>>
>> Product Name: LSI MegaRAID SAS 9261-8i
>> mfi0: 74819 (boot + 4s/0x0020/info) - Firmware version 2.120.183-1415
>> mfi0: 74822 (boot + 9s/0x0020/info) - Package version 12.12.0-0073
>> mfi0: 74823 (boot + 9s/0x0020/info) - Board Revision 15A
>>
>> Product Name: LSI MegaRAID SAS 9261-8i
>> mfi0: 72049 (boot + 4s/0x0020/info) - Firmware version 2.120.63-1242
>> mfi0: 72051 (boot + 6s/0x0020/info) - Package version 12.12.0-0048
>> mfi0: 72052 (boot + 6s/0x0020/info) - Board Revision 15A
>>
>> Product Name: LSI MegaRAID SAS 9240-8i
>> mfi0: 2463 (boot + 3s/0x0020/info) - Firmware version 2.130.354-1664
>> mfi0: 2464 (boot + 5s/0x0020/info) - Package version 20.10.1-0107
>> mfi0: 2465 (boot + 5s/0x0020/info) - Board Revision 04A
>
> Just to confirm when you say fine, have you checked to ensure none
> are reporting timeouts?
Yes.
Only the first two of these are from a 9.2 era system (also the ones with the
most recent firmware).
We did have timeout issues while testing this platform which were resolved by
taking the mfi driver from -HEAD at the time and setting hw.mfi.msi=1. The
oldest ones have been running for over two years.
I can go through our Perforce depot to tell you exactly what mfi driver they’re
running, if you care.
Regards,
Jan.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Device timeout from mfi(9) while booting 9.2-RELEASE
- Original Message - From: "Jan Mikkelsen" .. Just to confirm when you say fine, have you checked to ensure none are reporting timeouts? Yes. Only the first two of these are from a 9.2 era system (also the ones with the most recent firmware). We did have timeout issues while testing this platform which were resolved by taking the mfi driver from -HEAD at the time and setting hw.mfi.msi=1. The oldest ones have been running for over two years. Thats curious, hw.mfi.msi=1 is the default so you shouldn't need to change this. Also heads mfi is almost identical to 9.2 so not sure why you would need to update, could you clarify? Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Device timeout from mfi(9) while booting 9.2-RELEASE
On 7 Oct 2013, at 8:06 pm, Steven Hartland wrote: > - Original Message - From: "Jan Mikkelsen" > .. > >> Just to confirm when you say fine, have you checked to ensure none >> are reporting timeouts? > >> Yes. >> Only the first two of these are from a 9.2 era system (also the ones >> with the most recent firmware). >> We did have timeout issues while testing this platform which were >> resolved by taking the mfi driver from -HEAD at the time and setting >> hw.mfi.msi=1. The oldest ones have been running for over two years. > > Thats curious, hw.mfi.msi=1 is the default so you shouldn't need to > change this. > > Also heads mfi is almost identical to 9.2 so not sure why you would > need to update, could you clarify? The 9.2 system has the 9.2 driver and was not updated. It is a test system with a 9261-8i and a 9240-4i. The other machines are running 9.0 or 9.1 with a modified driver. The 9.0 systems have a patch that added the hw.mfi.msi sysctl with a default of zero. I just went back to our Perforce depot and checked the timing; that patch was applied to our local copy on 2011-12-08. My “running for over two years” was wrong, it is actually about a year and a half. At that point the 9261-8i was stable and we saw no further timeout errors even with the old firmware versions in my email. (looking through svn, this change was in rev 227562 to mfi_pci.c.) The loader.conf entry has been in our standard builds ever since, and even after the default value changed. Probably time to remove it. We started using the 9240-4i/8i in May 2012. We brought in changes from head mfi to support them. I’d need to go digging deeper to see exactly what the changes were. A quick look shows that this is when the hw.mfi.msi default changed in our copy of the code. In any case: These system are running and we don’t see timeout errors with the firmware versions I listed. There were also your later changes that improved the reliability of mfi. We brought those back into our 9.1 based systems, but the cards were working before those changes. Regards, Jan. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: pfsync between 8.4 and 9.2
On Wed, Oct 02, 2013 at 12:33:09PM +0100, Pete French wrote: P> Just to follow this up for anyuone finding the thread, after upgrading P> the other firewall to 9.2 as well, pfsync works fine agai. The failover P> actually seems a lot faster in fact, so it looks like a big improvements. Btw, pfsync between 9.x and 10.x is compatible, so provided you have a failover, you are encouraged to try 10-ALPHA4, where pf(4) has got performance improvements comparing to 9.x. More on pf(4) in 10.x: http://www.freebsd.org/news/status/report-2012-10-2012-12.html#SMP-Friendly-pf%284%29 Where to get latest 10.0-ALPHA4 release: http://www.freebsd.org/where.html#helptest -- Totus tuus, Glebius. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-RC4 amd64 panic: vm_page_unwire
On Sat, 05 Oct 2013, 10:57 +0300, Konstantin Belousov wrote: > Since you have a will to play with this, please try to bisect the > stable to see which commit introduced the regression (you said that 9.1 > does not panic). stable/9@r244654 is where the panic is introduced. So I am guessing that nullfs is an unanticipated necessary ingredient? I run jails on both systems and use nullfs to mount the host system's /usr /sbin /bin /lib /libexec read-only in the jails. The jails are managed with jail.conf(5) and the nullfs mounts are created and deleted with the jails via a per-jail mount.fstab directive in jail.conf. The panics I see (when ntpd or watchdogd exit during shutdown) happen after the jails have been removed (and their nullfs mounts deleted) FreeBSD 9.1-PRERELEASE #0 r244654: Mon Oct 7 20:48:44 AEST 2013 ns4: removed Stopping ntpd. Waiting for PIDS: 1900 panic: vm_page_unwire: page 0xfe0236f7eb60's wire count is zero cpuid = 5 KDB: stack backtrace: #0 0x804834a8 at kdb_backtrace+0x68 #1 0x8044a7fa at panic+0x21a #2 0x80679382 at vm_page_unwire+0x102 #3 0x806662c2 at vm_fault_unwire+0xd2 #4 0x8066e421 at vm_map_delete+0x171 #5 0x8066e69f at vm_map_remove+0x5f #6 0x80671969 at vmspace_exit+0xc9 #7 0x80413c7d at exit1+0x71d #8 0x80414c7e at sys_sys_exit+0xe #9 0x8069d0df at amd64_syscall+0x3bf #10 0x80687d67 at Xfast_syscall+0xf7 Additional information is in core.txt.31 in the same location indicated in my OP. -- John Marshall pgpctZUOjHkc1.pgp Description: PGP signature
Continuous timeout messages from 10.0 alpha4
This is a regression between alpha2 and alpha4. I first setup a disk to boot 10 just after alpha2 was tagged. A few days ago I updated to alpha4 and started getting timeout messages, I have just built alpha5 r256098 and still get them. I just had 10 running for a few hours and 3 of the messages log archives which syslog rotates each hour due to size contain 3370 2508 and 3162 timeout messages over 3 hours uptime. each entry is similar to -- Oct 7 19:00:02 leader kernel: ahcich1: Timeout on slot 15 port 0 Oct 7 19:00:02 leader kernel: ahcich1: is 4001 cs 8000 ss rs 8000 tfd 2451 serr cmd 4f17 With slot x cycling from 0-31 but not always in sequence. MB is ASUS P8H61M LE/USB3 - corei5 - 8MB - nvidia GT520 ahci0: port 0xf070-0xf077,0xf060-0xf063,0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem 0xfb305000-0xfb3057ff irq 20 at device 31.2 on pci0 ahci0: AHCI v1.30 with 4 3Gbps ports, Port Multiplier not supported With the following connected to ahcich1 (LG blu-ray burner) cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device Most relevant dmesg info would be (full dmesg/logs available) -- ahci0: port 0xf070-0xf077,0xf060-0xf063,0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem 0xfb305000-0xfb3057ff irq 20 at device 31.2 on pci0 ahci0: AHCI v1.30 with 4 3Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ahciem0: on ahci0 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 3.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada0: quirks=0x1<4K> ada0: Previously was known as ad4 ada1 at ahcich4 bus 0 scbus2 target 0 lun 0 ada1: ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada1: quirks=0x1<4K> ada1: Previously was known as ad8 ada2 at ahcich5 bus 0 scbus3 target 0 lun 0 ada2: ATA-6 SATA 2.x device ada2: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 512bytes) ada2: 76324MB (156312576 512 byte sectors: 16H 63S/T 16383C) ada2: Previously was known as ad10 ses0 at ahciem0 bus 0 scbus4 target 0 lun 0 ses0: SEMB S-E-S 2.00 device ses0: SEMB SES Device ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Listen queue overflow
On 01.08.2013 21:47, Mike Tancsa wrote: > After upgrading from a RELENG9 kernel from June 18th to July 27th, I am > seeing this odd new message. Is this a new bug, or just a new > diagnostic message ? I am guessing it happened after r253035 ? > > > sonewconn: pcb 0xfe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance > sonewconn: pcb 0xfe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance > sonewconn: pcb 0xfe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance > sonewconn: pcb 0xfe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance > sonewconn: pcb 0xfe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance > sonewconn: pcb 0xfe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance Try "netstat -Lan". ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
buildworld fails 9.1-STABLE -> 9.2.0-RELEASE
Hello freebsd-stable, I have a buildworld failure upgrading 9.1-stable (r250633) to 9.2.0-release. I take these steps: 1. rm -rf /usr/obj 2. rm -rf /usr/src 3. mkdir /usr/obj 4. mkdir /usr/src 5. svn co https://svn0.eu.freebsd.org/base/release/9.2.0/ /usr/src (this results in Revision: 256108) 6. cd /usr/src 7. make clean && make clean (just to be sure) 8. make buildworld This fails at the following point: ./contrib/llvm/tools/clang/lib/Basic/FileSystemStatCache.cpp /usr/src/lib/clang/libclangbasic/../../../contrib/llvm/tools/clang/lib/Basic /IdentifierTable.cpp /usr/src/lib/clang/libclangbasic/../../../contrib/llvm/ tools/clang/lib/Basic/LangOptions.cpp /usr/src/lib/clang/libclangbasic/../.. /../contrib/llvm/tools/clang/lib/Basic/Module.cpp /usr/src/lib/clang/ libclangbasic/../../../contrib/llvm/tools/clang/lib/Basic/ObjCRuntime.cpp /usr /src/lib/clang/libclangbasic/../../../contrib/llvm/tools/clang/lib/Basic /OpenMPKinds.cpp /usr/src/lib/clang/libclangbasic/../../../contrib/llvm/tools /clang/lib/Basic/OperatorPrecedence.cpp /usr/src/lib/clang/libclangbasic/../.. /../contrib/llvm/tools/clang/lib/Basic/SourceLocation.cpp /usr/src/lib/clang/ libclangbasic/../../../contrib/llvm/tools/clang/lib/Basic/SourceManager.cpp /usr /src/lib/clang/libclangbasic/../../../contrib/llvm/tools/clang/lib/Basic/ TargetInfo.cpp /usr/src/lib/clang/libclangbasic/../../../contrib/llvm/tools/ clang/lib/Basic/Targets.cpp /usr/src/lib/clang/libclangbasic/../../../contrib/ llvm/tools/clang/lib/Basic/TokenKinds.cpp /usr/src/lib/clang/libclangbasic/.. /../../contrib/llvm/tools/clang/lib/Basic/Version.cpp /usr/src/lib/clang/ libclangbasic/../../../contrib/llvm/tools/clang/lib/Basic/VersionTuple.cpp /usr/src/lib/clang/libclangbasic/../../../contrib/llvm/tools/clang/lib/Basic/ SourceManager.cpp:1100:10: fatal error: 'emmintrin.h' file not found #include ^ 1 error generated. mkdep: compile failed *** [.depend] Error code 1 Stop in /usr/src/lib/clang/libclangbasic. *** [depend] Error code 1 Stop in /usr/src/lib/clang. *** [cross-tools] Error code 1 Stop in /usr/src. *** [_cross-tools] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. I have no src.conf in /etc. make.conf looks like this: CC=clang CXX=clang++ CPP=clang-cpp # added by use.perl 2013-05-14 02:01:08 PERL_VERSION=5.14.2 Can anyone help? thanks, -- John ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Installing packages from 9.2 Release DVD
Dear All , In sysinstall , there are menu items to install packages from release DVD . In bsdinstall , there is NO such package installation menu items . Another problem is there is no any available information about this subject in the Handbook installation pages ( at least I could not find any one one ) . Is there any such available information link , and is there any possibility to include such information into Handbook pages and Release Notes templates ? When there is no such information , people will use pkg_add -r ... statement although many packages are already in the release DVD which means a large waste of band width . ( Please consider less experienced people : Each year , many persons are entering into an age to try FreeBSD without prior experience about FreeBSD . Lack of necessary information about install is an important obstacle for such new entries . ) Thank you very much . Mehmet Erol Sanliturk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
