Strange CAM errors
Hi, I have not noticed this before, but my system rebooted this morning and in the following security report I found a lot of messgaes in the dmesg-part like: +(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0 +(probe0:arcmsr0:0:16:1): CAM status: Command timeout +(probe0:arcmsr0:0:16:1): Retrying command +(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0 +(probe0:arcmsr0:0:16:1): CAM status: Command timeout +(probe0:arcmsr0:0:16:1): Retrying command And it seems that bus 16 is: +pass6 at arcmsr0 bus 0 scbus0 target 16 lun 0 +pass6: Areca RAID controller R001 Fixed Processor SCSI-0 device The system has been running FreeBSD zfs.digiware.nl 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #3: Wed Nov 14 13:25:55 CET 2012 r...@zfs.digiware.nl:/usr/obj/usr/srcs/src9/src/sys/ZFS amd64 for already a while. Anybody suggestions as to why I have these messages? They are during the boot sequence, so no smartd talking to the disks at that moment. --WjW ps: dmesg, config, etc at: http://www.tegenbosch28.nl/FreeBSD/Systems/ZFS ps2: upgrading to the most recent 9.1 ___ 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: Strange CAM errors
Hello :-) I have noticed similar behavior with one of my Toshiba DVD drives when disk was inserted, removing disk and/or drive solved the issue, but I guess it wtill exist in the driver..? Best regards, Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Dec 17, 2012 11:58 AM, Willem Jan Withagen w...@digiware.nl wrote: Hi, I have not noticed this before, but my system rebooted this morning and in the following security report I found a lot of messgaes in the dmesg-part like: +(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0 +(probe0:arcmsr0:0:16:1): CAM status: Command timeout +(probe0:arcmsr0:0:16:1): Retrying command +(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0 +(probe0:arcmsr0:0:16:1): CAM status: Command timeout +(probe0:arcmsr0:0:16:1): Retrying command And it seems that bus 16 is: +pass6 at arcmsr0 bus 0 scbus0 target 16 lun 0 +pass6: Areca RAID controller R001 Fixed Processor SCSI-0 device The system has been running FreeBSD zfs.digiware.nl 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #3: Wed Nov 14 13:25:55 CET 2012 r...@zfs.digiware.nl:/usr/obj/usr/srcs/src9/src/sys/ZFS amd64 for already a while. Anybody suggestions as to why I have these messages? They are during the boot sequence, so no smartd talking to the disks at that moment. --WjW ps: dmesg, config, etc at: http://www.tegenbosch28.nl/FreeBSD/Systems/ZFS ps2: upgrading to the most recent 9.1 ___ 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 ___ 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: NFS/ZFS hangs after upgrading from 9.0-RELEASE to -STABLE
On 13.12.2012 18:54, Andriy Gapon wrote: on 13/12/2012 19:46 olivier said the following: Thanks. I'll be sure to follow your suggestions next time this happens. I have a naive question/suggestion though. I see from browsing past discussions on ZFS problems that it has been suggested a number of times that problems that appear to originate in ZFS in fact come from lower layers; in particular because of driver bugs or disks in the process of failing. It seems that it can take a lot of time to troubleshoot such problems. I accept that ZFS behavior correctly leaves dealing with timeouts to lower layers, but it seems to me that the ZFS layer would be a great place to warn the user about issues and provide some information to troubleshoot them. For example, if some I/O requests get lost because of a buggy driver, the driver itself might not be the best place to identify those lost requests. But perhaps we could have a compile time option in ZFS code that spits out a warning if it gets stuck waiting for a particular request to come back for more than say 10 seconds, and identifies the problematic disk? I'm sure there would be cases where these warnings would be unwarranted, and I imagine that changes in the code to provide such warnings would impact performance; so one certainly would not want that code active by default. But someone in my position could certainly recompile the kernel with a ZFS debugging option turned on to figure out the problem. I understand that ZFS code comes from upstream, and that you guys probably want to keep FreeBSD-specific changes minimal. If that's a big problem, even just a patch provided as such that does not make it into the FreeBSD code base might be extremely useful. I wish I could help write something like that, but I know very little about the kernel or ZFS. I would certainly be willing to help with testing. Google for zfs deadman. This is already committed upstream and I think that it is imported into FreeBSD, but I am not sure... Maybe it's imported just into the vendor area and is not merged yet. So, when enabled this logic would panic a system as a way of letting know that something is wrong. You can read in the links why panic was selected for this job. And speaking FreeBSD-centric - I think that our CAM layer would be a perfect place to detect such issues in non-ZFS-specific way. I can try to merge the ZFS deadman stuff (r242732) to HEAD, but I guess this will be something for a 1-month MFC period. Afterwards, a 9-STABLE patch can be easily created. https://www.illumos.org/issues/3246 https://hg.openindiana.org/upstream/illumos/illumos-gate/rev/921a8bb4 Cheers, mm -- Martin Matuska FreeBSD committer http://blog.vx.sk ___ 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: freebsd-update mergemaster options
I am getting hundreds of files with conflicts like: current version # $FreeBSD: src/etc/auth.conf,v 1.6.32.1.4.1 2010/06/14 02:09:06 kensmith Exp $ === # $FreeBSD: src/etc/auth.conf,v 1.6.32.1.8.1 2012/03/03 06:15:13 kensmith Exp $ 8.3-RELEASE mergemaster took the master part of its name a bit seriously i use -cviFU randy ___ 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: Strange CAM errors
Check the smart results of each disk in the array you may have a failing disk. - Original Message - From: Willem Jan Withagen w...@digiware.nl To: FreeBSD Stable Users freebsd-stable@freebsd.org Sent: Monday, December 17, 2012 10:58 AM Subject: Strange CAM errors Hi, I have not noticed this before, but my system rebooted this morning and in the following security report I found a lot of messgaes in the dmesg-part like: +(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0 +(probe0:arcmsr0:0:16:1): CAM status: Command timeout +(probe0:arcmsr0:0:16:1): Retrying command +(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0 +(probe0:arcmsr0:0:16:1): CAM status: Command timeout +(probe0:arcmsr0:0:16:1): Retrying command And it seems that bus 16 is: +pass6 at arcmsr0 bus 0 scbus0 target 16 lun 0 +pass6: Areca RAID controller R001 Fixed Processor SCSI-0 device The system has been running FreeBSD zfs.digiware.nl 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #3: Wed Nov 14 13:25:55 CET 2012 r...@zfs.digiware.nl:/usr/obj/usr/srcs/src9/src/sys/ZFS amd64 for already a while. Anybody suggestions as to why I have these messages? They are during the boot sequence, so no smartd talking to the disks at that moment. --WjW ps: dmesg, config, etc at: http://www.tegenbosch28.nl/FreeBSD/Systems/ZFS ps2: upgrading to the most recent 9.1 ___ 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 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: thinkpad and synaptics
works for me on head, amd64, lenovo ideapad b450: [tiger@laptop]:~%dmesg | grep psm psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics Touchpad, device ID 0 [tiger@laptop]:~%grep syn /boot/loader.conf hw.psm.synaptics_support=1 Done that. xorg.conf: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Done that also. Section InputDevice Identifier Mouse0 Driver synaptics Option Protocol psm Option Device /dev/psm0 Option SHMConfig on OptionMinSpeed 7 OptionMaxSpeed 9 OptionAccelFactor 0.0015 Option ZAxisMapping 4 5 6 7 EndSection This is not what I did. I put both mouse0 and Touchpad0 into conf file. [tiger@laptop]:~%grep mouse /etc/rc.conf mousechar_start=3 #moused_enable=YES Ah! Ah! I put No and it made pointer frozen. [tiger@laptop]:~%pkg info -x input-s xf86-input-synaptics-1.5.0 X.Org synaptics input driver Done that. Frankly, I'd like to learn exact stept you've taken. One by one. I made all, even stupid tries, and failed without chance to have vertical scroll in any configu- ration. Best regards Zoran ___ 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:New Products,Finglee Polishing Pad
For more details on surface solution products,please login on: www.floorpolishingpad.com Finglee are professional supplier for these goods for concrete,stone,abrasive products. Inquiry me for offer! Rgds, camille Finglee Diamond Tools We Offer: diamond blade,segment,wire saw,grindingpolishing tools Web:www.finglee.com Tel:+86 0595 22496831 Fax:+86 0595 22496831 Airport: Quanzhou Jingjiang Airport or Xiamen Gaoqi International Airport Address:Jingxiu Jiangnan Qingmeng Developing Zone Quanzhou Fujian China ___ 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: Strange CAM errors
On 2012-12-17 15:38, Steven Hartland wrote: Check the smart results of each disk in the array you may have a failing disk. - Original Message - From: Willem Jan Withagen w...@digiware.nl To: FreeBSD Stable Users freebsd-stable@freebsd.org Sent: Monday, December 17, 2012 10:58 AM Subject: Strange CAM errors Hi, I have not noticed this before, but my system rebooted this morning and in the following security report I found a lot of messgaes in the dmesg-part like: +(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0 +(probe0:arcmsr0:0:16:1): CAM status: Command timeout +(probe0:arcmsr0:0:16:1): Retrying command +(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0 +(probe0:arcmsr0:0:16:1): CAM status: Command timeout +(probe0:arcmsr0:0:16:1): Retrying command And it seems that bus 16 is: +pass6 at arcmsr0 bus 0 scbus0 target 16 lun 0 +pass6: Areca RAID controller R001 Fixed Processor SCSI-0 device The system has been running FreeBSD zfs.digiware.nl 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #3: Wed Nov 14 13:25:55 CET 2012 r...@zfs.digiware.nl:/usr/obj/usr/srcs/src9/src/sys/ZFS amd64 for already a while. Anybody suggestions as to why I have these messages? They are during the boot sequence, so no smartd talking to the disks at that moment. --WjW ps: dmesg, config, etc at: http://www.tegenbosch28.nl/FreeBSD/Systems/ZFS ps2: upgrading to the most recent 9.1 'mmm, Smartd seems to think otherwise... 'camcontrol rescan all' actually delivers the same pack of errors. --WjW ___ 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: thinkpad and synaptics
On 12/17/12 12:25, Zoran Kolic wrote: works for me on head, amd64, lenovo ideapad b450: [tiger@laptop]:~%dmesg | grep psm psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics Touchpad, device ID 0 [tiger@laptop]:~%grep syn /boot/loader.conf hw.psm.synaptics_support=1 Done that. xorg.conf: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Done that also. Section InputDevice Identifier Mouse0 Driver synaptics Option Protocol psm Option Device /dev/psm0 Option SHMConfig on OptionMinSpeed 7 OptionMaxSpeed 9 OptionAccelFactor 0.0015 Option ZAxisMapping 4 5 6 7 EndSection This is not what I did. I put both mouse0 and Touchpad0 into conf file. [tiger@laptop]:~%grep mouse /etc/rc.conf mousechar_start=3 #moused_enable=YES Ah! Ah! I put No and it made pointer frozen. [tiger@laptop]:~%pkg info -x input-s xf86-input-synaptics-1.5.0 X.Org synaptics input driver Done that. Frankly, I'd like to learn exact stept you've taken. One by one. I made all, even stupid tries, and failed without chance to have vertical scroll in any configu- ration. I actually attempted this configuration, and it worked fine for me, with one difference: I had to leave moused_enabled=YES in rc.conf. FWIW, this is the configuration I had before, which also worked (although things didn't work as nicely as with the current one): In xorg.conf: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard Option AutoAddDevices Off EndSection [...] Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection In rc.conf: moused_enable=YES in loader.conf: hw.psm.synaptics_support=1 Best regards Zoran ___ 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 ___ 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: thinkpad and synaptics
As first, thanks for answer. Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard Option AutoAddDevices Off EndSection [...] Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection In rc.conf: moused_enable=YES in loader.conf: hw.psm.synaptics_support=1 OK. I know it is writen zillion times and it still does not work for me. It is thinkpad e320, amd64, 9.1, kms. I had a lot of problems regarding fonts and non working vertical scroll on the pad. What I did: put synaptics_support run moused changed xorg.conf in a million ways This xorg.conf is similar to mine. I also have psm0 in /dev/ spite I have no loader.conf option right now. I assume that installing xf86 synaptics did the job. Simply, it does not scroll, with this configuration. I might need to rest a day or two, to sleep and to read more. Best regards and, once more, thanks all for help. Zoran ___ 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: buildkernel error ...
On 12/17/2012 1:35 AM, Chris H wrote: hi all, I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64 yesterday I have cvsup-ed src and was trying to buildkernel bellow is error I receive: --- [ cut ] - ... 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_reference.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_sizeof.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_machdep.c cc -c -x assembler-with-cpp -DLOCORE -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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_switch.S /usr/src/sys/amd64/acpica/acpi_switch.S: Assembler messages: /usr/src/sys/amd64/acpica/acpi_switch.S:146: Error: no such instruction: `xsetbv' /usr/src/sys/amd64/acpica/acpi_switch.S:147: Error: no such instruction: `xrstor (%rbx)' *** Error code 1 Stop in /usr/obj/usr/src/sys/ZEUS_HOME. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- [ cut ] - nothing is changed in my kernel configuration file ... Greetings, I too attempted a buildworld, and a kernel yesterday (also synced yesterday). It failed with a similar message to yours. I have _never_ experianced world, or kernel issues in the 25yrs I've been using BSD exclusively. Given that the only thing that has changed is the addition of clang, I'd recommend performing a: make clean then try again with: make -DWITHOUT_CLANG buildworld KERNCONF=your_kernel_name_here replacing your_kernel_name_here with the actual name of your KERNCONF file. I'm in the middle of a buildworld as I write this, that I believe will conclusively prove that clang was the reason my last attempt failed. HTH, and best wishes. --Chris P.S. This was also 9.1 -- Zeus V. Panchenko jid:z...@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) ___ 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 ___ 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: Strange CAM errors
On Mon, Dec 17, 2012 at 9:26 AM, Willem Jan Withagen w...@digiware.nlwrote:
On 2012-12-17 15:38, Steven Hartland wrote:
Check the smart results of each disk in the array you may have a failing
disk.
- Original Message - From: Willem Jan Withagen
w...@digiware.nl
To: FreeBSD Stable Users freebsd-stable@freebsd.org
Sent: Monday, December 17, 2012 10:58 AM
Subject: Strange CAM errors
Hi,
I have not noticed this before, but my system rebooted this morning and
in the following security report I found a lot of messgaes in the
dmesg-part like:
+(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0
+(probe0:arcmsr0:0:16:1): CAM status: Command timeout
+(probe0:arcmsr0:0:16:1): Retrying command
+(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0
+(probe0:arcmsr0:0:16:1): CAM status: Command timeout
+(probe0:arcmsr0:0:16:1): Retrying command
And it seems that bus 16 is:
+pass6 at arcmsr0 bus 0 scbus0 target 16 lun 0
+pass6: Areca RAID controller R001 Fixed Processor SCSI-0 device
The system has been running
FreeBSD zfs.digiware.nl 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #3: Wed
Nov 14 13:25:55 CET 2012
r...@zfs.digiware.nl:/usr/obj/usr/srcs/src9/src/sys/ZFS amd64
for already a while.
Anybody suggestions as to why I have these messages?
They are during the boot sequence, so no smartd talking to the disks at
that moment.
--WjW
ps: dmesg, config, etc at:
http://www.tegenbosch28.nl/FreeBSD/Systems/ZFS
ps2: upgrading to the most recent 9.1
'mmm,
Smartd seems to think otherwise...
'camcontrol rescan all' actually delivers the same pack of errors.
--WjW
The timeouts are occurring on inquiry commands to non-zero LUNs. arcmsr(4)
is returning CAM_SEL_TIMEOUT instead of CAM_DEV_NOT_THERE for inquiry
commands to this device and LUN 0. CAM_DEV_NOT_THERE is preferred to
remove these types of warnings, and similar patches have gone into for
other SCSI drivers recently.
Can you try this patch?
Index: sys/dev/arcmsr/arcmsr.c
===
--- sys/dev/arcmsr/arcmsr.c (revision 244190)
+++ sys/dev/arcmsr/arcmsr.c (working copy)
@@ -2439,7 +2439,7 @@
char *buffer=pccb-csio.data_ptr;
if (pccb-ccb_h.target_lun) {
- pccb-ccb_h.status |= CAM_SEL_TIMEOUT;
+ pccb-ccb_h.status |= CAM_DEV_NOT_THERE;
xpt_done(pccb);
return;
}
___
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: buildkernel error ...
On 12/17/2012 1:35 AM, Chris H wrote: hi all, I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64 yesterday I have cvsup-ed src and was trying to buildkernel bellow is error I receive: --- [ cut ] - ... 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_reference.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_sizeof.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_machdep.c cc -c -x assembler-with-cpp -DLOCORE -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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_switch.S /usr/src/sys/amd64/acpica/acpi_switch.S: Assembler messages: /usr/src/sys/amd64/acpica/acpi_switch.S:146: Error: no such instruction: `xsetbv' /usr/src/sys/amd64/acpica/acpi_switch.S:147: Error: no such instruction: `xrstor (%rbx)' *** Error code 1 Stop in /usr/obj/usr/src/sys/ZEUS_HOME. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- [ cut ] - nothing is changed in my kernel configuration file ... Greetings, I too attempted a buildworld, and a kernel yesterday (also synced yesterday). It failed with a similar message to yours. I have _never_ experianced world, or kernel issues in the 25yrs I've been using BSD exclusively. Given that the only thing that has changed is the addition of clang, I'd recommend performing a: make clean then try again with: make -DWITHOUT_CLANG buildworld KERNCONF=your_kernel_name_here replacing your_kernel_name_here with the actual name of your KERNCONF file. I'm in the middle of a buildworld as I write this, that I believe will conclusively prove that clang was the reason my last attempt failed. HTH, and best wishes. --Chris P.S. This was also 9.1 -- Zeus V. Panchenko jid:z...@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) ___ 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 ___ 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: buildkernel error ...
On 2012-12-17 07:08, Zeus Panchenko wrote: I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64 yesterday I have cvsup-ed src and was trying to buildkernel bellow is error I receive: ... cc -c -x assembler-with-cpp -DLOCORE -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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_switch.S /usr/src/sys/amd64/acpica/acpi_switch.S: Assembler messages: /usr/src/sys/amd64/acpica/acpi_switch.S:146: Error: no such instruction: `xsetbv' /usr/src/sys/amd64/acpica/acpi_switch.S:147: Error: no such instruction: `xrstor (%rbx)' *** Error code 1 This looks like a problem with your assembler; did you run make buildworld before make buildkernel? ___ 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: How do I circumvent the use of clang during build?
have a look at /etc/src.conf and $ man src.cof you can set many buildworld options there. -- View this message in context: http://freebsd.1045724.n5.nabble.com/How-do-I-circumvent-the-use-of-clang-during-build-tp5769907p5770203.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ 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: Strange CAM errors
On 17-12-2012 20:16, Jim Harris wrote:
On Mon, Dec 17, 2012 at 9:26 AM, Willem Jan Withagen w...@digiware.nl
mailto:w...@digiware.nl wrote:
On 2012-12-17 15:38, Steven Hartland wrote:
Check the smart results of each disk in the array you may have a
failing
disk.
- Original Message - From: Willem Jan Withagen
w...@digiware.nl mailto:w...@digiware.nl
To: FreeBSD Stable Users freebsd-stable@freebsd.org
mailto:freebsd-stable@freebsd.org
Sent: Monday, December 17, 2012 10:58 AM
Subject: Strange CAM errors
Hi,
I have not noticed this before, but my system rebooted this
morning and
in the following security report I found a lot of messgaes in the
dmesg-part like:
+(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0
+(probe0:arcmsr0:0:16:1): CAM status: Command timeout
+(probe0:arcmsr0:0:16:1): Retrying command
+(probe0:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0
+(probe0:arcmsr0:0:16:1): CAM status: Command timeout
+(probe0:arcmsr0:0:16:1): Retrying command
And it seems that bus 16 is:
+pass6 at arcmsr0 bus 0 scbus0 target 16 lun 0
+pass6: Areca RAID controller R001 Fixed Processor SCSI-0 device
The system has been running
FreeBSD zfs.digiware.nl http://zfs.digiware.nl 9.1-PRERELEASE
FreeBSD 9.1-PRERELEASE #3: Wed
Nov 14 13:25:55 CET 2012
r...@zfs.digiware.nl:/usr/obj/usr/srcs/src9/src/sys/ZFS amd64
for already a while.
Anybody suggestions as to why I have these messages?
They are during the boot sequence, so no smartd talking to the
disks at
that moment.
--WjW
ps: dmesg, config, etc at:
http://www.tegenbosch28.nl/FreeBSD/Systems/ZFS
ps2: upgrading to the most recent 9.1
'mmm,
Smartd seems to think otherwise...
'camcontrol rescan all' actually delivers the same pack of errors.
--WjW
The timeouts are occurring on inquiry commands to non-zero LUNs.
arcmsr(4) is returning CAM_SEL_TIMEOUT instead of CAM_DEV_NOT_THERE for
inquiry commands to this device and LUN 0. CAM_DEV_NOT_THERE is
preferred to remove these types of warnings, and similar patches have
gone into for other SCSI drivers recently.
Can you try this patch?
Index: sys/dev/arcmsr/arcmsr.c
===
--- sys/dev/arcmsr/arcmsr.c (revision 244190)
+++ sys/dev/arcmsr/arcmsr.c (working copy)
@@ -2439,7 +2439,7 @@
char *buffer=pccb-csio.data_ptr;
if (pccb-ccb_h.target_lun) {
- pccb-ccb_h.status |= CAM_SEL_TIMEOUT;
+ pccb-ccb_h.status |= CAM_DEV_NOT_THERE;
xpt_done(pccb);
return;
}
Hi Jim,
The noise has gone down by a factor of 5, now I get:
(probe6:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0
(probe6:arcmsr0:0:16:1): CAM status: Unable to terminate I/O CCB request
(probe6:arcmsr0:0:16:1): Error 5, Unretryable error
(probe6:arcmsr0:0:16:2): INQUIRY. CDB: 12 40 0 0 24 0
Which is defined in sys/cam/cam.c
as CAM_UA_TERMIO, but that error is nowhere set in the arcmsr code
So I clearly do not yet know enough to hellp in this.
--WjW
For all of the ports on the adapter.
___
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
WRITE_FPDMA_QUEUED CAM status: ATA Status Error
Hi, Is there a way to tell / narrow down if an issue with errors like below are due to a bad cable or bad port multiplier ? The disks in a particular cage are throwing errors like these below. (RELENG9 from today) siis0@pci0:5:0:0: class=0x010400 card=0x71241095 chip=0x31241095 rev=0x02 hdr=0x00 vendor = 'Silicon Image, Inc.' device = 'SiI 3124 PCI-X Serial ATA Controller' class = mass storage subclass = RAID bar [10] = type Memory, range 64, base 0xb4408000, size 128, enabled bar [18] = type Memory, range 64, base 0xb440, size 32768, enabled bar [20] = type I/O Port, range 32, base 0x3000, size 16, enabled cap 01[64] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 07[40] = PCI-X 64-bit supports 133MHz, 2048 burst read, 12 split transactions cap 05[54] = MSI supports 1 message, 64 bit enabled with 1 message siisch2: Error while READ LOG EXT (ada3:siisch2:0:3:0): WRITE_FPDMA_QUEUED. ACB: 61 56 af 71 0a 40 40 00 00 00 00 00 (ada3:siisch2:0:3:0): CAM status: ATA Status Error (ada3:siisch2:0:3:0): ATA status: 00 () (ada3:siisch2:0:3:0): RES: 00 00 00 00 00 00 00 00 00 00 00 (ada3:siisch2:0:3:0): Retrying command siisch2: Error while READ LOG EXT (ada2:siisch2:0:2:0): WRITE_FPDMA_QUEUED. ACB: 61 07 dc d8 0b 40 40 00 00 00 00 00 (ada2:siisch2:0:2:0): CAM status: ATA Status Error (ada2:siisch2:0:2:0): ATA status: 00 () (ada2:siisch2:0:2:0): RES: 00 00 00 00 00 00 00 00 00 00 00 (ada2:siisch2:0:2:0): Retrying command (ada2:siisch2:0:2:0): WRITE_FPDMA_QUEUED. ACB: 61 01 0c 1e 06 40 40 00 00 00 00 00 (ada2:siisch2:0:2:0): CAM status: ATA Status Error (ada2:siisch2:0:2:0): ATA status: 00 () (ada2:siisch2:0:2:0): RES: 00 00 00 00 00 00 00 00 00 00 00 (ada2:siisch2:0:2:0): Retrying command (ada2:siisch2:0:2:0): WRITE_FPDMA_QUEUED. ACB: 61 06 2d 88 00 40 40 00 00 00 00 00 (ada2:siisch2:0:2:0): CAM status: ATA Status Error (ada2:siisch2:0:2:0): ATA status: 00 () (ada2:siisch2:0:2:0): RES: 00 00 00 00 00 00 00 00 00 00 00 (ada2:siisch2:0:2:0): Retrying command # smartctl -x /dev/ada2 smartctl 6.0 2012-10-10 r3643 [FreeBSD 9.1-PRERELEASE amd64] (local build) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Black Device Model: WDC WD2002FAEX-007BA0 Serial Number:WD-WMAY02759120 LU WWN Device Id: 5 0014ee 656c4b593 Firmware Version: 05.01D05 User Capacity:2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Device is:In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is:Mon Dec 17 17:04:28 2012 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, NOT FROZEN [SEC1] === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection:(29280) seconds. Offline data collection capabilities:(0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 298) minutes. Conveyance self-test routine recommended polling time:( 5) minutes. SCT capabilities: (0x3037) SCT Status supported. SCT Feature Control supported.
Re: Strange CAM errors
On Mon, Dec 17, 2012 at 2:45 PM, Willem Jan Withagen w...@digiware.nlwrote:
On 17-12-2012 20:16, Jim Harris wrote:
The timeouts are occurring on inquiry commands to non-zero LUNs.
arcmsr(4) is returning CAM_SEL_TIMEOUT instead of CAM_DEV_NOT_THERE for
inquiry commands to this device and LUN 0. CAM_DEV_NOT_THERE is
preferred to remove these types of warnings, and similar patches have
gone into for other SCSI drivers recently.
Can you try this patch?
Index: sys/dev/arcmsr/arcmsr.c
===
--- sys/dev/arcmsr/arcmsr.c (revision 244190)
+++ sys/dev/arcmsr/arcmsr.c (working copy)
@@ -2439,7 +2439,7 @@
char *buffer=pccb-csio.data_ptr;
if (pccb-ccb_h.target_lun) {
- pccb-ccb_h.status |= CAM_SEL_TIMEOUT;
+ pccb-ccb_h.status |= CAM_DEV_NOT_THERE;
xpt_done(pccb);
return;
}
Hi Jim,
The noise has gone down by a factor of 5, now I get:
(probe6:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0
(probe6:arcmsr0:0:16:1): CAM status: Unable to terminate I/O CCB request
(probe6:arcmsr0:0:16:1): Error 5, Unretryable error
(probe6:arcmsr0:0:16:2): INQUIRY. CDB: 12 40 0 0 24 0
Which is defined in sys/cam/cam.c
as CAM_UA_TERMIO, but that error is nowhere set in the arcmsr code
There is something out of sync on your system. I just noticed this, but
your original error messages were showing Command timeout
(CAM_CMD_TIMEOUT) even though the driver was returning CAM_SEL_TIMEOUT.
Now in this case, driver is returning CAM_DEV_NOT_THERE, but CAM is
printing error message for CAM_UA_TERMIO. In both cases, driver is
returning value X, but cam is interpreting it as X+1. So CAM and arcmsr(4)
seem to have a different idea of the values of the cam_status enumeration.
Can you provide details on your build environment? Are you building arcmsr
as a loadable module or do you specify device arcmsr in your kernel
config to link it statically? I'm suspecting loadable module, although I
have no idea how these values would get out of sync since this enumeration
hasn't changed in probably 10+ years.
-Jim
___
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: WRITE_FPDMA_QUEUED CAM status: ATA Status Error
Hi. On 18.12.2012 00:07, Mike Tancsa wrote: Is there a way to tell / narrow down if an issue with errors like below are due to a bad cable or bad port multiplier ? The disks in a particular cage are throwing errors like these below. (RELENG9 from today) All the controller, the port multiplier and the disks are firmware- based devices. All of them may have firmware problems, that is not possible to diagnose from outside. When controller is talking to disk, multiplier is transparent, so it may be impossible to say where exactly problem happen. Speaking about cables and physical links, the only kind of information I can imagine to check physical link is counters represented below: SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 21 Command failed due to ICRC error 0x0002 21 R_ERR response for data FIS 0x0003 20 R_ERR response for device-to-host data FIS 0x0004 21 R_ERR response for host-to-device data FIS 0x0005 20 R_ERR response for non-data FIS 0x0006 20 R_ERR response for device-to-host non-data FIS 0x0007 20 R_ERR response for host-to-device non-data FIS 0x000a 20 Device-to-host register FISes sent due to a COMRESET 0x000b 21 CRC errors within host-to-device FIS 0x8000 4 7720 Vendor specific They may be reported by disks. IIRC they may also be reported by port multiplier, but I've never tried to access them and haven't seen the existing tools for it, except via doing bin-banging with camcontrol. Whether the controller can report something alike, I don't remember. -- Alexander Motin ___ 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: Strange CAM errors
On 17-12-2012 23:10, Jim Harris wrote:
On Mon, Dec 17, 2012 at 2:45 PM, Willem Jan Withagen w...@digiware.nl
mailto:w...@digiware.nl wrote:
On 17-12-2012 20:16, Jim Harris wrote:
The timeouts are occurring on inquiry commands to non-zero LUNs.
arcmsr(4) is returning CAM_SEL_TIMEOUT instead of
CAM_DEV_NOT_THERE for
inquiry commands to this device and LUN 0. CAM_DEV_NOT_THERE is
preferred to remove these types of warnings, and similar patches have
gone into for other SCSI drivers recently.
Can you try this patch?
Index: sys/dev/arcmsr/arcmsr.c
===
--- sys/dev/arcmsr/arcmsr.c (revision 244190)
+++ sys/dev/arcmsr/arcmsr.c (working copy)
@@ -2439,7 +2439,7 @@
char *buffer=pccb-csio.data_ptr;
if (pccb-ccb_h.target_lun) {
- pccb-ccb_h.status |= CAM_SEL_TIMEOUT;
+ pccb-ccb_h.status |= CAM_DEV_NOT_THERE;
xpt_done(pccb);
return;
}
Hi Jim,
The noise has gone down by a factor of 5, now I get:
(probe6:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0
(probe6:arcmsr0:0:16:1): CAM status: Unable to terminate I/O CCB request
(probe6:arcmsr0:0:16:1): Error 5, Unretryable error
(probe6:arcmsr0:0:16:2): INQUIRY. CDB: 12 40 0 0 24 0
Which is defined in sys/cam/cam.c
as CAM_UA_TERMIO, but that error is nowhere set in the arcmsr code
There is something out of sync on your system. I just noticed this, but
your original error messages were showing Command timeout
(CAM_CMD_TIMEOUT) even though the driver was returning CAM_SEL_TIMEOUT.
Now in this case, driver is returning CAM_DEV_NOT_THERE, but CAM is
printing error message for CAM_UA_TERMIO. In both cases, driver is
returning value X, but cam is interpreting it as X+1. So CAM and
arcmsr(4) seem to have a different idea of the values of the cam_status
enumeration.
Can you provide details on your build environment? Are you building
arcmsr as a loadable module or do you specify device arcmsr in your
kernel config to link it statically? I'm suspecting loadable module,
although I have no idea how these values would get out of sync since
this enumeration hasn't changed in probably 10+ years.
arcmsr is build in the kernel
[/usr/src] w...@zfs.digiware.nl kldstat
Id Refs AddressSize Name
1 28 0x8020 b55be0 kernel
21 0x80d56000 6138 nullfs.ko
31 0x80d5d000 2153b0 zfs.ko
42 0x80f73000 5e38 opensolaris.ko
51 0x80f79000 f510 aio.ko
61 0x80f89000 2a20 coretemp.ko
71 0x81012000 316d4nfscl.ko
82 0x81044000 10827nfscommon.ko
And I just refetched 9.1-PRERELEASE this afternoon over svn
Could this have something to do with Clang gcc
Not that I did anything to change this.
Note that I have nothing changed other than the KERNEL CONFIG file.
And both kernel and world were build at the same time this afternoon.
With your patch I just only rebuild kernel and modules.
--WjW
___
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: How do I circumvent the use of clang during build?
Wouldn't this be a case where man src.conf on his system actually wouldn't tell the OP what he wanted, as clang was not available as option in 8? Of course the online version of that man page from RELENG_9* would. Best regards Andreas On Mon, Dec 17, 2012 at 9:54 PM, Beeblebrox zap...@berentweb.com wrote: have a look at /etc/src.conf and $ man src.cof you can set many buildworld options there. -- View this message in context: http://freebsd.1045724.n5.nabble.com/How-do-I-circumvent-the-use-of-clang-during-build-tp5769907p5770203.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ 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 ___ 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: Strange CAM errors
On Mon, Dec 17, 2012 at 3:21 PM, Willem Jan Withagen w...@digiware.nlwrote:
On 17-12-2012 23:10, Jim Harris wrote:
On Mon, Dec 17, 2012 at 2:45 PM, Willem Jan Withagen w...@digiware.nl
mailto:w...@digiware.nl wrote:
On 17-12-2012 20:16, Jim Harris wrote:
The timeouts are occurring on inquiry commands to non-zero LUNs.
arcmsr(4) is returning CAM_SEL_TIMEOUT instead of
CAM_DEV_NOT_THERE for
inquiry commands to this device and LUN 0. CAM_DEV_NOT_THERE is
preferred to remove these types of warnings, and similar patches
have
gone into for other SCSI drivers recently.
Can you try this patch?
Index: sys/dev/arcmsr/arcmsr.c
===
--- sys/dev/arcmsr/arcmsr.c (revision 244190)
+++ sys/dev/arcmsr/arcmsr.c (working copy)
@@ -2439,7 +2439,7 @@
char *buffer=pccb-csio.data_ptr;
if (pccb-ccb_h.target_lun) {
- pccb-ccb_h.status |= CAM_SEL_TIMEOUT;
+ pccb-ccb_h.status |= CAM_DEV_NOT_THERE;
xpt_done(pccb);
return;
}
Hi Jim,
The noise has gone down by a factor of 5, now I get:
(probe6:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0
(probe6:arcmsr0:0:16:1): CAM status: Unable to terminate I/O CCB
request
(probe6:arcmsr0:0:16:1): Error 5, Unretryable error
(probe6:arcmsr0:0:16:2): INQUIRY. CDB: 12 40 0 0 24 0
Which is defined in sys/cam/cam.c
as CAM_UA_TERMIO, but that error is nowhere set in the arcmsr
code
There is something out of sync on your system. I just noticed this, but
your original error messages were showing Command timeout
(CAM_CMD_TIMEOUT) even though the driver was returning CAM_SEL_TIMEOUT.
Now in this case, driver is returning CAM_DEV_NOT_THERE, but CAM is
printing error message for CAM_UA_TERMIO. In both cases, driver is
returning value X, but cam is interpreting it as X+1. So CAM and
arcmsr(4) seem to have a different idea of the values of the cam_status
enumeration.
Can you provide details on your build environment? Are you building
arcmsr as a loadable module or do you specify device arcmsr in your
kernel config to link it statically? I'm suspecting loadable module,
although I have no idea how these values would get out of sync since
this enumeration hasn't changed in probably 10+ years.
arcmsr is build in the kernel
[/usr/src] w...@zfs.digiware.nl kldstat
Id Refs AddressSize Name
1 28 0x8020 b55be0 kernel
21 0x80d56000 6138 nullfs.ko
31 0x80d5d000 2153b0 zfs.ko
42 0x80f73000 5e38 opensolaris.ko
51 0x80f79000 f510 aio.ko
61 0x80f89000 2a20 coretemp.ko
71 0x81012000 316d4nfscl.ko
82 0x81044000 10827nfscommon.ko
And I just refetched 9.1-PRERELEASE this afternoon over svn
Could this have something to do with Clang gcc
Not that I did anything to change this.
Note that I have nothing changed other than the KERNEL CONFIG file.
And both kernel and world were build at the same time this afternoon.
With your patch I just only rebuild kernel and modules.
Never mind my earlier comment on out-of-sync. It's another bug in
arcmsr(4) - CAM_REQ_CMP == 0x1, and in the LUN 0 case here it OR's the
status values together, causing the off-by-one issue we were seeing.
Please try the following patch instead (reverting earlier patch):
Index: sys/dev/arcmsr/arcmsr.c
===
--- sys/dev/arcmsr/arcmsr.c (revision 244190)
+++ sys/dev/arcmsr/arcmsr.c (working copy)
@@ -2432,14 +2432,13 @@
static void arcmsr_handle_virtual_command(struct AdapterControlBlock *acb,
union ccb * pccb)
{
- pccb-ccb_h.status |= CAM_REQ_CMP;
switch (pccb-csio.cdb_io.cdb_bytes[0]) {
case INQUIRY: {
unsigned char inqdata[36];
char *buffer=pccb-csio.data_ptr;
if (pccb-ccb_h.target_lun) {
- pccb-ccb_h.status |= CAM_SEL_TIMEOUT;
+ pccb-ccb_h.status |= CAM_DEV_NOT_THERE;
xpt_done(pccb);
return;
}
@@ -2455,6 +2454,7 @@
strncpy(inqdata[16], RAID controller , 16); /* Product
Identification */
strncpy(inqdata[32], R001, 4); /* Product Revision */
memcpy(buffer, inqdata, sizeof(inqdata));
+ pccb-ccb_h.status |= CAM_REQ_CMP;
xpt_done(pccb);
}
break;
@@ -2464,10 +2464,12 @@
pccb-ccb_h.status |= CAM_SCSI_STATUS_ERROR;
Re: Strange CAM errors
On 17-12-2012 23:43, Jim Harris wrote:
On Mon, Dec 17, 2012 at 3:21 PM, Willem Jan Withagen w...@digiware.nlwrote:
On 17-12-2012 23:10, Jim Harris wrote:
On Mon, Dec 17, 2012 at 2:45 PM, Willem Jan Withagen w...@digiware.nl
mailto:w...@digiware.nl wrote:
On 17-12-2012 20:16, Jim Harris wrote:
The timeouts are occurring on inquiry commands to non-zero LUNs.
arcmsr(4) is returning CAM_SEL_TIMEOUT instead of
CAM_DEV_NOT_THERE for
inquiry commands to this device and LUN 0. CAM_DEV_NOT_THERE is
preferred to remove these types of warnings, and similar patches
have
gone into for other SCSI drivers recently.
Can you try this patch?
Index: sys/dev/arcmsr/arcmsr.c
===
--- sys/dev/arcmsr/arcmsr.c (revision 244190)
+++ sys/dev/arcmsr/arcmsr.c (working copy)
@@ -2439,7 +2439,7 @@
char *buffer=pccb-csio.data_ptr;
if (pccb-ccb_h.target_lun) {
- pccb-ccb_h.status |= CAM_SEL_TIMEOUT;
+ pccb-ccb_h.status |= CAM_DEV_NOT_THERE;
xpt_done(pccb);
return;
}
Hi Jim,
The noise has gone down by a factor of 5, now I get:
(probe6:arcmsr0:0:16:1): INQUIRY. CDB: 12 20 0 0 24 0
(probe6:arcmsr0:0:16:1): CAM status: Unable to terminate I/O CCB
request
(probe6:arcmsr0:0:16:1): Error 5, Unretryable error
(probe6:arcmsr0:0:16:2): INQUIRY. CDB: 12 40 0 0 24 0
Which is defined in sys/cam/cam.c
as CAM_UA_TERMIO, but that error is nowhere set in the arcmsr
code
There is something out of sync on your system. I just noticed this, but
your original error messages were showing Command timeout
(CAM_CMD_TIMEOUT) even though the driver was returning CAM_SEL_TIMEOUT.
Now in this case, driver is returning CAM_DEV_NOT_THERE, but CAM is
printing error message for CAM_UA_TERMIO. In both cases, driver is
returning value X, but cam is interpreting it as X+1. So CAM and
arcmsr(4) seem to have a different idea of the values of the cam_status
enumeration.
Can you provide details on your build environment? Are you building
arcmsr as a loadable module or do you specify device arcmsr in your
kernel config to link it statically? I'm suspecting loadable module,
although I have no idea how these values would get out of sync since
this enumeration hasn't changed in probably 10+ years.
arcmsr is build in the kernel
[/usr/src] w...@zfs.digiware.nl kldstat
Id Refs AddressSize Name
1 28 0x8020 b55be0 kernel
21 0x80d56000 6138 nullfs.ko
31 0x80d5d000 2153b0 zfs.ko
42 0x80f73000 5e38 opensolaris.ko
51 0x80f79000 f510 aio.ko
61 0x80f89000 2a20 coretemp.ko
71 0x81012000 316d4nfscl.ko
82 0x81044000 10827nfscommon.ko
And I just refetched 9.1-PRERELEASE this afternoon over svn
Could this have something to do with Clang gcc
Not that I did anything to change this.
Note that I have nothing changed other than the KERNEL CONFIG file.
And both kernel and world were build at the same time this afternoon.
With your patch I just only rebuild kernel and modules.
Never mind my earlier comment on out-of-sync. It's another bug in
arcmsr(4) - CAM_REQ_CMP == 0x1, and in the LUN 0 case here it OR's the
status values together, causing the off-by-one issue we were seeing.
Please try the following patch instead (reverting earlier patch):
Index: sys/dev/arcmsr/arcmsr.c
===
--- sys/dev/arcmsr/arcmsr.c (revision 244190)
+++ sys/dev/arcmsr/arcmsr.c (working copy)
@@ -2432,14 +2432,13 @@
static void arcmsr_handle_virtual_command(struct AdapterControlBlock *acb,
union ccb * pccb)
{
- pccb-ccb_h.status |= CAM_REQ_CMP;
switch (pccb-csio.cdb_io.cdb_bytes[0]) {
case INQUIRY: {
unsigned char inqdata[36];
char *buffer=pccb-csio.data_ptr;
if (pccb-ccb_h.target_lun) {
- pccb-ccb_h.status |= CAM_SEL_TIMEOUT;
+ pccb-ccb_h.status |= CAM_DEV_NOT_THERE;
xpt_done(pccb);
return;
}
@@ -2455,6 +2454,7 @@
strncpy(inqdata[16], RAID controller , 16); /* Product
Identification */
strncpy(inqdata[32], R001, 4); /* Product Revision */
memcpy(buffer, inqdata, sizeof(inqdata));
+ pccb-ccb_h.status |= CAM_REQ_CMP;
xpt_done(pccb);
}
break;
@@ -2464,10 +2464,12 @@
pccb-ccb_h.status |=
Re: Strange CAM errors
On Mon, Dec 17, 2012 at 4:52 PM, Willem Jan Withagen w...@digiware.nlwrote: Right, That did the trick. Thanx for the code. --WjW Patch committed as r244369. It will get MFC'd but obviously won't be in 9.1. Thanks, -Jim ___ 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: buildkernel error ...
On 12/17/2012 1:35 AM, Chris H wrote: hi all, I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64 yesterday I have cvsup-ed src and was trying to buildkernel bellow is error I receive: --- [ cut ] - ... 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_reference.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_sizeof.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_machdep.c cc -c -x assembler-with-cpp -DLOCORE -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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_switch.S /usr/src/sys/amd64/acpica/acpi_switch.S: Assembler messages: /usr/src/sys/amd64/acpica/acpi_switch.S:146: Error: no such instruction: `xsetbv' /usr/src/sys/amd64/acpica/acpi_switch.S:147: Error: no such instruction: `xrstor (%rbx)' *** Error code 1 Stop in /usr/obj/usr/src/sys/ZEUS_HOME. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- [ cut ] - nothing is changed in my kernel configuration file ... Greetings, I too attempted a buildworld, and a kernel yesterday (also synced yesterday). It failed with a similar message to yours. I have _never_ experianced world, or kernel issues in the 25yrs I've been using BSD exclusively. Given that the only thing that has changed is the addition of clang, I'd recommend performing a: make clean then try again with: make -DWITHOUT_CLANG buildworld KERNCONF=your_kernel_name_here replacing your_kernel_name_here with the actual name of your KERNCONF file. I'm in the middle of a buildworld as I write this, that I believe will conclusively prove that clang was the reason my last attempt failed. HTH, and best wishes. --Chris P.S. This was also 9.1 -- Zeus V. Panchenko jid:z...@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) ___ 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 ___ freebsd-stable@freebsd.org mailing list
Re: buildkernel error ...
On 12/17/2012 1:35 AM, Chris H wrote: hi all, I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64 yesterday I have cvsup-ed src and was trying to buildkernel bellow is error I receive: --- [ cut ] - ... 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_reference.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_sizeof.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_machdep.c cc -c -x assembler-with-cpp -DLOCORE -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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_switch.S /usr/src/sys/amd64/acpica/acpi_switch.S: Assembler messages: /usr/src/sys/amd64/acpica/acpi_switch.S:146: Error: no such instruction: `xsetbv' /usr/src/sys/amd64/acpica/acpi_switch.S:147: Error: no such instruction: `xrstor (%rbx)' *** Error code 1 Stop in /usr/obj/usr/src/sys/ZEUS_HOME. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- [ cut ] - nothing is changed in my kernel configuration file ... Greetings, I too attempted a buildworld, and a kernel yesterday (also synced yesterday). It failed with a similar message to yours. I have _never_ experianced world, or kernel issues in the 25yrs I've been using BSD exclusively. Given that the only thing that has changed is the addition of clang, I'd recommend performing a: make clean then try again with: make -DWITHOUT_CLANG buildworld KERNCONF=your_kernel_name_here replacing your_kernel_name_here with the actual name of your KERNCONF file. I'm in the middle of a buildworld as I write this, that I believe will conclusively prove that clang was the reason my last attempt failed. HTH, and best wishes. --Chris P.S. This was also 9.1 -- Zeus V. Panchenko jid:z...@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) ___ 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 ___ freebsd-stable@freebsd.org mailing list
Re: How do I circumvent the use of clang during build?
Greetings Beeblebrox, and thank you for your reply. have a look at /etc/src.conf and $ man src.cof you can set many buildworld options there. Good advise! Thanks. --Chris -- View this message in context: http://freebsd.1045724.n5.nabble.com/How-do-I-circumvent-the-use-of-clang-during-build-tp5769907p5770203.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ 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 -- ___ 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: buildkernel error ...
On 2012-12-17 (Monday) 17:02:06 Chris H wrote: On 12/17/2012 1:35 AM, Chris H wrote: hi all, I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64 yesterday I have cvsup-ed src and was trying to buildkernel bellow is error I receive: --- [ cut ] - ... 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_reference.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_sizeof.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_machdep.c cc -c -x assembler-with-cpp -DLOCORE -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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_switch.S /usr/src/sys/amd64/acpica/acpi_switch.S: Assembler messages: /usr/src/sys/amd64/acpica/acpi_switch.S:146: Error: no such instruction: `xsetbv' /usr/src/sys/amd64/acpica/acpi_switch.S:147: Error: no such instruction: `xrstor (%rbx)' *** Error code 1 Stop in /usr/obj/usr/src/sys/ZEUS_HOME. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- [ cut ] - nothing is changed in my kernel configuration file ... Greetings, I too attempted a buildworld, and a kernel yesterday (also synced yesterday). It failed with a similar message to yours. I have _never_ experianced world, or kernel issues in the 25yrs I've been using BSD exclusively. Given that the only thing that has changed is the addition of clang, I'd recommend performing a: make clean then try again with: make -DWITHOUT_CLANG buildworld KERNCONF=your_kernel_name_here replacing your_kernel_name_here with the actual name of your KERNCONF file. I'm in the middle of a buildworld as I write this, that I believe will conclusively prove that clang was the reason my last attempt failed. HTH, and best wishes. --Chris P.S. This was also 9.1 -- Zeus V. Panchenko jid:z...@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to
Re: How do I circumvent the use of clang during build?
Greetings, and thank you for your reply. Wouldn't this be a case where man src.conf on his system actually wouldn't tell the OP what he wanted, as clang was not available as option in 8? Of course the online version of that man page from RELENG_9* would. Indeed, and _boy_ was I surprised, when I watched it start to build. I found no mention of it in updating either. Thanks again, for your reply. --Chris Best regards Andreas On Mon, Dec 17, 2012 at 9:54 PM, Beeblebrox zap...@berentweb.com wrote: have a look at /etc/src.conf and $ man src.cof you can set many buildworld options there. -- View this message in context: http://freebsd.1045724.n5.nabble.com/How-do-I-circumvent-the-use-of-clang-during-build-tp5769907p5770203.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ 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 ___ 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 -- ___ 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: buildkernel error ...
On 2012-12-17 (Monday) 17:02:06 Chris H wrote: On 12/17/2012 1:35 AM, Chris H wrote: hi all, I run FreeBSD 9.0-STABLE #1: Sun Apr 15 21:08:51 UTC 2012 amd64 yesterday I have cvsup-ed src and was trying to buildkernel bellow is error I receive: --- [ cut ] - ... 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_reference.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/xdr/xdr_sizeof.c 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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_machdep.c cc -c -x assembler-with-cpp -DLOCORE -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 -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -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 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/amd64/acpica/acpi_switch.S /usr/src/sys/amd64/acpica/acpi_switch.S: Assembler messages: /usr/src/sys/amd64/acpica/acpi_switch.S:146: Error: no such instruction: `xsetbv' /usr/src/sys/amd64/acpica/acpi_switch.S:147: Error: no such instruction: `xrstor (%rbx)' *** Error code 1 Stop in /usr/obj/usr/src/sys/ZEUS_HOME. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. --- [ cut ] - nothing is changed in my kernel configuration file ... Greetings, I too attempted a buildworld, and a kernel yesterday (also synced yesterday). It failed with a similar message to yours. I have _never_ experianced world, or kernel issues in the 25yrs I've been using BSD exclusively. Given that the only thing that has changed is the addition of clang, I'd recommend performing a: make clean then try again with: make -DWITHOUT_CLANG buildworld KERNCONF=your_kernel_name_here replacing your_kernel_name_here with the actual name of your KERNCONF file. I'm in the middle of a buildworld as I write this, that I believe will conclusively prove that clang was the reason my last attempt failed. HTH, and best wishes. --Chris P.S. This was also 9.1 -- Zeus V. Panchenkojid:z...@im.ibs.dn.ua IT Dpt., I.B.S. LLCGMT+2 (EET) ___ 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: thinkpad and synaptics
If you plan to use the Xorg synaptics driver you *must* remove moused_enable from rc.conf, Xorg can't use the synaptics mouse if the moused already sits on the /dev/psm0 device. This is not really well documented, tough. I've sent a PR to document pkg-message for xf85-input-synaptics but it has never been checked, http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148591 See the documentation in the patch.txt, it should works. Regards 2012/12/17 Zoran Kolic zko...@sbb.rs As first, thanks for answer. Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard Option AutoAddDevices Off EndSection [...] Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection In rc.conf: moused_enable=YES in loader.conf: hw.psm.synaptics_support=1 OK. I know it is writen zillion times and it still does not work for me. It is thinkpad e320, amd64, 9.1, kms. I had a lot of problems regarding fonts and non working vertical scroll on the pad. What I did: put synaptics_support run moused changed xorg.conf in a million ways This xorg.conf is similar to mine. I also have psm0 in /dev/ spite I have no loader.conf option right now. I assume that installing xf86 synaptics did the job. Simply, it does not scroll, with this configuration. I might need to rest a day or two, to sleep and to read more. Best regards and, once more, thanks all for help. Zoran ___ 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 -- Demelier David ___ 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
