8.2-PRE: hastd: Compile Error
What can I do to fix this? csup'd around 2pm Central (US) time from cvsup5. cc -O2 -pipe -I/usr/src/sbin/hastd -DINET -DINET6 -DYY_NO_UNPUT -DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c token.c cc1: warnings being treated as errors /usr/src/sbin/hastd/token.l:456: warning: function declaration isn't a prototype *** Error code 1 Stop in /usr/src/sbin/hastd. *** Error code 1 Stop in /usr/src/sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: 8.2-PRE: hastd: Compile Error
"Eugene Grosbein" wrote: >On 18.01.2011 04:38, Larry Rosenman wrote: >> What can I do to fix this? >> >> csup'd around 2pm Central (US) time from cvsup5. >> >> cc -O2 -pipe -I/usr/src/sbin/hastd -DINET -DINET6 -DYY_NO_UNPUT >-DYY_NO_INPUT -DHAVE_CRYPTO -std=gnu99 -fstack-protector >-Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter >-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type >-Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align >-Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs >-Wredundant-decls -Wno-pointer-sign -c token.c >> cc1: warnings being treated as errors >> /usr/src/sbin/hastd/token.l:456: warning: function declaration isn't >a prototype >> *** Error code 1 >> >> Stop in /usr/src/sbin/hastd. >> *** Error code 1 >> >> Stop in /usr/src/sbin. >> *** Error code 1 >> >> Stop in /usr/src. >> *** Error code 1 >> >> Stop in /usr/src. >> *** Error code 1 >> >> Stop in /usr/src. >> # $ > >Someone have to fix hastd's Makefile and change WARNS level there. >This problem breaks source upgrade. > >Eugene Grosbein Is anyone working on it? I'm trying to get a source upgrade from 8.0 to 8.2 done. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. ___ 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"
rsync corrupted MAC
Any ideas on which side or what might be broke here? ler/MAIL-ARCHIVE/2008/12/INBOX Corrupted MAC on input. Disconnecting: Packet corrupt rsync: connection unexpectedly closed (33845045 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [receiver=3.0.9] rsync: connection unexpectedly closed (1450 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9] The script: #!/bin/sh /usr/local/bin/rsync -Cavz --delete r...@tbh.lerctr.org:/etc/ \ /vault/backup/TBH/etc/ /usr/local/bin/rsync -Cavz --delete r...@tbh.lerctr.org:/home/ \ /vault/backup/TBH/home/ #/usr/local/bin/rsync -Cavz --delete r...@tbh.lerctr.org:/usr/local/pgsql/backups/ \ #/vault/backup/TBH/pgsql/ /usr/local/bin/rsync -Cavz --delete r...@tbh.lerctr.org:/var/named/ \ /vault/backup/TBH/named/ It seems to move and be at a random spot in the file. Then it will move to a different file. Ideas? Source is 8.2-STABLE, and the Destination/controller is 9.0-BETA3. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: rsync corrupted MAC
On 10/10/2011 10:47 AM, John Baldwin wrote: On Sunday, October 09, 2011 5:06:26 pm Larry Rosenman wrote: Any ideas on which side or what might be broke here? ler/MAIL-ARCHIVE/2008/12/INBOX Corrupted MAC on input. Disconnecting: Packet corrupt rsync: connection unexpectedly closed (33845045 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [receiver=3.0.9] rsync: connection unexpectedly closed (1450 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9] I've had somewhat similar issues (ssh getting corruption in its data stream) when a NIC in my netbook was corrupting packet data when it ran at 1G (it worked fine at 10/100). Pyun eventually fixed the issue by applying enough workarounds (it was likely a hardware bug in the NIC's chipset). However, it wasn't easy to debug unfortunately. :( Any ideas on where to start? from the 8.2 box (tbh.lerctr.org in the script): 8.2->PIX->Provider->Internet->Motorola SBG6580 (Time-Warner)->Trendnet TEG-160WS Gig switch->9.0 box (borg.lerctr.org). So, where do I start? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: rsync corrupted MAC
On 10/10/2011 3:57 PM, Louis Mamakos wrote: On Oct 10, 2011, at 2:38 PM, Larry Rosenman wrote: On 10/10/2011 10:47 AM, John Baldwin wrote: On Sunday, October 09, 2011 5:06:26 pm Larry Rosenman wrote: Any ideas on which side or what might be broke here? ler/MAIL-ARCHIVE/2008/12/INBOX Corrupted MAC on input. Disconnecting: Packet corrupt rsync: connection unexpectedly closed (33845045 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [receiver=3.0.9] rsync: connection unexpectedly closed (1450 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9] I've had somewhat similar issues (ssh getting corruption in its data stream) when a NIC in my netbook was corrupting packet data when it ran at 1G (it worked fine at 10/100). Pyun eventually fixed the issue by applying enough workarounds (it was likely a hardware bug in the NIC's chipset). However, it wasn't easy to debug unfortunately. :( Any ideas on where to start? from the 8.2 box (tbh.lerctr.org in the script): 8.2->PIX->Provider->Internet->Motorola SBG6580 (Time-Warner)->Trendnet TEG-160WS Gig switch->9.0 box (borg.lerctr.org). So, where do I start? I'd turn off IP / TCP / UDP checksum offloading on your NIC if it supports it, and see if you are getting network layer checksum errors. If the IP checksum is wrong, then it happened on the last hops between the NIC and memory or across the previous network hop. Good idea, but, it didn't show ANY errors on EITHER side (both are em nics). Next? $ ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=2098 ether 00:30:48:2e:99:ba inet 192.147.25.65 netmask 0xff00 broadcast 192.147.25.255 inet6 fe80::230:48ff:fe2e:99ba%em0 prefixlen 64 scopeid 0x1 inet 192.147.25.45 netmask 0xff00 broadcast 192.147.25.255 inet 192.147.25.11 netmask 0xff00 broadcast 192.147.25.255 nd6 options=3 media: Ethernet autoselect (100baseTX ) status: active $ $ uname -a FreeBSD thebighonker.lerctr.org 8.2-STABLE FreeBSD 8.2-STABLE #45: Sat Oct 8 10:57:43 CDT 2011 r...@thebighonker.lerctr.org:/usr/obj/usr/src/sys/THEBIGHONKER amd64 $ $ ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=2088 ether 00:30:48:8e:9f:f3 inet 192.168.200.4 netmask 0xff00 broadcast 192.168.200.255 inet6 fe80::230:48ff:fe8e:9ff3%em0 prefixlen 64 scopeid 0x1 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active $ uname -a FreeBSD borg.lerctr.org 9.0-BETA3 FreeBSD 9.0-BETA3 #1: Sun Oct 9 10:03:42 CDT 2011 r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE amd64 $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: rsync corrupted MAC
On Mon, 10 Oct 2011, Jeremy Chadwick wrote: On Mon, Oct 10, 2011 at 04:15:25PM -0500, Larry Rosenman wrote: On 10/10/2011 3:57 PM, Louis Mamakos wrote: On Oct 10, 2011, at 2:38 PM, Larry Rosenman wrote: On 10/10/2011 10:47 AM, John Baldwin wrote: On Sunday, October 09, 2011 5:06:26 pm Larry Rosenman wrote: Any ideas on which side or what might be broke here? ler/MAIL-ARCHIVE/2008/12/INBOX Corrupted MAC on input. Disconnecting: Packet corrupt rsync: connection unexpectedly closed (33845045 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [receiver=3.0.9] rsync: connection unexpectedly closed (1450 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9] I've had somewhat similar issues (ssh getting corruption in its data stream) when a NIC in my netbook was corrupting packet data when it ran at 1G (it worked fine at 10/100). Pyun eventually fixed the issue by applying enough workarounds (it was likely a hardware bug in the NIC's chipset). However, it wasn't easy to debug unfortunately. :( Any ideas on where to start? from the 8.2 box (tbh.lerctr.org in the script): 8.2->PIX->Provider->Internet->Motorola SBG6580 (Time-Warner)->Trendnet TEG-160WS Gig switch->9.0 box (borg.lerctr.org). So, where do I start? I'd turn off IP / TCP / UDP checksum offloading on your NIC if it supports it, and see if you are getting network layer checksum errors. If the IP checksum is wrong, then it happened on the last hops between the NIC and memory or across the previous network hop. Good idea, but, it didn't show ANY errors on EITHER side (both are em nics). Next? $ ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=2098 ether 00:30:48:2e:99:ba inet 192.147.25.65 netmask 0xff00 broadcast 192.147.25.255 inet6 fe80::230:48ff:fe2e:99ba%em0 prefixlen 64 scopeid 0x1 inet 192.147.25.45 netmask 0xff00 broadcast 192.147.25.255 inet 192.147.25.11 netmask 0xff00 broadcast 192.147.25.255 nd6 options=3 media: Ethernet autoselect (100baseTX ) status: active $ $ uname -a FreeBSD thebighonker.lerctr.org 8.2-STABLE FreeBSD 8.2-STABLE #45: Sat Oct 8 10:57:43 CDT 2011 r...@thebighonker.lerctr.org:/usr/obj/usr/src/sys/THEBIGHONKER amd64 $ $ ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=2088 ether 00:30:48:8e:9f:f3 inet 192.168.200.4 netmask 0xff00 broadcast 192.168.200.255 inet6 fe80::230:48ff:fe8e:9ff3%em0 prefixlen 64 scopeid 0x1 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active $ uname -a FreeBSD borg.lerctr.org 9.0-BETA3 FreeBSD 9.0-BETA3 #1: Sun Oct 9 10:03:42 CDT 2011 r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE amd64 $ Can you please provide output from the following commands executed on the machine showing the problem? The above commands show nothing useful, other than the fact that one machine is at 100/full and the other is at 1000/full (I don't know your network setup). Commands: * netstat -inbd -I em0 * sysctl -a dev.em.0 * Issue command "sysctl dev.em.0.debug=1", then type "dmesg" and provide all of the new output you will see at the bottom that pertains to the NIC If you Google this problem, you will find that the majority of the time it's caused by NIC drivers acting oddly. Also, I believe the em(4) driver in 9.x is slightly different than on 8.x, so I'm CC'ing Jack Vogel here. from 9.0: NameMtu Network Address Ipkts Ierrs Idrop Ibytes Opkts Oerrs Obytes Coll Drop em01500 00:30:48:8e:9f:f3 69776975 0 0 59660392277 52592789 0 104743924118 00 em01500 192.168.200.0 192.168.200.4 69759773 - - 58681934612 96397272 - 104003761109 -- em01500 fe80::230:48f fe80::230:48ff:fe0 - - 03 -248 -- dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.2.3 dev.em.0.%driver: em dev.em.0.%location: slot=0 function=0 dev.em.0.%pnpinfo: vendor=0x8086 device=0x1096 subvendor=0x15d9 subdevice=0x class=0x02 dev.em.0.%parent: pci6 dev.em.0.nvm: -1 dev.em.0.debug: -1 dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 66 dev.em.0.rx_abs_int_delay: 66 dev.em.0.tx_abs_int_delay: 66 dev.em.0.rx_processing_limit: 100 dev.em.0.flow_control: 3 dev.em.0.eee_control: 0 dev.em.0.link_irq: 0 dev.em.0.mbuf_alloc_fail: 0 dev.em.0.cluster_alloc_fail: 0 dev.em.0.dropped: 0 dev.em.0.tx_dma_fail: 21755 dev.em.0.rx_overruns: 0 dev.em.0.watchdog_timeouts: 0 dev.em.0.device_control: 1851969 dev.em.0.rx_control: 67141634 dev.em.0.fc_high_water: 30720 dev.em.0.fc_low_water: 29220 dev.em.0.queue0.txd_head: 136 dev.em.0.queue0.txd_tail: 136 dev.em.0.queue0.tx_irq: 0 dev.em.0.queue0.no_desc_avail:
Re: rsync corrupted MAC
They are not local to each other. See the diagram. They are across the internet from each other. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Jack Vogel wrote: Well, for a start I'd get both interfaces at the same speed, sounds like a hardware issue of some sort, cable or switch maybe? Jack On Mon, Oct 10, 2011 at 5:42 PM, Larry Rosenman wrote: On Mon, 10 Oct 2011, Jeremy Chadwick wrote: On Mon, Oct 10, 2011 at 04:15:25PM -0500, Larry Rosenman wrote: On 10/10/2011 3:57 PM, Louis Mamakos wrote: On Oct 10, 2011, at 2:38 PM, Larry Rosenman wrote: On 10/10/2011 10:47 AM, John Baldwin wrote: On Sunday, October 09, 2011 5:06:26 pm Larry Rosenman wrote: Any ideas on which side or what might be broke here? ler/MAIL-ARCHIVE/2008/12/INBOX Corrupted MAC on input. Disconnecting: Packet corrupt rsync: connection unexpectedly closed (33845045 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [receiver=3.0.9] rsync: connection unexpectedly closed (1450 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9] I've had somewhat similar issues (ssh getting corruption in its data stream) when a NIC in my netbook was corrupting packet data when it ran at 1G (it worked fine at 10/100). Pyun eventually fixed the issue by applying enough workarounds (it was likely a hardware bug in the NIC's chipset). However, it wasn't easy to debug unfortunately. :( Any ideas on where to start? from the 8.2 box (tbh.lerctr.org in the script): 8.2->PIX->Provider->Internet->Motorola SBG6580 (Time-Warner)->Trendnet TEG-160WS Gig switch->9.0 box (borg.lerctr.org). So, where do I start? I'd turn off IP / TCP / UDP checksum offloading on your NIC if it supports it, and see if you are getting network layer checksum errors. If the IP checksum is wrong, then it happened on the last hops between the NIC and memory or across the previous network hop. Good idea, but, it didn't show ANY errors on EITHER side (both are em nics). Next? $ ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=2098 ether 00:30:48:2e:99:ba inet 192.147.25.65 netmask 0xff00 broadcast 192.147.25.255 inet6 fe80::230:48ff:fe2e:99ba%em0 prefixlen 64 scopeid 0x1 inet 192.147.25.45 netmask 0xff00 broadcast 192.147.25.255 inet 192.147.25.11 netmask 0xff00 broadcast 192.147.25.255 nd6 options=3 media: Ethernet autoselect (100baseTX ) status: active $ $ uname -a FreeBSD thebighonker.lerctr.org 8.2-STABLE FreeBSD 8.2-STABLE #45: Sat Oct 8 10:57:43 CDT 2011 r...@thebighonker.lerctr.org:/usr/obj/usr/src/sys/THEBIGHONKER amd64 $ $ ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=2088 ether 00:30:48:8e:9f:f3 inet 192.168.200.4 netmask 0xff00 broadcast 192.168.200.255 inet6 fe80::230:48ff:fe8e:9ff3%em0 prefixlen 64 scopeid 0x1 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active $ uname -a FreeBSD borg.lerctr.org 9.0-BETA3 FreeBSD 9.0-BETA3 #1: Sun Oct 9 10:03:42 CDT 2011 r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE amd64 $ Can you please provide output from the following commands executed on the machine showing the problem? The above commands show nothing useful, other than the fact that one machine is at 100/full and the other is at 1000/full (I don't know your network setup). Commands: * netstat -inbd -I em0 * sysctl -a dev.em.0 * Issue command "sysctl dev.em.0.debug=1", then type "dmesg" and provide all of the new output you will see at the bottom that pertains to the NIC If you Google this problem, you will find that the majority of the time it's caused by NIC drivers acting oddly. Also, I believe the em(4) driver in 9.x is slightly different than on 8.x, so I'm CC'ing Jack Vogel here. from 9.0: NameMtu Network Address Ipkts Ierrs Idrop Ibytes Opkts Oerrs Obytes Coll Drop em01500 00:30:48:8e:9f:f3 69776975 0 0 59660392277 52592789 0 104743924118 00 em01500 192.168.200.0 192.168.200.4 69759773 - - 58681934612 96397272 - 104003761109 -- em0 1500 fe80::230:48f fe80::230:48ff:fe0 - - 03 -248 -- dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.2.3 dev.em.0.%driver: em dev.em.0.%location: slot=0 function=0 dev.em.0.%pnpinfo: vendor=0x8086 device=0x1096 subvendor=0x15d9 subdevice=0x class=0x02 dev.em.0.%parent: pci6 dev.em.0.nvm: -1 dev.em.0.debug: -1 dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 66 dev.em.0.rx_abs_int_delay: 66 dev.em.0.tx_abs_int_delay: 66 dev.em.0.rx_processing_limit: 100 dev.em.0.flow_control: 3 dev.em.0.eee_control: 0 dev.em.0.link_irq: 0 dev.em.0.mbuf_alloc_fail: 0
Re: rsync corrupted MAC
Not sure when it broke. I rebuilt the 9.0 server as 9.0, and ran the script and it started giving this. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Jack Vogel wrote: Oh, I see. So, did you have a previous working state? Jack On Tue, Oct 11, 2011 at 12:06 AM, Larry Rosenman wrote: They are not local to each other. See the diagram. They are across the internet from each other. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Jack Vogel wrote: Well, for a start I'd get both interfaces at the same speed, sounds like a hardware issue of some sort, cable or switch maybe? Jack On Mon, Oct 10, 2011 at 5:42 PM, Larry Rosenman wrote: On Mon, 10 Oct 2011, Jeremy Chadwick wrote: On Mon, Oct 10, 2011 at 04:15:25PM -0500, Larry Rosenman wrote: On 10/10/2011 3:57 PM, Louis Mamakos wrote: On Oct 10, 2011, at 2:38 PM, Larry Rosenman wrote: On 10/10/2011 10:47 AM, John Baldwin wrote: On Sunday, October 09, 2011 5:06:26 pm Larry Rosenman wrote: Any ideas on which side or what might be broke here? ler/MAIL-ARCHIVE/2008/12/INBOX Corrupted MAC on input. Disconnecting: Packet corrupt rsync: connection unexpectedly closed (33845045 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [receiver=3.0.9] rsync: connection unexpectedly closed (1450 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9] I've had somewhat similar issues (ssh getting corruption in its data stream) when a NIC in my netbook was corrupting packet data when it ran at 1G (it worked fine at 10/100). Pyun eventually fixed the issue by applying enough workarounds (it was likely a hardware bug in the NIC's chipset). However, it wasn't easy to debug unfortunately. :( Any ideas on where to start? from the 8.2 box (tbh.lerctr.org in the script): 8.2->PIX->Provider->Internet->Motorola SBG6580 (Time-Warner)->Trendnet TEG-160WS Gig switch->9.0 box (borg.lerctr.org). So, where do I start? I'd turn off IP / TCP / UDP checksum offloading on your NIC if it supports it, and see if you are getting network layer checksum errors. If the IP checksum is wrong, then it happened on the last hops between the NIC and memory or across the previous network hop. Good idea, but, it didn't show ANY errors on EITHER side (both are em nics). Next? $ ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=2098 ether 00:30:48:2e:99:ba inet 192.147.25.65 netmask 0xff00 broadcast 192.147.25.255 inet6 fe80::230:48ff:fe2e:99ba%em0 prefixlen 64 scopeid 0x1 inet 192.147.25.45 netmask 0xff00 broadcast 192.147.25.255 inet 192.147.25.11 netmask 0xff00 broadcast 192.147.25.255 nd6 options=3 media: Ethernet autoselect (100baseTX ) status: active $ $ uname -a FreeBSD thebighonker.lerctr.org 8.2-STABLE FreeBSD 8.2-STABLE #45: Sat Oct 8 10:57:43 CDT 2011 r...@thebighonker.lerctr.org:/usr/obj/usr/src/sys/THEBIGHONKER amd64 $ $ ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=2088 ether 00:30:48:8e:9f:f3 inet 192.168.200.4 netmask 0xff00 broadcast 192.168.200.255 inet6 fe80::230:48ff:fe8e:9ff3%em0 prefixlen 64 scopeid 0x1 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active $ uname -a FreeBSD borg.lerctr.org 9.0-BETA3 FreeBSD 9.0-BETA3 #1: Sun Oct 9 10:03:42 CDT 2011 r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE amd64 $ Can you please provide output from the following commands executed on the machine showing the problem? The above commands show nothing useful, other than the fact that one machine is at 100/full and the other is at 1000/full (I don't know your network setup). Commands: * netstat -inbd -I em0 * sysctl -a dev.em.0 * Issue command "sysctl dev.em.0.debug=1", then type "dmesg" and provide all of the new output you will see at the bottom that pertains to the NIC If you Google this problem, you will find that the majority of the time it's caused by NIC drivers acting oddly. Also, I believe the em(4) driver in 9.x is slightly different than on 8.x, so I'm CC'ing Jack Vogel here. from 9.0: NameMtu Network Address Ipkts Ierrs Idrop Ibytes Opkts Oerrs Obytes Coll Drop em01500 00:30:48:8e:9f:f3 69776975 0 0 59660392277 52592789 0 104743924118 00 em01500 192.168.200.0 192.168.200.4 69759773 - - 58681934612 96397272 - 104003761109 -- em0 1500 fe80::230:48f fe80::230:48ff:fe0 - - 03 -248 -- dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 7.2.3 dev.em.0.%driver: em dev.em.0.%location: slot=0 function=0 dev.em.0.%pnpinfo: vendor=0x8086 device=0x1096 subvendor=0x15d9 subdevice=0
9.0-RELEASE amd64: No Boot on VMWare Workstation
Is there a known issue with 9.0-RELEASE on amd64 VMWare Workstation? I tried to build a new VM on my new Lenovo W520 Laptop (Windows 7 Pro/64-Bit, 16G ram) and it gets to the Beastie menu, and times out, then dies. Any ideas? What can I provide? And, is there an issue with 9 in general, or could I install 8.3 and then source update it to 9 or 10? Thanks! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.0-RELEASE amd64: No Boot on VMWare Workstation
This is VMWare Workstation 8.0.3 booting off the release ISO. Ideas? On Tue, May 15, 2012 12:59 am, Adam Strohl wrote: > On 5/14/2012 22:18, Larry Rosenman wrote: >> Is there a known issue with 9.0-RELEASE on amd64 VMWare Workstation? > > Since nobody has chimed in I felt I should: > > I use FreeBSD 9.0 routinely under VMWare Workstation without issue (my > current VMWare Workstation version is 8.0.0 which is slightly out of > date, 8.0.3 is available). > >> I tried to build a new VM on my new Lenovo W520 Laptop (Windows 7 >> Pro/64-Bit, 16G ram) and it gets to the Beastie menu, and times out, >> then >> dies. >> >> Any ideas? >> >> What can I provide? > > The version of VMWare Workstation you are running. > >> And, is there an issue with 9 in general, or could I install 8.3 and >> then >> source update it to 9 or 10? > > I build test VMs for 9 and do test upgrades from 6.x, 7.x and 8.x to 9 > using VMWare Workstation on my desktop and laptop without issue. > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.0-RELEASE amd64: No Boot on VMWare Workstation
This is VMWare Workstation 8.0.3 booting off the release ISO. Ideas? On Tue, May 15, 2012 12:59 am, Adam Strohl wrote: > On 5/14/2012 22:18, Larry Rosenman wrote: >> Is there a known issue with 9.0-RELEASE on amd64 VMWare Workstation? > > Since nobody has chimed in I felt I should: > > I use FreeBSD 9.0 routinely under VMWare Workstation without issue (my > current VMWare Workstation version is 8.0.0 which is slightly out of > date, 8.0.3 is available). > >> I tried to build a new VM on my new Lenovo W520 Laptop (Windows 7 >> Pro/64-Bit, 16G ram) and it gets to the Beastie menu, and times out, >> then >> dies. >> >> Any ideas? >> >> What can I provide? > > The version of VMWare Workstation you are running. > >> And, is there an issue with 9 in general, or could I install 8.3 and >> then >> source update it to 9 or 10? > > I build test VMs for 9 and do test upgrades from 6.x, 7.x and 8.x to 9 > using VMWare Workstation on my desktop and laptop without issue. > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.0-RELEASE amd64: No Boot on VMWare Workstation
Ok, I'm just impatient. I let it sit, and it eventually came up. Would it be possible for the next 9.x release to set hw.memtest.tests="0" when we discover we're under a hypervisor to avoid doing the tests? (or default it to 0 in the installer kernel?)? On Tue, May 15, 2012 9:49 am, Larry Rosenman wrote: > This is VMWare Workstation 8.0.3 booting off the release ISO. > > Ideas? > > On Tue, May 15, 2012 12:59 am, Adam Strohl wrote: >> On 5/14/2012 22:18, Larry Rosenman wrote: >>> Is there a known issue with 9.0-RELEASE on amd64 VMWare Workstation? >> >> Since nobody has chimed in I felt I should: >> >> I use FreeBSD 9.0 routinely under VMWare Workstation without issue (my >> current VMWare Workstation version is 8.0.0 which is slightly out of >> date, 8.0.3 is available). >> >>> I tried to build a new VM on my new Lenovo W520 Laptop (Windows 7 >>> Pro/64-Bit, 16G ram) and it gets to the Beastie menu, and times out, >>> then >>> dies. >>> >>> Any ideas? >>> >>> What can I provide? >> >> The version of VMWare Workstation you are running. >> >>> And, is there an issue with 9 in general, or could I install 8.3 and >>> then >>> source update it to 9 or 10? >> >> I build test VMs for 9 and do test upgrades from 6.x, 7.x and 8.x to 9 >> using VMWare Workstation on my desktop and laptop without issue. >> > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 512-248-2683 E-Mail: l...@lerctr.org > US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 > > > ___ > 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" > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.0-RELEASE amd64: No Boot on VMWare Workstation
On Wed, May 16, 2012 10:04 am, Adam Strohl wrote: > On 5/16/2012 8:12, Larry Rosenman wrote: >> Ok, I'm just impatient. I let it sit, and it eventually came up. >> >> Would it be possible for the next 9.x release to set >> hw.memtest.tests="0" >> when we discover we're under a hypervisor to avoid doing the tests? (or >> default it to 0 in the installer kernel?)? >> > > FWIW this seems odd/unique to your setup. > > I see no such delay under any VMWare product, though I have not yet > upgraded to Workstation 8.0.3 from 8.0.0. > I believe this is due to the 8G of memory I put on it. (I like to build big VM's. It's directly proportional to the size of the VM. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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"
IPMI Console: No luck once OS is booted
I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893# # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.475 2007/04/10 21:40:12 pjd Exp $ cpu HAMMER ident BORG # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols #optionsSCHED_4BSD # 4BSD scheduler options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT# NFS usable as /, requires NFSCLIENT options NTFS# NT File System options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. #optionsSTOP_NMI# Stop CPUS using NMI instead of IPI options AUDIT options INCLUDE_CONFIG_FILE # Debugging for use in -current options KDB # Enable kernel debugger support. options KDB_TRACE # Enable kernel debugger support. options KDB_UNATTENDED # Enable kernel debugger support. options DDB # Support DDB. options GDB # Support remote GDB. options STACK #optionsINVARIANTS # Enable calls of extra sanity checking #optionsINVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS #optionsWITNESS # Enable checks to detect deadlocks and cycles #optionsWITNESS_SKIPSPIN# Don't run witness on spinlocks for speed # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel # Bus support. device acpi device pci # Floppy drives device fdc # ATA and ATAPI devices device
Re: IPMI Console: No luck once OS is booted
On Sat, 9 Aug 2008, Larry Rosenman wrote: I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. I hate it when I post something, and then look at one setting on the card, and fix it myself. There is a key release timeout checkbox on the keyboard/mouse settings tab for the KVM that wasn't checked. Checking it fixed it. Sorry for the noise. :( -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPMI Console: No luck once OS is booted
On Sat, 9 Aug 2008, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. I hate it when I post something, and then look at one setting on the card, and fix it myself. There is a key release timeout checkbox on the keyboard/mouse settings tab for the KVM that wasn't checked. Checking it fixed it. Sorry for the noise. :( Actually, it worked *ONCE*, and now is not behaving itself. Any ideas from other SuperMicro users? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPMI Console: No luck once OS is booted
On Sun, 10 Aug 2008, David Duchscher wrote: On Aug 10, 2008, at 8:24 AM, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. I hate it when I post something, and then look at one setting on the card, and fix it myself. There is a key release timeout checkbox on the keyboard/mouse settings tab for the KVM that wasn't checked. Checking it fixed it. Sorry for the noise. :( Actually, it worked *ONCE*, and now is not behaving itself. Any ideas from other SuperMicro users? I don't have that IPMI card but I can say we have other cards of theirs working. I would make sure the card is at the latest version of firmware. The AOC-SIMSO(+) card was not detected correctly until we upgraded. I don't know why the card is going away when freebsd boots since I assume you are on the dedicated LAN interface with its own IP address. Yes. It's not going away, just doesn't see the key strokes. We do have a few issues with Supermiro IPMI and FreeBSD that share the Intel NIC (em) with the OS. Once the NIC is detected, you can't talk to the IPMI card until the NIC is configured with ifconfig. Even just an ifconfig up will wake things back up. We ended up removing the em driver from the kernel and loading it as a module to reduce this window. The other issue is with bridging since the IPMI packets get gobbled up and never make it too the bridge. I do need to file PRs for these one of these days... -- DaveD -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPMI Console: No luck once OS is booted
On Sun, 10 Aug 2008, Daryl Richards wrote: What NIC does your server use? I'm currently trying to figure out a similar issue with my server, which use bge(4) em(4), and the IPMI card has it's own NIC. I have a Sun Fire X2200. I can access the LOM no problem once Linux or Solaris is booted. But, once FreeBSD boots, it's no longer accessible from the NIC. Serial still works fine, it's just access via web or ssh. This happens from a fresh install, and also I've rebuild to -STABLE, and no joy either. These two cases might be related. Hrm. That's interesting. On 10-Aug-08, at 9:24 AM, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: On Sat, 9 Aug 2008, Larry Rosenman wrote: I have a current RELENG_7 running on: http://www.supermicro.com/products/system/4U/7045/SYS-7045B-TR+.cfm with the -3+ IPMI card. I can interact with the BIOS, etc, but no joy once we get past the loader. Anyone have ideas? Attached is the kernel config, and the /var/run/dmesg.boot file. I hate it when I post something, and then look at one setting on the card, and fix it myself. There is a key release timeout checkbox on the keyboard/mouse settings tab for the KVM that wasn't checked. Checking it fixed it. Sorry for the noise. :( Actually, it worked *ONCE*, and now is not behaving itself. Any ideas from other SuperMicro users? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: IPMI Console: No luck once OS is booted
On Sun, 10 Aug 2008, David Duchscher wrote: On Aug 10, 2008, at 10:22 AM, Larry Rosenman wrote: I don't have that IPMI card but I can say we have other cards of theirs working. I would make sure the card is at the latest version of firmware. The AOC-SIMSO(+) card was not detected correctly until we upgraded. I don't know why the card is going away when freebsd boots since I assume you are on the dedicated LAN interface with its own IP address. Yes. It's not going away, just doesn't see the key strokes. Looking through your dmesg file, I don't see a USB keyboard being attached. On my system, the virtual keyboard is a USB keyboard. ukbd0: on uhub3 kbd2 at ukbd0 Good catch. When I set it to disable USB Mass Storage when no image is loaded, the ukbd came alive, and I'm typing this on the IPMI Console. Thanks! -- DaveD -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ICRC's
00:52:56.215 READ DMA Error 106 occurred at disk power-on lifetime: 40 hours (1 days + 16 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 2f 51 6c 4e 4a Error: ICRC, ABRT 47 sectors at LBA = 0x0a4e6c51 = 172911697 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- c8 00 80 00 6c 4e 4a 00 00:40:47.156 READ DMA c8 00 80 80 6b 4e 4a 00 00:40:47.156 READ DMA c8 00 80 00 6b 4e 4a 00 00:40:47.155 READ DMA c8 00 80 80 6a 4e 4a 00 00:40:47.155 READ DMA c8 00 80 00 6a 4e 4a 00 00:40:47.155 READ DMA SMART Self-test log structure revision number 1 Num Test_DescriptionStatus Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00%32 - # 2 Short offline Completed without error 00%10 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 100 Not_testing 200 Not_testing 300 Not_testing 400 Not_testing 500 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Ideas? This is on a SuperMicro SYS-7045-TR+ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ICRC's
On Sun, 10 Aug 2008, Jeremy Chadwick wrote: On Sun, Aug 10, 2008 at 06:01:34PM -0500, Larry Rosenman wrote: You have one or more of the following: 1. Faulty ATA cable 2. Faulty ATA port 3. Faulty ATA controller (doubtful, unless the errors are specific to one role (e.g. master or slave)) 4. A 2nd disk which is equally as bad (came from the same manufacturing batch, which is very likely if the drive is of the same vendor and model type, and manufacturing date (within a month or two)) We have a winner. I replaced the cable, and we get a clean scrub: pool: vault state: ONLINE scrub: scrub completed with 0 errors on Sun Aug 10 20:46:37 2008 config: NAMESTATE READ WRITE CKSUM vault ONLINE 0 0 0 raidz1ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad8 ONLINE 0 0 0 ad10ONLINE 0 0 0 ad12ONLINE 0 0 0 ad14ONLINE 0 0 0 ad4s1fONLINE 0 0 0 ad4s1eONLINE 0 0 0 ad4s1dONLINE 0 0 0 errors: No known data errors Much nicer. Thanks, Jeremy! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: (actually ZFS) Re: Will XFS be adopted
On Thu, 20 Nov 2008, Rudy wrote: Speaking of losing data on a ZFS system, I haven't yet (knock on wood) had a disk failure. Anyone have a disk failure occur and have an easy/hard time replacing the bad disk? I had a bad cable and also a bad disk. zpool scrub would whine about checksum errors, but I did NOT lose any data. Replaced the drive and still got the checksum errors. Replaced the cable, and it's been rock solid. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: whats best pracfive for ZFS on a whole disc these days ?
On Sat, November 14, 2009 5:43 pm, Daniel O'Connor wrote: > Stefan Bethke wrote: >> Am 28.10.2009 um 01:41 schrieb Daniel O'Connor: >> >>> On Wed, 28 Oct 2009, jfar...@goldsword.com wrote: >>>> Check the archives for stable@ and f...@. I believe that there was a >>>> thread not that long ago detailing exactly how to do that. IIRC, >>>> while it took a bit of work, it wasn't difficult. >>> Hmm do you have any idea what the subject was? I'm having trouble >>> finding it :( >> >> If you still need it, it was "ZFS pool corrupted on upgrade of -current >> (probably sata renaming)" on -current back in July. You probably need >> to read the full thread, and there are some caveats, but it's sometimes >> possible to glabel each device/partion, and zpool replace the original >> device/partition with the labelled one online. > > It's here.. > http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009440.html > > Quote... > > On Wed Jul 15 at 16:22, Freddie Cash wrote: > > Yep. It's as simple as: > > > > * label all the drives using glabel, while they're still attached to > > the pool > > * use "zpool replace pool ad4 label/disk01" to replace 1 drive > > * wait for it to resilver > > * use "zpool replace pool ad6 label/disk02" to replace the next > > drive > > * repeat the resilver and replace until all the devices are replaced > > > > This is what I did to one of our servers. Works quite nicely. > > > > There's no need to detach anything. > > I'll try it when I get home and see how it goes. When I try that, I get: # zpool status pool: vault state: ONLINE scrub: scrub completed after 3h4m with 0 errors on Wed Nov 11 04:32:00 2009 config: NAMESTATE READ WRITE CKSUM vault ONLINE 0 0 0 raidz1ONLINE 0 0 0 ada1ONLINE 0 0 0 ada2ONLINE 0 0 0 ada3ONLINE 0 0 0 ada4ONLINE 0 0 0 ada5ONLINE 0 0 0 ada0s1f ONLINE 0 0 0 ada0s1e ONLINE 0 0 0 ada0s1d ONLINE 0 0 0 errors: No known data errors # glabel label disk01 /dev/ada1 glabel: Can't store metadata on /dev/ada1: Operation not permitted. # Ideas? > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: whats best pracfive for ZFS on a whole disc these days ?
On Sat, November 14, 2009 6:03 pm, Daniel O'Connor wrote: > Larry Rosenman wrote: >> NAMESTATE READ WRITE CKSUM >> vault ONLINE 0 0 0 >>raidz1ONLINE 0 0 0 >> ada1ONLINE 0 0 0 >> ada2ONLINE 0 0 0 >> ada3ONLINE 0 0 0 >> ada4ONLINE 0 0 0 >> ada5ONLINE 0 0 0 >>ada0s1f ONLINE 0 0 0 >>ada0s1e ONLINE 0 0 0 >>ada0s1d ONLINE 0 0 0 >> >> errors: No known data errors >> # glabel label disk01 /dev/ada1 >> glabel: Can't store metadata on /dev/ada1: Operation not permitted. >> # >> >> Ideas? > > This is because glabel writes to the end of the disk (which is what it > uses to persist the label), if you haven't already labelled them it > can't add a one without destroying some data. > > I don't have this problem because I used GPT as a container and it has a > UUID for each partition made. That makes sense. I guess if I ever rebuild this one, I'll be better about it :) and, now that we have raidz boot, I'll just make the whole mess ZFS. :) LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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"
RELENG_7: Kernel Compile Failure
Just csup'd off cvsup17.us.freebsd.org: 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 -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 -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /usr/src/sys/kern/kern_conf.c /usr/src/sys/kern/kern_conf.c: In function 'giant_mmap': /usr/src/sys/kern/kern_conf.c:483: error: 'D_MMAP2' undeclared (first use in this function) /usr/src/sys/kern/kern_conf.c:483: error: (Each undeclared identifier is reported only once /usr/src/sys/kern/kern_conf.c:483: error: for each function it appears in.) /usr/src/sys/kern/kern_conf.c:484: error: 'struct cdevsw' has no member named 'd_mmap2' /usr/src/sys/kern/kern_conf.c: In function 'prep_cdevsw': /usr/src/sys/kern/kern_conf.c:677: error: 'D_MMAP2' undeclared (first use in this function) /usr/src/sys/kern/kern_conf.c:698: error: 'struct cdevsw' has no member named 'd_mmap2' /usr/src/sys/kern/kern_conf.c:698: error: 'struct cdevsw' has no member named 'd_mmap2' /usr/src/sys/kern/kern_conf.c:698: error: 'd_mmap2_t' undeclared (first use in this function) /usr/src/sys/kern/kern_conf.c:698: error: expected expression before ')' token /usr/src/sys/kern/kern_conf.c:698: error: 'struct cdevsw' has no member named 'd_mmap2' *** Error code 1 Stop in /usr/obj/usr/src/sys/THEBIGHONKER. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. # Ideas? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: RELENG_7: Kernel Compile Failure
On Sun, November 15, 2009 1:10 pm, David Wolfskill wrote: > On Sun, Nov 15, 2009 at 12:37:23PM -0600, Larry Rosenman wrote: >> ... >> /usr/src/sys/kern/kern_conf.c:698: error: 'struct cdevsw' has no member >> named 'd_mmap2' >> *** Error code 1 >> >> Stop in /usr/obj/usr/src/sys/THEBIGHONKER. >> *** Error code 1 >> >> Stop in /usr/src. >> *** Error code 1 >> >> Stop in /usr/src. >> # >> >> >> Ideas? >> ... > > Try a different mirror, perhaps? I've had no problems tracking stable/7 > daily (though I'm using SVN). Thanks. Pulled a update from cvsup5.us.freebsd.org, and changes were picked up. Can someone check the health of cvsup17.us.freebsd.org? > > Peace, > david > -- > David H. Wolfskillda...@catwhisker.org > Depriving a girl or boy of an opportunity for education is evil. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: 8.0-RELEASE -> -STABLE and size of /
On Sat, January 23, 2010 8:35 pm, Torfinn Ingolfsen wrote: > On Sat, 23 Jan 2010 16:20:54 -0800 > Kevin Oberman wrote: > >> Just for the record and to avoid further confusion, building a kernel >> with debug symbols does not take any more space in root. Another copy of >> the kernel is built but not installed into /kernel. The copy of the >> kernel >> in /kernel is always symbol-less. > > Perhaps my question should be changed to: > how do I configure the "make world" procedure so that no files ending > in '*symbol' get installed in /boot/kernel? add the following to /etc/make.conf: INSTALL_NODEBUG=yes > -- > Regards, > Torfinn Ingolfsen > > ___ > 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" > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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"
kernel compile failure
r device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse #device ural# Ralink Technology RT2500USB wireless NICs device urio# Diamond Rio 500 MP3 player #device uscanner# Scanners # # The cpufreq(4) driver provides support for non-ACPI CPU frequency control #device cpufreq # Direct Rendering modules for 3D acceleration. device drm # DRM core module required by DRM drivers device radeondrm # ATI Radeon options HWPMC_HOOKS device smbus # Bus support, required for smb below. device intpm device ichsmb device smb device iicbus # Bus support, required for ic/iic/iicsmb below. device iicbb device ic device iic device iicsmb # smb over i2c bridge device crypto # core crypto support device cryptodev # /dev/crypto for access to h/w device rndtest # FIPS 140-2 entropy tester device ipmi device smbios options SCTP #optionsBREAK_TO_DEBUGGER #optionsALT_BREAK_TO_DEBUGGER device coretemp# Core temp (CORE procs and newer) #ungarble messages options PRINTF_BUFR_SIZE=128 #KTR Stuff options KTR options KTR_COMPILE=(KTR_SCHED) options KTR_MASK=(KTR_SCHED) options KTR_ENTRIES=262144 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: kernel compile failure
For the record, it appears that cvsup17.us.freebsd.org is serving outdated files. $ find . -name ata.h ./sys/ata.h $ cd sys $ ls -l ata.h -rw-r--r-- 1 root wheel 25308 Feb 6 12:35 ata.h $ sudo -s Password: # rm ata.h # csup -h cvsup17.us.freebsd.org -L 2 -g /usr/share/examples/cvsup/stand* Parsing supfile "/usr/share/examples/cvsup/standard-supfile" Connecting to cvsup17.us.freebsd.org Connected to 65.212.71.21 Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection src-all/cvs Checkout src/sys/sys/ata.h Shutting down connection to server Finished successfully # ls -l ata.h -rw-r--r-- 1 root wheel 25308 Jan 19 06:58 ata.h # csup -h cvsup14.us.freebsd.org -L 2 -g /usr/share/examples/cvsup/stand* Parsing supfile "/usr/share/examples/cvsup/standard-supfile" Connecting to cvsup14.us.freebsd.org Connected to 216.87.78.137 Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing multiplexed-mode data connection Running Updating collection src-all/cvs Edit src/sys/netinet/libalias/alias_mod.c Add delta 1.4.2.3 2010.02.11.18.34.06 mjacob Edit src/sys/netinet/sctp_asconf.c Add delta 1.40.2.4 2010.02.11.18.34.06 mjacob Edit src/sys/netinet/sctputil.c Add delta 1.93.2.7 2010.02.11.18.34.06 mjacob Edit src/sys/nfsclient/bootp_subr.c Add delta 1.86.2.4 2010.02.11.18.34.06 mjacob Edit src/sys/nfsclient/nfs.h Add delta 1.110.2.2 2010.02.10.16.16.50 rmacklem Edit src/sys/nfsclient/nfs_bio.c Add delta 1.180.2.2 2010.02.10.16.16.50 rmacklem Edit src/sys/nfsclient/nfs_nfsiod.c Add delta 1.95.2.2 2010.02.10.16.16.50 rmacklem Edit src/sys/nfsclient/nfs_subs.c Add delta 1.163.2.3 2010.02.10.16.16.50 rmacklem Edit src/sys/nfsclient/nfs_vnops.c Add delta 1.318.2.8 2010.02.10.16.16.50 rmacklem Edit src/sys/nfsclient/nfsnode.h Add delta 1.66.2.3 2010.02.10.16.16.50 rmacklem Edit src/sys/pci/ncr.c Add delta 1.197.10.2 2010.02.11.18.34.06 mjacob Edit src/sys/powerpc/aim/mmu_oea.c Add delta 1.130.2.2 2010.02.11.18.34.06 mjacob Edit src/sys/rpc/clnt_dg.c Add delta 1.7.2.3 2010.02.11.18.34.06 mjacob Edit src/sys/sys/ata.h Add delta 1.41.2.7 2010.02.14.19.50.33 mav Edit src/sys/ufs/ffs/ffs_snapshot.c Add delta 1.150.2.2 2010.02.11.18.34.06 mjacob Edit src/tools/make_libdeps.sh Add delta 1.9.10.2 2010.02.15.11.29.27 ru Edit src/usr.bin/netstat/if.c Add delta 1.70.2.3 2010.02.10.00.34.13 delphij Edit src/usr.bin/netstat/main.c Add delta 1.96.2.3 2010.02.10.00.34.13 delphij Edit src/usr.bin/netstat/netstat.1 Add delta 1.63.2.2 2010.02.10.00.34.13 delphij Edit src/usr.bin/netstat/netstat.h Add delta 1.58.2.3 2010.02.10.00.34.13 delphij Edit src/usr.sbin/rtsold/rtsold.c Add delta 1.23.2.2 2010.02.13.16.25.33 ume Add delta 1.23.2.3 2010.02.13.16.28.25 ume Shutting down connection to server Finished successfully # $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: Alexander Motin [mailto:mav...@gmail.com] On Behalf Of Alexander Motin Sent: Monday, February 15, 2010 7:01 AM To: Larry Rosenman Cc: Jeremy Chadwick; freebsd-stable@freebsd.org Subject: Re: kernel compile failure Jeremy Chadwick wrote: > On Mon, Feb 15, 2010 at 03:43:36AM -0600, Larry Rosenman wrote: >> I'm getting: >> 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 -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 -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/cam/ata/ata_xpt.c >> /usr/src/sys/cam/ata/ata_xpt.c: In function 'probestart': >> /usr/src/sys/cam/ata/ata_xpt.c:331: error: 'ATA_SF_PUIS_SPINUP' undeclared (first use in this function) >> /usr/src/sys/cam/ata/ata_xpt.c:331: error: (Each undeclared identifier is reported only once >> /usr/src/sys/cam/ata/ata_xpt.c:331: error: for each function it appears in.) >> /usr/src/sys/cam/ata/ata_xpt.c: In function 'probedone': >> /usr/src/sys/cam/ata/ata_xpt.c:789: error: 'ATA_RESP_INCOMPLETE' undeclared (first use in this function) >> *** Error code 1 >> >> Stop in /usr/obj/usr/src/sys/BORG. >> *** Error code 1 >> >> Stop in /usr/src. >> *** Err
RE: kernel compile failure
Already done on Monday at 08:12am US/Central (GMT-6). -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: John Baldwin [mailto:j...@freebsd.org] Sent: Wednesday, February 17, 2010 3:42 PM To: freebsd-stable@freebsd.org Cc: Larry Rosenman; 'Alexander Motin'; 'Jeremy Chadwick' Subject: Re: kernel compile failure On Monday 15 February 2010 8:55:13 am Larry Rosenman wrote: > For the record, it appears that cvsup17.us.freebsd.org is serving outdated > files. Try sending an e-mail to h...@. The last time cvsup17 had issues the owner fixed them after seeing an e-mail to h...@. -- John Baldwin ___ 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"
Hang after flushing all buffers/no reboot
I have a amd64 system that when I try to reboot it, it hangs after the "All buffers flushed" message. I thought I had all the debug stuff in place (I'll attach the config and a dmesg), but I can't get it into ddb to get the backtrace :( Ideas? (This is with RELENG_7 of 2008-04-11). -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893# # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.475 2007/04/10 21:40:12 pjd Exp $ cpu HAMMER ident BORG # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols #optionsSCHED_4BSD # 4BSD scheduler options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL# Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device options NFSCLIENT # Network Filesystem Client options NFSSERVER # Network Filesystem Server options NFS_ROOT# NFS usable as /, requires NFSCLIENT options NTFS# NT File System options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS# Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY# BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_IA32 # Compatible with i386 binaries options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. #optionsSTOP_NMI# Stop CPUS using NMI instead of IPI options AUDIT options INCLUDE_CONFIG_FILE # Debugging for use in -current options KDB # Enable kernel debugger support. options KDB_TRACE # Enable kernel debugger support. options KDB_UNATTENDED # Enable kernel debugger support. options DDB # Support DDB. options GDB # Support remote GDB. options STACK #optionsINVARIANTS # Enable calls of extra sanity checking #optionsINVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS #optionsWITNESS # Enable checks to detect deadlocks and cycles #optionsWITNESS_SKIPSPIN# Don't run witness on spinlocks for speed # Make an SMP-capable kernel by default options SMP # Symmetric MultiProcessor Kernel # Bus support. device acpi device pci # Floppy drives device fdc # ATA and ATAPI devices dev
Re: Hang after flushing all buffers/no reboot
On Sat, 12 Apr 2008, Jeremy Chadwick wrote: On Sat, Apr 12, 2008 at 10:16:39AM -0500, Larry Rosenman wrote: I have a amd64 system that when I try to reboot it, it hangs after the "All buffers flushed" message. I thought I had all the debug stuff in place (I'll attach the config and a dmesg), but I can't get it into ddb to get the backtrace :( Ideas? Try playing with hw.acpi.disable_on_reboot and hw.acpi.handle_reboot. Seeting hw.acpi.handle_reboot = 1 (via sysctl, fwiw) seems to have at least worked once :) Thanks for the tip! I'm not sure if these are settable via sysctl or need to be done via loader.conf. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
calcru: time went backwards
I thought this was gone, but on a kernel from Saturday I'm seeing a bunch of these: calcru: runtime went backwards from 65109085931 usec to 61451418084 usec for pid 1384 (FahCore_78.exe) calcru: runtime went backwards from 65061446064 usec to 61427333429 usec for pid 1400 (FahCore_a0.exe) calcru: runtime went backwards from 65098513979 usec to 61461484768 usec for pid 1397 (FahCore_a0.exe) calcru: runtime went backwards from 7583892 usec to 7395604 usec for pid 1377 (FahCore_a0.exe) calcru: runtime went backwards from 7715084 usec to 7585681 usec for pid 1375 (FahCore_a0.exe) calcru: runtime went backwards from 1259 usec to 1189 usec for pid 1372 (FAH504-3-Linux.exe) calcru: runtime went backwards from 1295 usec to 1222 usec for pid 1369 (FAH504-2-Linux.exe) calcru: runtime went backwards from 5679294 usec to 5617155 usec for pid 1367 (FahCore_78.exe) calcru: runtime went backwards from 1846 usec to 1742 usec for pid 1364 (FAH504-Linux.exe) calcru: runtime went backwards from 3564 usec to 3363 usec for pid 1362 (getty) calcru: runtime went backwards from 2834 usec to 2674 usec for pid 1361 (getty) calcru: runtime went backwards from 2453 usec to 2315 usec for pid 1360 (getty) calcru: runtime went backwards from 4438 usec to 4188 usec for pid 1359 (getty) calcru: runtime went backwards from 3337 usec to 3149 usec for pid 1358 (getty) calcru: runtime went backwards from 3351 usec to 3163 usec for pid 1357 (getty) calcru: runtime went backwards from 3590 usec to 3387 usec for pid 1356 (getty) calcru: runtime went backwards from 5498 usec to 5188 usec for pid 1334 (inetd) calcru: runtime went backwards from 156 usec to 147 usec for pid 1307 (moused) calcru: runtime went backwards from 4315 usec to 4072 usec for pid 1292 (p4web) calcru: runtime went backwards from 1019 usec to 961 usec for pid 1236 (bacula-sd) calcru: runtime went backwards from 6084684 usec to 5742177 usec for pid 1180 (FAH504-Linux.exe) calcru: runtime went backwards from 12073757 usec to 11394126 usec for pid 1168 (FAH504-2-Linux.exe) calcru: runtime went backwards from 12053145 usec to 11374675 usec for pid 1156 (FAH504-3-Linux.exe) calcru: runtime went backwards from 28433 usec to 26833 usec for pid 822 (nfsd) calcru: runtime went backwards from 1880 usec to 1774 usec for pid 820 (mountd) calcru: runtime went backwards from 328751 usec to 310246 usec for pid 759 (java) calcru: runtime went backwards from 872 usec to 823 usec for pid 659 (devd) calcru: runtime went backwards from 14250 usec to 13448 usec for pid 659 (devd) calcru: runtime went backwards from 332 usec to 314 usec for pid 352 (adjkerntz) calcru: runtime went backwards from 1239633054 usec to 1183677040 usec for pid 190 (spa_zio_intr_1) calcru: runtime went backwards from 1234748390 usec to 1178920371 usec for pid 189 (spa_zio_intr_1) calcru: runtime went backwards from 1235958582 usec to 1180229129 usec for pid 188 (spa_zio_intr_1) calcru: runtime went backwards from 1235221753 usec to 117942 usec for pid 187 (spa_zio_intr_1) calcru: runtime went backwards from 10474 usec to 10311 usec for pid 44 (irq1: atkbd0) calcru: runtime went backwards from 280 usec to 265 usec for pid 42 (irq14: ata0) calcru: runtime went backwards from 284 usec to 268 usec for pid 33 (irq17: uhci0 ehci0) calcru: runtime went backwards from 1536 usec to 1450 usec for pid 29 (swi2: cambio) calcru: runtime went backwards from 6263 usec to 6175 usec for pid 26 (swi6: Giant taskq) calcru: runtime went backwards from 11857 usec to 11189 usec for pid 24 (swi5: +) calcru: runtime went backwards from 627055449 usec to 592838089 usec for pid 1 (init) calcru: runtime went backwards from 7763 usec to 7326 usec for pid 0 (swapper) How can I help debug? This is on a amd64 kernel, with Dual Xeon 5120's. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: calcru: time went backwards
On Tue, 15 Apr 2008, Jeremy Chadwick wrote: On Tue, Apr 15, 2008 at 10:11:38AM -0400, Scott Robbins wrote: On Tue, Apr 15, 2008 at 07:59:40AM -0500, Larry Rosenman wrote: I thought this was gone, but on a kernel from Saturday I'm seeing a bunch of these: This one is covered in the FAQ in the troubleshooting section, 5.19. And what the FAQ doesn't cover is here: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues * EIST (Intel SpeedStep) incompatibilities with Supermicro PDSMI+ motherboards (and possibly others) * Symptom: kernel outputs messages like kernel: calcru: negative runtime of -X usec for pid XX * Workaround: Disable the EIST feature in the BIOS. You can still achieve ACPI-based processor frequency throttling by using powerd(8). * Reference: http://lists.freebsd.org/pipermail/freebsd-questions/2006-October/133253.html What I find interesting is I hadn't seen these until this kernel update :( Thanks for the info, however. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: calcru: time went backwards
On Fri, 18 Apr 2008, Jeremy Chadwick wrote: On Fri, Apr 18, 2008 at 04:51:50PM +0300, Pertti Kosunen wrote: Larry Rosenman wrote: On Tue, 15 Apr 2008, Jeremy Chadwick wrote: And what the FAQ doesn't cover is here: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues * EIST (Intel SpeedStep) incompatibilities with Supermicro PDSMI+ motherboards (and possibly others) * Symptom: kernel outputs messages like kernel: calcru: negative runtime of -X usec for pid XX * Workaround: Disable the EIST feature in the BIOS. You can still achieve ACPI-based processor frequency throttling by using powerd(8). * Reference: http://lists.freebsd.org/pipermail/freebsd-questions/2006-October/133253.html What I find interesting is I hadn't seen these until this kernel update :( Same problem here with Tyan Toledo i3000R (S5191) motherboard if cpufreq module is loaded. 7.0-RELEASE (AMD64) didn't have this problem. Are you absolutely positive about this (re: amd64 not having the problem)? I can reproduce the issue documented in my Wiki page on i386 or amd64. The piece that seems to cause it, at least in the case of the PDSMI+, is EIST being enabled in the BIOS. For example, this is my a PDSMI+ system (amd64), which exhibits the problem (when EIST is enabled). EIST in the BIOS is disabled here: est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 928092806000928 device_attach: est0 attach returned 6 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 928092806000928 device_attach: est1 attach returned 6 powerd(8) is running and working perfectly, as shown below. Look closely at dev.cpu.0.freq and freq_levels: # ps -auxw | grep powerd root 714 0.0 0.1 5628 1172 ?? Ss Wed04AM 0:10.08 /usr/sbin/powerd -p 2000 # sysctl -a | grep dev.cpu.0.freq dev.cpu.0.freq: 297 dev.cpu.0.freq_levels: 2382/-1 2084/-1 1786/-1 1488/-1 1191/-1 893/-1 595/-1 297/-1 Under heavy load, the frequency gradually steps/climbs to 2382MHz as expected. During this time, absolutely no negative runtime messages appear (and have never appeared). If I reboot the box, enable EIST in the BIOS, and start FreeBSD, negative runtime messages begin almost immediately. My cpu frequency is ALWAYS at the full-version, since I have [EMAIL PROTECTED] processes running. This didn't start happening until the latest kernel Boot bmesg. Copyright (c) 1992-2008 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 7.0-STABLE #34: Sat Apr 12 10:06:17 CDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BORG Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU5120 @ 1.86GHz (1862.01-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0x4e3bd AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 usable memory = 4284116992 (4085 MB) avail memory = 4113575936 (3923 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 cryptosoft0: on motherboard acpi0: 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 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 cpu0: on acpi0 coretemp0: on cpu0 est0: on cpu0 est0: Setting 1867 MHz p4tcc0: on cpu0 cpu1: on acpi0 coretemp1: on cpu1 est1: on cpu1 est1: Setting 1867 MHz p4tcc1: on cpu1 cpu2: on acpi0 coretemp2: on cpu2 est2: on cpu2 est2: Setting 1867 MHz p4tcc2: on cpu2 cpu3: on acpi0 coretemp3: on cpu3 est3: on cpu3 est3: Setting 1867 MHz p4tcc3: on cpu3 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci1: on pcib1 pcib2: irq 16 at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 0.0 on pci2 pci3: on pcib3 pcib4: at device 0.0 on pci3 pci4: on pcib4 pcib5: at device 0.2 on pci3 pci5: on pcib5 pcib6: irq 18 at device 2.0 on pci2 pci6: on pcib6 em0: port 0x2000-0x201f mem 0xd800-0xd801 irq 18 at device 0.0 on pci6 em0: Using MSI interrupt em0: Ethernet address: 00:30:48:8e:9f:f3 em0: [FILTER] em1: port 0x2020-0x203f mem 0xd802-0xd803 irq 19 at device 0.1 on pci6 em1: Using MSI interrupt em1: Ethernet address: 00:30:48:8e:9f:f2 em1: [FILTER] pcib7: at device 0.3 on pci1 pci7: on pcib7 pcib8: at device 4.0 on pci0 pci8: on pcib8 pcib9: at
Re: lsof needs update
Thanks. I'll report to Vic, and see if we can get a fix soonish. On Sat, July 21, 2012 12:08 pm, Chris Rees wrote: > On 21 July 2012 18:04, Daniel Braniss wrote: >>> On 21 July 2012 10:36, Daniel Braniss wrote: >>> > hi, lsof on freebsd 9.1: >>> > COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >>> > ntpd1707 root cwd >>> unknown file >>> > system type: newnfs >>> > ntpd1707 root rtd >>> unknown file >>> > system type: newnfs >>> > ntpd1707 root txt >>> unknown file >>> > system type: newnfs >>> > ntpd1707 root txt >>> unknown file >>> > system type: newnfs >>> > ntpd1707 root txt >>> unknown file >>> > system type: newnfs >>> > ntpd1707 root txt >>> unknown file >>> > system type: newnfs >>> > ntpd1707 root txt >>> unknown file >>> > system type: newnfs >>> > ntpd1707 root txt >>> unknown file >>> > system type: newnfs >>> > ntpd1707 root txt >>> unknown file >>> > system type: newnfs >>> > ntpd1707 root txt >>> unknown file >>> > system type: newnfs >>> >>> Did you recompile lsof when upgrading? >>> >>> Chris >> I compiled it last week, but just in case I did it again, samr result >> >> lsof -v >> lsof version information: >> revision: 4.86 >> latest revision: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/ >> latest FAQ: ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/FAQ >> latest man page: >> ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/lsof_man >> constructed: Sat Jul 21 20:00:36 IDT 2012 >> constructed by and on: root@pe-00 >> compiler: cc >> compiler flags: -pipe -fno-strict-aliasing -DHASEFFNLINK=i_effnlink >> -DHASF_VNODE -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 >> -DHAS_VM_MEMATTR_T -DHAS_CDEV2PRIV -DHAS_NO_SI_UDEV -DHAS_SYS_SX_H >> -DHAS_ZFS -DHAS_V_LOCKF -DHAS_LOCKF_ENTRY -DHAS_NO_6PORT >> -DHAS_NO_6PPCB -DNEEDS_BOOLEAN_T -DFREEBSDV=9000 -DHASFDESCFS=2 >> -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHASUTMPX -DHAS_STRFTIME >> -DLSOF_VSTR="9.1-PRERELEASE" -I/usr/src/sys -O2 >> loader flags: -L./lib -llsof -lkvm >> system info: FreeBSD pe-00 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #6: >> Fri Jul 20 17:41:41 IDT 2012 >> danny@rnd:/home/obj/rnd/r+d/stable/9/sys/HUJI amd64 >> Anyone can list all files. >> /dev warnings are enabled. >> Kernel ID check is enabled. >> Device cache file read-only paths: >> Named via -D: none >> Named in environment variable LSOFDEVCACHE: none >> Personal path format (HASPERSDC): "%h/%p.lsof_%L" >> Modified personal path environment variable: LSOFPERSDCPATH >> LSOFPERSDCPATH value: none >> Personal path: /root/.lsof_pe-00 >> Device cache file write paths: >> Named via -D: none >> Named in environment variable LSOFDEVCACHE: none >> Personal path format (HASPERSDC): "%h/%p.lsof_%L" >> Modified personal path environment variable: LSOFPERSDCPATH >> LSOFPERSDCPATH value: none >> Personal path: /root/.lsof_pe-00 > > OK, I've copied in the lsof port maintainer too then, so he knows. > > Chris > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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"
Fwd: Re: zfs send/recv invalid data
I forgot to add current/stable to the list
TL;DR: there seems(!) to be something(!) unclean about an ssh path
between an 8.3-STABLE(r247820) and
10.0-CURRENT(r247826) box such that a zfs send stream is corrupted in
transit.
below is the thread from -fs about it, with sshd configs from both
sides.
If I copy the stream it works, but piping through ssh does NOT.
Original Message
Subject: Re: zfs send/recv invalid data
Date: 2013-03-06 04:46
From: Larry Rosenman
To: Steven Hartland
Cc: Ronald Klop ,
On 2013-03-06 02:38, Steven Hartland wrote:
- Original Message - From: "Larry Rosenman"
I received an "invalid data" in a zfs send (from 8.3) / zfs
recv (to 10.0) of a -R -I stream.
What data do I need to gather to figure out what side and
what's wrong?
I've already started zpool scrubs on both sides.
I can insert a tee to grab the stream on either/both sides if
that would help.
Is the problem repeatable or is it just a network glitch?
Ronald.
Repeatable...
Here is the exact error message:
receiving incremental stream of vault/home/ctr@2013-03-05-test3
into zroot/backups/TBH/home/ctr@2013-03-05-test3
cannot receive incremental stream: invalid backup stream
this is the script I'm running:
#!/bin/sh
DATE=`date "+%Y-%m-%d-BUG-REPRO"`
DATE2=`date -v "-1d" "+%Y-%m-%d"`
# snap the source
ssh r...@tbh.lerctr.org zfs snapshot -r vault@${DATE}
# zfs copy the source to here.
ssh r...@tbh.lerctr.org "zfs send -R -D -I vault@${DATE2}
vault@${DATE} | \
tee /tmp/backup.stream.send.${DATE} | \
ssh home.lerctr.org \"tee /tmp/backup.stream.receive.${DATE}
| zfs recv -u -v -d zroot/backups/TBH\""
# make sure we NEVER allow the backup stuff to automount.
/sbin/zfs list -H -t filesystem -r zroot/backups/TBH| \
awk '{printf "/sbin/zfs set canmount=noauto %s\n",$1}' | sh
both streams are in http://www.lerctr.org/~ler/ZFS_RECV
Your send and receive sides differ, which indicates your ssh
shell my not be clean.
Looking at the receive side its got what looks like a mail
message appended.
I suspect if you manually copy the receive copy to the 10 machine
and
the receive it will work fine.
we're copying mail files
and it still fails
I've put more example send/recv files in that directory.
we're copying home dirs, which include lots of mail.
(this one is my wife's)
Ideas?
I *CAN* give access to both sides via ssh.
The copy of the data stream on both sides should be identical
though and its not, which leads me to believe something is
corrupting the data on the way. Try the following:-
From source:-
zfs send -R -D -I vault@${DATE2} vault@${DATE} > test.stream
scp test.stream home.lerctr.org:~/
From target:
zfs recv -u -v -d zroot/backups/TBH < test.stream
If this works then there is something unclean about your ssh
shell.
Regards
Steve
send side:
# zfs send -R -D -I vault@2013-03-05 vault@2013-03-06 >/tmp/send.stream
# openssl md5 /tmp/send.stream
MD5(/tmp/send.stream)= 9cd1d73ea8411f1c222bc90e7bea3d33
# scp /tmp/send.stream home:/tmp/send.stream
send.stream 100% 1180MB 2.5MB/s
07:44
# uname -a
FreeBSD thebighonker.lerctr.org 8.3-STABLE FreeBSD 8.3-STABLE #54
r247820: Mon Mar 4 18:08:11 CST 2013
r...@thebighonker.lerctr.org:/usr/obj/usr/src/sys/THEBIGHONKER amd64
#
Receive side:
# uname -a
FreeBSD borg.lerctr.org 10.0-CURRENT FreeBSD 10.0-CURRENT #124 r247826:
Mon Mar 4 19:59:08 CST 2013
r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE amd64
# openssl md5 /tmp/send.stream
MD5(/tmp/send.stream)= 9cd1d73ea8411f1c222bc90e7bea3d33
# zfs recv -F -u -v -d zroot/backups/TBH < /tmp/send.stream
#
So, you are correct that something(tm) is unclean about the ssh path.
adding -current and -stable for diagnosing ssh issue.
sshd config on the 8.3-STABLE box:
# cat /etc/ssh/sshd_config
# $OpenBSD: sshd_config,v 1.87 2012/07/10 02:19:15 djm Exp $
# $FreeBSD: stable/8/crypto/openssh/sshd_config 247521 2013-03-01
02:06:04Z des $
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options override the
# default value.
# Note that some of FreeBSD's defaults differ from OpenBSD's, and
# FreeBSD has a few additional options.
#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
# Disable legacy (protocol version 1) support in the server for new
# installations. In future the default will change to require explicit
# activation of protocol 1
Protocol 2
# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_ke
Re: Reinstalling boot blocks on a ZFS-only system
On 2013-05-12 15:58, Jeremy Chadwick wrote:
On Sun, May 12, 2013 at 04:50:46PM -0400, Chris Ross wrote:
So, I've long known and it makes sense that when you're booted from a
ZFS volume, you can't mess with the boot-loader. And, I know a few
months ago I had a set of commands I would use when booted from a CD
that would initialize the network and copy the "release/boot" from
somewhere else so that I could install bootblocks and boot-loaders from
more recent code. Sadly, I didn't _record_ those commands I was using.
What do "people in the know" do when they want to update the bootblocks
of a ZFS-boot system? Or, have too few people followed this path so
far that they can boot UFS and do it with less difficulty?
The command is "gpart bootcode", however I cannot be bothered to
remember the syntax; I imagine it greatly depends on if you're using
GPT
vs. MBR, in addition to what your partition layout look like. Meaning:
there is no "universal standard", it depends entirely on how you set
your stuff up. But the command is definitely "gpart bootcode".
Next, AFAIK there is no need to boot alternate media (CD etc.) to
accomplish this.
You may also need to set kern.geom.debugflags=0x10 to inhibit GEOM's
"safety measure" / to permit writing to LBA 0; see GEOM(4) and search
for the word "foot".
Assuming a freebsd-boot type partition, and GPT type partition scheme,
this is what I
use on my ZFS boot system:
$ cat bin/update_boot.sh
#!/bin/sh
for i in `seq 0 5`
do
echo Disk ${i}
gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada${i}
done
$
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
___
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-update: No Keys?
Is there a known issue with the freebsd-update servers? thebighonker.lerctr.org /home/ler $ sudo ezjail-admin setup -u Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching public key from update4.freebsd.org... failed. Fetching public key from update2.freebsd.org... failed. Fetching public key from update5.freebsd.org... failed. Fetching public key from update6.freebsd.org... failed. Fetching public key from update3.freebsd.org... failed. No mirrors remaining, giving up. Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching public key from update6.freebsd.org... failed. Fetching public key from update4.freebsd.org... failed. Fetching public key from update5.freebsd.org... failed. Fetching public key from update3.freebsd.org... failed. Fetching public key from update2.freebsd.org... failed. No mirrors remaining, giving up. thebighonker.lerctr.org /home/ler $ this is coming from my colo. Thanks! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: freebsd-update: No Keys?
On 2015-09-04 10:21, Larry Rosenman wrote: Is there a known issue with the freebsd-update servers? thebighonker.lerctr.org /home/ler $ sudo ezjail-admin setup -u Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching public key from update4.freebsd.org... failed. Fetching public key from update2.freebsd.org... failed. Fetching public key from update5.freebsd.org... failed. Fetching public key from update6.freebsd.org... failed. Fetching public key from update3.freebsd.org... failed. No mirrors remaining, giving up. Looking up update.FreeBSD.org mirrors... 5 mirrors found. Fetching public key from update6.freebsd.org... failed. Fetching public key from update4.freebsd.org... failed. Fetching public key from update5.freebsd.org... failed. Fetching public key from update3.freebsd.org... failed. Fetching public key from update2.freebsd.org... failed. No mirrors remaining, giving up. thebighonker.lerctr.org /home/ler $ this is coming from my colo. Thanks! To answer my own question for the archives: The issue is that ezjail-admin is using freebsd-update, and using the HOSTS uname -r value. In this case it was 10.2-STABLE. If I fake it out with: export UNAME_r=10.2-RELEASE it works fine. I've sent a message to the ezjail maintainer with this info. It looks like ezjail needs to fake out freebsd-update when it's dealing with it's jail(s). Thanks to Glen Barber for some insights1 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
LD Segfaulting at r343001
.suffixes.mk /etc/make.conf
/usr/src/share/mk/local.sys.mk /usr/src/share/mk/src.sys.mk
/etc/src.conf /usr/src/Makefile.inc1 /usr/src/share/mk/bsd.compiler.mk
/usr/src/share/mk/bsd.opts.mk /usr/src/share/mk/bsd.cpu.mk
/usr/src/share/mk/src.opts.mk /usr/src/share/mk/bsd.own.mk
/usr/src/share/mk/bsd.linker.mk /usr/src/Makefile.libcompat
/usr/src/share/mk/bsd.subdir.mk /usr/src/share/mk/bsd.init.mk
/usr/src/share/mk/local.init.mk /usr/src/share/mk/src.init.mk'
.PATH='. /usr/src'
*** Error code 1
Stop.
make[2]: stopped in /usr/src
.ERROR_TARGET='libraries'
.ERROR_META_FILE=''
.MAKE.LEVEL='2'
MAKEFILE=''
.MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes
verbose'
_ERROR_CMD='.PHONY'
.CURDIR='/usr/src'
.MAKE='make'
.OBJDIR='/usr/obj/usr/src/amd64.amd64'
.TARGETS='libraries'
DESTDIR='/usr/obj/usr/src/amd64.amd64/tmp'
LD_LIBRARY_PATH=''
MACHINE='amd64'
MACHINE_ARCH='amd64'
MAKEOBJDIRPREFIX=''
MAKESYSPATH='/usr/src/share/mk'
MAKE_VERSION='20180512'
PATH='/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin:/usr/obj/usr/src/amd64.amd64/tmp/legacy/bin:/usr/obj/usr/src/amd64.amd64/tmp/usr/sbin:/usr/obj/usr/src/amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin'
SRCTOP='/usr/src'
OBJTOP='/usr/obj/usr/src/amd64.amd64'
.MAKE.MAKEFILES='/usr/src/share/mk/sys.mk
/usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk
/etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk
/usr/src/share/mk/src.sys.obj.mk /usr/src/share/mk/auto.obj.mk
/usr/src/share/mk/bsd.suffixes.mk /etc/make.conf
/usr/src/share/mk/local.sys.mk /usr/src/share/mk/src.sys.mk
/etc/src.conf /usr/src/Makefile.inc1 /usr/src/share/mk/bsd.compiler.mk
/usr/src/share/mk/bsd.opts.mk /usr/src/share/mk/bsd.cpu.mk
/usr/src/share/mk/src.opts.mk /usr/src/share/mk/bsd.own.mk
/usr/src/share/mk/bsd.linker.mk /usr/src/Makefile.libcompat
/usr/src/share/mk/bsd.subdir.mk /usr/src/share/mk/bsd.init.mk
/usr/src/share/mk/local.init.mk /usr/src/share/mk/src.init.mk'
.PATH='. /usr/src'
*** Error code 1
Stop.
make[1]: stopped in /usr/src
.ERROR_TARGET='_libraries'
.ERROR_META_FILE=''
.MAKE.LEVEL='1'
MAKEFILE=''
.MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes
verbose'
_ERROR_CMD='.PHONY'
.CURDIR='/usr/src'
.MAKE='make'
.OBJDIR='/usr/obj/usr/src/amd64.amd64'
.TARGETS='buildworld'
DESTDIR=''
LD_LIBRARY_PATH=''
MACHINE='amd64'
MACHINE_ARCH='amd64'
MAKEOBJDIRPREFIX=''
MAKESYSPATH='/usr/src/share/mk'
MAKE_VERSION='20180512'
PATH='/sbin:/bin:/usr/sbin:/usr/bin'
SRCTOP='/usr/src'
OBJTOP='/usr/obj/usr/src/amd64.amd64'
.MAKE.MAKEFILES='/usr/src/share/mk/sys.mk
/usr/src/share/mk/local.sys.env.mk /usr/src/share/mk/src.sys.env.mk
/etc/src-env.conf /usr/src/share/mk/bsd.mkopt.mk
/usr/src/share/mk/src.sys.obj.mk /usr/src/share/mk/auto.obj.mk
/usr/src/share/mk/bsd.suffixes.mk /etc/make.conf
/usr/src/share/mk/local.sys.mk /usr/src/share/mk/src.sys.mk
/etc/src.conf /usr/src/Makefile.inc1 /usr/src/share/mk/bsd.compiler.mk
/usr/src/share/mk/bsd.opts.mk /usr/src/share/mk/bsd.cpu.mk
/usr/src/share/mk/src.opts.mk /usr/src/share/mk/bsd.own.mk
/usr/src/share/mk/bsd.linker.mk /usr/src/Makefile.libcompat
/usr/src/share/mk/bsd.subdir.mk /usr/src/share/mk/bsd.init.mk
/usr/src/share/mk/local.init.mk /usr/src/share/mk/src.init.mk'
.PATH='. /usr/src'
*** Error code 1
Stop.
make: stopped in /usr/src
.ERROR_TARGET='buildworld'
.ERROR_META_FILE=''
.MAKE.LEVEL='0'
MAKEFILE=''
.MAKE.MODE='normal'
_ERROR_CMD='.PHONY'
.CURDIR='/usr/src'
.MAKE='make'
.OBJDIR='/usr/obj/usr/src/amd64.amd64'
.TARGETS='buildworld buildkernel'
DESTDIR=''
LD_LIBRARY_PATH=''
MACHINE='amd64'
MACHINE_ARCH='amd64'
MAKEOBJDIRPREFIX='/usr/obj'
MAKESYSPATH='/usr/src/share/mk'
MAKE_VERSION='20180512'
PATH='/sbin:/bin:/usr/sbin:/usr/bin'
SRCTOP='/usr/src'
OBJTOP='/usr/obj/usr/src/amd64.amd64'
⌂63% [l...@thebighonker.lerctr.org:/usr/src] base ‡ ^C
[l...@thebighonker.lerctr.org:/usr/src] base 130 ‡ sudo svn up /usr/src
Updating '.':
At revision 343001.
⌂70% [l...@thebighonker.lerctr.org:/usr/src] base ‡ uname -a
FreeBSD thebighonker.lerctr.org 12.0-STABLE FreeBSD 12.0-STABLE r342972
LER-MINIMAL amd64
⌂83% [l...@thebighonker.lerctr.org:/usr/src] base ‡
⌂68% [l...@thebighonker.lerctr.org:/usr/src] base ‡ cat /etc/src.conf
WITHOUT_GDB=YES
WITH_CCACHE_BUILD=yes
CCACHE_DIR=/var/cache/ccache
⌂69% [l...@thebighonker.lerctr.org:/usr/src] base ‡ cat /etc/make.conf
DEVELOPER=yes
WITH_PKGNG=yes
DEFAULT_VERSIONS+=ssl=openssl
#__EXIM__
LOG_FILE_PATH="syslog:${LOGDIR}/%slog"
LOGDIR=/var/log/exim
#
#APACHE_DEFAULT=2.2
#DEFAULT_VERSIONS+=apache=2.2
WITH_DEBUG_PORTS=mail/dovecot2 mail/dovecot2-pigeonhole
DEFAULT_VERSIONS+=php=7.0
#DEFAULT_VERSIONS+=linux=c6:x86_64
#KERNCONF=TCP
KERNCONF=LER-MINIMAL
⌂70% [l...@thebighonker.lerctr.org:/usr/src] base ‡
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[SOLVED] LD Segfaulting at r343001
On 01/13/2019 11:55 am, Larry Rosenman wrote: Upgraded my main public facing host to 12.0-STABLE (r342972) yesterday, and got ports all straightened out. Did an svn up to r343001 (current rev for stable/12) and get the following: Ideas? Not sure why, but killing the /usr/obj (I saved the old one if someone(tm) wants to look), fixes this. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: `uname -a' can't display revision
On 08/20/2019 6:18 am, KIRIYAMA Kazuhiko wrote: On Tue, 20 Aug 2019 13:47:55 +0900, Trond Endrestøl wrote: On Tue, 20 Aug 2019 11:00+0900, KIRIYAMA Kazuhiko wrote: > I've rebuild up to r351108 but `uname -a' can't display it's > revision number. Add this to /etc/src.conf: WITHOUT_REPRODUCIBLE_BUILD=yes Add above and rebuild with r351247, then admin@tbedfs:~ % uname -a FreeBSD tbedfs 12.0-STABLE FreeBSD 12.0-STABLE #0: Tue Aug 20 19:10:53 JST 2019 root@tbedfs:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 admin@tbedfs:~ % Only revision number ommitted. Why ? is your /usr/src an SVN checkout? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Panic: Page not present: RELENG_6
I got the following:
$ kgdb -c /var/crash/vmcore.1 kernel.debug
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined
symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x803fff800058
fault code = supervisor read data, page not present
instruction pointer = 0x8:0x803abb0e
stack pointer = 0x10:0xb5ebfa40
frame pointer = 0x10:0xb5ebfa90
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 57526 (sshd)
trap number = 12
panic: page fault
cpuid = 2
KDB: stack backtrace:
panic() at panic+0x253
trap_fatal() at trap_fatal+0x2c6
trap_pfault() at trap_pfault+0x243
trap() at trap+0x298
calltrap() at calltrap+0x5
--- trap 0xc, rip = 0x803abb0e, rsp = 0xb5ebfa40, rbp =
0xb5ebfa90 ---
pmap_remove_pages() at pmap_remove_pages+0xde
vmspace_exit() at vmspace_exit+0x9a
exit1() at exit1+0x38c
sys_exit() at sys_exit+0xe
syscall() at syscall+0x437
Xfast_syscall() at Xfast_syscall+0xa8
--- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x8016a096c, rsp =
0x7fffc038, rbp = 0x53c240 ---
Uptime: 36d18h48m54s
Physical memory: 4088 MB
Dumping 587 MB: 572 556 540 524 508 492 476 460 444 428 412 396 380 364 348 332
316 300 284 268 252 236 220 204 188 172 156 140 124 108 92 76 60 44 28 12
#0 doadump () at pcpu.h:172
172 __asm __volatile("movq %%gs:0,%0" : "=r" (td));
(kgdb) bt
#0 doadump () at pcpu.h:172
#1 0x802857f0 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:409
#2 0x80285cdb in panic (fmt=0x80410cac "%s") at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0x803b2c56 in trap_fatal (frame=0xc, eva=18446742979115617248) at
/usr/src/sys/amd64/amd64/trap.c:668
#4 0x803b2fe3 in trap_pfault (frame=0xb5ebf990, usermode=0) at
/usr/src/sys/amd64/amd64/trap.c:580
#5 0x803b3298 in trap (frame=
{tf_rdi = -140737488355328, tf_rsi = -140462618836904, tf_rdx = 0, tf_rcx
= 140733193433088, tf_r8 = 34358689803, tf_r9 = 3, tf_rax = 0, tf_rbx =
-2098796528, tf_rbp = -1242826096, tf_r10 = -1096448638976, tf_r11 = 1180350,
tf_r12 = -2098796528, tf_r13 = -1094700759104, tf_r14 = -140462610448384,
tf_r15 = 140737488355328, tf_trapno = 12, tf_addr = -140462618836904, tf_flags
= -2117134080, tf_err = 0, tf_rip = -2143634674, tf_cs = 8, tf_rflags = 66050,
tf_rsp = -1242826160, tf_ss = 16}) at /usr/src/sys/amd64/amd64/trap.c:353
#6 0x8039abdb in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:168
#7 0x803abb0e in pmap_remove_pages (pmap=0xff011ec007c0, sva=0,
eva=140737488355328) at /usr/src/sys/amd64/amd64/pmap.c:383
#8 0x803860ca in vmspace_exit (td=0xff01251e0be0) at vm_map.h:251
#9 0x8026c93c in exit1 (td=0xff01251e0be0, rv=65280) at
/usr/src/sys/kern/kern_exit.c:295
#10 0x8026d35e in sys_exit (td=0x8000,
uap=0x803fff800058) at /usr/src/sys/kern/kern_exit.c:99
#11 0x803b3937 in syscall (frame=
{tf_rdi = 255, tf_rsi = 4373030, tf_rdx = 0, tf_rcx = 0, tf_r8 = 0, tf_r9
= 0, tf_rax = 1, tf_rbx = 255, tf_rbp = 5489216, tf_r10 = 0, tf_r11 = 0, tf_r12
= 16, tf_r13 = 5507248, tf_r14 = 20, tf_r15 = 5507296, tf_trapno = 12, tf_addr
= 34384731144, tf_flags = 12, tf_err = 2, tf_rip = 34383464812, tf_cs = 43,
tf_rflags = 514, tf_rsp = 140737488339000, tf_ss = 35})
at /usr/src/sys/amd64/amd64/trap.c:803
#12 0x8039ad78 in Xfast_syscall () at
/usr/src/sys/amd64/amd64/exception.S:270
#13 0x0008016a096c in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)
I do have the dump and debug kernel available.
Ideas?
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED]
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic: Page not present: RELENG_6
On Wed, 1 Aug 2007, Gavin Atkinson wrote: On Fri, 27 Jul 2007, Larry Rosenman wrote: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x803fff800058 fault code = supervisor read data, page not present instruction pointer = 0x8:0x803abb0e stack pointer = 0x10:0xb5ebfa40 frame pointer = 0x10:0xb5ebfa90 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 57526 (sshd) trap number = 12 panic: page fault cpuid = 2 KDB: stack backtrace: panic() at panic+0x253 trap_fatal() at trap_fatal+0x2c6 trap_pfault() at trap_pfault+0x243 trap() at trap+0x298 calltrap() at calltrap+0x5 --- trap 0xc, rip = 0x803abb0e, rsp = 0xb5ebfa40, rbp = 0xb5ebfa90 --- pmap_remove_pages() at pmap_remove_pages+0xde vmspace_exit() at vmspace_exit+0x9a exit1() at exit1+0x38c sys_exit() at sys_exit+0xe syscall() at syscall+0x437 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x8016a096c, rsp = 0x7fffc038, rbp = 0x53c240 --- Uptime: 36d18h48m54s How recent is the source used to build this kernel? June 18th. FreeBSD thebighonker.lerctr.org 6.2-STABLE FreeBSD 6.2-STABLE #0: Mon Jun 18 14:32:04 CDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/THEBIGHONKER amd64 Gavin -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Panic: Page not present: RELENG_6
On Fri, 24 Aug 2007, Gavin Atkinson wrote: On Wed, 2007-08-01 at 10:06 -0500, Larry Rosenman wrote: On Wed, 1 Aug 2007, Gavin Atkinson wrote: On Fri, 27 Jul 2007, Larry Rosenman wrote: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x803fff800058 fault code = supervisor read data, page not present instruction pointer = 0x8:0x803abb0e stack pointer = 0x10:0xb5ebfa40 frame pointer = 0x10:0xb5ebfa90 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 57526 (sshd) trap number = 12 panic: page fault cpuid = 2 KDB: stack backtrace: panic() at panic+0x253 trap_fatal() at trap_fatal+0x2c6 trap_pfault() at trap_pfault+0x243 trap() at trap+0x298 calltrap() at calltrap+0x5 --- trap 0xc, rip = 0x803abb0e, rsp = 0xb5ebfa40, rbp = 0xb5ebfa90 --- pmap_remove_pages() at pmap_remove_pages+0xde vmspace_exit() at vmspace_exit+0x9a exit1() at exit1+0x38c sys_exit() at sys_exit+0xe syscall() at syscall+0x437 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x8016a096c, rsp = 0x7fffc038, rbp = 0x53c240 --- Uptime: 36d18h48m54s How recent is the source used to build this kernel? June 18th. I don't think it is what I suspected it might be then. Can you recreate it with newer sources? Gavin I haven't seen it again, and the system is currently running sources from: FreeBSD thebighonker.lerctr.org 6.2-STABLE FreeBSD 6.2-STABLE #1: Sat Aug 4 14:32:38 CDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/THEBIGHONKER amd64 August 4. Thanks! LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Sudden wierd SATA problem on RELENG_7 (Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up))
I saw really strange stuff with one bad SATA cable on my 6 drive ZFS array. It would work most of the time, but the scrub would either cough up CRC's or hang. I wound up replacing the disk *AND* the cable, and it's been fine since. This is on a SuperMicro chassis with Intel chips. YMMV -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Joe Karthauser Sent: Friday, May 22, 2009 3:45 PM To: Alexander Motin Cc: freebsd-stable@freebsd.org; Kip Macy Subject: Re: Sudden wierd SATA problem on RELENG_7 (Re: ZFS hanging at kernel boot now, but didn't before... (Re: ZFS MFC heads up)) This appears to have gone away now. I unplugged the bay that was causing the trouble, and the system booted just fine on the remaining 4 drives. Then I plugged the bay back in (live) and did an atacontrol detach/attach on that bus (I wonder why I always have to do that). The drive was seen, and ZFS resilvered itself. I'm doing a ZFS scrub now to make sure that everything is good, and I'll do a reboot and see if it's all ok after that. Strange, so it looks like a cable might have got a little loose or something. I wonder why that would have hung the kernel probe though. Joe on 22/05/2009 20:40 Joe Karthauser said the following: > Hi Alexander, > > I've love it if you were able to provide some insight into this problem. > > I'm going to try switching sata cables around next to see if the problem > goes away if I disconnect some combination of bays. > > Thanks, > Joe > > on 22/05/2009 19:39 Kip Macy said the following: >> Motin is your best bet in tracking down ATA problems. >> >> Cheers, >> Kip >> >> >> On Fri, May 22, 2009 at 10:40 AM, Joe Karthauser wrote: >>> Hi Kip, >>> >>> I seriously don't understand what has happened. If I boot kernel.old >>> I still >>> get the same problem. Very confusing. :(. >>> >>> Joe >>> >>> on 21/05/2009 19:28 Kip Macy said the following: >>>> I have no idea what is happening. I think our best bet is having >>>> someone with insight into ATA provide us with help in adding >>>> diagnostics. >>>> >>>> Sorry for the trouble. Perhaps you can just roll back to 7.2 for now. >>>> >>>> Cheers, >>>> Kip >>>> >>>> >>>> On Thu, May 21, 2009 at 10:50 AM, Joe Karthauser >>>> wrote: >>>>> Hmm, I've had a bit of a miserable afternoon trying to fight my >>>>> RELENG_7 >>>>> server, which now doesn't boot. :(. >>>>> >>>>> So, it's a ZRAID2 pool with a ufs/gmirror root partition split over 5 >>>>> disks >>>>> (gmirror on 500Mb partition on each of five disks, and zraid2 over the >>>>> rest >>>>> of each drive). >>>>> >>>>> What I did was to update the userland, and then reboot. I didn't >>>>> upgrade >>>>> the >>>>> kernel (but I've subsequently done that and have the same problem). >>>>> >>>>> What happens is that the kernel hangs booting just after displaying a >>>>> LABEL >>>>> message or ZFS pool/spool message. I _can_ get it to boot if I boot >>>>> single >>>>> user with acpi switched off. When I do that I can manually start >>>>> zfs, and >>>>> mount all the partitions. However, one of the disks is missing >>>>> more >>>>> on >>>>> that next. >>>>> >>>>> The machine is running a gigabyte motherboard (domestic gamer P35 >>>>> board, >>>>> similar to this >>>>> >>>>> http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?Produ ctID=2533, >>>>> >>>>> although it might be a DS4 variant). I've got 5 of the 6 sata ports >>>>> wired >>>>> to a 5 unit SATA hot swap bay (5 drives vertially mounted into 3 >>>>> 5-1/4" >>>>> bays >>>>> kind of thing). >>>>> >>>>> Now, because of the gmirror I can boot the system on any disk, or >>>>> combination of plugged in disks. I should be able to succeed with the >>>>> kernel probe up to the attempt to mount the root
Re: I've borked my ZFS system upgrading to -STABLE
On Thu, 28 May 2009, Ruben van Staveren wrote: On 28 mei 2009, at 19:33, Niki Denev wrote: Just curious... doesn't a "zfs upgrade -a" do the same thing? The zpool upgrade is just for the pools, but the filesystems keep their original settings so we need to do that in a seperate move There is both a zpool upgrade and a zfs upgrade command. The zfs upgrade does the filesystems, and the zpool upgrade does the pool. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: Adding multiipul virtual domains?
I wouldn't wish plesk on my worst enemy. Qmail, and non-standard stuff all the way around. I have clients that use it, and I cringe when I have to debug/change something. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Daniel Anson Sent: Tuesday, June 23, 2009 2:47 PM To: Michael Grant; allnetgr...@yahoo.com Cc: sta...@freebsd.org Subject: RE: Adding multiipul virtual domains? Try running plesk. --D -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Michael Grant Sent: Tuesday, June 23, 2009 2:21 PM To: allnetgr...@yahoo.com Cc: sta...@freebsd.org Subject: Re: Adding multiipul virtual domains? On Tue, Jun 23, 2009 at 17:04, eculp wrote: > Quoting ALLnetgroup : > >> The server has 1 domain name already setup along with: >> >> sendmail >> Webmin >> Apache Web Server >> MySQL >> Apache Tomcat >> Squid Proxy >> SOCKS5 >> PERL >> Mod PERL >> PHP >> OpenSSH >> phpBB >> RoundCube WebMail >> >> When I add a new virtual host I would like the host to have it's own >> directory, website and the services above. There is nothing that I know of that will automatically "add a new virtual domain" to a machine in all of these systems. I have my own home brew perl scripts which do such things but they are not usable outside my own environment. Many other people I have talked to have done the same thing or just configured each of these individually. If you are not technically savvy enough to write your own configuration management system or to modify the configuration files individually, you might consider instead of having your own machine to use a web hosting company which automatically installs and configures this stuff for you via a control panel. Incidentally this is not the first time I have seen a need for some larger "meta" confutation system for unix/linux in general. It's absolutely true that adding a domain to a system is often a multi-step process and it need not be. Like adding a user in the old days when you first edited the passwd file, the group file, made the home directory and copied over some dot files there, now it's all automated in the adduser command. A user might have several domains, mail, one or more web sites, etc. All of this gets configured into lots of different files. Then think what happens when you get rid of a user. There really aught to be some easier way which is why I ended up writing my own scripts. Michael Grant ___ 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" Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com, and delete the original message. Your cooperation is appreciated. ___ 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: Extreme console latency during disk IO (8.0-RC1, previous releases also affected according to others)
On Tue, 13 Oct 2009, Ivan Voras wrote: Robert N. M. Watson wrote: On 13 Oct 2009, at 14:33, Ivan Voras wrote: If (1) is highly variable during I/O, it's almost certainly a property of the VM technology you're using, and there's nought to be done about it in the guest OS. Here's an example of a ping session with 0.1s resolution during a few seconds-stall in ssh: 64 bytes from 161.53.72.188: icmp_seq=1576 ttl=64 time=0.383 ms 64 bytes from 161.53.72.188: icmp_seq=1577 ttl=64 time=0.405 ms 64 bytes from 161.53.72.188: icmp_seq=1578 ttl=64 time=0.360 ms 64 bytes from 161.53.72.188: icmp_seq=2304 ttl=64 time=4.194 ms 64 bytes from 161.53.72.188: icmp_seq=2305 ttl=64 time=0.454 ms 64 bytes from 161.53.72.188: icmp_seq=2306 ttl=64 time=0.376 ms note huge packet loss. It looks like it's VM fault or something like it. It sounds like the VM is failing to execute the guest during certain types of I/O. A bit of scheduler tracing in the host OS probably wouldn't go amiss to confirm that the VM really is suspending the guest It's VMWare ESXi underneath, which is *Officially Not Linux* though some ducks may disagree - anyway, I suspect tracing the host in this way is next to impossible without some kind of diamondium-level contract. What information do you need? I have a platinum VMWare contract. What version of ESXi? LER ___ 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" -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: Extreme console latency during disk IO (8.0-RC1, previous releases also affected according to others)
On Tue, 13 Oct 2009, Ivan Voras wrote: 2009/10/13 Larry Rosenman : note huge packet loss. It looks like it's VM fault or something like it. It sounds like the VM is failing to execute the guest during certain types of I/O. A bit of scheduler tracing in the host OS probably wouldn't go amiss to confirm that the VM really is suspending the guest It's VMWare ESXi underneath, which is *Officially Not Linux* though some ducks may disagree - anyway, I suspect tracing the host in this way is next to impossible without some kind of diamondium-level contract. What information do you need? I have a platinum VMWare contract. What version of ESXi? Hi, It is ESXi 3.5 - but if the problem is really in ESXi I presume anyone could reproduce it. My setup is nothing special - Xeon 5405, 8 GB RAM, SATA drives on ICH9. As for what data is needed, it depends on what you can get - from this discussion thread it looks like it would be enough to verify that disk IO doesn't leave VM processes waiting (i.e. that disk IO doesn't interfere with CPU-bound or idle virtual machines). Though now when I think of it - doesn't Linux ATA driver poll IO in some funky way, expecting to get lower latency that way? Have you looked at the information available via the performance tab(s) in the client pointing at the ESXi server? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ 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: Skylake Loader Performance 10.3-BETA3
On 2016-03-07 16:21, Will Green wrote: On 2016-03-07 17:24, Steven Hartland wrote: On 07/03/2016 16:43, Will Green wrote: On 4 Mar 2016, at 18:49, Mark Dixon wrote: Will Green sundivenetworks.com> writes: I am happy to test patches and/or current on this server if that helps. If you want more details on the motherboard/system I have started a post on it at http://buildwithbsd.org/hw/skylake_xeon_server.html I've made the UEFI switch which worked fine, but I'm also happy to help out with testing if anyone looks at this. Are you booting from ZFS? Unless I’ve missed something this isn’t yet supported by the installer, but it is possible to get working manually. Pretty sure you missed something and those changes where merged, imp should be able to confirm. You're right: that was an error on my part. I've now got ZFS boot working with UEFI. :) I booted the Skylake motherboard with FreeBSD-10.3-RC1-amd64-uefi-memstick.img and it successfully installed to ZFS *and* loaded at normal speed. Looks like UEFI is the way to go on Skylake systems. All tests have gone well so far. Thanks I noted the same. Legacy on my Skylake laptop was slow as molasses. UEFI Rocks. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Noisy (empty) CD
Is there work going on to silence this when the cd drive is empty? May 10 09:26:46 thebighonker devd: Processing event '!system=CAM subsystem=periph type=error device=cd0 serial="" cam_status="0xcc" scsi_status=2 scsi_sense="70 02 3a 01" CDB="00 00 00 00 00 00 " ' May 10 09:27:16 thebighonker last message repeated 10 times thebighonker.lerctr.org /home/ler $ uname -aKU FreeBSD thebighonker.lerctr.org 10.3-STABLE FreeBSD 10.3-STABLE #40 r299365: Tue May 10 09:14:53 CDT 2016 r...@thebighonker.lerctr.org:/usr/obj/usr/src/sys/GENERIC amd64 1003501 1003501 thebighonker.lerctr.org /home/ler $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Noisy (empty) CD
On 2016-05-10 09:56, Alan Somers wrote: > On Tue, May 10, 2016 at 8:28 AM, Larry Rosenman wrote: > >> Is there work going on to silence this when the cd drive is empty? >> >> May 10 09:26:46 thebighonker devd: Processing event '!system=CAM >> subsystem=periph type=error device=cd0 serial="" cam_status="0xcc" >> scsi_status=2 scsi_sense="70 02 3a 01" CDB="00 00 00 00 00 00 " ' >> May 10 09:27:16 thebighonker last message repeated 10 times >> >> thebighonker.lerctr.org [1] /home/ler $ uname -aKU >> FreeBSD thebighonker.lerctr.org [1] 10.3-STABLE FreeBSD 10.3-STABLE #40 >> r299365: Tue May 10 09:14:53 CDT 2016 >> r...@thebighonker.lerctr.org:/usr/obj/usr/src/sys/GENERIC amd64 1003501 >> 1003501 >> thebighonker.lerctr.org [1] /home/ler $ > > Yes. In the long term, scottl is trying to quell messages like that. In the > short term, you can easily silence it with /etc/syslog.conf rules. In fact, > it shouldn't even there with the default syslog.conf. Have you modified > yours? Can you please share the modifications? > > -Alan # $FreeBSD: stable/10/etc/syslog.conf 260519 2014-01-10 17:56:23Z asomers $ # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field # separators. If you are sharing this file between systems, you # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. *.err;kern.warning;auth.notice;mail.crit /dev/console *.info;authpriv.none;kern.debug;lpr.info;mail.crit;news.err;cron.none;local0.none;local1.none /var/log/messages security.* /var/log/security auth.info;authpriv.info /var/log/auth.log #auth.info;authpriv.info |exec /usr/local/sbin/sshit mail.info /var/log/maillog mail.debug /var/log/debug.maillog local1.* /var/log/cisco.log lpr.info /var/log/lpd-errs ftp.info /var/log/xferlog cron.* /var/log/cron # Uncomment this if you wish to see messages produced by devd #!devd #*.>=notice /var/log/devd.log *.=debug /var/log/debug.log *.emerg * # uncomment this to log all writes to /dev/console to /var/log/console.log console.info /var/log/console.log # uncomment this to enable logging of all log messages to /var/log/all.log # touch /var/log/all.log and chmod it to mode 600 before it will work *.* /var/log/all.log # uncomment this to enable logging to a remote loghost named loghost #*.* @loghost # uncomment these if you're running inn #news.crit /var/log/news/news.crit #news.err /var/log/news/news.err #news.notice /var/log/news/news.notice local0.* /var/log/pg-prod.log #!startslip #*.* /var/log/slip.log #!ppp #*.* /var/log/ppp.log -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 Links: -- [1] http://thebighonker.lerctr.org ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Noisy (empty) CD
On 2016-05-10 10:07, Alan Somers wrote: > On Tue, May 10, 2016 at 8:59 AM, Larry Rosenman wrote: > > On 2016-05-10 09:56, Alan Somers wrote: > > On Tue, May 10, 2016 at 8:28 AM, Larry Rosenman wrote: > Is there work going on to silence this when the cd drive is empty? > > May 10 09:26:46 thebighonker devd: Processing event '!system=CAM > subsystem=periph type=error device=cd0 serial="" cam_status="0xcc" > scsi_status=2 scsi_sense="70 02 3a 01" CDB="00 00 00 00 00 00 " ' > May 10 09:27:16 thebighonker last message repeated 10 times > > thebighonker.lerctr.org [1] /home/ler $ uname -aKU > FreeBSD thebighonker.lerctr.org [1] 10.3-STABLE FreeBSD 10.3-STABLE #40 > r299365: Tue May 10 09:14:53 CDT 2016 > r...@thebighonker.lerctr.org:/usr/obj/usr/src/sys/GENERIC amd64 1003501 > 1003501 > thebighonker.lerctr.org [1] /home/ler $ > > Yes. In the long term, scottl is trying to quell messages like that. In the > short term, you can easily silence it with /etc/syslog.conf rules. In fact, > it shouldn't even there with the default syslog.conf. Have you modified > yours? Can you please share the modifications? > > -Alan # $FreeBSD: stable/10/etc/syslog.conf 260519 2014-01-10 17:56:23Z asomers $ # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field # separators. If you are sharing this file between systems, you # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. *.err;kern.warning;auth.notice;mail.crit /dev/console *.info;authpriv.none;kern.debug;lpr.info [2];mail.crit;news.err;cron.none;local0.none;local1.none /var/log/messages security.* /var/log/security auth.info [3];authpriv.info [4] /var/log/auth.log #auth.info [3];authpriv.info [4] |exec /usr/local/sbin/sshit mail.info [5] /var/log/maillog mail.debug /var/log/debug.maillog local1.* /var/log/cisco.log lpr.info [2] /var/log/lpd-errs ftp.info [6] /var/log/xferlog cron.* /var/log/cron # Uncomment this if you wish to see messages produced by devd #!devd #*.>=notice /var/log/devd.log *.=debug /var/log/debug.log *.emerg * # uncomment this to log all writes to /dev/console to /var/log/console.log console.info [7] /var/log/console.log # uncomment this to enable logging of all log messages to /var/log/all.log # touch /var/log/all.log and chmod it to mode 600 before it will work *.* /var/log/all.log # uncomment this to enable logging to a remote loghost named loghost #*.* @loghost # uncomment these if you're running inn #news.crit /var/log/news/news.crit #news.err /var/log/news/news.err #news.notice /var/log/news/news.notice local0.* /var/log/pg-prod.log #!startslip #*.* /var/log/slip.log #!ppp #*.* /var/log/ppp.log The messages you're seeing are printed by devd at loglevel info, and I see that you're directing *.info to /var/log/messages. If you change that to the default "*.notice" then you won't see the offending messages, or if you prefix the line with "!-devd" like this: !-devd *.info;authpriv.none;kern.debug;lpr.info [2];mail.crit;news.err;cron.none;local0.none;local1.none /var/log/messages In the latter case, I recommend that you enable /var/log/devd.log at level notice. -Alan Done and THANKS. thebighonker.lerctr.org /home/ler $ cat /etc/syslog.conf # $FreeBSD: stable/10/etc/syslog.conf 260519 2014-01-10 17:56:23Z asomers $ # # Spaces ARE valid field separators in this file. However, # other *nix-like systems still insist on using tabs as field # separators. If you are sharing this file between systems, you # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. *.err;kern.warning;auth.notice;mail.crit /dev/console !-devd *.info;authpriv.none;kern.debug;lpr.info;mail.crit;news.err;cron.none;local0.none;local1.none /var/log/messages security.* /var/log/security auth.info;authpriv.info /var/log/auth.log #auth.info;authpriv.info |exec /usr/local/sbin/sshit mail.info /var/log/maillog mail.debug /var/log/debug.maillog local1.* /var/log/cisco.log lpr.info /var/log/lpd-errs ftp.info /var/log/xferlog cron.* /var/log/cron # Uncomment this if you wish to see messages produced by devd !devd *.>=notice /var/log/devd.log *.=debug /var/log/debug.log *.emerg * # uncomment this to log all writes to /dev/console to /var/log/console.log console.info /var/log/console.log # uncomment this to enable logging of all log messages to /var/log/all.log # touch /var/log/all.log and chmod it to mode 600 before it will work *.* /var/log/all.log # uncomment this to enable logging to a remote loghost named loghost #*.* @loghost # uncomment these if you're running inn #news.crit /var/log/news/news.crit #news.err /var/log/news/news.err #news.notice /var/log/news/news.notice local0.* /var/log/pg-prod.log #!startslip #*.* /var/log/slip.log
Re: 11.0-BETA1 'ifconfig igb0 media auto' causes panic in llentry_free()
On 2016-07-13 15:32, Maxim Sobolev wrote: Hi, we are seeing consistent crash doing 'ifconfig igb0 media auto' after interface has been provisioned by the dhcpclient. This is stable/11 sources from svn revision 302593. That problem did not happen to us before the upgrade from from 11.0-ALPHA3, svn revision 301898 from head. Sreenshot of the backtrace is here: http://sobomax.sippysoft.com/DSC00012.JPG -Maxim see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 11.0-BETA1 'ifconfig igb0 media auto' causes panic in llentry_free()
NOTE: I get an insta-panic on boot :( I'm waiting for Gleb to respond. On 2016-07-13 15:57, Maxim Sobolev wrote: > Thanks, looks like the same issue. I'll try the patch from ticket. > > -Max > > On Wed, Jul 13, 2016 at 1:46 PM, Larry Rosenman wrote: > > On 2016-07-13 15:32, Maxim Sobolev wrote: > Hi, we are seeing consistent crash doing 'ifconfig igb0 media auto' after > interface has been provisioned by the dhcpclient. This is stable/11 sources > from svn revision 302593. > > That problem did not happen to us before the upgrade from from 11.0-ALPHA3, > svn revision 301898 from head. > > Sreenshot of the backtrace is here: > http://sobomax.sippysoft.com/DSC00012.JPG > > -Maxim see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884 > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 [1] E-Mail: l...@lerctr.org > US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 Links: -- [1] tel:%2B1%20214-642-9640 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 10.3 slow boot on Supermicro X11SSW-F
On 2016-07-14 13:36, Kurt Jaeger wrote: Hi! > I installed FreeBSD 10.3 on brand new machine Supermicro X11SSW-F. It > sits on top of 4x 1TB Samsung SSDs on ZFS RAIDZ2. > > The booting is painfully slow from BTX to menu to kernel loading. I have the same problem on a Supermicro X11SSH-LN4F. > I found this blog post solving the same problem > http://smyck.net/2016/06/15/freebsd-slow-zfs-bootloader/ I'll test that solution. Thanks for the pointer! Tested, works -- I took the 12.0-CURRENT boot files: gpart bootcode -b pmbr ada0 gpart -p gptzfsboot -i 1 ada0 cp zfsloader /boot/zfsloader Before: ca. 660 seconds to reboot, now 77 seconds to reboot. Now, if someone could explain, why... there were some buffering changes and other stuff in the boot blocks/loader. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
upgrade: can't installworld????
trying to installworld on a box I just recompiled from 10.3 to 11.0, and
am running the 11.0-STABLE kernel.
I get:
===> lib/libbsdstat (install)
install -C -o root -g wheel -m 444 libprivatebsdstat.a /usr/lib/
install -C -o root -g wheel -m 444 libprivatebsdstat_p.a /usr/lib/
install -s -o root -g wheel -m 444 libprivatebsdstat.so.1 /usr/lib/
strip: open /usr/lib//libprivatebsdstat.so.1 failed: No such file or
directory
install: strip command strip failed on /usr/lib//libprivatebsdstat.so.1
*** Error code 70
Stop.
bmake[5]: stopped in /usr/src/lib/libbsdstat
*** Error code 1
Stop.
bmake[4]: stopped in /usr/src/lib
*** Error code 1
Stop.
bmake[3]: stopped in /usr/src
*** Error code 1
Stop.
bmake[2]: stopped in /usr/src
*** Error code 1
Stop.
bmake[1]: stopped in /usr/src
*** Error code 1
Stop.
make: stopped in /usr/src
thebighonker.lerctr.org /usr/src #
This is just the first error. If I add STRIP= to /etc/make.conf, it
gets further, but other issues come up.
Ideas?
thebighonker.lerctr.org /usr/src # cat /etc/make.conf
#DEVELOPER=yes
@WITH_PKGNG=yes
#DEFAULT_VERSIONS+=ssl=openssl
#__EXIM__
LOG_FILE_PATH="syslog:${LOGDIR}/%slog"
LOGDIR=/var/log/exim
#
#APACHE_DEFAULT=2.2
#DEFAULT_VERSIONS+=apache=2.2
WITH_DEBUG_PORTS=mail/dovecot2 mail/dovecot2-pigeonhole
DEFAULT_VERSIONS+=php=7.0
#STRIP=
#INSTALL_RSYMLINK= ln -sf
thebighonker.lerctr.org /usr/src #
thebighonker.lerctr.org /usr/src # cat /etc/src.conf
WITHOUT_GDB=YES
thebighonker.lerctr.org /usr/src #
thebighonker.lerctr.org /usr/src # cat /etc/src-env.conf
WITH_META_MODE=yes
thebighonker.lerctr.org /usr/src #
thebighonker.lerctr.org /usr/src # svn info
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/stable/11
Relative URL: ^/stable/11
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 309062
Node Kind: directory
Schedule: normal
Last Changed Author: gnn
Last Changed Rev: 309057
Last Changed Date: 2016-11-23 07:14:19 -0600 (Wed, 23 Nov 2016)
thebighonker.lerctr.org /usr/src #
thebighonker.lerctr.org /usr/src # uname -a
FreeBSD thebighonker.lerctr.org 11.0-STABLE FreeBSD 11.0-STABLE #0
r309059: Wed Nov 23 11:34:39 CST 2016
r...@thebighonker.lerctr.org:/usr/obj/usr/src/sys/GENERIC amd64
thebighonker.lerctr.org /usr/src #
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: upgrade: can't installworld????
On 2016-11-23 12:27, Larry Rosenman wrote: trying to installworld on a box I just recompiled from 10.3 to 11.0, and am running the 11.0-STABLE kernel. I get: ===> lib/libbsdstat (install) install -C -o root -g wheel -m 444 libprivatebsdstat.a /usr/lib/ install -C -o root -g wheel -m 444 libprivatebsdstat_p.a /usr/lib/ install -s -o root -g wheel -m 444 libprivatebsdstat.so.1 /usr/lib/ strip: open /usr/lib//libprivatebsdstat.so.1 failed: No such file or directory install: strip command strip failed on /usr/lib//libprivatebsdstat.so.1 *** Error code 70 [snip] Something(tm) went wonky(tm) with the bootfs. I created a new bootfs, and was able to installworld to it, and boot off of it. Not sure WTF is wrong with the old one, but... -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [ZFS] files in a weird situtation
On 2016-12-18 11:16, Adam Vande More wrote: On Sun, Dec 18, 2016 at 2:30 AM, David Marec wrote: It fails on «No such file or directory». I can't even replicate this portion of things. Running it under truss might provide more insight into what is happening. This file missing, not much works. I have installed a copy into `/usr/lib` to make the system run again. So, I can't install a new world: `install -C` fails in the same way. I think you have larger issues than a single corrupt file. I had a similar weirdness back a few weeks ago. I basically rebuilt my boot filesystem with a full make installworld destdir= and killed off the old one once I had everything there. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic in nvidia module
On 3/27/17, 11:34 AM, "Jonathan Chen" wrote: On 28 March 2017 at 07:12, David Marec wrote: > greeting, > > Tracking 11-Stable, > - now : 316014, - > kernel panics on 'page fault' within nvidia module. > The system boots and works well ( 'vt' in graphic mode) until xorg starts. Everytime you sync up STABLE, you have to rebuild your nvidia-driver port, as it produces kernel modules that are tied closely the current kernel. I also had a panic when I moved up my STABLE-11/amd installation yesterday, but after a de-install and rebuild of the nvidia-driver port, I'm up and running again. Cheers. -- Jonathan Chen I fixed the issue by adding: PORTS_MODULES+=x11/nvidia-driver To my /etc/make.conf so it gets rebuilt on every kernel build. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 11.0 and tw_cli fail
On Tue, May 30, 2017 at 11:40:48PM +0100, Gary Palmer wrote: > > % file tw_cli > tw_cli: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), statically > linked, for FreeBSD 5.4, stripped > > Try COMPAT_FREEBSD5 > > Regards, > > Gary > Out of curiousity, how much code (binary) do the COMPAT_FREEBSD* bits add to the kernel/modules? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 11.1-BETA1: lsof build failure
Current lsof is 4.90M. Larry Sysutils/lsof maintainer On 6/14/17, 8:13 AM, "Peter" wrote: FYI, please check if reproducible and/or issue: Installed this from SVN & local build: 11.1-BETA1 FreeBSD 11.1-BETA1 #0 r319858:319867M ... amd64 Then tried to update lsof-4.90.f,8 and got this error: cc -pipe -DNEEDS_BOOL_TYPEDEF -DHASTASKS -DHAS_PAUSE_SBT -DHASEFFNLINK=i_effnlink -DHASF_VNODE -DHAS_FILEDESCENT -DHAS_TMPFS -DHASWCTYPE_H -DHASSBSTATE -DHAS_KVM_VNODE -DHAS_UFS1_2 -DHAS_VM_MEMATTR_T -DHAS_CDEV2PRIV -DHAS_NO_SI_UDEV -DHAS_SYS_SX_H -DHASFUSEFS -DHAS_ZFS -DHAS_V_LOCKF -DHAS_LOCKF_ENTRY -DHAS_NO_6PORT -DHAS_NO_6PPCB -DNEEDS_BOOLEAN_T -DHAS_SB_CCC -DHAS_FDESCENTTBL -DFREEBSDV=11000 -DHASFDESCFS=2 -DHASPSEUDOFS -DHASNULLFS -DHASIPv6 -DHASUTMPX -DHAS_STRFTIME -DLSOF_VSTR="11.1-BETA1" -I/usr/src/sys -O2 -c dvch.c -o dvch.o --- dnode.o --- dnode.c:906:13: error: no member named 'i_dev' in 'struct inode' if (i->i_dev ~ ^ dnode.c:916:27: error: no member named 'i_dev' in 'struct inode' dev = Dev2Udev((KA_T)i->i_dev); ~ ^ 2 errors generated. *** [dnode.o] Error code 1 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
11.1: HP DL360G5 Hang at CD during boot
I just filed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220193 since I've now seen this twice since we moved to 11.1-BETA. Please let me know what else I can provide, bearing in mind that I'm remote from the box. -- Larry Rosenman http://people.FreeBSD.org/~ler Phone: +1 214-642-9640 E-Mail: l...@freebsd.org US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: drm / drm2 removal in 12
On Mon, Aug 27, 2018 at 06:21:57AM +0800, blubee blubeeme wrote: > > You seem to miss the point where the you avoid breaking the system for any > users not on the bleeding edge. > > You technically adept guys can keep on hacking away, jumping through hoops > and building your stuff as you see fit. > Nobody will come take your steal your code away in the night. Feel free to > keep on working on it, until implementing it > doesn't break "old users" do the engineering work and improve your > implementation. > > There are so many seemingly dead code projects around this linuxkpi stuff > that you guys just pump out code and abandon > inconsistent lack of documentation, lack of testing, it's just a huge mess. > > Work on cleaning all that stuff up and bring something sensible to the > table, you cannot put onus on the core team to maintain > that mess going forward because you're not capable of doing it yourselves. If you don't like breakage, don't run HEAD/-CURRENT. If it's not out in HEAD/-CURRENT, we (the project, speaking as a ports committer) can't move forward. -- Larry Rosenman https://people.FreeBSD.org/~ler/ Phone: +1 214-642-9640 E-Mail: l...@freebsd.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 signature.asc Description: PGP signature
Crash, pagefault, not sure why/where.
35}) at /usr/src/sys/amd64/amd64/trap.c:792 #13 0x80439bd8 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:270 #14 0x00080180478c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) # Script done on Mon Oct 2 05:59:55 2006 Any ideas? I have the core/kernel that I can make available. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Crash, pagefault, not sure why/where.
I can also make a shell account available if a dev wants to nose around.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Larry Rosenman
Sent: Monday, October 02, 2006 6:03 AM
To: freebsd-stable@freebsd.org
Subject: Crash, pagefault, not sure why/where.
FreeBSD thebighonker.lerctr.org 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #72:
Sat Sep 30 18:29:33 CDT 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/THEBIGHONKER amd64
With a kernel from Saturday, I got this one shot panic:
Script started on Mon Oct 2 05:59:35 2006
# kgdb kernel.0 vmcore.0
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x80004200
fault code = supervisor read, page not present
instruction pointer = 0x8:0x80448c6b
stack pointer = 0x10:0xb5f0aa70
frame pointer = 0x10:0x840
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 82598 (exim-4.63-0)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 1d10h4m44s
Dumping 4095 MB (3 chunks)
chunk 0: 1MB (152 pages) ... ok
chunk 1: 3071MB (786032 pages) 3055 3039 3023 3007 2991 2975 2959 2943
2927 2911 2895 2879 2863 2847 2831 2815 2799 2783 2767 2751 2735 2719 2703
2687 2671 2655 2639 2623 2607 2591 2575 2559 2543 2527 2511 2495 2479 2463
2447 2431 2415 2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239 2223
2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 2047 2031 2015 1999 1983
1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743
1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503
1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263
1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023
1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719
703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415
399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111
95 79 63 47 31 15 ... ok
chunk 2: 1024MB (262144 pages) 1009 993 977 961 945 929 913 897 881 865
849 833 817 801 785 769 753 737 721 705 689 673 657 641 625 609 593 577 561
545 529 513 497 481 465 449 433 417 401 385 369 353 337 321 305 289 273 257
241 225 209 193 177 161 145 129 113 97 81 65 49 33 17 1
#0 doadump () at pcpu.h:172
172 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:172
#1 0x0004 in ?? ()
#2 0x802abcd7 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:409
#3 0x802ac371 in panic (fmt=0xff0061c2 "Xs\021\217")
at /usr/src/sys/kern/kern_shutdown.c:565
#4 0x8044e1bf in trap_fatal (frame=0xff0061c2,
eva=18446742976598209368) at /usr/src/sys/amd64/amd64/trap.c:660
#5 0x8044e4df in trap_pfault (frame=0xb5f0a9c0, usermode=0)
at /usr/src/sys/amd64/amd64/trap.c:573
#6 0x8044e80d in trap (frame=
{tf_rdi = -140737488355328, tf_rsi = -140737488338432, tf_rdx = 0,
tf_rcx = 8650752, tf_r8 = 178, tf_r9 = -1096448638976, tf_rax = 0, tf_rbx =
-2131593008, tf_rbp = 2112, tf_r10 = 1249540, tf_r11 = 132564, tf_r12 =
-1096474529440, tf_r13 = -140462610448384, tf_r14 = 140737488355328, tf_r15
= 0, tf_trapno = 12, tf_addr = -140737488338432, tf_flags = -2104448720,
tf_err = 0, tf_rip = -2142991253, tf_cs = 8, tf_rflags = 66050, tf_rsp =
-1242518912, tf_ss = 16})
at /usr/src/sys/amd64/amd64/trap.c:352
#7 0x80439a3b in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:168
#8 0x80448c6b in pmap_remove_pages (pmap=0xff00b5067160, sva=0,
eva=140737488355328) at /usr/src/sys/amd64/amd64/pmap.c:378
#9 0x80407364 in vmspace_exit (td=0xff0061c2) at
vm_map.h:251
---Type to continue, or q to quit---
#10 0x8028d59d in exit1 (td=0xff0061c2, rv=0)
at /usr/src/sys/kern/kern_exit.c:295
#11 0x8028e5ee in sys_exit (td=0x8000,
uap=0x800
RE: EV1 Servers makes me sick
Colin Percival wrote: > Eduardo Meyer wrote: >> "if your server is re-imaged with 6.0 vs the 5.4 version currently >> installed we will not be able to support this. We have found that the >> versions after 5.4 are inherantly unstable. Please let us know what >> course of action you would like to take." > > EV1Servers has never been a major supporter of FreeBSD -- back when > they were RackShack, it took a petition of several hundred people > before they started offering FreeBSD at all. > > I wonder if they'll start offering more recent FreeBSD releases next > month after FreeBSD 5.4 becomes unsupported... > I know I was able to request (from ThePlanet, which merged with EV1) a FreeBSD-6.1 system, and they didn't give me the "unsupported" line. (this was within the last month for one of my clients). LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Crash, pagefault, not sure why/where.
On Mon, 2 Oct 2006, Larry Rosenman wrote: I can also make a shell account available if a dev wants to nose around. LER Should I just send-pr this dump info and hold on to the 4G vmcore for a while? LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Random Crash/Dump/6.2-PRE (30/Sep/2006 sources)....
518944, tf_r9 = 140737488349032, tf_rax = 1, tf_rbx = 0, tf_rbp = 6291740, tf_r10 = 140737488347824, tf_r11 = 4, tf_r12 = 0, tf_r13 = 0, tf_r14 = 0, tf_r15 = 0, tf_trapno = 12, tf_addr = 6262784, tf_flags = 1, tf_err = 2, tf_rip = 34384922508, tf_cs = 43, tf_rflags = 514, tf_rsp = 140737488349160, tf_ss = 35}) at /usr/src/sys/amd64/amd64/trap.c:792 #13 0x80439bd8 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:270 #14 0x00080180478c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) # Script done on Mon Oct 2 05:59:55 2006 vmcore and sources etc available on request. I can also make a shell account and whatever else available if a dev wants to investigate. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: can't build kernel on RELENG_6
Ion-Mihai IOnut Tetcu wrote: > Hi, > > > Anyone else seeing thins ? > > > ===> ath (all) > ===> ath_hal (all) > ===> ath_rate_amrr (all) > make: don't know how to make > /usr/src/sys/modules/ath_rate_amrr/../../contrib/dev/ath/freebsd/ah_osdep.h. > Stop *** Error code 2 Are you doing a make -DNO_CLEAN? If so, do a full make buildkernel I saw this with -DNO_CLEAN, and a full buildkernel fixed it. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
LOR, 23/Nov/2006 sources, RELENG_6
This may already be fixed, known, but... Dec 3 13:14:41 thebighonker kernel: lock order reversal: Dec 3 13:14:41 thebighonker kernel: 1st 0xff0093904c00 kqueue (kqueue) @ /usr/src/sys/kern/kern_event.c:1547 Dec 3 13:14:41 thebighonker kernel: 2nd 0xff007ffb16a8 struct mount mtx (struct mount mtx) @ /usr/src/sys/ufs/ufs/ufs_vnops.c:138 Dec 3 13:14:41 thebighonker kernel: KDB: stack backtrace: Dec 3 13:14:41 thebighonker kernel: witness_checkorder() at witness_checkorder+0x4da Dec 3 13:14:41 thebighonker kernel: _mtx_lock_flags() at _mtx_lock_flags+0x5c Dec 3 13:14:41 thebighonker kernel: ufs_itimes() at ufs_itimes+0x58 Dec 3 13:14:41 thebighonker kernel: ufs_getattr() at ufs_getattr+0x1f Dec 3 13:14:41 thebighonker kernel: VOP_GETATTR_APV() at VOP_GETATTR_APV+0x74 Dec 3 13:14:41 thebighonker kernel: filt_vfsread() at filt_vfsread+0x74 Dec 3 13:14:41 thebighonker kernel: knote() at knote+0xd5 Dec 3 13:14:41 thebighonker kernel: VOP_WRITE_APV() at VOP_WRITE_APV+0x17d Dec 3 13:14:41 thebighonker kernel: vn_write() at Dec 3 13:14:41 thebighonker kernel: vn_write+0x1ec Dec 3 13:14:41 thebighonker kernel: Dec 3 13:14:41 thebighonker kernel: dofilewrite() at dofilewrite+0x87 Dec 3 13:14:41 thebighonker kernel: kern_writev() at kern_writev+0x51 Dec 3 13:14:41 thebighonker kernel: write() at write+0x4a Dec 3 13:14:41 thebighonker kernel: syscall() at syscall+0x4b2 Dec 3 13:14:41 thebighonker kernel: Xfast_syscall() at Xfast_syscall+0xa8 Dec 3 13:14:41 thebighonker kernel: --- syscall (4, FreeBSD ELF64, write), rip = 0x4363dc, rsp = 0x7fffdd08, rbp = 0x1e --- -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: LOR, 23/Nov/2006 sources, RELENG_6
On Sun, 3 Dec 2006, Kostik Belousov wrote: Please, try the patch http://people.freebsd.org/~kib/kqueue-lor.1.patch I had to manually apply the vnode_if.src portion. All the other hunks applied to a today cvsup from RELENG_6. Waiting for the compile to finish. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.2-PRE: Fatal Trap?
EMAIL PROTECTED]:0:0: class=0x06 card=0x31161106 chip=0x31161106 rev=0x00
hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT8375 ProSavageDDR PM266/KM266 CPU to PCI Bridge'
class= bridge
subclass = HOST-PCI
[EMAIL PROTECTED]:1:0: class=0x060400 card=0x0080 chip=0xb0911106 rev=0x00
hdr=0x01
vendor = 'VIA Technologies Inc'
device = 'VT8633 Apollo Pro 266 CPU to AGP Controller'
class= bridge
subclass = PCI-PCI
[EMAIL PROTECTED]:9:0: class=0x02 card=0x905510b7 chip=0x905510b7 rev=0x30
hdr=0x00
vendor = '3COM Corp, Networking Division'
device = '3C905B-TX Fast Etherlink 10/100 PCI TX NIC'
class= network
subclass = ethernet
[EMAIL PROTECTED]:10:0: class=0x02 card=0x905510b7 chip=0x905510b7 rev=0x30
hdr=0x00
vendor = '3COM Corp, Networking Division'
device = '3C905B-TX Fast Etherlink 10/100 PCI TX NIC'
class= network
subclass = ethernet
[EMAIL PROTECTED]:16:0: class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0x80
hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:16:1: class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0x80
hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:16:2: class=0x0c0300 card=0x30381106 chip=0x30381106 rev=0x80
hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT82x UHCI USB 1.1 Controller (All VIA Chipsets)'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:16:3: class=0x0c0320 card=0x50041458 chip=0x31041106 rev=0x82
hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT6202 USB 2.0 Enhanced Host Controller'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:17:0: class=0x060100 card=0x31771106 chip=0x31771106 rev=0x00
hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT8235 PCI to ISA Bridge'
class= bridge
subclass = PCI-ISA
[EMAIL PROTECTED]:17:1: class=0x01018a card=0x05711106 chip=0x05711106 rev=0x06
hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT82 EIDE Controller (All VIA Chipsets)'
class= mass storage
subclass = ATA
[EMAIL PROTECTED]:17:5: class=0x040100 card=0xa0021458 chip=0x30591106 rev=0x50
hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT8233/33A/8235/8237 AC97 Enhanced Audio Controller'
class= multimedia
subclass = audio
[EMAIL PROTECTED]:19:0: class=0x02 card=0x813910ec chip=0x813910ec rev=0x10
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter'
class= network
subclass = ethernet
[EMAIL PROTECTED]:0:0: class=0x03 card=0xd0001458 chip=0x8d045333 rev=0x00
hdr=0x00
vendor = 'S3 Graphics Co., Ltd.'
device = '86C420 ProSavage DDR'
class= display
subclass = VGA
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2-PRE: Fatal Trap?
On Sat, 30 Dec 2006, Robert Watson wrote: On Sat, 30 Dec 2006, Larry Rosenman wrote: I had to on an emergency basis replace my aging P-1 Firewall. The guys at my hosting company gave me an AthlonXP 2200+, and with 6.1 (all the way up to today's RELENG_6_1), it works fine. I tried(!) to put 6.2-PRE (RELENG_6) on it, but no matter what I do, it panics when either NTPD or SSHD starts (depending on whats first). Unfortunately, I don't have the exact panic (it's a page not present, and if I understood my remote eyes/hands right, a NULL de-reference). The box is 300+ miles away (Distance from Austin, TX to Dallas, TX). Anyone got ideas? It looks like the attached patch was missed in the MFC I just pointed at. Could you try applying it? You can also fetch it from: http://www.watson.org/~robert/freebsd/20061230-20061230-tcp_pcb_fix.diff Robert N M Watson Computer Laboratory University of Cambridge Normally, I'd be more than happy to, but, given: 1) the box is 300+ miles away 2) I do NOT have access to remote hands again till Tuesday (Holiday) 3) this is my firewall between all my services and the rest of the world and if down, I'm off the air :( I wish I could, but can't afford to be down for the 5 days :( Thanks for the diagnosis, however, as I was going nuts. Thanks, Larry Rosenman -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2-PRE: Fatal Trap?
On Sat, 30 Dec 2006, Robert Watson wrote: On Sat, 30 Dec 2006, Karol Kwiatkowski wrote: It looks like the attached patch was missed in the MFC I just pointed at. Could you try applying it? You can also fetch it from: http://www.watson.org/~robert/freebsd/20061230-20061230-tcp_pcb_fix.diff Normally, I'd be more than happy to, but, given: 1) the box is 300+ miles away 2) I do NOT have access to remote hands again till Tuesday (Holiday) 3) this is my firewall between all my services and the rest of the world and if down, I'm off the air :( I wish I could, but can't afford to be down for the 5 days :( Thanks for the diagnosis, however, as I was going nuts. I've gone ahead and MFC'd the missing tcp_subr.c patch and the change now appears stable on by 6-STABLE test box. I'd appreciate it if other people experiencing the panic could slide forward to confirm (or perhaps less ideally, not confirm) that this fixes the problem for them also. [snip] I can confirm (now that I saw other confirmations), that the fix is the correct one (I'm up on: FreeBSD fw.lerctr.org 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Sat Dec 30 17:14:04 CST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Thanks Robert and all for the very quick work with a really sparse bug report. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Panic/RELENG_6...
# kgdb -c vmcore.1 /usr/obj/usr/src/sys/THEBIGHONKER/kernel.debug
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Unde
fined symbol
"ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
Slab at 0x81fc7d88, freei 43 = 0.
panic: Duplicate free of item 0x81fc7810 from zone
0xff00bff6d340(PV
ENTRY)
cpuid = 1
KDB: stack backtrace:
panic() at panic+0x253
uma_dbg_free() at uma_dbg_free+0x188
uma_zfree_arg() at uma_zfree_arg+0x60
pmap_remove_pages() at pmap_remove_pages+0x1d1
vmspace_exit() at vmspace_exit+0x9a
exit1() at exit1+0x38f
sys_exit() at sys_exit+0xe
syscall() at syscall+0x4d1
Xfast_syscall() at Xfast_syscall+0xa8
--- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x80146777c, rsp =
0x7fffe52 8, rbp =
0x572000 ---
Uptime: 10d17h24m40s
Physical memory: 4087 MB
Dumping 598 MB: 583 567 551 535 519 503 487 471 455 439 423 407 391 375 359 343
327 311 295 279 263
247 231 215 199 183 167 151 135 119 103 87 71 55 39 23 7
#0 doadump () at pcpu.h:172
172 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:172
#1 0x80296699 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:409
#2 0x8029612b in panic (
fmt=0x804c47a8 "Duplicate free of item %p from zone %p(%s)\n")
at /usr/src/sys/kern/kern_shutdown.c:565
#3 0x803d8c58 in uma_dbg_free (zone=0xff00bff6d340,
slab=0x81fc7d88, item=0x81fc7810)
at /usr/src/sys/vm/uma_dbg.c:302
#4 0x803d6950 in uma_zfree_arg (zone=0xff00bff6d340,
item=0x81fc7810, udata=0x0) at /usr/src/sys/vm/uma_core.c:2276
#5 0x80423e31 in pmap_remove_pages (pmap=0xff00a576fe20, sva=0,
eva=140737488355328) at /usr/src/sys/amd64/amd64/pmap.c:2597
#6 0x803e0fba in vmspace_exit (td=0xff00ac8954c0) at vm_map.h:251
#7 0x8027bf3f in exit1 (td=0xff00ac8954c0, rv=0)
at /usr/src/sys/kern/kern_exit.c:295
#8 0x8027cace in sys_exit (td=0x0, uap=0x0)
at /usr/src/sys/kern/kern_exit.c:99
#9 0x80429dd1 in syscall (frame=
{tf_rdi = 0, tf_rsi = 0, tf_rdx = 34381131040, tf_rcx = 8, tf_r8 = 0, tf_r
9 = 0, tf_rax = 1, tf_rbx = 0, tf_rbp =
5709824, tf_r10 = 0, tf_r11 = 0, tf_r12
= 5677056, tf_r13 = 15, tf_r14 = 35, tf_r15 = 140737488348784, tf_trapno = 12, t
f_addr = 34382333184, tf_flags =
102739200, tf_err = 2, tf_rip = 34381133692, tf
---Type to continue, or q to quit---
_cs = 43, tf_rflags = 514, tf_rsp = 140737488348456, tf_ss = 35})
at /usr/src/sys/amd64/amd64/trap.c:792
#10 0x80414d68 in Xfast_syscall ()
at /usr/src/sys/amd64/amd64/exception.S:270
#11 0x00080146777c in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)
What can I do to help?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DRM disabled?
On Sun, 14 Jan 2007, Larry Rosenman wrote: Greetings, I finally have FreeBSD back on my HP ZE5700US Laptop. I was wondering if anyone knew why the DRM is being disabled. I have the agp device static in the kernel, and have attached a dmesg, as well as the X log, and also the full kernel config. kern/100958 has a patch that fixes this. I've sent a tickler to GNATS asking for an MFC. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: DRM disabled?
On Mon, 15 Jan 2007, Stanislav Sedov wrote: On Sun, 14 Jan 2007 11:56:43 -0600 (CST) Larry Rosenman mentioned: Greetings, I finally have FreeBSD back on my HP ZE5700US Laptop. I was wondering if anyone knew why the DRM is being disabled. I have the agp device static in the kernel, and have attached a dmesg, as well as the X log, and also the full kernel config. Ideas? For dri to work you should install recent Xorg (7.1 - 7.2) as drm on your card will not work with 6.9. You can find instructions how to obtain Xorg 7.2 featured ports tree on http://wiki.freebsd.org/. However, you might want to wait until Xorg modular will be committed into the tree. Hopefully, that will be done soon. Actually, PR kern/100958 fixes the agpgart issue, and then the DRI stuff attaches and seems(!) to work. Can we get that PR commited? -- Stanislav Sedov ST4096-RIPE -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
MFC Request: kern/100958?
Greetings, Can we get kern/100958 MFC'd? It's been in -CURRENT since September, and fixes a problem for me with my laptop getting the AGPGART device attached. Thanks! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Clamav-90_2 Lockup with freebsd 6.2
I've seen it go loop as well on my Dual-Xeon. I did just switch it to libthr, but still had one occurace. I did switch maxthreads to 1. If I can test, please let me know. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Blapp Sent: Tuesday, February 27, 2007 11:37 AM To: Sergey N. Voronkov Cc: freebsd-stable@freebsd.org Subject: Re: Clamav-90_2 Lockup with freebsd 6.2 Hi, >> Change the threading lib. It fixed it for us. >> >> % cat /etc/libmap.conf >> [clamd] >> libc_r.so.5 libthr.so.2 >> libc_r.so.6 libthr.so.2 >> libthr.so.2 libthr.so.2 >> libpthread.so.1 libthr.so.2 >> libpthread.so.2 libthr.so.2 Even with libthr the CPU usage is still far too high ... I'm currently looking at the code. Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Clamav-90_2 Lockup with freebsd 6.2
On Sat, 10 Mar 2007, Mike Jakubik wrote: Martin Blapp wrote: Clamd with libpthread.so is still broken. Please use libthr.so. I'm currently investigating why libpthreads.so has problems with clamd, and it looks to me like a library bug. This may be related to a problem i had with Mysql on a large server recently. Mysql threads would start eating a lot of CPU and staying around forever. I switched to libthr and the problem went away. Sorry, i don't have any more info than this, because it is a production server i cant mess around with it any more. I've seen the high-cpu stuff with ClamAV_0.90_3, even with libthr. Anyone got a fix? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Crash
FahCore_78.exe)
179calcru: runtime went backwards from 107492416053 usec to 107491646622
usec f
or pid 60113 (FahCore_78.exe)
163calcru: runtime went backwards from 107492416053 usec to 107491857664
usec f
or pid 60113 (FahCore_78.exe)
calcru: runtime went backwards from 107492416053 usec to 107492068758 usec
for p
id 60113 (FahCore_78.exe)
147calcru: runtime went backwards from 107492416053 usec to 107492279065
usec f
or pid 60113 (FahCore_78.exe)
131calcru: runtime went backwards from 107492416053 usec to 107491490234
usec f
or pid 60113 (FahCore_78.exe)
115calcru: runtime went backwards from 107492416053 usec to 107491701727
usec f
or pid 60113 (FahCore_78.exe)
99calcru: runtime went backwards from 107492416053 usec to 107491912670
usec fo
r pid 60113 (FahCore_78.exe)
calcru: runtime went backwards from 107492416053 usec to 107492123832 usec
for p
id 60113 (FahCore_78.exe)
83calcru: runtime went backwards from 107492416053 usec to 107492335365
usec fo
r pid 60113 (FahCore_78.exe)
67calcru: runtime went backwards from 107492416053 usec to 107491546145
usec fo
r pid 60113 (FahCore_78.exe)
51calcru: runtime went backwards from 107492416053 usec to 107491757253
usec fo
r pid 60113 (FahCore_78.exe)
calcru: runtime went backwards from 107492416053 usec to 107491968870 usec
for p
id 60113 (FahCore_78.exe)
35calcru: runtime went backwards from 107492416053 usec to 107491492783
usec fo
r pid 60113 (FahCore_78.exe)
19calcru: runtime went backwards from 107492416053 usec to 107491703760
usec fo
r pid 60113 (FahCore_78.exe)
3
#0 doadump () at pcpu.h:172
172 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:172
#1 0x802853b0 in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:409
#2 0x8028589b in panic (fmt=0x8040d54c "%s")
at /usr/src/sys/kern/kern_shutdown.c:565
#3 0x803b1916 in trap_fatal (frame=0xc, eva=18446742977252509472)
at /usr/src/sys/amd64/amd64/trap.c:668
#4 0x803b1e68 in trap (frame=
{tf_rdi = -1096384115336, tf_rsi = -2141391232, tf_rdx = 65, tf_rcx =
0, tf_r8 = -1096384411016, tf_r9 = 65, tf_rax = 3, tf_rbx = -1096384115336,
tf_rbp = -1246062192, tf_r10 = 64, tf_r11 = -140737488355328, tf_r12 = 0,
tf_r13 = 2, tf_r14 = 352, tf_r15 = 2, tf_trapno = 12, tf_addr = -44,
tf_flags = 2, tf_err = 0, tf_rip = -2143762426, tf_cs = 8, tf_rflags =
65542, tf_rsp = -1246062240, tf_ss = 16}) at
/usr/src/sys/amd64/amd64/trap.c:239
#5 0x8039a06b in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:168
#6 0x8038c806 in vm_page_alloc (object=0x0, pindex=2, req=352)
at /usr/src/sys/vm/vm_page.c:935
#7 0x803a8471 in _pmap_allocpte (pmap=0xff013f66a7c0,
ptepindex=2, flags=1) at /usr/src/sys/amd64/amd64/pmap.c:1126
#8 0x803a8835 in pmap_allocpte (pmap=0xff013f66a7c0,
va=4194304,
flags=1) at /usr/src/sys/amd64/amd64/pmap.c:1313
#9 0x803aa7d6 in pmap_copy (dst_pmap=0xff013f66a7c0,
---Type to continue, or q to quit---
src_pmap=0xff007fe909e0, dst_addr=65, len=0, src_addr=4194304)
at /usr/src/sys/amd64/amd64/pmap.c:2409
#10 0x80385d3d in vmspace_fork (vm1=0xff00ba6a0d78)
at /usr/src/sys/vm/vm_map.c:2499
#11 0x80381281 in vm_forkproc (td=0xff00b6114720,
p2=0xff00a9028358, td2=0xff010cebc720, flags=20)
at /usr/src/sys/vm/vm_glue.c:540
#12 0x8026e4e5 in fork1 (td=0xff00b6114720, flags=20, pages=0,
procp=0xb5ba9b70) at /usr/src/sys/kern/kern_fork.c:672
#13 0x8026ebcc in fork (td=0xff00b6114720,
uap=0x805cf680)
at /usr/src/sys/kern/kern_fork.c:98
#14 0x803b25f7 in syscall (frame=
{tf_rdi = 3, tf_rsi = 140737488349072, tf_rdx = 140737488349056,
tf_rcx = 34382993660, tf_r8 = -2143111624, tf_r9 = 140737488349048, tf_rax =
2, tf_rbx = 1, tf_rbp = 3, tf_r10 = 140737488348272, tf_r11 = 2, tf_r12 =
6217728, tf_r13 = 0, tf_r14 = 0, tf_r15 = 0, tf_trapno = 12, tf_addr =
34386217776, tf_flags = 49, tf_err = 2, tf_rip = 34384509644, tf_cs = 43,
tf_rflags = 514, tf_rsp = 140737488349048, tf_ss = 35}) at
/usr/src/sys/amd64/amd64/trap.c:803
#15 0x8039a208 in Xfast_syscall ()
at /usr/src/sys/amd64/amd64/exception.S:270
#16 0x00080179facc in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)
Any ideas? April 10 6.2/amd64 sources.
LER
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683E-Mail: [EMAIL PROTECTED]
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: New ports on older stable (4.11)
I have Exim/ClamAV and SpamAssassin from Ports on a 4.11 system. Works fine :) LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Hyperthreading in 6.x ... still frowned upon?
Spartak Radchenko wrote: > On Wed, May 03, 2006 at 11:42:18AM -0300, Marc G. Fournier wrote: >> >> In 4.x, it was a 'shut it off' sort of deal .. my new amd64 don't >> appear to have it enabled, but my older i386 server that I just >> upgraded to 6.x does: > > I am not sure I understood your problem correctly... Do you want > to enable hyperthreading on amd64? But they have no such thing. > Intel only. you do know that EM64T Xeons *DO* have hyperthreading, and (can) run an amd64 kernel? $ sysctl hw hw.machine: amd64 hw.model: Intel(R) Xeon(TM) CPU 3.00GHz hw.ncpu: 4 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bad pte panic, no dump :(
Greetings, FreeBSD/amd64 6.1-STABLE (June 18, 18:44 US/Central), running on Intel EM64T Xeons. got a one-off bad pte panic, and when it tried to dump to a gmirror slice, it hung. Box had been rock stable. Had an issue with a neighbor (NFS server to this box) box yesterday, and had to force reboot it to get the NFS stuff back in sync, and all I thought(!) was ok. The out of the blue, while talking IMAP to this one, got the bad pte panic. when the box came back up, it had a massive amount of fsck to do, and then resync the mirror. While the mirror was re-syncing, there were times when I saw LOTS of processes blocked in ufs or getblk or related wait_chans. I'm not sure there is anything more I can provide (no serial console, and the box is in a colo cage 3.5 hours (by car) north of me. Just an FYI, and suggestions welcome. Thanks for listening to my rant. Larry Rosenman -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: AMD-64
Jack Stone wrote: > Folks, please bear with this one. > > I have 2 new AMD-64 servers on an Abit AN8 MB: > CPU: AMD Athlon(tm) 64 Processor 3800+ > ACPI APIC Table: > nVidia nForce4 > > I must have been asleep because now just discovered the amd64 > platform. > > If I install the new FBSD-6.0-amd64 release, I get the amd64 install. > However, I know the time will come to update/upgrade. I haven't > figured out how to make the system stop using the old: /sys/i386/conf > rather than: > /sys/amd64/conf > > If I try to upgrade the "i386" to the amd64, I keep getting the > "i386" build and the kernel build fails. What machine is in the kernel config? Also, the cputype is HAMMER It needs to be amd64. > > I'm wondering if the tweaking needed can be fixed in my make.conf? > > Here's the pertinent lines in my file: > CPUTYPE=athlon64 > CFLAGS= -O -pipe > COPTFLAGS= -O -pipe > NO_LIB32=true > > Any tips on the proper approach to solve this problem will be > appreciated. > > Thanks, > Jack > > _ > Don't just search. Find. Check out the new MSN Search! > http://search.msn.click-url.com/go/onm00200636ave/direct/01/ > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3683 US ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: AMD-64
Do you have an amd64 buildworld in /usr/obj ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: AMD-64
I suspect that is the problem. Try killing it and it should be better. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: AMD-64
On Sun, 15 Jan 2006, Jack Stone wrote: The uname -a (before new amd64 kernel) says: [EMAIL PROTECTED]>> uname -a FreeBSD sagegate.net 6.0-RELEASE-p1 FreeBSD 6.0-RELEASE-p1 #0: Sat Dec 24 12:50:35 CST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SINGLEKERNEL i386 Now, just did a new cvsup after deleting /usr/obj and a new buildworld I am stopped immediately when starting the buildkernel: Ok, are you trying to configure an AMD64 world running on an i386 kernel? If so, I think you need to say: make buildworld MACHINE=amd64 or some other magic. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Gmirror'd SWAP: no dump?
Are there any plans to support dumping to a gmirror'd swapfile? My FreeBSD/amd64 6.0-STABLE as of today doesn't seem to want to do it. Thanks, LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Gmirror'd SWAP: no dump?
Igor Robul wrote: > On Wed, Jan 18, 2006 at 12:44:27PM -0600, Larry Rosenman wrote: >> Are there any plans to support dumping to a gmirror'd swapfile? > Dumping occurs when kernel is in "bad condition", so GEOM can not be > safe used (for example panic in GEOM code). > > Check archives for last month of 2005 for longer explanation. I was afraid of that. What's the recommendation for how to Set up a 2-disk system with mirroring then? All the HOWTO's I've seen have the entire disk mirrored, including all the pieces. My current setup is 3 BSD partitions in 1 FDISK slice. With the entire disk (da0/da1) mirrored. How can I set it up to allow dumps? (I wouldn't mind having double the swap :) ) LER >> >> My FreeBSD/amd64 6.0-STABLE as of today doesn't seem to want to do >> it. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3683 US ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Gmirror'd SWAP: no dump?
Christoph Schug wrote: > On Thu, Jan 19, 2006, Larry Rosenman wrote: > >> All the HOWTO's I've seen have the entire disk mirrored, including >> all the pieces. > > See [1] how to setup a GEOM on a slice basis. You only have to skip > swap and mind the correct /etc/fstab entry. From my experience, it is > best to hardcode all providers using '-h' at all gmirror insert > operations for a slice based setup. > > [1] http://people.freebsd.org/~rse/mirror/ > > Hope this helps > -cs Would the lack of -h cause gmirror to hang at startup? I'd see the Gmirror code come up, and then the machine would hang. In this kind of setup, I still saw the 'b' partition mirrored. (since I basically Only have da0s1/da1s1). -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3683 US ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Gmirror'd SWAP: no dump?
Gavin Atkinson wrote: > On Thu, 2006-01-19 at 05:49 -0600, Larry Rosenman wrote: >> Igor Robul wrote: >>> On Wed, Jan 18, 2006 at 12:44:27PM -0600, Larry Rosenman wrote: >>>> Are there any plans to support dumping to a gmirror'd swapfile? >>> Dumping occurs when kernel is in "bad condition", so GEOM can not be >>> safe used (for example panic in GEOM code). >>> >>> Check archives for last month of 2005 for longer explanation. >> >> I was afraid of that. What's the recommendation for how to Set up a >> 2-disk system with mirroring then? >> >> All the HOWTO's I've seen have the entire disk mirrored, including >> all the pieces. >> >> My current setup is 3 BSD partitions in 1 FDISK slice. With the >> entire disk (da0/da1) mirrored. >> >> How can I set it up to allow dumps? > > If you look at the mirror status, you'll see each disk is assigned a > priority. > > In theory, "The component with the biggest priority is used [...] as > a master component when resynchronization is needed, e.g. after a > power failure when the device was open for writing." (gmirror(8)). > Therefore, if you set dumps to /dev/da0s1b (or whichever swap > partition is on the disk with the biggest priority), the machine can > dump to the disk directly, and will end up resyncing to the other > disk on reboot (which it would have had to do anyway due to the > panic), and your dump will be doubly safe. The problem with this idea is the fact that the da0s1b device is NOT available: $ ls -l /dev/da?s1? ls: /dev/da?s1?: No such file or directory $ -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3683 US ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Gmirror'd SWAP: no dump?
Craig Boston wrote: > On Thu, Jan 19, 2006 at 02:53:42PM +, Thomas Hurst wrote: >>> IIRC I had the problem that 'gmirror insert' without '-h' not always >>> inserted the slice specified by the entire block device (e.g. >>> /dev/ad4s1 vs. /dev/ad4). Apparently there is some auto detection >>> code and/or gmirror cannot differ correctly, but that's just a >>> guess. Specifing '-h' fixed it in my case. >> >> As I understand it, gmirror writes its metadata on the last sector of >> the provider; when tasting devices it will look at the last sector of >> ad4, find the metadata and use that as the provider for your mirror; >> you can either hardcode the provider name there to override it, or >> make the slice 1 sector smaller so gmirror tastes ad4, finds >> nothing, then goes on to taste ad4s1 correctly. > > This was fixed for most cases by adding the size of the provider to > the metadata. ad4 should be a different size than ad4s1 as the > partition table has to go somewhere... > > Looks like it was fixed in HEAD in Feb 2005, and MFC'd to 5.x in > March. Shouldn't have ever been a problem for 6.x release. > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/geom/mirror/g_mirror.c#rev1.19 .2.8 > Hrm. With using the method for slices as specified on the ~rse page, I got repeatable lockups. With specifying the entire disk, it works as normal, but no dump device. Suggestions on how to enable dump, **AND** reliable boot would be appreciated. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
GEOM Mirror: Swap/Dump
Is there any recommended solution to getting dumps when you have the entire disk mirrored with gmirror? I've tried the slice based mirroring, but it seems to be unreliable on booting (at least for me with ahd(4) connected disks on FreeBSD 6.0-STABLE amd64. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: GEOM Mirror: Swap/Dump
Kris Kennaway wrote: > On Thu, Jan 26, 2006 at 04:37:00PM -0600, Larry Rosenman wrote: >> Is there any recommended solution to getting dumps when you have the >> entire disk mirrored with gmirror? > > Wasn't this asked+answered about 2 days ago? > > Kris I didn't see the answer, other than the slice-based stuff, which as I state above, didn't work for me. LER -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named weirdness...
> to 5 minutes.
>
> Mark
> >
> > LER
> >
> > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [001103 06:20]:
> > >
> > > Because a NOTIFY is supposed to be sent whenever a master,
> > > not just the primary master, loads a new copy of a zone.
> > > This allows "master -> slave -> slave" to work out of the box.
> > >
> > > Mark
> > >
> > > > Why is OUR named sending notify's for a SECONDARY zone?
> > > >
> > > > lerbsd# tail /var/log/messages
> > > > Nov 3 03:35:50 lerbsd named[9613]: listening on [127.0.0.1].53 (lo0)
> > > > Nov 3 03:35:50 lerbsd named[9613]: Forwarding source address is
> > > > [0.0.0.0].1745
> > > > Nov 3 03:35:50 lerbsd named[9614]: Ready to answer queries.
> > > > Nov 3 03:36:01 lerbsd named[9614]: Sent NOTIFY for "lerctr.org IN SOA
> > > > 2000110100" (lerctr.org); 1 NS, 1 A
> > > > Nov 3 03:36:01 lerbsd named[9614]: suppressing duplicate notify
> > > > ("lerctr.org" IN SOA)
> > > > Nov 3 03:36:01 lerbsd last message repeated 3 times
> > > > Nov 3 03:36:28 lerbsd named[9614]: Sent NOTIFY for "lerctr.org IN SOA
> > > > 2000110100" (lerctr.org); 6 NS, 6 A
> > > > Nov 3 03:37:04 lerbsd named-xfer[9627]: send AXFR query 0 to
> > > > 207.158.72.11
> > > > Nov 3 03:37:04 lerbsd named[9614]: slave zone "lerctr.org" (IN)
> > > > loaded (serial 2000110300)
> > > > Nov 3 03:37:29 lerbsd named[9614]: Sent NOTIFY for "lerctr.org IN SOA
> > > > 2000110300" (lerctr.org); 6 NS, 6 A
> > > > lerbsd#
> > > >
> > > >
> > > > --
> > > > Larry Rosenman http://www.lerctr.org/~ler
> > > > Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED]
> > > > US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
> > > >
> > > >
> > > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > > with "unsubscribe freebsd-stable" in the body of the message
> > > --
> > > Mark Andrews, Nominum Inc.
> > > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > > PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
> > >
> > >
> > > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > > with "unsubscribe freebsd-stable" in the body of the message
> > --
> > Larry Rosenman http://www.lerctr.org/~ler
> > Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED]
> > US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-stable" in the body of the message
> --
> Mark Andrews, Nominum Inc.
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED]
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: [EMAIL PROTECTED]
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: named weirdness...
No, there is another A record for ns-a. * Bap <[EMAIL PROTECTED]> [001103 10:57]: > Shouln't you have > IN NS lerami.lerctr.org. > if it is SOA? > > Bap. > > > Looks like it just took 20+minutes, and not on the notify: > > Nov 3 09:31:52 lerami named[828]: master zone "lerctr.org" (IN) > > loaded (serial > > 2000110302) > > Nov 3 09:32:00 lerami named[828]: Sent NOTIFY for "lerctr.org IN SOA" > > (lerctr.o > > rg); 6 NS, 6 A > > Nov 3 09:32:00 lerami named[828]: Received NOTIFY answer from > > 207.158.64.11 for > > "lerctr.org IN SOA" > > Nov 3 09:32:00 lerami named[828]: Received NOTIFY answer from > > 207.158.64.10 for > > "lerctr.org IN SOA" > > Nov 3 09:32:00 lerami named[828]: Received NOTIFY answer from > > 206.138.224.150 f > > or "lerctr.org IN SOA" > > Nov 3 09:32:00 lerami named[828]: Received NOTIFY answer from > > 206.66.10.46 for > > "lerctr.org IN SOA" > > Nov 3 09:32:01 lerami named[828]: approved AXFR from > > [207.158.64.11].57862 for > > "lerctr.org" > > Nov 3 09:32:01 lerami named[828]: zone transfer (AXFR) of > > "lerctr.org" (IN) to > > [207.158.64.11].57862 > > Nov 3 09:32:01 lerami named[828]: approved AXFR from > > [207.158.64.10].44387 for > > "lerctr.org" > > Nov 3 09:32:01 lerami named[828]: zone transfer (AXFR) of > > "lerctr.org" (IN) to > > [207.158.64.10].44387 > > Nov 3 09:32:01 lerami named[828]: approved AXFR from > > [206.66.10.46].4003 for "l > > erctr.org" > > Nov 3 09:32:01 lerami named[828]: zone transfer (AXFR) of > > "lerctr.org" (IN) to > > [206.66.10.46].4003 > > Nov 3 09:32:01 lerami named[828]: approved AXFR from > > [206.138.224.150].2706 for > > "lerctr.org" > > Nov 3 09:32:01 lerami named[828]: zone transfer (AXFR) of > > "lerctr.org" (IN) to > > [206.138.224.150].2706 > > Nov 3 09:33:54 lerami named[828]: approved AXFR from > > [192.67.63.1].2182 for "le > > rctr.org" > > Nov 3 09:33:54 lerami named[828]: zone transfer (AXFR) of > > "lerctr.org" (IN) to > > [192.67.63.1].2182 > > Nov 3 09:51:42 lerami named[828]: approved AXFR from > > [207.158.72.45].1038 for " > > lerctr.org" > > Nov 3 09:51:42 lerami named[828]: zone transfer (AXFR) of > > "lerctr.org" (IN) to > > [207.158.72.45].1038 > > Nov 3 09:52:00 lerami named[828]: rcvd NOTIFY(lerctr.org, IN, SOA) > > from [207.15 > > 8.72.45].1745 > > Nov 3 09:52:00 lerami named[828]: NOTIFY(SOA) for non-secondary name > > (lerctr.or > > g), from [207.158.72.45].1745 > > Nov 3 10:06:08 lerami named[828]: unapproved AXFR from > > [208.184.13.196].1077 fo > > r "lerctr.org" (acl) > > Nov 3 10:06:20 lerami named[828]: unapproved AXFR from > > [208.184.13.196].1078 fo > > r "lerctr.org" (acl) > > Nov 3 10:08:16 lerami named[828]: approved AXFR from > > [207.136.8.252].4060 for " > > lerctr.org" > > Nov 3 10:08:16 lerami named[828]: zone transfer (AXFR) of > > "lerctr.org" (IN) to > > [207.136.8.252].4060 > > $ > > * Larry Rosenman <[EMAIL PROTECTED]> [001103 09:48]: > > > * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [001103 08:17]: > > > > > > > > > ok, but it didn't seem to hear the notify from 207.158.72.11 (same > > > > > net) and load it. (8.2.2-P5 on UnixWare 7). All the others > > > > > (all 4 other 2ndary's). > > > > > > > > All the log shows is named starting/reloading. > > > Ok, I upped the soa serial: > > > Nov 3 09:31:52 lerami named[828]: master zone "lerctr.org" (IN) > > > loaded (serial > > > 2000110302) > > > Nov 3 09:32:00 lerami named[828]: Sent NOTIFY for "lerctr.org IN SOA" > > > (lerctr.o > > > rg); 6 NS, 6 A > > > Nov 3 09:32:00 lerami named[828]: Received NOTIFY answer from > > > 207.158.64.11 for > > > "lerctr.org IN SOA" > > > Nov 3 09:32:00 lerami named[828]: Received NOTIFY answer from > > > 207.158.64.10 for > > > "lerctr.org IN SOA" > > > Nov 3 09:32:00 lerami named[828]: Received NOTIFY answer from > > > 206.138.224.150 f > > > or "lerctr.org IN SOA" > > > Nov 3 09:32:00 lerami named[828]: Received NOTIFY answer from > >
