Re: [SPF:fail] Re: [PATCH] SASL problems with spnego on 8.0-BETA4
On 23/02/2010 14:18, Alexander Nedotsukov wrote: The patch in question was committed a few month ago. I can only add that on my 8-STABLE machine the combination of cyrus/gssapi/openldap works fine. You have to check if output of ldd /usr/lib/libgssapi_krb5.so produce output like this: /usr/lib/libgssapi_krb5.so: libgssapi.so.10 = /usr/lib/libgssapi.so.10 (0x281ac000) libkrb5.so.10 = /usr/lib/libkrb5.so.10 (0x2830) libhx509.so.10 = /usr/lib/libhx509.so.10 (0x281b5000) libcrypto.so.6 = /lib/libcrypto.so.6 (0x2835b000) libroken.so.10 = /usr/lib/libroken.so.10 (0x281e9000) libasn1.so.10 = /usr/lib/libasn1.so.10 (0x284ae000) libcom_err.so.5 = /usr/lib/libcom_err.so.5 (0x281f8000) libcrypt.so.5 = /lib/libcrypt.so.5 (0x28527000) libc.so.7 = /lib/libc.so.7 (0x2808e000) On 23.02.2010, at 2:06, George Mamalakis wrote: On 07/10/2009 07:38, John Marshall wrote: access with gssapi auth from a client succeeded. Perhaps George Mamalakis could test the _spnego case? Guys, I am terribly sorry to tell you that I just now saw this conversation(!?!! 4 months later !!!). This is due to the fact that at that time I was mainly tracking the fbsd-stable list (my first email started in fbsd-stable list), and since I use filters in thunderbird, I never got to see your emails in my inbox...truly sorry once more!!! I don't know if Alexander's patch is still valid but from what I realize -since I have built many systems based on fbsd-stable (with latest sources) and I had to hack krb5-config in order to achieve correct behavior of cyrus/gssapi/spnego/openldap- it hasn't yet been commited to fbsd8-stable sources. If so, I will apply it on my machines and rerun my applications. Sorry again for the delay! -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 Alexander, using sources of 19/02/2010, I recompiled cyrus with the original /usr/bin/krb5-config, and ldapwhoami worked fine. The output of ldd /usr/lib/libgssapi_krb5.so is the one to be expected, so things must be ok. The only problem I still have, and which has to do with freebsd/heimdal/openldap/cyrus bundle, is that openldap-sasl-client (i386) segfaults when using ldapwhoami if run without having obtained a ticket first. I have sent an email to fbsd-stable list with subject: openldap client GSSAPI authentication segfaults in fbsd8stable i386 regarding this issue, where I list all my tests on all different machines, and a stack trace of the system where ldapwhoami segfaults. I have received no answer for this topic yet, but I think that if some of you reads it, he may find an answer. At the time of this writing, on fbsd8stable systems (i386) with heimdal/openldap-sasl-client/cyrus-sasl, ldapwhoami and ldapsearch segfault when called without a ticket. Thank you for your answer, and I am looking forward to see some feedback on this issue. Best regards, George Mamalakis -- George Mamalakis IT Officer Electrical and Computer Engineer (Aristotle Un. of Thessaloniki), MSc (Imperial College of London) Department of Electrical and Computer Engineering Faculty of Engineering Aristotle University of Thessaloniki phone number : +30 (2310) 994379 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [SPF:fail] Re: [PATCH] SASL problems with spnego on 8.0-BETA4
On 25/02/2010 13:42, George Mamalakis wrote: I have sent an email to fbsd-stable list with subject: openldap client GSSAPI authentication segfaults in fbsd8stable i386 regarding this issue, where I list all my tests on all different machines, and a stack trace of the system where ldapwhoami segfaults. I have received no answer for this topic yet, but I think that if some of you reads it, he may find an answer. At the time of this writing, on fbsd8stable systems (i386) with heimdal/openldap-sasl-client/cyrus-sasl, ldapwhoami and ldapsearch segfault when called without a ticket. Moreover, as stated in this mail (subject: openldap client GSSAPI authentication segfaults in fbsd8stable i386), which I have copied in this email along with one correction after this paragraph, the problem seems to be with gss_release_buffer () from /usr/lib/libgssapi.so.10. Please read my comment and little hack we tried over this function, on the end of the aforementioned email, I think it will help. Thank you all for your help, once more. Dear all, I am facing many instabilities in FBSD8 with openldap-client and sasl authentication (GSSAPI in particular). I have setup an openldap 2.4.1 server with gssapi support (through cyrus-sasl-2.1.23) on a fbsd8-stable amd64 latest sources, in a esxi host. In the same host I have setup two fbsd8-stable i386 clients; one has latest sources, the other one is installed via the iso-image of January's fbsd snapshot; on both systems openldap client and sasl is installed (all ldap/cyrus versions on all hosts mentioned in this email are the same). My laptop has fbsd8-i386 stable (sources 25 January 2010), and on my laptop I have setup an fbsd8-stable i386 (snapshot iso image) on a virtualbox client. Lastly, on the esxi host I have setup another fbsd8-stable amd64 system, to act as an ldap client (latest sources). To summarize, and put a label-number on each host, we have: 1 - esxi: fbsd8(latest) amd64 openldap server 2 - esxi: fbsd8(latest) i386 openldap client 3 - esxi: fbsd8(snapshot) i386 openldap client 4 - esxi: fbsd8(latest) amd64 openldap client 5 - laptop: fbsd8(jan 25) i386 openldap client 6 - laptop/vbox: fbsd8(snapshot) i386 openldap client The openldap server is installed in a jail, and the client is tested in the same jail. Kerberos works on all machines (same /etc/krb5.conf), and ldap as well. In all machines, line 96 of /usr/bin/krb5-config is changed to read: lib_flags=$lib_flags -lgssapi -lgssapi_spnego -lgssapi_krb5 -lheimntlm instead of: lib_flags=$lib_flags -lgssapi -lheimntlm which was the default, since without these lines I couldn't get gssapi authentication to work for cyrus (and spnego). This change was made after recommendations given from this very mailing list, and I was very happy to see that the ldap server worked as I expected. On all system, cat /usr/local/etc/openldap/ldap.conf: BASEdc=ee,dc=auth,dc=gr URI ldap://ldap.ee.auth.gr SASL_MECHGSSAPI without kiniting in any client I get the following outcomes when I give ldapwhoami (with no arguments): 1: SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Local error (-2) additional info: SASL(-1): generic failure: GSSAPI Error: Miscellaneous failure (see text) (unknown mech-code 2 for mech unknown) which is expected. 2: SASL/GSSAPI authentication started Segmentation fault: 11 (core dumped) which is not rational at all 3: SASL/GSSAPI authentication started Segmentation fault: 11 (core dumped) 4: SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Local error (-2) additional info: SASL(-1): generic failure: GSSAPI Error: Miscellaneous failure (see text) (unknown mech-code 2 for mech unknown) which is the same as 1 (as expected) 5: SASL/GSSAPI authentication started Segmentation fault: 11 (core dumped) 6: SASL/GSSAPI authentication started Segmentation fault: 11 (core dumped) if I kinit to mamalos, ldapwhoami returns: 1: SASL/GSSAPI authentication started SASL username: mama...@ee.auth.gr SASL SSF: 56 SASL data security layer installed. dn:uid=mamalos,ou=people,dc=ee,dc=auth,dc=gr which is super! 2: SASL/GSSAPI authentication started Segmentation fault: 11 (core dumped) which is dramatic. 3: SASL/GSSAPI authentication started Segmentation fault: 11 (core dumped) 4: SASL/GSSAPI authentication started ldap_sasl_interactive_bind_s: Local error (-2) additional info: SASL(-1): generic failure: GSSAPI Error: Miscellaneous failure (see text) (unknown mech-code 2529638919 for mech unknown) which is very strange, since mech-code seems unnaturally large. 5: SASL/GSSAPI authentication started SASL username: mama...@ee.auth.gr SASL SSF: 56 SASL data security layer installed. dn:uid=mamalos,ou=people,dc=ee,dc=auth,dc=gr which is super, but without kinit the same command segfaulted on this machine 6: SASL/GSSAPI authentication started SASL username: mama...@ee.auth.gr SASL SSF: 56 SASL data security
ATA CDROM no more detected with ATA_CAM under VMWare WS
Hello, Updating a -CURRENT system from Jan 10 to Feb 21, under VMWare WS 5.5.9, the virtual ATA CDROM is no more detected. This is with an ATA_CAM kernel. The CDROM is detected with a non ATA_CAM kernel. Here are: demesg 2010/01/10 source, ATA_CAM kernel Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #0: Tue Jan 12 16:08:41 CET 2010 t...@zaza.home.tbf:/home/obj/home/src/sys/VMWARE i386 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1.86GHz (1859.06-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6d8 Stepping = 8 Features=0xfe9fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS AMD Features=0x10NX real memory = 268435456 (256 MB) avail memory = 253235200 (241 MB) module_register_init: MOD_LOAD (vesa, 0xc06e4fd0, 0) error 6 acpi0: PTLTD RSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge on hostb0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1050-0x105f at device 7.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x1060-0x107f irq 9 at device 7.2 on pci0 uhci0: [ITHREAD] usbus0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 pci0: bridge at device 7.3 (no driver attached) vgapci0: VGA-compatible display port 0x1440-0x144f mem 0xf000-0xf7ff, 0xe800-0xe87f at device 15.0 on pci0 le0: AMD PCnet-PCI port 0x1080-0x10ff irq 11 at device 16.0 on pci0 le0: 16 receive buffers, 4 transmit buffers le0: Ethernet address: 00:0c:29:69:06:7f le0: [ITHREAD] pcm0: AudioPCI ES1371-A port 0x1400-0x143f irq 10 at device 17.0 on pci0 pcm0: Cirrus Logic CS4297A AC97 Codec pcm0: [ITHREAD] pcm0: Playback: DAC1,DAC2 / Record: ADC acpi_acad0: AC Adapter on acpi0 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 ppc0: Parallel port port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppc0: [ITHREAD] ppbus0: Parallel port bus on ppc0 uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] uart1: 16550 or compatible port 0x2f8-0x2ff irq 3 on acpi0 uart1: [FILTER] fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: 1440-KB 3.5 drive on fdc0 drive 0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xc-0xc7fff,0xc8000-0xc8fff, 0xdc000-0xd,0xe-0xe3fff pnpid ORM on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 12 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 1859059329 Hz quality 800 Timecounters tick every 10.000 msec usbus0: 12Mbps Full Speed USB v1.0 ugen0.1: Intel at usbus0 uhub0: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0 uhub0: 2 ports with 2 removable, self powered ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: VMware Virtual IDE Hard Drive 0001 ATA-4 device ada0: 33.300MB/s transfers (UDMA2, PIO size 32768bytes) ada0: 8192MB (16777216 512 byte sectors: 15H 63S/T 16383C) cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: SONY DVD+-RW DW-D56A PDS7 Removable CD-ROM SCSI-0 device cd0: 33.300MB/s transfers (UDMA2, PIO size 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ada0s1a Verbose dmesg 2010/02/21 source ATA_CAM kernel Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #0: Tue Feb 23 15:16:12 CET 2010 t...@zaza.home.tbf:/home/obj/home/src/sys/VMWARE i386 Preloaded elf kernel /boot/kernel/kernel at 0xc092e000. Preloaded elf module /boot/kernel/snd_es137x.ko at 0xc092e19c. Preloaded elf module /boot/kernel/sound.ko at 0xc092e24c. Timecounter i8254 frequency 1193182 Hz quality 0 Calibrating
panic ia64 r204293
I'm upgrading from 8.0-stable to 9.0-current. Got this panic. Any advice? many thanks anton ## Loading.: FreeBSD Starting: FreeBSD Consoles: EFI console FreeBSD/ia64 EFI boot, Revision 2.1 (me...@mech-as28.men.bris.ac.uk, Thu Feb 25 10:06:10 GMT 2010) Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0xa5209d+0x1c6933 syms=[0x8+0x80400+0x8+0x751a2] \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Entering /boot/kernel/kernel at 0xe4078000... GDB: debug ports: uart GDB: current port: uart KDB: debugger backends: ddb gdb KDB: current backend: ddb Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #0 r204293: Thu Feb 25 12:38:11 GMT 2010 me...@mech-as28.men.bris.ac.uk:/usr/obj/usr/src/sys/ZEEV ia64 WARNING: WITNESS option enabled, expect reduced performance. CPU: Madison II (1600 Mhz Itanium 2) Origin = GenuineIntel Revision = 2 Features = 0x1LB real memory = 12849717248 (12254 MB) avail memory = 12585984000 (12002 MB) FPSWA Revision = 0x10012, Entry = 0xe040ffcc4050 ACPI Warning: 32/64X length mismatch in Gpe0Block: 32/16 (20100121/tbfadt-625) ACPI Warning: 32/64X length mismatch in Gpe1Block: 32/16 (20100121/tbfadt-625) acpi0: HP on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 32-bit timer at 3.579545MHz iomem 0xff5c1004-0xff5c1007 on acpi0 cpu0: ACPI CPU on acpi0 acpi_tz0: Thermal Zone on acpi0 pcib0: ACPI Host-PCI bridge on acpi0 pci0: ACPI PCI bus on pcib0 ohci0: NEC uPD 9210 USB controller mem 0x80002000-0x80002fff irq 16 at device 1.0 on pci0 ohci0: [ITHREAD] usbus0: NEC uPD 9210 USB controller on ohci0 ohci1: NEC uPD 9210 USB controller mem 0x80001000-0x80001fff irq 17 at device 1.1 on pci0 ohci1: [ITHREAD] usbus1: NEC uPD 9210 USB controller on ohci1 ehci0: NEC uPD 720100 USB 2.0 controller mem 0x8000-0x80ff irq 18 at device 1.2 on pci0 ehci0: [ITHREAD] usbus2: EHCI version 0.95 usbus2: NEC uPD 720100 USB 2.0 controller on ehci0 pci0: mass storage, ATA at device 2.0 (no driver attached) pcib1: ACPI Host-PCI bridge on acpi0 pci32: ACPI PCI bus on pcib1 mpt0: LSILogic 1030 Ultra4 Adapter port 0x2100-0x21ff mem 0x903a-0x903b,0x9038-0x9039 irq 27 at device 1.0 on pci32 mpt0: [ITHREAD] mpt0: MPI Version=1.2.12.0 mpt1: LSILogic 1030 Ultra4 Adapter port 0x2000-0x20ff mem 0x9036-0x9037,0x9034-0x9035 irq 28 at device 1.1 on pci32 mpt1: [ITHREAD] mpt1: MPI Version=1.2.12.0 em0: Intel(R) PRO/1000 Network Connection 6.9.25 port 0x2240-0x227f mem 0x9032-0x9033,0x9028-0x902f irq 29 at device 2.0 on pci32 em0: [FILTER] em0: Ethernet address: 00:13:21:5b:05:1c em1: Intel(R) PRO/1000 Network Connection 6.9.25 port 0x2200-0x223f mem 0x9030-0x9031 irq 30 at device 2.1 on pci32 em1: [FILTER] em1: Ethernet address: 00:13:21:5b:05:1d pcib2: ACPI Host-PCI bridge on acpi0 pci64: ACPI PCI bus on pcib2 pcib3: ACPI Host-PCI bridge on acpi0 pci96: ACPI PCI bus on pcib3 pcib4: ACPI Host-PCI bridge on acpi0 pci128: ACPI PCI bus on pcib4 pcib5: ACPI Host-PCI bridge on acpi0 pci192: ACPI PCI bus on pcib5 isp0: Qlogic ISP 2422 PCI FC-AL Adapter port 0xc000-0xc0ff mem 0xe004-0xe0040fff irq 71 at device 1.0 on pci192 isp0: [ITHREAD] pcib6: ACPI Host-PCI bridge on acpi0 pci224: ACPI PCI bus on pcib6 uart0: 16550 or compatible mem 0xf8051000-0xf805100f irq 82 at device 1.0 on pci224 uart0: [FILTER] puc0: HP Diva Serial [GSP] uart1: Non-standard ns8250 class UART with FIFOs on puc0 uart1: [FILTER] uart1: console (9600,n,8,1) uart2: Non-standard ns8250 class UART with FIFOs on puc0 uart2: [FILTER] uart3: Non-standard ns8250 class UART with FIFOs on puc0 uart3: [FILTER] vgapci0: VGA-compatible display port 0xe000-0xe0ff mem 0xf000-0xf7ff,0xf804-0xf804 at device 2.0 on pci224 uart4: 16550 or compatible iomem 0xff5e-0xff5e0007 irq 34 on acpi0 uart4: [FILTER] uart5: 16550 or compatible iomem 0xff5e2000-0xff5e2007 irq 35 on acpi0 uart5: [FILTER] uart5: debug port (9600,n,8,1) Timecounter ITC frequency 16 Hz quality 0 Timecounters tick every 1.000 msec IP Filter: v4.1.28 initialized. Default = block all, Logging = enabled usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 (xpt0:isp0:0:-1:-1): rescan already queued ugen0.1: NEC at usbus0 uhub0: NEC OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0 ugen1.1: NEC at usbus1 uhub1: NEC OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus1 ugen2.1: NEC at usbus2 uhub2: NEC EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus2 uhub1: 2 ports with 2
Re: panic ia64 r204293
On Thu, Feb 25, 2010 at 2:14 PM, Anton Shterenlikht me...@bristol.ac.uk wrote: I'm upgrading from 8.0-stable to 9.0-current. Got this panic. Any advice? Do you have options SMP in your custom kernel? Try to boot with GENERIC kernel. many thanks anton ## Loading.: FreeBSD Starting: FreeBSD Consoles: EFI console FreeBSD/ia64 EFI boot, Revision 2.1 (me...@mech-as28.men.bris.ac.uk, Thu Feb 25 10:06:10 GMT 2010) Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0xa5209d+0x1c6933 syms=[0x8+0x80400+0x8+0x751a2] \ Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... Entering /boot/kernel/kernel at 0xe4078000... GDB: debug ports: uart GDB: current port: uart KDB: debugger backends: ddb gdb KDB: current backend: ddb Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #0 r204293: Thu Feb 25 12:38:11 GMT 2010 me...@mech-as28.men.bris.ac.uk:/usr/obj/usr/src/sys/ZEEV ia64 WARNING: WITNESS option enabled, expect reduced performance. CPU: Madison II (1600 Mhz Itanium 2) Origin = GenuineIntel Revision = 2 Features = 0x1LB real memory = 12849717248 (12254 MB) avail memory = 12585984000 (12002 MB) FPSWA Revision = 0x10012, Entry = 0xe040ffcc4050 ACPI Warning: 32/64X length mismatch in Gpe0Block: 32/16 (20100121/tbfadt-625) ACPI Warning: 32/64X length mismatch in Gpe1Block: 32/16 (20100121/tbfadt-625) acpi0: HP on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 32-bit timer at 3.579545MHz iomem 0xff5c1004-0xff5c1007 on acpi0 cpu0: ACPI CPU on acpi0 acpi_tz0: Thermal Zone on acpi0 pcib0: ACPI Host-PCI bridge on acpi0 pci0: ACPI PCI bus on pcib0 ohci0: NEC uPD 9210 USB controller mem 0x80002000-0x80002fff irq 16 at device 1.0 on pci0 ohci0: [ITHREAD] usbus0: NEC uPD 9210 USB controller on ohci0 ohci1: NEC uPD 9210 USB controller mem 0x80001000-0x80001fff irq 17 at device 1.1 on pci0 ohci1: [ITHREAD] usbus1: NEC uPD 9210 USB controller on ohci1 ehci0: NEC uPD 720100 USB 2.0 controller mem 0x8000-0x80ff irq 18 at device 1.2 on pci0 ehci0: [ITHREAD] usbus2: EHCI version 0.95 usbus2: NEC uPD 720100 USB 2.0 controller on ehci0 pci0: mass storage, ATA at device 2.0 (no driver attached) pcib1: ACPI Host-PCI bridge on acpi0 pci32: ACPI PCI bus on pcib1 mpt0: LSILogic 1030 Ultra4 Adapter port 0x2100-0x21ff mem 0x903a-0x903b,0x9038-0x9039 irq 27 at device 1.0 on pci32 mpt0: [ITHREAD] mpt0: MPI Version=1.2.12.0 mpt1: LSILogic 1030 Ultra4 Adapter port 0x2000-0x20ff mem 0x9036-0x9037,0x9034-0x9035 irq 28 at device 1.1 on pci32 mpt1: [ITHREAD] mpt1: MPI Version=1.2.12.0 em0: Intel(R) PRO/1000 Network Connection 6.9.25 port 0x2240-0x227f mem 0x9032-0x9033,0x9028-0x902f irq 29 at device 2.0 on pci32 em0: [FILTER] em0: Ethernet address: 00:13:21:5b:05:1c em1: Intel(R) PRO/1000 Network Connection 6.9.25 port 0x2200-0x223f mem 0x9030-0x9031 irq 30 at device 2.1 on pci32 em1: [FILTER] em1: Ethernet address: 00:13:21:5b:05:1d pcib2: ACPI Host-PCI bridge on acpi0 pci64: ACPI PCI bus on pcib2 pcib3: ACPI Host-PCI bridge on acpi0 pci96: ACPI PCI bus on pcib3 pcib4: ACPI Host-PCI bridge on acpi0 pci128: ACPI PCI bus on pcib4 pcib5: ACPI Host-PCI bridge on acpi0 pci192: ACPI PCI bus on pcib5 isp0: Qlogic ISP 2422 PCI FC-AL Adapter port 0xc000-0xc0ff mem 0xe004-0xe0040fff irq 71 at device 1.0 on pci192 isp0: [ITHREAD] pcib6: ACPI Host-PCI bridge on acpi0 pci224: ACPI PCI bus on pcib6 uart0: 16550 or compatible mem 0xf8051000-0xf805100f irq 82 at device 1.0 on pci224 uart0: [FILTER] puc0: HP Diva Serial [GSP] uart1: Non-standard ns8250 class UART with FIFOs on puc0 uart1: [FILTER] uart1: console (9600,n,8,1) uart2: Non-standard ns8250 class UART with FIFOs on puc0 uart2: [FILTER] uart3: Non-standard ns8250 class UART with FIFOs on puc0 uart3: [FILTER] vgapci0: VGA-compatible display port 0xe000-0xe0ff mem 0xf000-0xf7ff,0xf804-0xf804 at device 2.0 on pci224 uart4: 16550 or compatible iomem 0xff5e-0xff5e0007 irq 34 on acpi0 uart4: [FILTER] uart5: 16550 or compatible iomem 0xff5e2000-0xff5e2007 irq 35 on acpi0 uart5: [FILTER] uart5: debug port (9600,n,8,1) Timecounter ITC frequency 16 Hz quality 0 Timecounters tick every 1.000 msec IP Filter: v4.1.28 initialized. Default = block all, Logging = enabled usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 (xpt0:isp0:0:-1:-1): rescan already queued ugen0.1: NEC at usbus0 uhub0: NEC OHCI root
Re: openldap client GSSAPI authentication segfaults in fbsd8stable i386
To sum things up.
By fixing my /etc/hosts to read as it should (this needs some work too,
the behavior with the 'wrong' /etc/hosts is unexpected), ldapwhoami
works fine IF (AND ONLY IF) someone kinits to a user principal;
otherwise it segfaults. My default binding method is GSSAPI, hence the
segfault. If I use simple bind (ldapwhoami -W -D 'blabla') it works
fine. If I LD_PRELOAD the hacked library lala.so, which is created
like this:
lala.c:
int gss_release_buffer(void *a, void *b) {
return 0;
}
# gcc -c -fPIC -shared lala.c -o lala.so
and if I haven't obtained any kerberos tickets, then
# ldapwhoami
SASL/GSSAPI authentication started
Segmentation fault: 11 (core dumped)
once I ldpreload the above fake-library, then:
# LD_PRELOAD=./lala.so ldapwhoami
SASL/GSSAPI authentication started
ldap_sasl_interactive_bind_s: Local error (-2)
additional info: SASL(-1): generic failure: GSSAPI Error:
Miscellaneous failure (see text) (unknown mech-code 2 for mech unknown)
which is what is expected.
This, maybe implies that something is freed by gss_release_buffer that
normally shouldn't.
amd64 won't hang in the same test (so no need to ld_preload anything),
but shares the same problem with i386 when /etc/hosts is not as expected
(to recreate the /etc/hosts problem, place in your /etc/hosts file two
fqdns for the ldap server's IP, but write the ldap server's fqdn second
in turn).
Thank you all and have a nice evening.
--
George Mamalakis
IT Officer
Electrical and Computer Engineer (Aristotle Un. of Thessaloniki),
MSc (Imperial College of London)
Department of Electrical and Computer Engineering
Faculty of Engineering
Aristotle University of Thessaloniki
phone number : +30 (2310) 994379
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: panic ia64 r204293
forwarding to the list just for record. -- Gianni -- Forwarded message -- From: Anton Shterenlikht me...@bristol.ac.uk Date: Thu, Feb 25, 2010 at 3:14 PM Subject: Re: (no subject) To: Marc Lörner loer...@gmx.de Cc: giovanni.tremate...@gmail.com, freebsd-i...@freebsd.org, mar...@freebsd.org On Thu, Feb 25, 2010 at 03:02:41PM +0100, Marc Lörner wrote: On Thu, Feb 25, 2010 at 2:14 PM, Anton Shterenlikht me...@bristol.ac.uk wrote: I'm upgrading from 8.0-stable to 9.0-current. Got this panic. Any advice? Do you have options SMP in your custom kernel? Try to boot with GENERIC kernel. I think this is no problem because SMP is already turned on in GENERIC kernel. yes, my fault, I copied the kernel config file from my other UP box. All is well now. many thanks for your help anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: panic ia64 r204293
On Thu, 25 Feb 2010, Giovanni Trematerra wrote: Try to boot with GENERIC kernel. I think this is no problem because SMP is already turned on in GENERIC kernel. yes, my fault, I copied the kernel config file from my other UP box. All is well now. In fact, my fault. I had a bug in three assertions in the recent netisr.c revision to add a monitoring sysctl, which essentially triggered only on UP. I committed a fix to that a bit earlier today. Please let me know if it recurs after the fix (r204303). Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: time doesn't work?
2010/2/17 Pyun YongHyeon pyu...@gmail.com: On Wed, Feb 17, 2010 at 01:12:53PM -0800, Xin LI wrote: Hi, On Sun, Feb 14, 2010 at 10:20 AM, Gavin Atkinson gavinfreebsd@ury.york.ac.uk wrote: /mnt: write failed, filesystem is full gzip: write: No space left on device gzip: output file: randomfile.gz wrong size (1673592832 != -1), deleting gzip: leaving original randomfile 0.000u 85.063s 1:25.10 99.9% ??0+0k 12440+12839io 7pf+0w Does reverting r202387, 202441 and 202534 make any difference? Yes, reverting these revisions makes everything back to normal (including top -P). I'm not sure this is also related with breakage of systat -vmstat 1 on amd64 CURRENT. systat(1) shows The alternate system clock has died! Reverting to ``pigs'' display. message and does not work as expected. When I run systat(1) on sparc64 CURRENT it worked as expected so I vaguely guess it's related with attilio's change.(CCed) [CC'ing also others that may got this issue] Can you please upgrade to the newest CURRENT, try the attached patch and report if system choiches the right timer alone: http://www.freebsd.org/~attilio/Sandvine/STABLE_8/statclock_aliasing/statclock-fixup.diff with 'alone', I mean that you might strip from config all the helping tips (machdep.lapic_allclocks). Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Seeing the dreaded ZFS: i/o error - all block copies unavailable on 9.0-CURRENT
On Wednesday 24 February 2010 10:12:25 pm Chris wrote: So it sounds like somehow my system is trying to use the old boot2 method when I don't hit F12. I'm guessing the difference is due to how the hard drive is getting presented to the boot loader by the BIOS. How can I get rid of the legacy boot system and use only the ZFS bootloader? Does F12 enable PXE booting or some such? I can't really tell from your e- mails exactly what the difference in the two cases are. The BIOS doesn't really tell the boot code much of anything. It just loads the first sector of the disk into RAM at 0x7c00, puts the BIOS drive number (typically 0x80) into the %dl register, and starts executing the code it just loaded. Unless hitting F12 is somehow booting from a different physical drive (and thus either loading different boot code or passing a different value of %dl to another copy of the same boot code), it shouldn't make any difference. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ATA_CAM-ed mvsata(4) on OpenRD-client
Hi mav.
On Fri, 19 Feb 2010 22:36:12 +0200
Alexander Motin m...@freebsd.org wrote:
xpt_sim_opened() at 0xc0904048 = xpt_sim_opened+0x218
scp=0xc0904048 rlv=0xc0905940 (0xc0905940 = xpt_register_async+0xd0)
rsp=0xc0d62d8c rfp=0xc0d62e34
xpt_register_async() at 0xc0905880 = xpt_register_async+0x10
scp=0xc0905880 rlv=0xc090d484 (0xc090d484 = ata_get_xport+0x2198)
rsp=0xc0d62e38 rfp=0xc0d62e44
r10=0x r9=0x
r8=0x005fffcc r7=0xc35593c0 r6=0xc0b62170 r5=0xc0be74d0
r4=0x001c
Even more unexpected. I've searched all sources for xpt_sim_opened()
call and found only one place - in atapi-cam.c, which shouldn't be used
in your case. You are using different sources, or there is a garbage in
stack?
I tried to printf-debug, so I got what's happen.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- -
module_register_init: MOD_LOAD(elf32) called in
module_register_init: MOD_LOAD(elf32 on elf kernel/elf kernel) called out
module_register_init: MOD_LOAD(shell) called in
module_register_init: MOD_LOAD(shell on elf kernel/elf kernel) called out
module_register_init: MOD_LOAD(if_lo) called in
module_register_init: MOD_LOAD(if_lo on elf kernel/elf kernel) called out
lo0: bpf attached
[DEBUG] xpt_config called #4501@/usr/src/sys/cam/cam_xpt.c
[DEBUG] xpt_config #4532@/usr/src/sys/cam/cam_xpt.c
[DEBUG] xpt_config #4538@/usr/src/sys/cam/cam_xpt.c
[DEBUG] periphdriver_init(1), init = 1 #132@/usr/src/sys/cam/cam_periph.c
[DEBUG] periphdriver_init:, i = 0, driver_name = ada
[DEBUG] periphdriver_init:, i = 1, driver_name = probe
[DEBUG] periphdriver_init:, i = 2, driver_name = pmp
spin lock 0xc3789100 () held by 0xc3632348 (tid 0) too long
panic: spin lock held too long
KDB: enter: panic
[ thread pid 0 tid 10 ]
Stopped at 0xc09dede0 = kdb_enter+0x48:ldrbr15, [r15, r15, ror
r15]!
db show lock 0xc3789100
class: spin mutex
name:
flags: {SPIN, RECURSE}
state: {OWNED}
owner: 0xc3632348 (tid 0, pid 0, )
recursed: -251133952
db bt
Tracing pid 0 tid 10 td 0xc0be6ab0
kdb_enter() at 0xc09deda8 = kdb_enter+0x10
scp=0xc09deda8 rlv=0xc09b572c (0xc09b572c = panic+0xcc)
rsp=0xc0d6ec10 rfp=0xc0d6ec24
r4=0x0100
panic() at 0xc09b5674 = panic+0x14
scp=0xc09b5674 rlv=0xc09a99fc (0xc09a99fc = _thread_lock_flags+0x170)
rsp=0xc0d6ec38 rfp=0xc0d6ec80
_thread_lock_flags() at 0xc09a989c = _thread_lock_flags+0x10
scp=0xc09a989c rlv=0xc09ec7c0 (0xc09ec7c0 = turnstile_claim+0x16c)
rsp=0xc0d6ec84 rfp=0xc0d6eca0
r10=0xc0bf244c r9=0x
r8=0xc3562000 r7=0x0044 r6=0xc3562000 r5=0xc3789100
r4=0xc0b68548
turnstile_claim() at 0xc09ec768 = turnstile_claim+0x114
scp=0xc09ec768 rlv=0xc09ecad8 (0xc09ecad8 = turnstile_wait+0x23c)
rsp=0xc0d6eca4 rfp=0xc0d6eccc
r7=0xc0be6ab0 r6=0xc3789100
r5=0xc0b68548 r4=0x
turnstile_wait() at 0xc09ec8ac = turnstile_wait+0x10
scp=0xc09ec8ac rlv=0xc09a9568 (0xc09a9568 = _mtx_lock_sleep+0x11c)
rsp=0xc0d6ecd0 rfp=0xc0d6ed00
r10=0xc0b4aa58 r9=0x
r8=0x r7=0x r6=0xc0be6ab0 r5=0xc3562000
r4=0xc35fe974
_mtx_lock_sleep() at 0xc09a945c = _mtx_lock_sleep+0x10
scp=0xc09a945c rlv=0xc09a9650 (0xc09a9650 = _mtx_lock_flags+0x88)
rsp=0xc0d6ed04 rfp=0xc0d6ed2c
r10=0xc0d6ed60 r9=0xc0903a68
r8=0x r7=0x07c7 r6=0xc0b4aa58 r5=0x
r4=0xc35fe974
_mtx_lock_flags() at 0xc09a95d8 = _mtx_lock_flags+0x10
scp=0xc09a95d8 rlv=0xc0903e98 (0xc0903e98 = xpt_unlock_buses+0x148)
rsp=0xc0d6ed30 rfp=0xc0d6ed58
r8=0xc0be33fc r7=0xc090e838
r6=0xc370 r5=0xc0b4aa58 r4=0xc3788b80
xpt_unlock_buses() at 0xc0903e28 = xpt_unlock_buses+0xd8
scp=0xc0903e28 rlv=0xc0903f54 (0xc0903f54 = xpt_unlock_buses+0x204)
rsp=0xc0d6ed5c rfp=0xc0d6ed78
r10=0xc0be3410 r9=0xc0b4aa58
r8=0x r7=0xc090e838 r6=0x0080 r5=0x
r4=0x0001
xpt_unlock_buses() at 0xc0903f34 = xpt_unlock_buses+0x1e4
scp=0xc0903f34 rlv=0xc0905d5c (0xc0905d5c = xpt_register_async+0xd0)
rsp=0xc0d6ed7c rfp=0xc0d6ee24
xpt_register_async() at 0xc0905c9c = xpt_register_async+0x10
scp=0xc0905c9c rlv=0xc090e818 (0xc090e818 = ata_get_xport+0x2d54)
rsp=0xc0d6ee28 rfp=0xc0d6ee34
r10=0x r9=0x
r8=0x005fffcc r7=0xc3584460 r6=0xc0b4aa58 r5=0x0002
r4=0x0008
ata_get_xport() at 0xc090e808 = ata_get_xport+0x2d44
scp=0xc090e808 rlv=0xc09008a4 (0xc09008a4 = periphdriver_init+0x9c)
rsp=0xc0d6ee38 rfp=0xc0d6ee50
periphdriver_init() at 0xc0900818 = periphdriver_init+0x10
scp=0xc0900818 rlv=0xc0904620 (0xc0904620 = xpt_alloc_ccb+0xbc)
rsp=0xc0d6ee54 rfp=0xc0d6ee74
r5=0xc0b4ab9c r4=0x
xpt_alloc_ccb() at 0xc09045a0 = xpt_alloc_ccb+0x3c
scp=0xc09045a0 rlv=0xc09d4e84 (0xc09d4e84 = vaccess_acl_posix1e+0x628)
rsp=0xc0d6ee78
Re: time doesn't work?
2010/2/25 Pyun YongHyeon pyu...@gmail.com: On Thu, Feb 25, 2010 at 04:48:28PM +0100, Attilio Rao wrote: 2010/2/17 Pyun YongHyeon pyu...@gmail.com: On Wed, Feb 17, 2010 at 01:12:53PM -0800, Xin LI wrote: Hi, On Sun, Feb 14, 2010 at 10:20 AM, Gavin Atkinson gavinfreebsd@ury.york.ac.uk wrote: /mnt: write failed, filesystem is full gzip: write: No space left on device gzip: output file: randomfile.gz wrong size (1673592832 != -1), deleting gzip: leaving original randomfile 0.000u 85.063s 1:25.10 99.9% ??0+0k 12440+12839io 7pf+0w Does reverting r202387, 202441 and 202534 make any difference? Yes, reverting these revisions makes everything back to normal (including top -P). I'm not sure this is also related with breakage of systat -vmstat 1 on amd64 CURRENT. systat(1) shows The alternate system clock has died! ??Reverting to ``pigs'' display. message and does not work as expected. When I run systat(1) on sparc64 CURRENT it worked as expected so I vaguely guess it's related with attilio's change.(CCed) [CC'ing also others that may got this issue] Can you please upgrade to the newest CURRENT, try the attached patch and report if system choiches the right timer alone: http://www.freebsd.org/~attilio/Sandvine/STABLE_8/statclock_aliasing/statclock-fixup.diff with 'alone', I mean that you might strip from config all the helping tips (machdep.lapic_allclocks). With the patch above, systat(1) seems to work as expected. One thing I see is dmesg output is RTC BIOS diagnostic error 11memory_size I'm not sure whether I had this message in previous kernel. It is likely you had after the incriminating revision but not because the previous patch broke it, just because the previous patch does enable atrtc (while the old kernel didn't do this). Attilio -- Peace can only be achieved by understanding - A. Einstein ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: time doesn't work?
On Thu, Feb 25, 2010 at 04:48:28PM +0100, Attilio Rao wrote: 2010/2/17 Pyun YongHyeon pyu...@gmail.com: On Wed, Feb 17, 2010 at 01:12:53PM -0800, Xin LI wrote: Hi, On Sun, Feb 14, 2010 at 10:20 AM, Gavin Atkinson gavinfreebsd@ury.york.ac.uk wrote: /mnt: write failed, filesystem is full gzip: write: No space left on device gzip: output file: randomfile.gz wrong size (1673592832 != -1), deleting gzip: leaving original randomfile 0.000u 85.063s 1:25.10 99.9% ??0+0k 12440+12839io 7pf+0w Does reverting r202387, 202441 and 202534 make any difference? Yes, reverting these revisions makes everything back to normal (including top -P). I'm not sure this is also related with breakage of systat -vmstat 1 on amd64 CURRENT. systat(1) shows The alternate system clock has died! ??Reverting to ``pigs'' display. message and does not work as expected. When I run systat(1) on sparc64 CURRENT it worked as expected so I vaguely guess it's related with attilio's change.(CCed) [CC'ing also others that may got this issue] Can you please upgrade to the newest CURRENT, try the attached patch and report if system choiches the right timer alone: http://www.freebsd.org/~attilio/Sandvine/STABLE_8/statclock_aliasing/statclock-fixup.diff with 'alone', I mean that you might strip from config all the helping tips (machdep.lapic_allclocks). With the patch above, systat(1) seems to work as expected. One thing I see is dmesg output is RTC BIOS diagnostic error 11memory_size I'm not sure whether I had this message in previous kernel. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Seeing the dreaded ZFS: i/o error - all block copies unavailable on 9.0-CURRENT
on 25/02/2010 19:58 Chris said the following: On Thu, Feb 25, 2010 at 8:06 AM, John Baldwin j...@freebsd.org wrote: On Wednesday 24 February 2010 10:12:25 pm Chris wrote: So it sounds like somehow my system is trying to use the old boot2 method when I don't hit F12. I'm guessing the difference is due to how the hard drive is getting presented to the boot loader by the BIOS. How can I get rid of the legacy boot system and use only the ZFS bootloader? Does F12 enable PXE booting or some such? The only options I have when I press F12 are to either boot from my hard drive or to boot from my optical drive. Is there any way to more verbosely see what is happening at the bootloader level? I guess that F12 that you describe is handled by BIOS. Do you have other HDDs in this system? What is your default boot order (configured in BIOS)? -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ATA CDROM no more detected with ATA_CAM under VMWare WS
Claude Buisson wrote: Updating a -CURRENT system from Jan 10 to Feb 21, under VMWare WS 5.5.9, the virtual ATA CDROM is no more detected. This is with an ATA_CAM kernel. The CDROM is detected with a non ATA_CAM kernel. ata1: reset tp1 mask=01 ostat0=50 ostat1=ff ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0x1 (aprobe0:ata1:0:0:0): SIGNATURE: eb14 (aprobe0:ata1:0:0:0): Spinning up device (aprobe0:ata1:0:0:0): ATA status error (aprobe0:ata1:0:0:0): SETFEATURES SPIN-UP. ACB: ef 07 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:0:0): CAM status: ATA Status Error (aprobe0:ata1:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (aprobe0:ata1:0:0:0): RES: 51 04 00 00 00 00 00 00 00 00 00 (aprobe0:ata1:0:0:0): Retrying command Seems device reports Response Incomplete bit set in IDENTIFY PACKET DEVICE command result, which makes CAM try to power it up. Could you comment ATA_RESP_INCOMPLETE check in ata_xpt.c and show me result of `camcontrol identify cd0 -v` output after it? -- Alexander Motin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: time doesn't work?
On Thu, Feb 25, 2010 at 08:39:01PM +0100, Attilio Rao wrote: 2010/2/25 Pyun YongHyeon pyu...@gmail.com: On Thu, Feb 25, 2010 at 04:48:28PM +0100, Attilio Rao wrote: 2010/2/17 Pyun YongHyeon pyu...@gmail.com: On Wed, Feb 17, 2010 at 01:12:53PM -0800, Xin LI wrote: Hi, On Sun, Feb 14, 2010 at 10:20 AM, Gavin Atkinson gavinfreebsd@ury.york.ac.uk wrote: /mnt: write failed, filesystem is full gzip: write: No space left on device gzip: output file: randomfile.gz wrong size (1673592832 != -1), deleting gzip: leaving original randomfile 0.000u 85.063s 1:25.10 99.9% ??0+0k 12440+12839io 7pf+0w Does reverting r202387, 202441 and 202534 make any difference? Yes, reverting these revisions makes everything back to normal (including top -P). I'm not sure this is also related with breakage of systat -vmstat 1 on amd64 CURRENT. systat(1) shows The alternate system clock has died! ??Reverting to ``pigs'' display. message and does not work as expected. When I run systat(1) on sparc64 CURRENT it worked as expected so I vaguely guess it's related with attilio's change.(CCed) [CC'ing also others that may got this issue] Can you please upgrade to the newest CURRENT, try the attached patch and report if system choiches the right timer alone: http://www.freebsd.org/~attilio/Sandvine/STABLE_8/statclock_aliasing/statclock-fixup.diff with 'alone', I mean that you might strip from config all the helping tips (machdep.lapic_allclocks). With the patch above, systat(1) seems to work as expected. One thing I see is dmesg output is RTC BIOS diagnostic error 11memory_size I'm not sure whether I had this message in previous kernel. It is likely you had after the incriminating revision but not because the previous patch broke it, just because the previous patch does enable atrtc (while the old kernel didn't do this). Thank you for clarifying this. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Seeing the dreaded ZFS: i/o error - all block copies unavailable on 9.0-CURRENT
On Thursday 25 February 2010 12:58:13 pm Chris wrote: On Thu, Feb 25, 2010 at 8:06 AM, John Baldwin j...@freebsd.org wrote: On Wednesday 24 February 2010 10:12:25 pm Chris wrote: So it sounds like somehow my system is trying to use the old boot2 method when I don't hit F12. I'm guessing the difference is due to how the hard drive is getting presented to the boot loader by the BIOS. How can I get rid of the legacy boot system and use only the ZFS bootloader? Does F12 enable PXE booting or some such? The only options I have when I press F12 are to either boot from my hard drive or to boot from my optical drive. Is there any way to more verbosely see what is happening at the bootloader level? No. So it sounds like F12 pops up some sort of boot menu, and that in the broken case you just let the machine boot off of the disk normally? I can't really tell from your e-mails exactly what the difference in the two cases are. The BIOS doesn't really tell the boot code much of anything. It just loads the first sector of the disk into RAM at 0x7c00, puts the BIOS drive number (typically 0x80) into the %dl register, and starts executing the code it just loaded. Unless hitting F12 is somehow booting from a different physical drive (and thus either loading different boot code or passing a different value of %dl to another copy of the same boot code), it shouldn't make any difference. -- John Baldwin -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ATA CDROM no more detected with ATA_CAM under VMWare WS
Alexander Motin wrote: Claude Buisson wrote: Updating a -CURRENT system from Jan 10 to Feb 21, under VMWare WS 5.5.9, the virtual ATA CDROM is no more detected. This is with an ATA_CAM kernel. The CDROM is detected with a non ATA_CAM kernel. ata1: reset tp1 mask=01 ostat0=50 ostat1=ff ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: reset tp2 stat0=00 stat1=00 devices=0x1 (aprobe0:ata1:0:0:0): SIGNATURE: eb14 (aprobe0:ata1:0:0:0): Spinning up device (aprobe0:ata1:0:0:0): ATA status error (aprobe0:ata1:0:0:0): SETFEATURES SPIN-UP. ACB: ef 07 00 00 00 40 00 00 00 00 00 00 (aprobe0:ata1:0:0:0): CAM status: ATA Status Error (aprobe0:ata1:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (aprobe0:ata1:0:0:0): RES: 51 04 00 00 00 00 00 00 00 00 00 (aprobe0:ata1:0:0:0): Retrying command Seems device reports Response Incomplete bit set in IDENTIFY PACKET DEVICE command result, which makes CAM try to power it up. Could you comment ATA_RESP_INCOMPLETE check in ata_xpt.c and show me result of `camcontrol identify cd0 -v` output after it? Here it is: r...@zaza# camcontrol identify cd0 -v pass1: Raw identify data: 0: 85c4 8: 3130 3030 3030 3030 3030 3030 16: 3030 3030 3030 3031 0040 3030 24: 3030 3030 3031 564d 7761 7265 2056 6972 32: 7475 616c 2049 4445 2043 4452 4f4d 2044 40: 7269 7665 2020 2020 2020 2020 2020 48: 0f00 0200 0200 0006 56: 0007 0007 64: 0003 0078 0078 0078 0078 72: 0004 0009 80: 001e 0017 4218 4000 4000 4218 4000 4000 88: 0407 96: 104: 112: 120: 128: 136: 144: 152: 160: 168: 176: 184: 192: 200: 208: 216: 224: 232: 240: 248: pass1: VMware Virtual IDE CDROM Drive 0001 ATAPI-4 device pass1: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) protocol ATA/ATAPI-4 device model VMware Virtual IDE CDROM Drive firmware revision 0001 serial number 1001 cylinders 0 heads 0 sectors/track 0 sector size logical 512, physical 512, offset 0 LBA supported LBA48 not supported PIO supported PIO4 DMA supported WDMA2 UDMA2 Feature Support EnableValue Vendor read ahead no no write cacheno no flush cacheno no overlapno Tagged Command Queuing (TCQ) no no SMART no no microcode download no no security no no power management yes yes advanced power management no no 0/0x00 automatic acoustic management no no 0/0x00 0/0x00 media status notification no no power-up in Standbyno no write-read-verify no no 0/0x0 unload no no free-fall no no data set management (TRIM) no dmesg say: cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: SONY DVD+-RW DW-D56A PDS7 Removable CD-ROM SCSI-0 device cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present The VMWare virtual device being connected at boot the the physical device Hope this help, Claude Buisson ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Wed, Dec 23, 2009 at 08:18:48AM +, Aditya Sarawgi wrote: On Tue, Dec 22, 2009 at 07:53:31PM -0800, Weongyo Jeong wrote: Hello, Now bwn(4) is available at the public and waiting test and review. The status of this driver is *alpha* so could make panics, warnings and errors. Please let me know if you encounter problems. The following NICs all I have are only tested on the little endian 64bit machine and big endian 32bit machine. - Broadcom BCM4306 802.11b/g Wireless - Broadcom BCM4318 802.11b/g Wireless I tested basic RX, TX and WPA association as STA mode and checked it worked. As you might know there are still a lot of TODO in the driver so you could see some verbose messages during testing so please ignore or let me know it makes problems. == How to build and load == # cd /usr/src/sys # fetch http://people.freebsd.org/~weongyo/bwn_20091222.tar.gz # tar xzf bwn_20091222.tar.gz # cd modules/ssb # make make install # cd ../.. # cd modules/bwn # make make install # cd somewhere # fetch http://people.freebsd.org/~weongyo/bwn_ports_20091222.tar.gz # tar xzf bwn_ports_20091222.tar.gz # cd sysutils/b43-fwcutter # make install clean # cd ../.. # cd net/bwn-firmware-kmod # make install clean # # kldload ssb # kldload bwn_v4_ucode # kldload if_bwn regards, Weongyo Jeong Hi, The driver doesn't work with BCM4315, here's what dmesg shows ssb0: Broadcom BCM4315 802.11b/g Wireless mem 0xf400-0xf4003fff irq 19 at device 0.0 on pci6 bwn0 on ssb0 bwn0: unsupported PHY type (5) device_attach: bwn0 attach returned 6 FYI bwn(4) driver is committed into FreeBSD tree. I think the driver supports your LP PHY device. After cvsup please try to rebuild siba_bwn and bwn modules. Could you please test with it? Please let me know and send me your full dmesg when you encounters the following problems: - if the driver doesn't work or is unstable. - if it prints debugging or verbose messages. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on ia64/ia64
TB --- 2010-02-26 00:10:10 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-02-26 00:10:10 - starting HEAD tinderbox run for ia64/ia64 TB --- 2010-02-26 00:10:10 - cleaning the object tree TB --- 2010-02-26 00:10:26 - cvsupping the source tree TB --- 2010-02-26 00:10:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2010-02-26 00:10:56 - building world TB --- 2010-02-26 00:10:56 - MAKEOBJDIRPREFIX=/obj TB --- 2010-02-26 00:10:56 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-02-26 00:10:56 - TARGET=ia64 TB --- 2010-02-26 00:10:56 - TARGET_ARCH=ia64 TB --- 2010-02-26 00:10:56 - TZ=UTC TB --- 2010-02-26 00:10:56 - __MAKE_CONF=/dev/null TB --- 2010-02-26 00:10:56 - cd /src TB --- 2010-02-26 00:10:56 - /usr/bin/make -B buildworld World build started on Fri Feb 26 00:10:56 UTC 2010 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Fri Feb 26 01:45:13 UTC 2010 TB --- 2010-02-26 01:45:13 - generating LINT kernel config TB --- 2010-02-26 01:45:13 - cd /src/sys/ia64/conf TB --- 2010-02-26 01:45:13 - /usr/bin/make -B LINT TB --- 2010-02-26 01:45:13 - building LINT kernel TB --- 2010-02-26 01:45:13 - MAKEOBJDIRPREFIX=/obj TB --- 2010-02-26 01:45:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-02-26 01:45:13 - TARGET=ia64 TB --- 2010-02-26 01:45:13 - TARGET_ARCH=ia64 TB --- 2010-02-26 01:45:13 - TZ=UTC TB --- 2010-02-26 01:45:13 - __MAKE_CONF=/dev/null TB --- 2010-02-26 01:45:13 - cd /src TB --- 2010-02-26 01:45:13 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Fri Feb 26 01:45:14 UTC 2010 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] awk -f /src/sys/conf/kmod_syms.awk rt2561fw.kld export_syms | xargs -J% objcopy % rt2561fw.kld ld -Bshareable -d -warn-common -o rt2561fw.ko rt2561fw.kld objcopy --strip-debug rt2561fw.ko === ralfw/rt2561s (all) uudecode -p /src/sys/modules/ralfw/rt2561s/../../../contrib/dev/ral/rt2561s.fw.uu rt2561s.fw rt2561s.fw rt2561s.fw cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/ia64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/ia64/src/sys/LINT -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -std=iso9899:1999 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c rt2561sfw.c /libexec/ld-elf.so.1: Cannot open /lib/libncurses.so.8 *** Error code 1 Stop in /src/sys/modules/ralfw/rt2561s. *** Error code 1 Stop in /src/sys/modules/ralfw. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-02-26 02:11:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-02-26 02:11:26 - ERROR: failed to build lint kernel TB --- 2010-02-26 02:11:26 - 4947.09 user 718.20 system 7276.20 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on sparc64/sparc64
TB --- 2010-02-26 01:49:28 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-02-26 01:49:28 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2010-02-26 01:49:28 - cleaning the object tree TB --- 2010-02-26 01:50:20 - cvsupping the source tree TB --- 2010-02-26 01:50:20 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2010-02-26 01:50:46 - building world TB --- 2010-02-26 01:50:46 - MAKEOBJDIRPREFIX=/obj TB --- 2010-02-26 01:50:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-02-26 01:50:46 - TARGET=sparc64 TB --- 2010-02-26 01:50:46 - TARGET_ARCH=sparc64 TB --- 2010-02-26 01:50:46 - TZ=UTC TB --- 2010-02-26 01:50:46 - __MAKE_CONF=/dev/null TB --- 2010-02-26 01:50:46 - cd /src TB --- 2010-02-26 01:50:46 - /usr/bin/make -B buildworld World build started on Fri Feb 26 01:50:46 UTC 2010 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries [...] cc -fPIC -DPIC -O2 -pipe -I/src/gnu/lib/libreadline/readline/.. -I/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline -DHAVE_CONFIG_H -DRL_LIBRARY_VERSION='5.2' -std=gnu99 -fstack-protector -c /src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/signals.c -o signals.So cc -fPIC -DPIC -O2 -pipe -I/src/gnu/lib/libreadline/readline/.. -I/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline -DHAVE_CONFIG_H -DRL_LIBRARY_VERSION='5.2' -std=gnu99 -fstack-protector -c /src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/util.c -o util.So cc -fPIC -DPIC -O2 -pipe -I/src/gnu/lib/libreadline/readline/.. -I/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline -DHAVE_CONFIG_H -DRL_LIBRARY_VERSION='5.2' -std=gnu99 -fstack-protector -c /src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/kill.c -o kill.So cc -fPIC -DPIC -O2 -pipe -I/src/gnu/lib/libreadline/readline/.. -I/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline -DHAVE_CONFIG_H -DRL_LIBRARY_VERSION='5.2' -std=gnu99 -fstack-protector -c /src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/undo.c -o undo.So cc -fPIC -DPIC -O2 -pipe -I/src/gnu/lib/libreadline/readline/.. -I/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline -DHAVE_CONFIG_H -DRL_LIBRARY_VERSION='5.2' -std=gnu99 -fstack-protector -c /src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/macro.c -o macro.So cc -fPIC -DPIC -O2 -pipe -I/src/gnu/lib/libreadline/readline/.. -I/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline -DHAVE_CONFIG_H -DRL_LIBRARY_VERSION='5.2' -std=gnu99 -fstack-protector -c /src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/input.c -o input.So cc -fPIC -DPIC -O2 -pipe -I/src/gnu/lib/libreadline/readline/.. -I/src/gnu/lib/libreadline/readline/../../../../contrib/libreadline -DHAVE_CONFIG_H -DRL_LIBRARY_VERSION='5.2' -std=gnu99 -fstack-protector -c /src/gnu/lib/libreadline/readline/../../../../contrib/libreadline/callback.c -o callback.So /libexec/ld-elf.so.1: Cannot open /lib/libedit.so.7 *** Error code 1 Stop in /src/gnu/lib/libreadline/readline. *** Error code 1 Stop in /src/gnu/lib/libreadline. *** Error code 1 Stop in /src/gnu/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-02-26 02:11:33 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-02-26 02:11:33 - ERROR: failed to build world TB --- 2010-02-26 02:11:33 - 914.84 user 215.25 system 1325.48 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on sparc64/sun4v
TB --- 2010-02-26 02:08:02 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-02-26 02:08:02 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2010-02-26 02:08:02 - cleaning the object tree TB --- 2010-02-26 02:08:16 - cvsupping the source tree TB --- 2010-02-26 02:08:16 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2010-02-26 02:08:29 - building world TB --- 2010-02-26 02:08:29 - MAKEOBJDIRPREFIX=/obj TB --- 2010-02-26 02:08:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-02-26 02:08:29 - TARGET=sun4v TB --- 2010-02-26 02:08:29 - TARGET_ARCH=sparc64 TB --- 2010-02-26 02:08:29 - TZ=UTC TB --- 2010-02-26 02:08:29 - __MAKE_CONF=/dev/null TB --- 2010-02-26 02:08:29 - cd /src TB --- 2010-02-26 02:08:29 - /usr/bin/make -B buildworld World build started on Fri Feb 26 02:08:30 UTC 2010 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools [...] cc -c -I /src/gnu/usr.bin/cc/cc_tools/../libiberty -O2 -pipe -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/obj/sun4v/src/tmp/usr\ -DCROSS_COMPILE -I/obj/sun4v/src/tmp/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/include -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libcpp/include -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libdecnumber -g -DGENERATOR_FILE -DHAVE_CONFIG_H -std=gnu89 -I/obj/sun4v/src/tmp/legacy/usr/include -o lbasename.o /src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libiberty/lbasename.c cc -c -I /src/gnu/usr.bin/cc/cc_tools/../libiberty -O2 -pipe -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/obj/sun4v/src/tmp/usr\ -DCROSS_COMPILE -I/obj/sun4v/src/tmp/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/include -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libcpp/include -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libdecnumber -g -DGENERATOR_FILE -DHAVE_CONFIG_H -std=gnu89 -I/obj/sun4v/src/tmp/legacy/usr/include -o make-temp-file.o /src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libiberty/make-temp-file.c cc -c -I /src/gnu/usr.bin/cc/cc_tools/../libiberty -O2 -pipe -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/obj/sun4v/src/tmp/usr\ -DCROSS_COMPILE -I/obj/sun4v/src/tmp/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/include -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libcpp/include -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libdecnumber -g -DGENERATOR_FILE -DHAVE_CONFIG_H -std=gnu89 -I/obj/sun4v/src/tmp/legacy/usr/include -o md5.o /src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libiberty/md5.c cc -c -I /src/gnu/usr.bin/cc/cc_tools/../libiberty -O2 -pipe -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/obj/sun4v/src/tmp/usr\ -DCROSS_COMPILE -I/obj/sun4v/src/tmp/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/include -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libcpp/include -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libdecnumber -g -DGENERATOR_FILE -DHAVE_CONFIG_H -std=gnu89 -I/obj/sun4v/src/tmp/legacy/usr/include -o obstack.o /src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libiberty/obstack.c cc -c -I /src/gnu/usr.bin/cc/cc_tools/../libiberty -O2 -pipe -I. -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\/obj/sun4v/src/tmp/usr\ -DCROSS_COMPILE -I/obj/sun4v/src/tmp/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/src/gnu/usr.bin/cc/cc_tools/../cc_tools -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/config -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/include -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libcpp/include -I/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libdecnumber -g -DGENERATOR_FILE -DHAVE_CONFIG_H -std=gnu89 -I/obj/sun4v/src/tmp/legacy/usr/include -o partition.o /src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcclibs/libiberty/partition.c cc -c -I /src/gnu/usr.bin/cc/cc_tools/../libiberty -O2
Re: Plans for BIND and DNSSEC readiness
On Mon, 22 Feb 2010 00:12, dougb@ wrote: PGP Command Output gpg: Signature made Mon Feb 22 00:12:14 2010 EST using DSA key ID D5B2F0FB gpg: Good signature from Doug Barton do...@dougbarton.us gpg: aka Doug Barton do...@freebsd.org gpg: aka Doug Barton do...@dougbarton.net --- Begin PGP Signed Message Verified 2010-02-25 21:12:11 -- I've made a post to -arch regarding my plans for BIND in the base, along with some information about getting ready for DNSSEC, including the upcoming signing of the root zone. You can find the message at http://lists.freebsd.org/pipermail/freebsd-arch/2010-February/009908.html. If you have any feedback regarding any of these topics, please follow up to that thread. Regards, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ End PGP Signed Message Verified 2010-02-25 21:12:11 --- Little late for a reply, But thanks for keeping this updated as this is obviously very important information that not everyone usually comes across. At least I didn't hear anything about it till now. Thanks Doug, -- jhell ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Seeing the dreaded ZFS: i/o error - all block copies unavailable on 9.0-CURRENT
On Thu, Feb 25, 2010 at 1:08 PM, John Baldwin j...@freebsd.org wrote: On Thursday 25 February 2010 12:58:13 pm Chris wrote: On Thu, Feb 25, 2010 at 8:06 AM, John Baldwin j...@freebsd.org wrote: On Wednesday 24 February 2010 10:12:25 pm Chris wrote: So it sounds like somehow my system is trying to use the old boot2 method when I don't hit F12. I'm guessing the difference is due to how the hard drive is getting presented to the boot loader by the BIOS. How can I get rid of the legacy boot system and use only the ZFS bootloader? Does F12 enable PXE booting or some such? The only options I have when I press F12 are to either boot from my hard drive or to boot from my optical drive. Is there any way to more verbosely see what is happening at the bootloader level? No. So it sounds like F12 pops up some sort of boot menu, and that in the broken case you just let the machine boot off of the disk normally? Right. Upon powering on, to get the system to boot normally, I hit the F12 key which brings up a box that lets me choose either my hard disk or my optical drive to boot. When I do not hit F12, I get the LBA errors and the ZFS: i/o error - all block copies unavailable error shown in previous posts to this thread. If I boot into the non-F12 broken state and leave the system alone, it appears to try and boot twice and gets the same LBA errors and the same ZFS error. Again, if I install FreeBSD off an installation CD and use sysinstall to install a typical UFS-based system it boots without any trouble at all, F12 or not, leading me to believe that there's some sort of difference between the plain bootloader and the ZFS-enabled bootloader with respect to the way they interact with the BIOS. Another oddity I noticed is that if I change the SATA mode in the BIOS to IDE Native mode, the hard drive activity light stays on, even when the system is booted and is sitting idle. If I change it to AHCI, I do not see this. I doubt this has any relation to ZFS, but it was just an interesting observation. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
