Re: Deprecating base system ftpd?
Am 06.04.2021 um 12:08 schrieb Helge Oldach : > > Stefan Bethke wrote on Tue, 06 Apr 2021 11:29:34 +0200 (CEST): >> Strato did disable FTP access over a year ago, > > Actually it was effective October 20, 2020. You are correct; I was remembering the announcement, not the switch off. > and instructed customers on how to use SSH-based access instead, > > They have a completely different incentive (avoiding cleartext passwords > over the Internet, and reportedly they had a number of cases where > customers where affected by password snooping) than a local admin person > on a local network not exposed to the public. > >> so it's definitely possible, and people are moving towards more secure >> protocols, even when (non-technical) end users are affected. > > No doubt about that. Any information about the ticket volume triggered > by this deprecation? I have no insight into Strato's operations, but from having to support a bunch of non-technical people who are customers, I'd say it was relatively painless, because Strato provided good instructions, and the (non-techincal) customers were using GUI clients already anyway where they only needed to switch from FTP to SFTP. Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: Deprecating base system ftpd?
Am 05.04.2021 um 21:01 schrieb Patrick M. Hausen : > > But still even on "the Internet", FTP is the most used method for customers > of static website hosting. You cannot teach these people what an SSH key is. > Just my experience, but backed by a load of customer interactions over more > than 20 years ... Strato did disable FTP access over a year ago, and instructed customers on how to use SSH-based access instead, so it's definitely possible, and people are moving towards more secure protocols, even when (non-technical) end users are affected. Srefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Updating to 13-stable and existing ZFS pools: any gotchas?
I'm planning to upgrade three production machines with existing ZFS pools to 13-stable. Is there anything I need to pay attention to wrt OpenZFS? Or should it be fully transparent, apart from updating loader? My (limited) testing with VMs went without a hitch, but I want to make sure I don't paint myself into a corner. Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: APU3 ethernet can't transmit
Argh! It was my el cheapo desktop switch. I tried two ports and two cables, they were working with my laptop, but not with the APU. Only when I hooked up a different device this evening and couldn't talk to it did I think of the switch. Powercycling "fixed" it. Time for an upgrade, I think. Stefan > Am 23.01.2021 um 12:50 schrieb Stefan Bethke : > > > I've tried one more time with this in rc.conf: > > network_interfaces="igb0" > ifconfig_igb0="-lro -vlanhwtso -tso4 -vlanhwfilter -rxcsum -txcsum -vlanhwtag > -vlanmtu -vlanhwcsum -tso6 -txcsum6" > > Whick produces this: options=802020 > > No joy. What's interesting is that the left LED on the plug in blinking with > about 2Hz, so clearly the PHY or controller is unhappy about something. The > i210 datasheet has a table with all modes the LEDs support, but it doesn't > mention this fast blinking. The right LED is on constantly, which should > indicate a link. This is the same on all three ports, irrespective of > configuration. > > I also just tried netbooting, and that doesn't seem to be working either. So > I guess it's time to RMA it. > > Stefan > >> Am 23.01.2021 um 11:28 schrieb Bob Bishop : >> >> Hi, >> >> FWIW I found that applying -lro didn’t work retrospectively, it had to be >> done when the interface was first configured. Might apply to other options >> too. >> >> -- >> Bob Bishop >> r...@gid.co.uk >> >>> On 22 Jan 2021, at 23:42, Graham Menhennitt >>> wrote: >>> >>> Try "ifconfig $ifname -rxcsum -txcsum" and possibly " -vlanhwtso -tso4" as >>> well. >>> >>> Graham >>> >>> On 23/01/2021 8:10 am, Stefan Bethke wrote: >>>> I have a weird situation with an PCEngines APU3, where I can't seem to be >>>> able to transmit packets through either of the igb interfaces. With >>>> tcpdump, I can see packets arriving, and the interface flags appear to be >>>> just fine: >>>> >>>> options=e527bb >>>> ether 00:0d:b9:58:xx:xx >>>> inet6 fe80::20d:b9ff::%igb0 prefixlen 64 scopeid 0x1 >>>> inet6 2a02:8108:4840::::: prefixlen 64 autoconf >>>> inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 >>>> media: Ethernet autoselect (1000baseT ) >>>> status: active >>>> nd6 options=23 >>>> >>>> dhclient is running on that interfaces, and I got an IPv6 address through >>>> RA. >>>> >>>> Assigning an address manually doesn't change anything. >>>> >>>> igb0@pci0:1:0:0:class=0x02 card=0x8086 chip=0x157b8086 >>>> rev=0x03 hdr=0x00 >>>> vendor = 'Intel Corporation' >>>> device = 'I210 Gigabit Network Connection' >>>> class = network >>>> subclass = ethernet >>>> >>>> # freebsd-version >>>> 12.2-RELEASE >>>> >>>> I installed 12.2-REL a couple of weeks ago, and haven't done anything >>>> since. >>>> >>>> Tried the three different port with different cables on different switch >>>> ports, which are working fine with other machines. >>>> >>>> I'm installing updates now via a USB adapter. >>>> >>>> Any suggestions? >>>> >>>> >>>> Stefan >>>> >>>> -- >>>> Stefan BethkeFon +49 151 14070811 >>>> >>> ___ >>> 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" > > -- > Stefan BethkeFon +49 151 14070811 > -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: APU3 ethernet can't transmit
I've tried one more time with this in rc.conf: network_interfaces="igb0" ifconfig_igb0="-lro -vlanhwtso -tso4 -vlanhwfilter -rxcsum -txcsum -vlanhwtag -vlanmtu -vlanhwcsum -tso6 -txcsum6" Whick produces this: options=802020 No joy. What's interesting is that the left LED on the plug in blinking with about 2Hz, so clearly the PHY or controller is unhappy about something. The i210 datasheet has a table with all modes the LEDs support, but it doesn't mention this fast blinking. The right LED is on constantly, which should indicate a link. This is the same on all three ports, irrespective of configuration. I also just tried netbooting, and that doesn't seem to be working either. So I guess it's time to RMA it. Stefan > Am 23.01.2021 um 11:28 schrieb Bob Bishop : > > Hi, > > FWIW I found that applying -lro didn’t work retrospectively, it had to be > done when the interface was first configured. Might apply to other options > too. > > -- > Bob Bishop > r...@gid.co.uk > >> On 22 Jan 2021, at 23:42, Graham Menhennitt wrote: >> >> Try "ifconfig $ifname -rxcsum -txcsum" and possibly " -vlanhwtso -tso4" as >> well. >> >> Graham >> >> On 23/01/2021 8:10 am, Stefan Bethke wrote: >>> I have a weird situation with an PCEngines APU3, where I can't seem to be >>> able to transmit packets through either of the igb interfaces. With >>> tcpdump, I can see packets arriving, and the interface flags appear to be >>> just fine: >>> >>> options=e527bb >>>ether 00:0d:b9:58:xx:xx >>>inet6 fe80::20d:b9ff::%igb0 prefixlen 64 scopeid 0x1 >>>inet6 2a02:8108:4840::::: prefixlen 64 autoconf >>>inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 >>>media: Ethernet autoselect (1000baseT ) >>>status: active >>>nd6 options=23 >>> >>> dhclient is running on that interfaces, and I got an IPv6 address through >>> RA. >>> >>> Assigning an address manually doesn't change anything. >>> >>> igb0@pci0:1:0:0:class=0x02 card=0x8086 chip=0x157b8086 >>> rev=0x03 hdr=0x00 >>>vendor = 'Intel Corporation' >>>device = 'I210 Gigabit Network Connection' >>>class = network >>>subclass = ethernet >>> >>> # freebsd-version >>> 12.2-RELEASE >>> >>> I installed 12.2-REL a couple of weeks ago, and haven't done anything since. >>> >>> Tried the three different port with different cables on different switch >>> ports, which are working fine with other machines. >>> >>> I'm installing updates now via a USB adapter. >>> >>> Any suggestions? >>> >>> >>> Stefan >>> >>> -- >>> Stefan Bethke Fon +49 151 14070811 >>> >> ___ >> 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" -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: APU3 ethernet can't transmit
Am 22.01.2021 um 22:38 schrieb Stefan Bethke : > > Am 22.01.2021 um 22:10 schrieb Stefan Bethke : >> >> I have a weird situation with an PCEngines APU3, where I can't seem to be >> able to transmit packets through either of the igb interfaces. With tcpdump, >> I can see packets arriving, and the interface flags appear to be just fine: >> >> options=e527bb >> ether 00:0d:b9:58:xx:xx >> inet6 fe80::20d:b9ff::%igb0 prefixlen 64 scopeid 0x1 >> inet6 2a02:8108:4840::::: prefixlen 64 autoconf >> inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 >> media: Ethernet autoselect (1000baseT ) >> status: active >> nd6 options=23 >> >> dhclient is running on that interfaces, and I got an IPv6 address through RA. >> >> Assigning an address manually doesn't change anything. >> >> igb0@pci0:1:0:0:class=0x02 card=0x8086 chip=0x157b8086 >> rev=0x03 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'I210 Gigabit Network Connection' >> class = network >> subclass = ethernet >> >> # freebsd-version >> 12.2-RELEASE >> >> I installed 12.2-REL a couple of weeks ago, and haven't done anything since. >> >> Tried the three different port with different cables on different switch >> ports, which are working fine with other machines. >> >> I'm installing updates now via a USB adapter. > > Updating the firmware to apu2_v4.11.0.6.rom didn't change a thing. Somebody > suggested turning off LRO, but that didn't help either. > > I have another APU2 with 12.1 that is doing just fine. I guess I can > downgrade and see if that changes anything. Debian is not happy about the interfaces either, so I'm guessing its a hardware problem. Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: APU3 ethernet can't transmit
Am 22.01.2021 um 22:10 schrieb Stefan Bethke : > > I have a weird situation with an PCEngines APU3, where I can't seem to be > able to transmit packets through either of the igb interfaces. With tcpdump, > I can see packets arriving, and the interface flags appear to be just fine: > > options=e527bb >ether 00:0d:b9:58:xx:xx >inet6 fe80::20d:b9ff::%igb0 prefixlen 64 scopeid 0x1 >inet6 2a02:8108:4840::::: prefixlen 64 autoconf >inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 >media: Ethernet autoselect (1000baseT ) >status: active >nd6 options=23 > > dhclient is running on that interfaces, and I got an IPv6 address through RA. > > Assigning an address manually doesn't change anything. > > igb0@pci0:1:0:0:class=0x02 card=0x8086 chip=0x157b8086 > rev=0x03 hdr=0x00 >vendor = 'Intel Corporation' >device = 'I210 Gigabit Network Connection' >class = network >subclass = ethernet > > # freebsd-version > 12.2-RELEASE > > I installed 12.2-REL a couple of weeks ago, and haven't done anything since. > > Tried the three different port with different cables on different switch > ports, which are working fine with other machines. > > I'm installing updates now via a USB adapter. Updating the firmware to apu2_v4.11.0.6.rom didn't change a thing. Somebody suggested turning off LRO, but that didn't help either. I have another APU2 with 12.1 that is doing just fine. I guess I can downgrade and see if that changes anything. Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
APU3 ethernet can't transmit
I have a weird situation with an PCEngines APU3, where I can't seem to be able to transmit packets through either of the igb interfaces. With tcpdump, I can see packets arriving, and the interface flags appear to be just fine: options=e527bb ether 00:0d:b9:58:xx:xx inet6 fe80::20d:b9ff::%igb0 prefixlen 64 scopeid 0x1 inet6 2a02:8108:4840::::: prefixlen 64 autoconf inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 media: Ethernet autoselect (1000baseT ) status: active nd6 options=23 dhclient is running on that interfaces, and I got an IPv6 address through RA. Assigning an address manually doesn't change anything. igb0@pci0:1:0:0:class=0x02 card=0x8086 chip=0x157b8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'I210 Gigabit Network Connection' class = network subclass = ethernet # freebsd-version 12.2-RELEASE I installed 12.2-REL a couple of weeks ago, and haven't done anything since. Tried the three different port with different cables on different switch ports, which are working fine with other machines. I'm installing updates now via a USB adapter. Any suggestions? Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
IPMI KVM mouse in absolute/tablet mode?
I'm setting up an ASRockRack X470D4U2-2T (https://www.asrockrack.com/general/productdetail.asp?Model=X470D4U2-2T#Specifications <https://www.asrockrack.com/general/productdetail.asp?Model=X470D4U2-2T#Specifications>). It's one of the few Ryzen boards with ECC support and an IPMI KVM (AST2500). Working with the web-based KVM is working well, including installing FreeBSD 12.1 from the disk1 image through the virtual CD drive. However, moused seems to not understand the absolute addressing employed by the emulated USB mouse. The mouse pointer fails to move, and the dmesg output only lists the Z axis: ugen0.6: at usbus0 ukbd0 on uhub2 ukbd0: on usbus0 kbd2 at ukbd0 ums0 on uhub2 ums0: on usbus0 ums0: 3 buttons and [Z] coordinates ID=0 When I switch from "Absolute Mouse Mode" to "Relative Mouse Mode", the pointer moves, and the dmesg shows X, Y, and Z: ugen0.6: at usbus0 (disconnected) ukbd0: at uhub2, port 5, addr 5 (disconnected) ukbd0: detached ums0: at uhub2, port 5, addr 5 (disconnected) ums0: detached ugen0.6: at usbus0 ukbd0 on uhub2 ukbd0: on usbus0 kbd2 at ukbd0 ums0 on uhub2 ums0: on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 I couldn't immediately find anything about support for the absolute/tablet mode. Thanks, Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: Using VLAN ID 1 (was: CARP under Hyper-V: weird things happen)
Only tangential to your main issues, but: > Am 31.05.2020 um 18:07 schrieb Eugene M. Zheganin : > > Another weird this is that vlan1 is refusing to work (seems like packets are > never received on the VM side) unless its configured on another adapter in > the -Untagged (once again powershell term for SetVmNetworkAdapterVlan). I believe it is best practice to not use VLAN ID 1 in your network design because many vendors assign it a special role, and it can be hard to reconfigure that on the devices. The virtual switch might have the same issue. Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: nvme0 error
Am 30.04.2020 um 20:06 schrieb Warner Losh : > > I'm thinking percent used 110 may be the thing it's alerting on, the standard > says: Thanks! I figured as much, but I wasn't sure how to interpret the data. I've noticed that filesystem access appears to have slowed on that box. It's sister shows only 27 percentage used, and seems to work ust as always. Thanks, Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
nvme0 error
nvme0: async event occurred (type 0x1, info 0x00, page 0x02) nvme0: device reliability degraded Should I be concerned? I'm using this Samsung SSD as cache and log for ZFS on a 12-stable machine. nvd0: NVMe namespace nvd0: 122104MB (250069680 512 byte sectors) # nvmecontrol logpage -p 2 nvme0 SMART/Health Information Log Critical Warning State: 0x04 Available spare: 0 Temperature: 0 Device reliability:1 Read only: 0 Volatile memory backup:0 Temperature:311 K, 37.85 C, 100.13 F Available spare:100 Available spare threshold: 10 Percentage used:110 Data units (512,000 byte) read: 18417596 Data units written: 164091845 Host read commands: 499986873 Host write commands:1491808067 Controller busy time (minutes): 48315 Power cycles: 59 Power on hours: 20432 Unsafe shutdowns: 26 Media errors: 0 No. error info log entries: 22 Warning Temp Composite Time:0 Error Temp Composite Time: 0 Temperature Sensor 1: 311 K, 37.85 C, 100.13 F Temperature Sensor 2: 330 K, 56.85 C, 134.33 F Temperature 1 Transition Count: 0 Temperature 2 Transition Count: 0 Total Time For Temperature 1: 0 Total Time For Temperature 2: 0 Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: make kernel ignore broken SATA disk
Am 12.04.2020 um 20:44 schrieb Chris : > > On Sun, 12 Apr 2020 16:37:06 +0200 Stefan Bethke s...@lassitu.de said > >> I have a server I don't have physical access to right now, which has a broken >> SATA disk that produces mostly errors (but not entirely). >> The disk has two partitions that are part of a zpool each. I can't bring the >> system up with this disk being online, because ZFS is trying its darndest to >> use it. >> I already renamed the GPT partitions in the hope that ZFS would not find them >> anymore, but it does. >> I can't gpart destroy -f ada1 because "device busy". > FTR it's gpart destroy -F (note the case difference) :-) Sorry, that was a typo in the transcription. Even when using -F, it won't delete the table. Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: make kernel ignore broken SATA disk
Am 12.04.2020 um 19:59 schrieb Warner Losh : > > Boot single user. Zfs won't import and you can do what you need. Not if you have root on ZFS, and it's on the affected pool. Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: make kernel ignore broken SATA disk
Am 12.04.2020 um 19:24 schrieb Eugene Grosbein : > > Try something like this at loader prompt: > > set hint.ahcich.5.disabled=1 Thank you, that did the trick! Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: make kernel ignore broken SATA disk
Am 12.04.2020 um 18:53 schrieb Ian Lepore : > > On Sun, 2020-04-12 at 16:37 +0200, Stefan Bethke wrote: >> I have a server I don't have physical access to right now, which has >> a broken SATA disk that produces mostly errors (but not entirely). >> >> The disk has two partitions that are part of a zpool each. I can't >> bring the system up with this disk being online, because ZFS is >> trying its darndest to use it. >> >> I already renamed the GPT partitions in the hope that ZFS would not >> find them anymore, but it does. >> >> I can't gpart destroy -f ada1 because "device busy". >> >> Is there a way, ideally in the loader, to tell the kernel to ignore >> ada1 and/or ahcich5? Or can I force ZFS some other way to ignore the >> disk? I do have a spare disk I can use to replace the failed one, but >> I can't get the machine into a state where I could even issue the >> zpool replace command. > > The the loader prompt (or in loader.conf without 'set'): > > set hint.ada.1.disabled=1 Doesn't seem to have any effect. ada1 still probed, and still prints error messages to the console. Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: make kernel ignore broken SATA disk
Am 12.04.2020 um 19:03 schrieb Slawa Olhovchenkov : > > On Sun, Apr 12, 2020 at 06:38:10PM +0200, Stefan Bethke wrote: > >> >> >>> Am 12.04.2020 um 18:31 schrieb Slawa Olhovchenkov : >>> >>> On Sun, Apr 12, 2020 at 06:24:09PM +0200, Stefan Bethke wrote: >>> >>>> Am 12.04.2020 um 17:43 schrieb Slawa Olhovchenkov : >>>>> >>>>> On Sun, Apr 12, 2020 at 04:37:06PM +0200, Stefan Bethke wrote: >>>>> >>>>>> I have a server I don't have physical access to right now, which has a >>>>>> broken SATA disk that produces mostly errors (but not entirely). >>>>>> >>>>>> The disk has two partitions that are part of a zpool each. I can't bring >>>>>> the system up with this disk being online, because ZFS is trying its >>>>>> darndest to use it. >>>>>> >>>>>> I already renamed the GPT partitions in the hope that ZFS would not find >>>>>> them anymore, but it does. >>>>>> >>>>>> I can't gpart destroy -f ada1 because "device busy". >>>>>> >>>>>> Is there a way, ideally in the loader, to tell the kernel to ignore ada1 >>>>>> and/or ahcich5? Or can I force ZFS some other way to ignore the disk? I >>>>>> do have a spare disk I can use to replace the failed one, but I can't >>>>>> get the machine into a state where I could even issue the zpool replace >>>>>> command. >>>>> >>>>> `zpool offline pool device` if you have enoght redundancy? >>>> >>>> I do, but the command doesn't return. Instead, I'm getting loads of sata >>>> error message. >>> >>> What you zpool configuration? >> >> This is from the working system. The identifiers are slightly different, but >> the structure is identical. > > what about `zpool detach ` ? Now I can't boot into single user mode anymore, ZFS just waits forever, and the kernel is printing an endless chain of SATA error messages. I really need a way to remove the broken disk before ZFS tries to access it, or a way to stop ZFS from try to access the disk. Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: make kernel ignore broken SATA disk
> Am 12.04.2020 um 18:31 schrieb Slawa Olhovchenkov : > > On Sun, Apr 12, 2020 at 06:24:09PM +0200, Stefan Bethke wrote: > >> Am 12.04.2020 um 17:43 schrieb Slawa Olhovchenkov : >>> >>> On Sun, Apr 12, 2020 at 04:37:06PM +0200, Stefan Bethke wrote: >>> >>>> I have a server I don't have physical access to right now, which has a >>>> broken SATA disk that produces mostly errors (but not entirely). >>>> >>>> The disk has two partitions that are part of a zpool each. I can't bring >>>> the system up with this disk being online, because ZFS is trying its >>>> darndest to use it. >>>> >>>> I already renamed the GPT partitions in the hope that ZFS would not find >>>> them anymore, but it does. >>>> >>>> I can't gpart destroy -f ada1 because "device busy". >>>> >>>> Is there a way, ideally in the loader, to tell the kernel to ignore ada1 >>>> and/or ahcich5? Or can I force ZFS some other way to ignore the disk? I do >>>> have a spare disk I can use to replace the failed one, but I can't get the >>>> machine into a state where I could even issue the zpool replace command. >>> >>> `zpool offline pool device` if you have enoght redundancy? >> >> I do, but the command doesn't return. Instead, I'm getting loads of sata >> error message. > > What you zpool configuration? This is from the working system. The identifiers are slightly different, but the structure is identical. # zpool status pool: data state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: resilvered 176K in 0 days 00:01:28 with 0 errors on Sun May 26 21:24:54 2019 config: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 mirror-0ONLINE 0 0 0 gpt/ls0data ONLINE 0 0 0 gpt/ls1data ONLINE 0 0 0 logs gpt/data0logONLINE 0 0 0 cache gpt/data0cache ONLINE 0 0 0 errors: No known data errors pool: ls-host state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: scrub repaired 0 in 0 days 00:06:33 with 0 errors on Sun Apr 12 11:46:25 2020 config: NAME STATE READ WRITE CKSUM ls-host ONLINE 0 0 0 mirror-0ONLINE 0 0 0 gpt/ls0host ONLINE 0 0 0 gpt/ls1host ONLINE 0 0 0 logs gpt/host0logONLINE 0 0 0 cache gpt/host0cache ONLINE 0 0 0 errors: No known data errors -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: make kernel ignore broken SATA disk
Am 12.04.2020 um 18:29 schrieb Eugene Grosbein : > > 12.04.2020 21:57, Stefan Bethke wrote: > >>>> Is there a way, ideally in the loader, to tell the kernel to ignore ada1 >>>> and/or ahcich5? Or can I force ZFS some other way to ignore the disk? I do >>>> have a spare disk I can use to replace the failed one, but I can't get the >>>> machine into a state where I could even issue the zpool replace command. >>> >>> It depends on the HDD controller the disk is attached to. What controller >>> and driver does it have? >> >> This is from an identlical machine without disk issues: >> >> # camcontrol devlist >> at scbus4 target 0 lun 0 (ada0,pass0) >> at scbus5 target 0 lun 0 (ada1,pass1) >> at scbus6 target 0 lun 0 (ada2,pass2) >>at scbus8 target 0 lun 0 (pass3) >> # pciconf -lv >> ... >> ahci0@pci0:0:23:0:class=0x010601 card=0x088415d9 chip=0xa1028086 rev=0x31 >> hdr=0x00 >>vendor = 'Intel Corporation' >>device = 'Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller >> [AHCI Mode]' >>class = mass storage >>subclass = SATA > > And your FreeBSD version? FreeBSD 12.1-STABLE r358833 amd64 Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: make kernel ignore broken SATA disk
Am 12.04.2020 um 17:43 schrieb Slawa Olhovchenkov : > > On Sun, Apr 12, 2020 at 04:37:06PM +0200, Stefan Bethke wrote: > >> I have a server I don't have physical access to right now, which has a >> broken SATA disk that produces mostly errors (but not entirely). >> >> The disk has two partitions that are part of a zpool each. I can't bring the >> system up with this disk being online, because ZFS is trying its darndest to >> use it. >> >> I already renamed the GPT partitions in the hope that ZFS would not find >> them anymore, but it does. >> >> I can't gpart destroy -f ada1 because "device busy". >> >> Is there a way, ideally in the loader, to tell the kernel to ignore ada1 >> and/or ahcich5? Or can I force ZFS some other way to ignore the disk? I do >> have a spare disk I can use to replace the failed one, but I can't get the >> machine into a state where I could even issue the zpool replace command. > > `zpool offline pool device` if you have enoght redundancy? I do, but the command doesn't return. Instead, I'm getting loads of sata error message. -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: make kernel ignore broken SATA disk
> Am 12.04.2020 um 16:45 schrieb Eugene Grosbein : > > 12.04.2020 21:37, Stefan Bethke wrote: > >> I have a server I don't have physical access to right now, which has a >> broken SATA disk that produces mostly errors (but not entirely). >> >> The disk has two partitions that are part of a zpool each. I can't bring the >> system up with this disk being online, because ZFS is trying its darndest to >> use it. >> >> I already renamed the GPT partitions in the hope that ZFS would not find >> them anymore, but it does. >> >> I can't gpart destroy -f ada1 because "device busy". >> >> Is there a way, ideally in the loader, to tell the kernel to ignore ada1 >> and/or ahcich5? Or can I force ZFS some other way to ignore the disk? I do >> have a spare disk I can use to replace the failed one, but I can't get the >> machine into a state where I could even issue the zpool replace command. > > It depends on the HDD controller the disk is attached to. What controller and > driver does it have? This is from an identlical machine without disk issues: # camcontrol devlist at scbus4 target 0 lun 0 (ada0,pass0) at scbus5 target 0 lun 0 (ada1,pass1) at scbus6 target 0 lun 0 (ada2,pass2) at scbus8 target 0 lun 0 (pass3) # pciconf -lv ... ahci0@pci0:0:23:0: class=0x010601 card=0x088415d9 chip=0xa1028086 rev=0x31 hdr=0x00 vendor = 'Intel Corporation' device = 'Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode]' class = mass storage subclass = SATA ... dmesg: ahci0: port 0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem 0xdf41-0xdf411fff,0xdf41e000-0xdf4 1e0ff,0xdf41d000-0xdf41d7ff irq 16 at device 23.0 on pci0 ahci0: AHCI v1.31 with 8 6Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ahcich6: at channel 6 on ahci0 ahcich7: at channel 7 on ahci0 ahciem0: on ahci0 ada0 at ahcich4 bus 0 scbus4 target 0 lun 0 ada0: ACS-2 ATA SATA 3.x device ada0: Serial Number Z1F4GVC3 ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 2861588MB (5860533168 512 byte sectors) ada0: quirks=0x1<4K> ada1 at ahcich5 bus 0 scbus5 target 0 lun 0 ada1: ACS-2 ATA SATA 3.x device ada1: Serial Number W1F5180B ada1: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 2861588MB (5860533168 512 byte sectors) ada1: quirks=0x1<4K> ada2 at ahcich6 bus 0 scbus6 target 0 lun 0 ada2: ACS-2 ATA SATA 3.x device ada2: Serial Number Z1F4EJEQ ada2: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 2861588MB (5860533168 512 byte sectors) ada2: quirks=0x1<4K> Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
make kernel ignore broken SATA disk
I have a server I don't have physical access to right now, which has a broken SATA disk that produces mostly errors (but not entirely). The disk has two partitions that are part of a zpool each. I can't bring the system up with this disk being online, because ZFS is trying its darndest to use it. I already renamed the GPT partitions in the hope that ZFS would not find them anymore, but it does. I can't gpart destroy -f ada1 because "device busy". Is there a way, ideally in the loader, to tell the kernel to ignore ada1 and/or ahcich5? Or can I force ZFS some other way to ignore the disk? I do have a spare disk I can use to replace the failed one, but I can't get the machine into a state where I could even issue the zpool replace command. Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
carp can't delete address
I’ve just set up carp (for the first time) and it seems the virtual address is not being removed on the backup host: May 23 20:55:09 xxx kernel: carp: 1@igb0: INIT -> BACKUP (initialization complete) May 23 20:55:12 xxx kernel: carp: 1@igb0: BACKUP -> MASTER (master timed out) May 23 20:56:33 xxx kernel: carp: 1@igb0: MASTER -> BACKUP (more frequent advertisement received) May 23 20:56:33 xxx kernel: igb0: deletion failed: 3 ifconfig shows the address as active: # ifconfig igb0 igb0: flags=8943 metric 0 mtu 1500 options=e527bb ether ac:1f:6b:12:34:56 inet 212.12.xxx.xxx/24 broadcast 212.12.xxx.xxx inet 212.12.xxx.yyy/32 broadcast 212.12.xxx.yyy vhid 1 inet6 fe80::ae1f:6bff:...%igb0/64 scopeid 0x1 carp: BACKUP vhid 1 advbase 1 advskew 200 media: Ethernet autoselect (1000baseT ) status: active nd6 options=21 Is there a configuration I can/need to adjust? uname -a FreeBSD foo.example.com 12.0-STABLE FreeBSD 12.0-STABLE r344052 EISENBOOT amd64 Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: poudriere(-devel) ports updating question
> Am 05.03.2019 um 15:09 schrieb tech-lists : > > Hi, > > There are several categories of ports I'd like to avoid for some > architectures. For example, I don't want x11 for mips.mips64. Or astronomy. > But let's say, for this architecture, I want to build everything else. > > I can't see a way of excluding categories with poudriere ports when > updating the ports tree - the only workaround I can see is to download > another tree, call it something and then manually edit that tree, and then > set the build off with -p port-treename. Every time I want to > make a bulk run. > > Basically I'm looking for exclude mask functionality when updating a > ports tree with poudriere ports. > > Do I need to do this manually or have I missed something? I don’t think it’s easy to do that. How would you handle dependencies? (For example, some ports require X11 libs and stuff, even though they’re in a different category.) Do you want to save time on builds by excluding pkgs that you know you’ll never need? Or what is your goal with this? In my setup, I rely on the regular packages from the official repo, but for those pkg that I need built with different options, I run a custom list. You could try to produce a filtered list of all ports, removing those that you’d never select manually, and let poudriere figure out what needs to be built. Something along the lines of: - update ports - list all ports | grep -v '^x11/' - run poudriere with resulting list Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: Boot from one drive and load FreeBSD from another
Am 11.01.2019 um 23:08 schrieb Walter Parker : > If I create a FreeBSD-boot partition on the SAS drive and a FreeBSD-zfs > partition on the ZFS mirror, will the boot partition loader automatically > find the ZFS pool? If not, is there anything special I can do to force a > boot? Set up a UFS filesystem on one of the disks that the BIOS can access and put everything under /boot into it. Install boot or gptboot (not zfsboot or gptzfsboot) with gpart, since loader will only work on that UFS filesystem. Since loader can’t find your root file system (as the BIOS has no access to those disks), you need to set the path to the root filesystem in loader.conf (see loader.conf(3), vfs.root.mountfrom). For ZFS, that something like zfs:poolname/path/to/rootfs. This will instruct the kernel to mount root from that spec. Normally, loader figures this out automatically, by probing the disks for metadata (ZFS) or by analyzing fstab (UFS), but in your case, it can’t. You’ll probably want to add an entry for /boot to your fstab, so updates will update the boot partition instead of the /boot directory on your ZFS root. HTH, Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: Trouble booting from EFI with 12-stable
> Am 11.01.2019 um 19:35 schrieb Stefan Bethke : > > > >> Am 11.01.2019 um 15:04 schrieb Kyle Evans : >> >> On Fri, Jan 11, 2019 at 5:05 AM Stefan Bethke wrote: >>> >>> The loader stumbles over this error and then drops to the prompt: >>> efi-autoresizecons not found >>> >>> module_path is then not set, and loader can’t load the kernel. Typing in >>> everything by hand will boot the system OK. >>> >>> I just did a regular make installworld installkernel (previous install was >>> from mid-december). Do I need to update the boot blocks or the EFI >>> partition? >>> >> >> Hi, >> >> Interesting; this is generally an indicator that your loader >> (/boot/loader.efi in 12.0 EFI-land) is out-of-date with respect to >> scripts. For that I'd go ahead and double-check that /boot/loader.efi >> was actually updated *and* update the contents of the ESP -- that >> particular change was paired with another one that stopped doing any >> resizing in boot1. > > I thought as much. Is there a succinct step-by-step to install/update > everything involved in the UEFI boot process? The Handbook appears to have > very little on UEFI booting… The UEFI man page has a good explanation of which files are involved in booting: https://www.freebsd.org/cgi/man.cgi?query=uefi=8=freebsd-release-ports I mounted the ESP and copied /boot/boot1.efi to /boot/efi/EFI/BOOT/BOOTX64.EFI. Surprisingly, the new boot1.efi is much smaller than what I had before (according to the timestamp from November), but using that, booting seems to be restored. # grep efi /etc/fstab /dev/ada0p2 /boot/efi msdos rw,noauto 0 0 # mount /boot/efi # ls -l /boot/efi/EFI/BOOT/BOOTX64.EFI /boot/efi/EFI/BOOT/bak/BOOTX64.EFI -rwxr-xr-x 1 root wheel 81920 Jan 11 18:43 /boot/efi/EFI/BOOT/BOOTX64.EFI* -rwxr-xr-x 1 root wheel 410112 Nov 25 16:27 /boot/efi/EFI/BOOT/bak/BOOTX64.EFI* Thanks, Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: Trouble booting from EFI with 12-stable
> Am 11.01.2019 um 15:04 schrieb Kyle Evans : > > On Fri, Jan 11, 2019 at 5:05 AM Stefan Bethke wrote: >> >> The loader stumbles over this error and then drops to the prompt: >> efi-autoresizecons not found >> >> module_path is then not set, and loader can’t load the kernel. Typing in >> everything by hand will boot the system OK. >> >> I just did a regular make installworld installkernel (previous install was >> from mid-december). Do I need to update the boot blocks or the EFI partition? >> > > Hi, > > Interesting; this is generally an indicator that your loader > (/boot/loader.efi in 12.0 EFI-land) is out-of-date with respect to > scripts. For that I'd go ahead and double-check that /boot/loader.efi > was actually updated *and* update the contents of the ESP -- that > particular change was paired with another one that stopped doing any > resizing in boot1. I thought as much. Is there a succinct step-by-step to install/update everything involved in the UEFI boot process? The Handbook appears to have very little on UEFI booting… Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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"
Trouble booting from EFI with 12-stable
The loader stumbles over this error and then drops to the prompt: efi-autoresizecons not found module_path is then not set, and loader can’t load the kernel. Typing in everything by hand will boot the system OK. I just did a regular make installworld installkernel (previous install was from mid-december). Do I need to update the boot blocks or the EFI partition? Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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 12 and Nocona
Am 08.01.2019 um 10:34 schrieb Marek Zarychta : > W dniu 03.01.2019 o 14:13, Stefan Bethke pisze: >>> I have under supervision a few old servers running 11.2-STABLE. The >>> hardware is almost for retirement, but still in working condition. It's >>> all old Nocona NetBurst microarchitecture. I have recently tried do >>> upgrade OS two of them to 12.0-STABLE, but failed. When I use old >>> bootloader the boot freezes on blue highlighted "Booting" stage, when I >>> tried to use 12 loader, it freezes earlier, on loading kernel modules. >>> The kernel was compiled from fresh sources for CPUTYPE?=nocona. >>> 11.2-STABLE is fine with this optimization and the same kernel boots >>> fine on newer hardware. >>> >>> It is fair, that 11 EOL is expected September 30, 2021 and these servers >>> will likely be retired before this date, but some questions arise: >>> >>> Is such old hardware still supported? Is it possible (how to) debug the >>> booting process? >> >> The first step is to try with known-good bits: can you boot these machines >> off the 12.0 ISO or memstick images? Can you load your kernel and modules >> with the loader from the ISO/memstick? Does GENERIC built without any flags >> work? >> >> If any of these don’t work, try to be as specific as possible when reporting >> problems. For example, the exact make of mainboard (kenv output) and the >> BIOS version, and any relevant BIOS settings are likely important for >> problems regarding the loader. If the kernel and modules load, you can try a >> verbose boot to see better how far the kernel gets. >> >> I’d be really surprised if the CPUs themselves would cause trouble. > > > The first step is done. The affected hardware doesn't boot from official > 12.0-RELEASE CD either. Loader also freezes at the stage of loading > kernel modules. These servers are old Maxdata Platinum 500 and 3200. > Some time ago I have submitted dmesgs to NYC BUG dmesg repository[1][2]. > > Both configurations are fine with 11-STABLE, so I am not going to > upgrade them and I am replying only FYI. > > > [1] https://dmesgd.nycbug.org/index.cgi?do=view=3790 > <https://dmesgd.nycbug.org/index.cgi?do=view=3790> > [2] https://dmesgd.nycbug.org/index.cgi?do=view=4111 > <https://dmesgd.nycbug.org/index.cgi?do=view=4111> I think it would be great to get some input from someone familiar with the new loader. I’ve cc’ed Warner, Kyle and Toomas, as they were listed in the quarterly status report. Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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 12 and Nocona
> I have under supervision a few old servers running 11.2-STABLE. The > hardware is almost for retirement, but still in working condition. It's > all old Nocona NetBurst microarchitecture. I have recently tried do > upgrade OS two of them to 12.0-STABLE, but failed. When I use old > bootloader the boot freezes on blue highlighted "Booting" stage, when I > tried to use 12 loader, it freezes earlier, on loading kernel modules. > The kernel was compiled from fresh sources for CPUTYPE?=nocona. > 11.2-STABLE is fine with this optimization and the same kernel boots > fine on newer hardware. > > It is fair, that 11 EOL is expected September 30, 2021 and these servers > will likely be retired before this date, but some questions arise: > > Is such old hardware still supported? Is it possible (how to) debug the > booting process? The first step is to try with known-good bits: can you boot these machines off the 12.0 ISO or memstick images? Can you load your kernel and modules with the loader from the ISO/memstick? Does GENERIC built without any flags work? If any of these don’t work, try to be as specific as possible when reporting problems. For example, the exact make of mainboard (kenv output) and the BIOS version, and any relevant BIOS settings are likely important for problems regarding the loader. If the kernel and modules load, you can try a verbose boot to see better how far the kernel gets. I’d be really surprised if the CPUs themselves would cause trouble. Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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"
ZFS high write IO in single user mode
I have two hosts that are configured identically (in a kind of manual hot-standby configuration), running a set of jails each. ZFS datasets for the jails and bhyve VMs are synced across regularly. When one of the machines exhibits a problem, I can shut down the problematic jails or the whole machine, and start the jails/VMs on the other host. This has been working really well for the past ~10 years. A couple of years ago, one of the ZFS pools on one of the machines developed some logical inconsistencies that were not detected by zpool scrub. The only indication that something was amiss was high disk IO, in particular, writes, even when no processes were running. I eventually resolved that situation by recreating the zpool and restoring the datasets from the working machine. About a year ago, I upgraded the hardware and in the process created fresh pools. This has been running well. Since about two days ago, I now have the situation again where I have a steady write rate even in single user mode, with the root dataset mounted read only, and the second pool that contains the jail datasets not mounted at all. I only have a video console (via IPMI KVM) so I won’t transcribe the complete output, but here’s what I think are significant observations: gstat reports ~30 writes/sec on each of the two disks that make up the zmirror pool. mount shows the root dataset to be mounted read-only. zpool status takes a really long time, and then reports that everything is fine for both pools (boot/os and jails). smartctl doesn’t show any problems for either of the disks. I’m happy to just wipe the pools and start fresh, but I’d like to use this opportunity to hopefully figure out why ZFS appears to act weirdly, and hopefully find a permanent fix. This is 11-stable from September 13th. Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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"
if_bridge and CARP causes hangs
I’ve just stumbled on this problem, which seems to be quite old and still unresolved. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319 As a quick summary: if you configure CARP on an if_bridge interface, the CARP state changes will (always/with a high probability) create a deadlock between CARP and the if_bridge code, leading to the machine becoming unresponsive. There is a suggested patch, but work on it seems to be very slow: https://reviews.freebsd.org/D3133 I would love to see a fix in 11-stable or 12.0. Is there something I can do to help move this forward? Regards, Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: Bind to port <1024 in jail
> Am 20.08.2018 um 18:32 schrieb Bjoern A. Zeeb > : > > On 20 Aug 2018, at 16:22, Stefan Bethke wrote: > >>>> Is there a way to allow regular processes to bind to low ports? >>> >>> you have to set it on the base system; alternatively with vnet you might >>> be able to change it per-jail. >> >> Do you feel it’s OK to enable VIMAGE in -stable? When I tried last in 2016, >> I had stability issues, I think related to pf. > > “If you know what you are doing it won’t panic” ;-) I think with 12 I’d be > a lot more confident about stability. Most fixes could not and were not > MFCed. OK then, should I move to -current and try there? I’ve not tracked -current on a production box in years (I think the last time was around 3 or 4), but I’m willing to give it a go, seeing that the code freeze is about to start. Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: Bind to port <1024 in jail
> Am 20.08.2018 um 16:59 schrieb Bjoern A. Zeeb > : > > On 20 Aug 2018, at 14:47, Stefan Bethke wrote: > >> I have a Go program (acme-dns) that wants to bind 53, 80, and 443, and I’d >> rather have it run as a non-privileged user. The program doesn’t provide a >> facility to drop privs after binding the ports. I’m planning to run it in a >> jail. >> >> After some googling, it appears that a couple of years ago I should have >> been able to do: >> sysctl net.inet.ip.portrange.reservedhigh=0 >> and allow all processes to bind to „low“ ports. This does not work in my >> jails on a 11-stable host. >> >> $ sudo sysctl net.inet.ip.portrange.reservedhigh=0 >> net.inet.ip.portrange.reservedhigh: 1023 >> sysctl: net.inet.ip.portrange.reservedhigh=0: Operation not permitted >> >> Securelevel should not interfere: >> $ sysctl kern.securelevel >> kern.securelevel: -1 >> >> Is there a way to allow regular processes to bind to low ports? > > you have to set it on the base system; alternatively with vnet you might be > able to change it per-jail. Do you feel it’s OK to enable VIMAGE in -stable? When I tried last in 2016, I had stability issues, I think related to pf. Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: Bind to port <1024 in jail
Am 20.08.2018 um 16:59 schrieb Eugene Grosbein : > > 20.08.2018 21:47, Stefan Bethke wrote: > >> I have a Go program (acme-dns) that wants to bind 53, 80, and 443, and I’d >> rather have it run as a non-privileged user. The program doesn’t provide a >> facility to drop privs after binding the ports. I’m planning to run it in a >> jail. >> >> After some googling, it appears that a couple of years ago I should have >> been able to do: >> sysctl net.inet.ip.portrange.reservedhigh=0 >> and allow all processes to bind to „low“ ports. This does not work in my >> jails on a 11-stable host. >> >> $ sudo sysctl net.inet.ip.portrange.reservedhigh=0 >> net.inet.ip.portrange.reservedhigh: 1023 >> sysctl: net.inet.ip.portrange.reservedhigh=0: Operation not permitted >> >> Securelevel should not interfere: >> $ sysctl kern.securelevel >> kern.securelevel: -1 >> >> Is there a way to allow regular processes to bind to low ports? > > Yes. Just use mac_portacl kernel module: kldload mac_portacl > > Once loaded, it duplicates net.inet.ip.portrange.reservedhigh protection > with its own security.mac.portacl.port_high, so it's safe to disable > "reservedhigh" for whole system by running sysctl > net.inet.ip.portrange.reservedhigh=0 > for host. > > The trick is that mac_portacl provides a way to selectively give permission > for non-root UID > to bind low ports: > > security.mac.portacl.rules=uid:88:tcp:80,uid:88:tcp:443,uid:53:tcp:53,uid:53:udp:53 > > It works just fine for a host and I use it for name servers utilizing port 53 > for a box with dynamically created interfaces, so it may bind the port for > distinct IP addresses > after it dropped privilegies when new interface is created and get new IP > assigned. > > I have not tried it for a jails, though. Please try and respond. Thanks, but do I understand correctly that the security.mac.portacl.rules are system-wide and not per-jail? I’m running ~10 jails on this host, and I don’t want to allow all of them to bind to low ports. Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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"
Bind to port <1024 in jail
I have a Go program (acme-dns) that wants to bind 53, 80, and 443, and I’d rather have it run as a non-privileged user. The program doesn’t provide a facility to drop privs after binding the ports. I’m planning to run it in a jail. After some googling, it appears that a couple of years ago I should have been able to do: sysctl net.inet.ip.portrange.reservedhigh=0 and allow all processes to bind to „low“ ports. This does not work in my jails on a 11-stable host. $ sudo sysctl net.inet.ip.portrange.reservedhigh=0 net.inet.ip.portrange.reservedhigh: 1023 sysctl: net.inet.ip.portrange.reservedhigh=0: Operation not permitted Securelevel should not interfere: $ sysctl kern.securelevel kern.securelevel: -1 Is there a way to allow regular processes to bind to low ports? Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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"
Booting off ZFS pool with failed ZIL/cache device
Folks, my ZIL/cache SSD apparently just died. Rebooting the system with the SATA M.2 SSD hung, so I removed the card from the system. On powerup, loader acts normally, all four SATA disks (main Raid-Z1 devices) are all probed successfully, but mount root fails: ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 1.000 msec ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA8-ACS SATA 3.x device ada0: Serial Number Z5Q7K0RIFFRC ada0: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes) ada0: Command Queueing enabled ada0: 4769307MB (9767541168 512 byte sectors) ada1 at ahcich2 bus 0 scbus2 target 0 lun 0 ada1: ATA8-ACS SATA 3.x device ada1: Serial Number Y5PIK0A2FFRC ada1: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes) ada1: Command Queueing enabled ada1: 4769307MB (9767541168 512 byte sectors) ada2 at ahcich3 bus 0 scbus3 target 0 lun 0 ada2: ATA8-ACS SATA 3.x device ada2: Serial Number 36D2K0VZFFRC ada2: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes) ada2: Command Queueing enabled ada2: 4769307MB (9767541168 512 byte sectors) ada3 at ahcich4 bus 0 scbus4 target 0 lun 0 ada3: ATA8-ACS SATA 3.x device ada3: Serial Number Z5SDK0J3FFRC ada3: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes) ada3: Command Queueing enabled ada3: 4769307MB (9767541168 512 byte sectors) pass4 at ahciem0 bus 0 scbus6 target 0 lun 0 pass4: SEMB S-E-S 2.00 device Trying to mount root from zfs:p2/be/11 []... GEOM_MIRROR: Device mirror/p2swap launched (4/4). random: unblocking device. Mounting from zfs:p2/be/11 failed with error 6; retrying for 3 more seconds Mounting from zfs:p2/be/11 failed with error 6. Loader variables: vfs.root.mountfrom=zfs:p2/be/11 Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/cd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot> Is there an easy way to boot into single user mode and remove the ZIL/cache devices that are not there anymore? Or do I need a USB key to boot off of and zfs import the pool first? Thanks, Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: MMC problem on APU2 with 11.2
Am 16.07.2018 um 10:06 schrieb Ruben : > > Hi Stefan, > > > What kind of device are you trying to connect? > > > > Kind regards, > > > Ruben > > On 07/16/2018 08:22 AM, Stefan Bethke wrote: >> Am 15.07.2018 um 13:32 schrieb Ruben : >>> I remember reading somewhere that PC Engines recommends running the >>> "legacy" version of the firmware if the OS is FreeBSD/PFSense etc. Perhaps >>> worth a try to "upgrade" to the legacy series of firmware? >> I’ve just tried with 4.0.18, and the US3 ports don’t work any better. >> Instead, the EHCI controller complains about not being able to set up the >> device properly. I went back to 4.8.0.1. > I'm not a contributer to FreeBSD code (so please don't expect any patches > from me) but if its something I happen to have lying around somewhere I might > be able to reproduce your problem. There's a thread over on freebsd-usb@ with plenty of detail. I have a Transcend USB stick and a Huawei LTE stick that both have problems on the USB3 ports. It appears certain transactions time out or are otherwise not completed successfully. Stefan -- Stefan BethkeFon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: MMC problem on APU2 with 11.2
Am 15.07.2018 um 13:32 schrieb Ruben : > > I remember reading somewhere that PC Engines recommends running the "legacy" > version of the firmware if the OS is FreeBSD/PFSense etc. Perhaps worth a try > to "upgrade" to the legacy series of firmware? I’ve just tried with 4.0.18, and the US3 ports don’t work any better. Instead, the EHCI controller complains about not being able to set up the device properly. I went back to 4.8.0.1. Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: MMC problem on APU2 with 11.2
> Am 14.07.2018 um 16:34 schrieb Ruben : > > Hi Graham, > > On 07/14/2018 06:03 AM, Graham Menhennitt wrote: >> This probably isn't much use to you, but I'm running FreeBSD 11-Stable on >> two APU2s. But I'm booting from SSD, not SDHC. No problems here. >> >> Graham >> ___ > > Thank you for your feedback. Good to hear more list ppl are running APU2's :) > > I think the issue was triggered by the SDHC/MMC driver in 11.2 and the APU2's > firmware because after updating the firmware I ran (4.0.7) to the most recent > firmware available on https://pcengines.github.io/#lr-10 (4.0.18 legacy), the > problem was solved. > > Since PC Engines advises users to only run the github firmware if users have > the possibility to de-brick their units (which I only learned about > afterwards and requires special hardware..) I guess some caution is advised. > > > The board seems to be running fine with 11.2 now so I'm happy :) I’m having problems with the two USB3 ports at the back, and I have the non-legacy BIOS version 4.8.0.1. Are USB devices working as expected for you? Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: Unable to boot memstick on APU2
It appears that I just got lucky the one time. The same USB stick continues to mount only about half the time; other USB devices also have problems. It appears to me that the APU2 USB3 controller is not working correctly. I’ve started a new thread over on freebsd-usb@ Stefan > Am 09.07.2018 um 13:12 schrieb Stefan Bethke : > > Thanks for the suggestions! > > I did manage to get a working stick; the first couple of tries I did from m > MacBook Pro; finally I moved the stick to a physical FreeBSD box. Maybe the > Mac somehow "repaired" the GPT/MBR on the stick, making it invisible to the > FreeBSD kernel? But then at least da0 should have shown up. Maybe I just got > lucky. > > If anyone is interested, I can try re-creating the issues for a week or two > while I still have the APU in a lab setting. > > Stefan > >> Am 08.07.2018 um 18:02 schrieb Stefan Bethke : >> >> I'm stumped by a weird error: loader loads the kernel, and the kernel probes >> the USB stick successfully, but da0 never shows up. I’ve tried with >> FreeBSD-11.1-RELEASE-amd64-memstick.img and >> FreeBSD-11.2-RELEASE-amd64-memstick.img. >> >> While at the mount root prompt, unplugging and replugging the USB stick and >> entering . repeatedly will show the kernel messages, but "da0 at umass0" >> never shows up. >> >> I’ve added a couple entries to /boot/loader.conf: >> # cat /mnt/boot/loader.conf >> vfs.mountroot.timeout="10" >> beastie_disable="YES" >> comconsole_speed="115200" >> console="comconsole" >> autoboot_delay="1" >> >> >> Here’s the console output from 11.1: >> Consoles: internal video/keyboard ce+0x67 >> BIOS drive C: is disk0 t vpanic+0x177 >> BIOS drive D: is disk1 t panic+0x43 >> BIOS 638kB/3668660kB available memory +0x1d95 >> 4 0x80a93b68 at start_init+0x48 >> FreeBSD/x86 bootstrap loader, Revision 1.1 >> (Fri Jul 21 02:03:08 UTC 2017 r...@releng2.nyi.freebsd.org) >> Loading /boot/defaults/loader.conf >> //boot/kernel/kernel text=0x14972f8 data=0x1384c0+0x4c15e8 >> syms=[0x8+0x15e8b0+0x8+0x178422]ild 20170228 >> /080 MB ECC DRAM >> Hit [Enter] to boot immediately, or any other key for command prompt. >> Booting [/boot/kernel/kernel]... >> Copyright (c) 1992-2017 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 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017 >> r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >> FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM >> 4.0.0) >> VT(vga): resolution 640x480 >> CPU: AMD GX-412TC SOC(998.15-MHz K8-class >> CPU) >> Origin="AuthenticAMD" Id=0x730f01 Family=0x16 Model=0x30 Stepping=1 >> Features=0x178bfbff >> Features2=0x3ed8220b >> AMD Features=0x2e500800 >> AMD >> Features2=0x1d4037ff >> Structured Extended Features=0x8 >> XSAVE Features=0x1 >> SVM: NP,NRIP,AFlush,DAssist,NAsids=8 >> TSC: P-state invariant, performance statistics >> real memory = 4815060992 (4592 MB) >> avail memory = 4087992320 (3898 MB) >> Event timer "LAPIC" quality 100 >> ACPI APIC Table: >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> FreeBSD/SMP: 1 package(s) x 4 core(s) >> ioapic1: Changing APIC ID to 5 >> ioapic0 irqs 0-23 on motherboard >> ioapic1 irqs 24-55 on motherboard >> SMP: AP CPU #1 Launched! >> SMP: AP CPU #2 Launched! >> SMP: AP CPU #3 Launched! >> Timecounter "TSC" frequency 998148849 Hz quality 1000 >> random: entropy device external interface >> kbd0 at kbdmux0 >> netmap: loaded module >> module_register_init: MOD_LOAD (vesa, 0x80f5b220, 0) error 19 >> nexus0 >> vtvga0: on motherboard >> cryptosoft0: on motherboard >> acpi0: on motherboard >> acpi0: Power Button (fixed) >> cpu0: on acpi0 >> cpu1: on acpi0 >> cpu2: on acpi0 >> cpu3: on acpi0 >> atrtc0: port 0x70-0x71 irq 8 on acpi0 >> Event timer "RTC" frequency 32768 Hz quality 0 >> attimer0: port 0x40-0x43 irq 0 on acpi0 >> Timecounter "i8254" frequency 1193182 Hz quality 0 >> Event timer "i8254" frequency 1193182 Hz quality 100 >> Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 >> acpi_timer0
Re: Passing through USB serial to bhyve VM
FWIW, I’ve opened a bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229712 > Am 11.07.2018 um 23:41 schrieb Stefan Bethke : > > It’s been a while since I last dealt with serial devices. Apparently, when > passing through a serial device on the host to a COM port in the VM, CTS/RTS > are not (correctly) passed through. With >set ctsrts off > in ppp.conf I could get ppp to dial successfully. > > > Stefan > >> Am 11.07.2018 um 19:22 schrieb Stefan Bethke : >> >> I’m trying to access a Huawei USB LTE stick from a Bhyve VM like so: >> # cat /var/vm/mgmt/mgmt.conf >> loader="bhyveload" >> cpu=1 >> memory=256M >> network0_type="virtio-net" >> network0_switch="lan" >> disk0_type="virtio-blk" >> disk0_name="disk0" >> disk0_dev="sparse-zvol" >> uuid="53854567-8358-11e8-9638-000db94be2cc" >> network0_mac="58:9c:fc:04:1d:52" >> bhyve_options="-lcom2,/dev/cuaU0“ >> >> On the host, I can connect ppp(8), but inside the VM, ppp(8) appears not to >> be able to talk to the USB device. Using cu(1), I can talk to it just fine >> though. I’m not sure how to debug this further. Is this supposed to just >> work, or am I missing some obvious configuration bit? >> >> [root@mgmt ~]# cu -l cuau1 -s 115200 >> Connected >> ATZ >> OK >> ATI >> Manufacturer: huawei >> Model: E3272 >> Revision: 22.436.07.02.1202 >> IMEI: 867503015nn >> +GCAP: +CGSM,+DS,+ES >> >> OK >> ~ >> [EOT] >> [root@mgmt ~]# ppp >> Working in interactive mode >> Using interface: tun0 >> Phase: PPP Started (interactive mode). >> ppp ON mgmt> dial >> Phase: bundle: Establish >> Phase: deflink: closed -> opening >> Phase: deflink: Connected! >> Phase: deflink: opening -> dial >> Chat: deflink: Dial attempt 1 of 1 >> ppp ON mgmt> Chat: Send: ATZ >> Chat: Expect(5): OK >> Chat: Expect timeout >> Chat: Send: ATZ >> Chat: Expect(5): OK >> Chat: Expect timeout >> Warning: Chat script failed >> Phase: deflink: dial -> hangup >> Phase: deflink: Disconnected! >> Phase: deflink: Connect time: 11 secs: 0 octets in, 0 octets out >> Phase: deflink: 0 packets in, 0 packets out >> Phase: total 0 bytes/sec, peak 0 bytes/sec on Wed Jul 11 21:14:43 2018 >> Phase: deflink: hangup -> closed >> Phase: bundle: Dead >> ppp ON mgmt> quit >> [root@mgmt ~]# cat /etc/ppp/ppp.conf >> default: >> enable dns >> set log local LCP IPCP Phase Chat >> set log all >> set timeout 0 >> ident UMTS >> set authname eplus >> set authkey internet >> set cd off >> set device /dev/cuau1 >> set speed 115200 >> set dial "ABORT BUSY ABORT NO\\sCARRIER \ >> ABORT VOICE ABORT NO\\sDIALTONE ABORT NO\\sDIAL\\sTONE ABORT ERROR \ >> ABORT NO\\sANSWER ABORT DELAYED TIMEOUT 5 \ >> \"\" ATZ OK-ATZ-OK \ >> AT+CFUN=1 OK \ >> AT+CREG? OK \ >> AT+COPS? OK \ >> AT+CSQ OK \ >> AT^HCSQ? OK \ >> AT+cgdcont=1,\\\"IP\\\",\\\"internet.eplus.de\\\" OK \ >> ATDT*99***1# CONNECT" >> set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 >> add default HISADDR >> >> >> Stefan >> >> -- >> Stefan BethkeFon +49 151 14070811 >> >> >> ___ >> 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" > > -- > Stefan BethkeFon +49 151 14070811 > > > ___ > 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" -- Stefan BethkeFon +49 151 14070811 ___ 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: Passing through USB serial to bhyve VM
It’s been a while since I last dealt with serial devices. Apparently, when passing through a serial device on the host to a COM port in the VM, CTS/RTS are not (correctly) passed through. With set ctsrts off in ppp.conf I could get ppp to dial successfully. Stefan > Am 11.07.2018 um 19:22 schrieb Stefan Bethke : > > I’m trying to access a Huawei USB LTE stick from a Bhyve VM like so: > # cat /var/vm/mgmt/mgmt.conf > loader="bhyveload" > cpu=1 > memory=256M > network0_type="virtio-net" > network0_switch="lan" > disk0_type="virtio-blk" > disk0_name="disk0" > disk0_dev="sparse-zvol" > uuid="53854567-8358-11e8-9638-000db94be2cc" > network0_mac="58:9c:fc:04:1d:52" > bhyve_options="-lcom2,/dev/cuaU0“ > > On the host, I can connect ppp(8), but inside the VM, ppp(8) appears not to > be able to talk to the USB device. Using cu(1), I can talk to it just fine > though. I’m not sure how to debug this further. Is this supposed to just > work, or am I missing some obvious configuration bit? > > [root@mgmt ~]# cu -l cuau1 -s 115200 > Connected > ATZ > OK > ATI > Manufacturer: huawei > Model: E3272 > Revision: 22.436.07.02.1202 > IMEI: 867503015nn > +GCAP: +CGSM,+DS,+ES > > OK > ~ > [EOT] > [root@mgmt ~]# ppp > Working in interactive mode > Using interface: tun0 > Phase: PPP Started (interactive mode). > ppp ON mgmt> dial > Phase: bundle: Establish > Phase: deflink: closed -> opening > Phase: deflink: Connected! > Phase: deflink: opening -> dial > Chat: deflink: Dial attempt 1 of 1 > ppp ON mgmt> Chat: Send: ATZ > Chat: Expect(5): OK > Chat: Expect timeout > Chat: Send: ATZ > Chat: Expect(5): OK > Chat: Expect timeout > Warning: Chat script failed > Phase: deflink: dial -> hangup > Phase: deflink: Disconnected! > Phase: deflink: Connect time: 11 secs: 0 octets in, 0 octets out > Phase: deflink: 0 packets in, 0 packets out > Phase: total 0 bytes/sec, peak 0 bytes/sec on Wed Jul 11 21:14:43 2018 > Phase: deflink: hangup -> closed > Phase: bundle: Dead > ppp ON mgmt> quit > [root@mgmt ~]# cat /etc/ppp/ppp.conf > default: >enable dns >set log local LCP IPCP Phase Chat > set log all >set timeout 0 >ident UMTS >set authname eplus >set authkey internet >set cd off >set device /dev/cuau1 >set speed 115200 >set dial "ABORT BUSY ABORT NO\\sCARRIER \ >ABORT VOICE ABORT NO\\sDIALTONE ABORT NO\\sDIAL\\sTONE ABORT ERROR \ >ABORT NO\\sANSWER ABORT DELAYED TIMEOUT 5 \ >\"\" ATZ OK-ATZ-OK \ >AT+CFUN=1 OK \ >AT+CREG? OK \ >AT+COPS? OK \ >AT+CSQ OK \ > AT^HCSQ? OK \ >AT+cgdcont=1,\\\"IP\\\",\\\"internet.eplus.de\\\" OK \ >ATDT*99***1# CONNECT" > set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 >add default HISADDR > > > Stefan > > -- > Stefan BethkeFon +49 151 14070811 > > > ___ > 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" -- Stefan BethkeFon +49 151 14070811 ___ 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"
Passing through USB serial to bhyve VM
I’m trying to access a Huawei USB LTE stick from a Bhyve VM like so: # cat /var/vm/mgmt/mgmt.conf loader="bhyveload" cpu=1 memory=256M network0_type="virtio-net" network0_switch="lan" disk0_type="virtio-blk" disk0_name="disk0" disk0_dev="sparse-zvol" uuid="53854567-8358-11e8-9638-000db94be2cc" network0_mac="58:9c:fc:04:1d:52" bhyve_options="-lcom2,/dev/cuaU0“ On the host, I can connect ppp(8), but inside the VM, ppp(8) appears not to be able to talk to the USB device. Using cu(1), I can talk to it just fine though. I’m not sure how to debug this further. Is this supposed to just work, or am I missing some obvious configuration bit? [root@mgmt ~]# cu -l cuau1 -s 115200 Connected ATZ OK ATI Manufacturer: huawei Model: E3272 Revision: 22.436.07.02.1202 IMEI: 867503015nn +GCAP: +CGSM,+DS,+ES OK ~ [EOT] [root@mgmt ~]# ppp Working in interactive mode Using interface: tun0 Phase: PPP Started (interactive mode). ppp ON mgmt> dial Phase: bundle: Establish Phase: deflink: closed -> opening Phase: deflink: Connected! Phase: deflink: opening -> dial Chat: deflink: Dial attempt 1 of 1 ppp ON mgmt> Chat: Send: ATZ Chat: Expect(5): OK Chat: Expect timeout Chat: Send: ATZ Chat: Expect(5): OK Chat: Expect timeout Warning: Chat script failed Phase: deflink: dial -> hangup Phase: deflink: Disconnected! Phase: deflink: Connect time: 11 secs: 0 octets in, 0 octets out Phase: deflink: 0 packets in, 0 packets out Phase: total 0 bytes/sec, peak 0 bytes/sec on Wed Jul 11 21:14:43 2018 Phase: deflink: hangup -> closed Phase: bundle: Dead ppp ON mgmt> quit [root@mgmt ~]# cat /etc/ppp/ppp.conf default: enable dns set log local LCP IPCP Phase Chat set log all set timeout 0 ident UMTS set authname eplus set authkey internet set cd off set device /dev/cuau1 set speed 115200 set dial "ABORT BUSY ABORT NO\\sCARRIER \ ABORT VOICE ABORT NO\\sDIALTONE ABORT NO\\sDIAL\\sTONE ABORT ERROR \ ABORT NO\\sANSWER ABORT DELAYED TIMEOUT 5 \ \"\" ATZ OK-ATZ-OK \ AT+CFUN=1 OK \ AT+CREG? OK \ AT+COPS? OK \ AT+CSQ OK \ AT^HCSQ? OK \ AT+cgdcont=1,\\\"IP\\\",\\\"internet.eplus.de\\\" OK \ ATDT*99***1# CONNECT" set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR Stefan -- Stefan BethkeFon +49 151 14070811 ___ 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: Unable to boot memstick on APU2
Thanks for the suggestions! I did manage to get a working stick; the first couple of tries I did from m MacBook Pro; finally I moved the stick to a physical FreeBSD box. Maybe the Mac somehow "repaired" the GPT/MBR on the stick, making it invisible to the FreeBSD kernel? But then at least da0 should have shown up. Maybe I just got lucky. If anyone is interested, I can try re-creating the issues for a week or two while I still have the APU in a lab setting. Stefan > Am 08.07.2018 um 18:02 schrieb Stefan Bethke : > > I'm stumped by a weird error: loader loads the kernel, and the kernel probes > the USB stick successfully, but da0 never shows up. I’ve tried with > FreeBSD-11.1-RELEASE-amd64-memstick.img and > FreeBSD-11.2-RELEASE-amd64-memstick.img. > > While at the mount root prompt, unplugging and replugging the USB stick and > entering . repeatedly will show the kernel messages, but "da0 at umass0" > never shows up. > > I’ve added a couple entries to /boot/loader.conf: > # cat /mnt/boot/loader.conf > vfs.mountroot.timeout="10" > beastie_disable="YES" > comconsole_speed="115200" > console="comconsole" > autoboot_delay="1" > > > Here’s the console output from 11.1: > Consoles: internal video/keyboard ce+0x67 > BIOS drive C: is disk0 t vpanic+0x177 > BIOS drive D: is disk1 t panic+0x43 > BIOS 638kB/3668660kB available memory +0x1d95 > 4 0x80a93b68 at start_init+0x48 > FreeBSD/x86 bootstrap loader, Revision 1.1 > (Fri Jul 21 02:03:08 UTC 2017 r...@releng2.nyi.freebsd.org) > Loading /boot/defaults/loader.conf > //boot/kernel/kernel text=0x14972f8 data=0x1384c0+0x4c15e8 > syms=[0x8+0x15e8b0+0x8+0x178422]ild 20170228 > /080 MB ECC DRAM > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel]... > Copyright (c) 1992-2017 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 11.1-RELEASE #0 r321309: Fri Jul 21 02:08:28 UTC 2017 >r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM > 4.0.0) > VT(vga): resolution 640x480 > CPU: AMD GX-412TC SOC(998.15-MHz K8-class CPU) > Origin="AuthenticAMD" Id=0x730f01 Family=0x16 Model=0x30 Stepping=1 > > Features=0x178bfbff > > Features2=0x3ed8220b > AMD Features=0x2e500800 > AMD > Features2=0x1d4037ff > Structured Extended Features=0x8 > XSAVE Features=0x1 > SVM: NP,NRIP,AFlush,DAssist,NAsids=8 > TSC: P-state invariant, performance statistics > real memory = 4815060992 (4592 MB) > avail memory = 4087992320 (3898 MB) > Event timer "LAPIC" quality 100 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) > ioapic1: Changing APIC ID to 5 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-55 on motherboard > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > Timecounter "TSC" frequency 998148849 Hz quality 1000 > random: entropy device external interface > kbd0 at kbdmux0 > netmap: loaded module > module_register_init: MOD_LOAD (vesa, 0x80f5b220, 0) error 19 > nexus0 > vtvga0: on motherboard > cryptosoft0: on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > atrtc0: port 0x70-0x71 irq 8 on acpi0 > Event timer "RTC" frequency 32768 Hz quality 0 > attimer0: port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x818-0x81b on acpi0 > hpet0: iomem 0xfed0-0xfed003ff on acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 950 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 2.2 on pci0 > pcib1: failed to allocate initial I/O port window: 0x1000-0x1fff > pci1: on pcib1 > igb0: mem > 0xfe60-0xfe61,0xfe62-0xfe623fff at device 0.0 on pci1 > igb0: Using MSIX interrupts with 5 vectors > igb0: Ethernet address: 00:0d:b9:4b:e2:cc > igb0: Bound queue 0 to cpu 0 > igb0: Bound queue 1 to cpu 1 > igb0: Bound queue 2 to cpu 2 > igb0: Bound queue 3 to cpu 3 > igb0: netmap queues/sl
Unable to boot memstick on APU2
B v3.0 ahci0: port 0x4010-0x4017,0x4020-0x4023,0x4018-0x401f,0x4024-0x4027,0x4000-0x400f mem 0xfeb25000-0xfeb253ff at device 17.0 on pci0 ahci0: AHCI v1.30 with 2 6Gbps ports, Port Multiplier supported with FBS ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ehci0: mem 0xfeb25400-0xfeb254ff at device 19.0 on pci0 usbus1: EHCI version 1.0 usbus1 on ehci0 usbus1: 480Mbps High Speed USB v2.0 isab0: at device 20.3 on pci0 isa0: on isab0 sdhci_pci0: mem 0xfeb25500-0xfeb255ff at device 20.7 on pci0 sdhci_pci0: 1 slot(s) allocated uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: console (115200,n,8,1) orm0: at iomem 0xef000-0xe on isa0 ppc0: cannot reserve I/O port range uart1: <16550 or compatible> at port 0x2f8 irq 3 on isa0 hwpstate0: on cpu0 Timecounters tick every 1.000 msec nvme cam probe device init ugen1.1: at usbus1 ugen0.1: <0x1022 XHCI root HUB> at usbus0 uhub0: on usbus1 uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ACS-4 ATA SATA 3.x device ada0: Serial Number A4620782148900312898 ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 15272MB (31277232 512 byte sectors) Trying to mount root from ufs:/dev/ufs/FreeBSD_Install [ro,noatime]... Root mount waiting for: usbus1 usbus0 uhub1: 4 ports with 4 removable, self powered uhub0: 2 ports with 2 removable, self powered Root mount waiting for: usbus1 usbus0 ugen1.2: at usbus1 uhub2 on uhub0 uhub2: on usbus1 Root mount waiting for: usbus1 usbus0 ugen0.2: at usbus0 umass0 on uhub1 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x8100 umass0:2:0: Attached to scbus2 uhub2: 4 ports with 4 removable, self powered mountroot: waiting for device /dev/ufs/FreeBSD_Install... Mounting from ufs:/dev/ufs/FreeBSD_Install failed with error 19. Loader variables: vfs.root.mountfrom=ufs:/dev/ufs/FreeBSD_Install vfs.root.mountfrom.options=ro,noatime Manual root filesystem specification: : [options] Mount using filesystem and with the specified (optional) option list. eg. ufs:/dev/da0s1a zfs:tank cd9660:/dev/cd0 ro (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) ? List valid disk boot devices . Yield 1 second (for background tasks) Abort manual input mountroot> ? List of GEOM managed disk devices: diskid/DISK-A4620782148900312898 ada0 mountroot> . mountroot> ? List of GEOM managed disk devices: diskid/DISK-A4620782148900312898 ada0 -- Stefan BethkeFon +49 151 14070811 ___ 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: 802.1X authenticator for FreeBSD
> Am 18.10.2017 um 18:35 schrieb Peter Ankerstål <pe...@pean.org>: > > > >> On 17 Oct 2017, at 22:27, Chris Ross <cross+free...@distal.com> wrote: >> >> >> wpa_supplicant is the client we use at work, on Linux systems. But, it’s >> also the tool described in the FreeBSD wireless configuration pages, so I >> know it can be used there. >> >> I haven’t tried FreeBSD with wired 802.1x myself, but just a thought I had. >> >> - Chris >> > Its my understanding that wpa_supplicant is actually a working client in > FreeBSD. But I’m looking for the server side of this. > > It would be just fine if it worked just like hostapd (control access of one > nic) and dont have any control over switchports or whatever. Another nice way > of doing it would be to have some sort of integration with authpf or pf > itself. I’m under the impression that the authenticator function in a wired network is usually part of the switch, and the switch will talk to some authentication server like RADIUS, giving it the port number of the connected device and additional information. If FreeBSD had such a function, I think it would be limited to point-to-point Ethernet links, 802.1x being a link-layer protocol. Stefan -- Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 signature.asc Description: Message signed with OpenPGP
Re: Trouble with SM961 in SuperMicro X11
It’s an SM961, not PM951. > Am 21.07.2017 um 20:24 schrieb Stefan Bethke <s...@lassitu.de>: > > I have a fresh SuperMicro SYS-5019S-M and I’ve installed a Samsung SM961 > 128GBB, which I want to use as a ZFS cache. > > After installing 11.1-RC3, I’m getting the below errors during boot, and > trying to read or write to it produces the same message. > > Is there a tunable to make this work? A quick test with Windows did not show > any issues. > > > Stefan > > -- > Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 > > > > Copyright (c) 1992-2017 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 11.1-RC3 #0 r320976: Fri Jul 14 02:20:44 UTC 2017 >r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM > 4.0.0) > VT(vga): resolution 640x480 > CPU: Intel(R) Xeon(R) CPU E3-1240 v6 @ 3.70GHz (3696.16-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x906e9 Family=0x6 Model=0x9e Stepping=9 > > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND> > AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM> > AMD Features2=0x121<LAHF,ABM,Prefetch> > Structured Extended > Features=0x29c6fbf<FSGSBASE,TSCADJ,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE> > XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES> > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > TSC: P-state invariant, performance statistics > real memory = 68719476736 (65536 MB) > avail memory = 8195840 (63579 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: < > > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads > random: unblocking device. > ioapic0 irqs 0-23 on motherboard > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #4 Launched! > SMP: AP CPU #5 Launched! > SMP: AP CPU #6 Launched! > SMP: AP CPU #7 Launched! > Timecounter "TSC-low" frequency 1848080854 Hz quality 1000 > random: entropy device external interface > kbd1 at kbdmux0 > netmap: loaded module > module_register_init: MOD_LOAD (vesa, 0x80f5b220, 0) error 19 > random: registering fast source Intel Secure Key RNG > random: fast provider: "Intel Secure Key RNG" > nexus0 > vtvga0: on motherboard > cryptosoft0: on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > cpu4: on acpi0 > cpu5: on acpi0 > cpu6: on acpi0 > cpu7: on acpi0 > hpet0: iomem 0xfed0-0xfed003ff on acpi0 > Timecounter "HPET" frequency 2400 Hz quality 950 > Event timer "HPET" frequency 2400 Hz quality 550 > atrtc0: port 0x70-0x77 irq 8 on acpi0 > atrtc0: Warning: Couldn't map I/O. > Event timer "RTC" frequency 32768 Hz quality 0 > attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pci0: <old, non-VGA display device> at device 19.0 (no driver attached) > xhci0: mem 0xdf40-0xdf40 irq > 16 at device 20.0 on pci0 > xhci0: 32 bytes context size, 64-bit DMA > usbus0 on xhci0 > usbus0: 5.0Gbps Super Speed USB v3.0 > pci0: at device 22.0 (no driver attached) > pci0: at device 22.1 (no driver attached) > ahci0: port > 0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem > 0xdf41-0xdf411fff,0xdf41e000-0xdf41e0ff,0xdf41d000-0xdf41d7ff irq 16 at > device 23.0 on pci0 > ahci0: AHCI v1.31 with 8 6Gbps ports, Port Multiplier not supported > ahcich0: at channel 0 on ahci0 > ahcich1: at channel 1 on ahci0 > ahcich2: at channel 2 on ahci0 > ahcich3: at channel 3 on ahci0 > ahcich4: at channel 4 on ahci0 > ahcich5: at channel 5 on ahci0 > ahcich6: at channel 6 on ahci0 > ahcich7: at channel 7 on ahci0 > a
Trouble with PM961 in SuperMicro X11
I have a fresh SuperMicro SYS-5019S-M and I’ve installed a Samsung SM961 128GBB, which I want to use as a ZFS cache. After installing 11.1-RC3, I’m getting the below errors during boot, and trying to read or write to it produces the same message. Is there a tunable to make this work? A quick test with Windows did not show any issues. Stefan -- Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 Copyright (c) 1992-2017 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 11.1-RC3 #0 r320976: Fri Jul 14 02:20:44 UTC 2017 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) VT(vga): resolution 640x480 CPU: Intel(R) Xeon(R) CPU E3-1240 v6 @ 3.70GHz (3696.16-MHz K8-class CPU) Origin="GenuineIntel" Id=0x906e9 Family=0x6 Model=0x9e Stepping=9 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND> AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM> AMD Features2=0x121<LAHF,ABM,Prefetch> Structured Extended Features=0x29c6fbf<FSGSBASE,TSCADJ,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,NFPUSG,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PROCTRACE> XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 68719476736 (65536 MB) avail memory = 8195840 (63579 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: < > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads random: unblocking device. ioapic0 irqs 0-23 on motherboard SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #7 Launched! Timecounter "TSC-low" frequency 1848080854 Hz quality 1000 random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0x80f5b220, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 vtvga0: on motherboard cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 2400 Hz quality 950 Event timer "HPET" frequency 2400 Hz quality 550 atrtc0: port 0x70-0x77 irq 8 on acpi0 atrtc0: Warning: Couldn't map I/O. Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: <old, non-VGA display device> at device 19.0 (no driver attached) xhci0: mem 0xdf40-0xdf40 irq 16 at device 20.0 on pci0 xhci0: 32 bytes context size, 64-bit DMA usbus0 on xhci0 usbus0: 5.0Gbps Super Speed USB v3.0 pci0: at device 22.0 (no driver attached) pci0: at device 22.1 (no driver attached) ahci0: port 0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem 0xdf41-0xdf411fff,0xdf41e000-0xdf41e0ff,0xdf41d000-0xdf41d7ff irq 16 at device 23.0 on pci0 ahci0: AHCI v1.31 with 8 6Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 ahcich4: at channel 4 on ahci0 ahcich5: at channel 5 on ahci0 ahcich6: at channel 6 on ahci0 ahcich7: at channel 7 on ahci0 ahciem0: on ahci0 pcib1: irq 16 at device 28.0 on pci0 pci1: on pcib1 igb0: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xe000-0xe01f mem 0xdf30-0xdf37,0xdf38-0xdf383fff irq 16 at device 0.0 on pci1 igb0: Using MSIX interrupts with 5 vectors igb0: Ethernet address: ac:1f:6b:18:06:6e igb0: Bound queue 0 to cpu 0 igb0: Bound queue 1 to cpu 1 igb0: Bound queue 2 to cpu 2 igb0: Bound queue 3 to cpu 3 igb0: netmap queues/slots: TX 4/1024, RX 4/1024 pcib2: irq 17 at device 28.1 on pci0 pci2: on pcib2 igb1: <Intel(R) PRO/1000 Network Connection, Version - 2.5.3-k> port 0xd000-0xd01f mem 0xdf
Re: 11 stable vagrant images: page fault
> Am 07.05.2017 um 07:11 schrieb jungle boogie <jungleboog...@gmail.com>: > > I'm using 11-stable Vagrant image from here: > https://atlas.hashicorp.com/freebsd/boxes/FreeBSD-11.0-STABLE > (tried 20th of April and 5th of April). > > Unfortunately, I can only get the VM to stay up for about 9 seconds, because > it's in a constant reboot loop. > > This command will stop the reboot: > VBoxManage setextradata stable_default_1494131864056_36337 > "VBoxInternal/PDM/HaltOnReset" 1 > > And when doing so, I see this failure: > http://imgur.com/a/USHdB > > I can download 11-stable and 12-current vdh files and import those into > virtualbox, resulting in those not crashing. > 11-stable is from the 20th of April. Out of curiosity, can you try: https://atlas.hashicorp.com/stblassitude/boxes/freebsd-11 I was unhappy with the official images, so I’m building my own. On my Mac, I can run my image (including the latest freebsd-update patches), without problems. The main difference in my image is that the freebsd-update patches are already rolled into the image, so there’s no reboot cycle with vagrant up. I’m updating the image every couple of weeks. The packer config is at https://github.com/stblassitude/packer-freebsd Stefan -- Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 ___ 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: zpool asize problem on 11.0
> Am 12.01.2017 um 23:29 schrieb Stefan Bethke <s...@lassitu.de>: > > I’ve just created two pools on a freshly partitioned disk, using 11.0 amd64, > and the shift appears to be 9: > > # zpool status -v host > pool: host > state: ONLINE > status: One or more devices are configured to use a non-native block size. > Expect reduced performance. > action: Replace affected devices with devices that support the > configured block size, or migrate data to a properly configured > pool. > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > host ONLINE 0 0 0 > gpt/host0 ONLINE 0 0 0 block size: 512B configured, > 4096B native > > errors: No known data errors > > # zdb host | grep ashift >ashift: 9 >ashift: 9 > > But: > # sysctl vfs.zfs.min_auto_ashift > vfs.zfs.min_auto_ashift: 12 > > Of course, I’ve noticed this only after restoring all the backups, and > getting ready to put the box back into production. > > Is this expected behaviour? I guess there’s no simple fix, and I have to > start over from scratch? I had falsely assumed that vfs.zfs.min_auto_ashift would be 12 in all circumstances. It appears when running FreeBSD 11.0p2 in VirtualBox, it can be 9. And my target disk was attached to the host and mapped into the VM as a „native disk image“, but the 4k native sector size apparently got lost in that abstraction. The output above is with the disk installed in the target system with a native AHCI connection, and the system booted from that disk. I’ve certainly learned to double check the ashift property on creating pools. Stefan -- Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 ___ 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"
zpool asize problem on 11.0
I’ve just created two pools on a freshly partitioned disk, using 11.0 amd64, and the shift appears to be 9: # zpool status -v host pool: host state: ONLINE status: One or more devices are configured to use a non-native block size. Expect reduced performance. action: Replace affected devices with devices that support the configured block size, or migrate data to a properly configured pool. scan: none requested config: NAME STATE READ WRITE CKSUM host ONLINE 0 0 0 gpt/host0 ONLINE 0 0 0 block size: 512B configured, 4096B native errors: No known data errors # zdb host | grep ashift ashift: 9 ashift: 9 But: # sysctl vfs.zfs.min_auto_ashift vfs.zfs.min_auto_ashift: 12 Of course, I’ve noticed this only after restoring all the backups, and getting ready to put the box back into production. Is this expected behaviour? I guess there’s no simple fix, and I have to start over from scratch? Stefan -- Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 ___ 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: Upgrading boot from GPT(BIOS) to GPT(UEFI)
> Am 17.12.2016 um 07:12 schrieb Ian Smith <smi...@nimnet.asn.au>: > > On Fri, 16 Dec 2016 18:08:34 +0100, Fernando Herrero Carrón wrote: >> My only reason for wanting to boot with UEFI is faster boot, >> everything is working fine otherwise. > > I'm skeptical that UEFI boot would be any or noticeably faster than via > BIOS, but am interested in hearing of any experiences regarding that. In a very quick test with VirtualBox with 10.3-Release, ZFS, booting with BIOS and autoboot_delay=0, it takes 15 seconds to display „Booting…“. With 11.0-R and BIOS it takes about 12. With 11.0-R and EFI enabled, it takes less than 3 seconds. On real hardware other factors will likely diminish the difference. Stefan -- Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 ___ 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: Uppercase RE matching problems in FreeBSD 11
Am 06.11.2016 um 22:27 schrieb Baptiste Daroussin <b...@freebsd.org>: > >> But under what circumstances would [A-Z] mean anything other than a >> character whose Unicode codepoint is between U+0041 and U+005A, inclusive? >> Especially given the locale in the example is en_US.UTF-8. Or, put another >> way, why would an implementation interpret [A-Z] as anything other than >> [ABCDE…XYZ]? > > The collation rules for unicode comes from: http://cldr.unicode.org/ and they > do > match the one on linux for example and the one on illumos. > > On some gnu tool they explicitly decide to be non locale aware to avoid that > kind of "surprises" >> >> From reading your reference, I can see in 9.3.5.7: >>> In the POSIX locale, a range expression represents the set of collating >>> elements that fall between two elements in the collation sequence, >>> inclusive. In other locales, a range expression has unspecified behavior[…] >> >> So even if the observed behaviour is conforming, I’d think it’s still highly >> undesirable. >> > That works for POSIX locale aka C aka ASCII only world So what do I set my LANG and LC variables to? I do want UTF-8, but I do also want my scripts to continue to work. Clearly, en_US.UTF-8 is not what I want. Is it C.UTF-8? Or do I set LANG=en_US.UTF-8 and LC_COLLATE=C? Stefan -- Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 ___ 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: Uppercase RE matching problems in FreeBSD 11
> Am 06.11.2016 um 22:14 schrieb Stefan Ehmann <shoes...@gmx.net>: > >> That is rather surprising. Is there a normative reference for the >> treatment of bracket expressions and character classes when using >> locales other than C and/or encodings like UTF-8? > > I found an interesting article about this issue in gawk: > https://www.gnu.org/software/gawk/manual/html_node/Ranges-and-Locales.html OK, I give up. Back to jwz: "now you have two problems.“ Although with en_US.UTF-8 on other systems, I have not had that experience. A quick check on stuff I have immediate access to: macOS 10.12: $ echo 'abcdABCD' | sed 's/[A-Z]/X/g’ abcd Ubuntu 14.04.5 $ echo 'abcdABCD' | sed 's/[A-Z]/X/g’ abcd FreeBSD 10-stable $ echo 'abcdABCD' | sed 's/[A-Z]/X/g' abcd Stefan -- Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 ___ 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: Uppercase RE matching problems in FreeBSD 11
> Am 06.11.2016 um 22:06 schrieb Baptiste Daroussin <b...@freebsd.org>:
>
> On Sun, Nov 06, 2016 at 09:57:00PM +0100, Stefan Bethke wrote:
>>
>>> Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin <b...@freebsd.org>:
>>>
>>> On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote:
>>>> I happened to run an old script today that uses sed(1) to extract the
>>>> system
>>>> boot time from the kern.boottime sysctl MIB. On 11.0 this no longer works
>>>> as
>>>> expected:
>>>>
>>>> $ sysctl kern.boottime
>>>> kern.boottime: { sec = 1478380714, usec = 145351 } Sat Nov 5 16:18:34 2016
>>>> $ sysctl kern.boottime | sed -e 's/.*\([A-Z].*\)$/\1/'
>>>> v 5 16:18:34 2016
>>>>
>>>> sed passes over 'S' and 'N' until it hits 'v', which it considers uppercase
>>>> apparently. This is with LANG=en_US.UTF-8. If I set LANG=C, it works as
>>>> expected:
>>>>
>>>> $ sysctl kern.boottime | LANG=C sed -e 's/.*\([A-Z].*\)$/\1/'
>>>> Nov 5 16:18:34 2016
>>>>
>>>> Testing every lowercase character separately gives even more inconsistent
>>>> results:
>>>>
>>>> $ cat <>
>>>> Here sed thinks every lowercase character except for 'a' is uppercase! This
>>>> differs from the first test where sed did not think 'o' is uppercase.
>>>> Again,
>>>> the above behaves as expected with LANG=C.
>>>>
>>>> Does anyone have any insight into this? This is likely to break a lot of
>>>> existing code.
>>>>
>>>
>>> Yes A-Z only means uppercase in an ASCII only world in a unicode world it
>>> means
>>> AaBb... Z because there are way more characters that simple A-Z. In FreeBSD
>>> 11
>>> we have a unicode collation instead of falling back in on LC_COLLATE=C which
>>> means ascii only
>>>
>>> For regrexp for example one should use the classes: :upper: or :lower:.
>>
>> That is rather surprising. Is there a normative reference for the treatment
>> of bracket expressions and character classes when using locales other than C
>> and/or encodings like UTF-8?
>
> http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap09.html
>
> For example:
>
> "Regular expressions are a context-independent syntax that can represent a
> wide
> variety of character sets and character set orderings, where these character
> sets are interpreted according to the current locale. While many regular
> expressions can be interpreted differently depending on the current locale,
> many
> features, such as character class expressions, provide for contextual
> invariance
> across locales.“
Sorry, maybe I wasn’t clear enough with my question. When a character class
fits the problem, it is clearly advantageous.
But under what circumstances would [A-Z] mean anything other than a character
whose Unicode codepoint is between U+0041 and U+005A, inclusive? Especially
given the locale in the example is en_US.UTF-8. Or, put another way, why would
an implementation interpret [A-Z] as anything other than [ABCDE…XYZ]?
From reading your reference, I can see in 9.3.5.7:
> In the POSIX locale, a range expression represents the set of collating
> elements that fall between two elements in the collation sequence, inclusive.
> In other locales, a range expression has unspecified behavior[…]
So even if the observed behaviour is conforming, I’d think it’s still highly
undesirable.
Stefan
--
Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811
___
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: Uppercase RE matching problems in FreeBSD 11
> Am 06.11.2016 um 12:07 schrieb Baptiste Daroussin <b...@freebsd.org>:
>
> On Sat, Nov 05, 2016 at 08:23:25PM -0500, Greg Rivers wrote:
>> I happened to run an old script today that uses sed(1) to extract the system
>> boot time from the kern.boottime sysctl MIB. On 11.0 this no longer works as
>> expected:
>>
>> $ sysctl kern.boottime
>> kern.boottime: { sec = 1478380714, usec = 145351 } Sat Nov 5 16:18:34 2016
>> $ sysctl kern.boottime | sed -e 's/.*\([A-Z].*\)$/\1/'
>> v 5 16:18:34 2016
>>
>> sed passes over 'S' and 'N' until it hits 'v', which it considers uppercase
>> apparently. This is with LANG=en_US.UTF-8. If I set LANG=C, it works as
>> expected:
>>
>> $ sysctl kern.boottime | LANG=C sed -e 's/.*\([A-Z].*\)$/\1/'
>> Nov 5 16:18:34 2016
>>
>> Testing every lowercase character separately gives even more inconsistent
>> results:
>>
>> $ cat <> Here sed thinks every lowercase character except for 'a' is uppercase! This
>> differs from the first test where sed did not think 'o' is uppercase. Again,
>> the above behaves as expected with LANG=C.
>>
>> Does anyone have any insight into this? This is likely to break a lot of
>> existing code.
>>
>
> Yes A-Z only means uppercase in an ASCII only world in a unicode world it
> means
> AaBb... Z because there are way more characters that simple A-Z. In FreeBSD 11
> we have a unicode collation instead of falling back in on LC_COLLATE=C which
> means ascii only
>
> For regrexp for example one should use the classes: :upper: or :lower:.
That is rather surprising. Is there a normative reference for the treatment of
bracket expressions and character classes when using locales other than C
and/or encodings like UTF-8?
Stefan
--
Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811
___
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: Have I got this VIMAGE setup correct?
Am 04.01.2016 um 02:33 schrieb Garrett Wollman <woll...@bimajority.org>: > > For now, I think I'll just use exec.prestart to manually configure a > MAC address. It would be nice if the LAA MAC addresses we generated > were both random on initial creation (to better avoid duplicates) and > stable over reboot. (Likewise the bridge(4) MAC address.) Or > alternatively if we just had rc.conf support for explicitly > configuring the MAC address of every interface, since ifconfig doesn't > let you configure L2 and L3 addresses on the same command line. I’ve had good experiences with using create_args_ in rc.conf. I believe that ifconfig only let’s you work with only one address family per invocation. Stefan -- Stefan Bethke <s...@lassitu.de> Fon +49 151 14070811 create_args_tap0="ether 02:00:00:00:01:00" create_args_tap1="ether 02:00:00:00:01:01" create_args_tap2="ether 02:00:00:00:01:02" create_args_tap3="ether 02:00:00:00:01:03" create_args_tap4="ether 02:00:00:00:01:04" create_args_vlan100="vlandev em0 vlan 100 up" create_args_vlan101="vlandev em0 vlan 101 up" create_args_vlan102="vlandev em0 vlan 102 up" create_args_vlan103="vlandev em0 vlan 103 up" create_args_vlan104="vlandev em0 vlan 104 up" create_args_bridge100="ether 02:00:00:00:00:64 addm vlan100" create_args_bridge101="ether 02:00:00:00:00:65 addm vlan101" create_args_bridge102="ether 02:00:00:00:00:66 addm vlan102 addm tap0 addm tap1 fib 1" create_args_bridge103="ether 02:00:00:00:00:67" create_args_bridge104="ether 02:00:00:00:00:68" ___ 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: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9
Am 03.02.2013 um 10:57 schrieb Chris Rees cr...@freebsd.org: On 3 February 2013 03:55, Kimmo Paasiala kpaas...@gmail.com wrote: There is no PR yet with my fix and therefor no commit to ports tree that would fix the problem. I'll file a PR soon (TM). The problem was in base, and is fixed there. Huh? With -current r246283, I still get a segfault from sudo unless I have Kimmo's patch. Is there some confusion about which problem is addressed by Kimmo's patch? Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9
Am 30.01.2013 um 07:21 schrieb Kimmo Paasiala kpaas...@gmail.com: On Wed, Jan 30, 2013 at 7:27 AM, James ja...@hicag.org wrote: I was able to correct the problem as well by prefixing strnvis, avoiding the symbol collision. I also found PR: ports/172941 which also has a fix. Using my patch or the patch in ports/172941 fixes the segfault for me in stable/9. However, I quickly ran into another problem. I can't remember the error message exactly, it was something like Unable to initialize PAM: Unknown file descriptor. A ktrace didn't reveal anything obvious. I'll try to test it out tomorrow. -- James. Try the attached patch. Just drop it into /usr/ports/security/pam_ssh_agent_auth/files directory and recompile. This will make the port use the system strnvis() with correctly ordered arguments if one is available (HAVE_STRNVIS defined) and an _openbsd suffixed version if not. -Kimmo patch-strnvis.txt Working great for me! Is this on any committers radar? I don't see a PR for it. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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.1 RELENG_9 Unable to cleanly dismount root partition on shutdown
Am 27.08.2012 um 11:06 schrieb Matt Smith: I posted on this mailing list two weeks ago and never received any replies so I decided to raise a PR via the web form. But I think I submitted it under the wrong category and it's marked as low priority as well. But I think this is something that is a potential serious problem if I end up getting a corrupted filesystem so I'm posting here again in the hope somebody can help this time. The PR is amd64/170646. I'm now running the latest RELENG_9 code as of 25th August as I've done a new buildworld/kernel. I still get the same problem. When I reboot it I get WARNING: / was not properly dismounted and it rebuilds from journal. On shutdown I get the messages pasted below. I'm running amd64 with GPT partitioning, UFS2 with softupdates and softupdates journalling enabled. I have a custom kernel but I don't think I took anything important out of it. Syncing disks, vnodes remaining...7 7 2 0 0 done All buffers synced. fsync: giving up on dirty 0xfe0007102780: tag devfs, type VCHR usecount 1, writecount 0, refcount 2292 mountedhere 0xfe00729ca00 flags (VI(0x200)) v_object 0xfe0005101910 ref 0 pages 23509 lock type devfs: EXCL by thread 0xfe00018fe08e0 (pid 1) dev label/root umount of / failed (35) Then when the box comes back up again it detects that / was not unmounted cleanly and recovers from journal before marking it clean once more. My fstab: /dev/label/root / ufs rw 1 1 /dev/label/swap none swap sw 0 0 Is there a particular reason you've decided to glabel your partitions instead of using GPT labels? Which device did you do the newfs on, the GPT partition or the glabel device? My hunch is that the label metadata sector at the end of the GPT partition is interfering with the filesystem. I'd try labelling my partitions (gpart modify -i 2 -l root ada0; gpart modify -i 3 -l swap), then change fstab to reference the gpt labels (dev(gpt/root) instead of the glabel ones. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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
panic: GPF in kernel
Setting up new hardware (i5 CPU, 16 GB RAM) and doing a burn-in test running make buildworld in a loop. After a couple of hours, I got this panic. 8-stable is from January, ZFS root. Does this correlate with any recently fixed bugs, or is this likely a hardware issue? # uname -a FreeBSD dhcp62.lassitu.de 8.2-STABLE FreeBSD 8.2-STABLE #0: Fri Feb 24 23:22:57 UTC 2012 r...@dhcp62.lassitu.de:/usr/obj/freebsd/checkout/src/sys/EISENBOOT amd64 Fatal trap 9: general protection fault while in kernel mode cpuid = 3; apic id = 06 instruction pointer = 0x20:0x805460c5 stack pointer = 0x28:0xff84830119d0 frame pointer = 0x28:0xff8483011a60 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 = 38198 (cc1) trap number = 9 panic: general protection fault cpuid = 3 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x37 panic() at panic+0x187 trap_fatal() at trap_fatal+0x290 trap() at trap+0x180 calltrap() at calltrap+0x8 --- trap 0x9, rip = 0x805460c5, rsp = 0xff84830119d0, rbp = 0xff8483011a60 --- pmap_remove_pages() at pmap_remove_pages+0x275 vmspace_exit() at vmspace_exit+0x9a exit1() at exit1+0x3b3 sys_exit() at sys_exit+0xe amd64_syscall() at amd64_syscall+0x24f Xfast_syscall() at Xfast_syscall+0xfc --- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x84ba3c, rsp = 0x7fffdf68, rbp = 0x7fffdfa0 --- (kgdb) bt #0 doadump () at /freebsd/checkout/src/sys/kern/kern_shutdown.c:263 #1 0x802eab00 in boot (howto=260) at /freebsd/checkout/src/sys/kern/kern_shutdown.c:441 #2 0x802eafa1 in panic (fmt=Variable fmt is not available. ) at /freebsd/checkout/src/sys/kern/kern_shutdown.c:614 #3 0x8054dc80 in trap_fatal (frame=0x9, eva=Variable eva is not available. ) at /freebsd/checkout/src/sys/amd64/amd64/trap.c:825 #4 0x8054e2a0 in trap (frame=0xff8483011920) at /freebsd/checkout/src/sys/amd64/amd64/trap.c:621 #5 0x80534cb8 in calltrap () at /freebsd/checkout/src/sys/amd64/amd64/exception.S:228 #6 0x805460c5 in pmap_remove_pages (pmap=0xff01982838d8) at /freebsd/checkout/src/sys/amd64/amd64/pmap.c:4087 #7 0x8051a61a in vmspace_exit (td=0xff017efca8a0) at /freebsd/checkout/src/sys/vm/vm_map.c:405 #8 0x802b93d3 in exit1 (td=0xff017efca8a0, rv=Variable rv is not available. ) at /freebsd/checkout/src/sys/kern/kern_exit.c:298 #9 0x802ba61e in sys_exit (td=Variable td is not available. ) at /freebsd/checkout/src/sys/kern/kern_exit.c:106 #10 0x8054d1ff in amd64_syscall (td=0xff017efca8a0, traced=0) at subr_syscall.c:114 #11 0x80534fac in Xfast_syscall () at /freebsd/checkout/src/sys/amd64/amd64/exception.S:387 #12 0x0084ba3c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: random problem with 8.3 from yesterday
Am 22.02.2012 um 07:34 schrieb Erich Dollansky: tunefs -L NewDeviceName /dev/da0a Either this call or the mount command does not work randomly. When I then try to mount the device on /dev/da0a it does not work always. I do not know what this causes, I am only randomly able to reproduce it. It might be affected by removing the device or keeping it plugged in. You need to be more specific: what does not work mean? Output, results? Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Custom kernel poll summary (was: Re: Reducing the need to compile a custom kernel)
Am 14.02.2012 um 12:37 schrieb Alexander Leidinger: 1 FLOWTABLE The last time I included this in a kernel it seemed to have odd effects on TCP connections. Admittedly, that was probably two years or so ago, and I never bothered to find out what was happening in detail. Is it safe now? Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: UFS corruption panic
Am 15.01.2012 um 05:20 schrieb Joe Holden: Guys Is a panic **really** appropriate for a filesystem that isn't even in fstab? ie; panic: ufs_dirbad: /mnt: bad dir ino 3229 at offset 0: mangled entry Which happened to be an file-backed md volume that got changed as I forgot to unmount it beforehand, however as a result there is now inconsistencies and probably data corruption or even missing data on other important filesystems (ie; /, /var etc) because there wasn't even a sync or any kind of other sensible behaviour. Yes, a panic is the correct action here. While I agree that it's super annoying, the filesystem notices that something is *really* wrong. Instead of letting the problem fester and continue to corrupt data, it stops the system. Most filesystems work under the assumption that they're the sole owner of the disk. This means that any changes to the on-disk data must come from filesystem code itself; if that data is inconstistent, it must be a bug in the filesystem code. At this point, panic is the only course of action to avoid even greater damage to the data. In other words: don't do that then :-) Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: TCP Reassembly Issues
I think I've got it - a stupid 1 line logic bug. My apologies for missing it when I reviewed the patch which introduced the bug (patch was committed to head as r226113, MFCed to stable/9 as r226228). Due to some miscommunication, the initial patch was committed to and MFCed from head much later than it should have been in the 9.0 release cycle and instead of being included in the BETAs, didn't make it in until 9.0-RC1 I believe i.e. only RC1 and RC2 should be experiencing the issue. Could those who have reported the bug and are able to recompile their kernel to test a patch please try the following and report back to the list: http://people.freebsd.org/~lstewart/patches/misctcp/tcp_reass_plugzoneleak_10.x.r227986.patch The patch is against head r227986 but will apply and work correctly for 9.0 as well. I'm a happy camper! Thanks, Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: TCP Reassembly Issues
Am 25.11.2011 um 00:35 schrieb Adrian Chadd: Have you tried disabling the tcp offload features of your NIC? I'm using my em0 as a VLAN trunk, and I'm under the impression that that disables all the hardware assists in the controller. Also, the LAN vlan is bridged via OpenVPN and tap, making the whole bunch promiscous, which I believe also forces off the acceleration. em0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=219bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC ether 00:1c:c0:7d:8c:50 inet6 fe80::21c:c0ff:fe7d:8c50%em0 prefixlen 64 scopeid 0x1 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active bridge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 02:00:00:00:00:01 inet6 2001:470:1f0b:1064::1 prefixlen 64 inet 44.128.65.1 netmask 0xffc0 broadcast 44.128.65.63 inet6 fe80::21c:c0ff:fe7d:8c50%bridge0 prefixlen 64 scopeid 0xd nd6 options=21PERFORMNUD,AUTO_LINKLOCAL id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: vlan1 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP ifmaxaddr 0 port 15 priority 128 path cost 55 member: tap0 flags=143LEARNING,DISCOVER,AUTOEDGE,AUTOPTP ifmaxaddr 0 port 14 priority 128 path cost 200 vlan1: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=3RXCSUM,TXCSUM ether 00:1c:c0:7d:8c:50 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active vlan: 1 parent interface: em0 em0@pci0:0:25:0:class=0x02 card=0x50038086 chip=0x10cd8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82567LF-2 Gigabit Network Connection' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 09[e0] = vendor (length 6) Intel cap 2 version 0 -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: TCP Reassembly Issues
Am 24.11.2011 um 21:30 schrieb Kris Bauer: On Thu, Nov 24, 2011 at 1:20 PM, Raul r...@turing.b2n.org wrote: I am seeing the same sorts of things in netstat vmstat: # netstat -s -p tcp |grep mem 742935 discarded due to memory problems # vmstat -z |grep tcpreass tcpreass: 40, 16464, 16340, 124, 131485,955443, 0 Same here: root@diesel:~# netstat -s -p tcp |grep mem 529211 discarded due to memory problems root@diesel:~# vmstat -z |grep tcpreass tcpreass:40, 1680,1679, 1, 118846,831450, 0 root@diesel:~# uname -a FreeBSD diesel.lassitu.de 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #20: Fri Nov 18 21:57:59 CET 2011 r...@diesel.lassitu.de:/usr/obj/usr/src/sys/DIESEL amd64 root@diesel:~# uptime 11:01PM up 5 days, 23:15, 1 user, load averages: 0.14, 0.04, 0.01 root@diesel:~# svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: http://mirror.hanse.de/svn/freebsd/base/stable/9 Repository Root: http://mirror.hanse.de/svn/freebsd/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 227665 Node Kind: directory Schedule: normal Last Changed Author: fabient Last Changed Rev: 227664 Last Changed Date: 2011-11-18 15:41:48 +0100 (Fri, 18 Nov 2011) I regularly copy large files off my Tivo trans-atlantic (125ms RTT), and TCP connections currently stall after about 500 megs, never recovering. I suspect this is connected, as it started immediately after upgrading the machine to 9-stable. As far as I can tell, the problem does not exist with 8-stable. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: SIOCGIFADDR broken on 9.0-RC1?
Am 15.11.2011 um 23:35 schrieb GR: So, I switched to static assignement and it changes the behaviour (and fixes the bug). My guess is that during the time waiting for the DHCP offer, all aliases are already configured on the network interface, and the IP address given by DHCP is added at the end of the tail. Is that a wanted behaviour? I find it dangerous (i.e. not exactly what a user is expecting). A bit of background, as best I understand it and remember from Stevens: Interfaces in BSD do not have a notion of primary and additional addresses; interfaces just have any number of addresses associated with them. There's no inherent ordering in this list (except for how the current implementation seems to keep them in the order they were configured). To be able to associate proper routes with interface addresses, the recommendation for multiple IPv4 addresses on an Ethernet interface is to have one of them have the proper netmask for the network, and configure the remainder with a netmask of 255.255.255.255. But that's solely for the benefit of the routing table; the interface itself doesn't really care. Reading the rc.conf man page could give you the impression that there are primary and alias addresses, but the networking code doesn't really work like that. The new ipv4_addrs_interface syntax exposes the actual behavior in a more direct way. Jeremy gave you a hint on how to fix your immediate problem, but the real answer is that the program needs to be fixed that makes assumptions about meaning attached to the first configured IPv4 address. HTH, Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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
Running portupgrade from cron (was: /usr/bin/script eating 100% cpu with portupgrade and xargs)
Am 23.10.2011 um 08:47 schrieb Chris Rees: Worst of all, you're running portupgrade from cron without reading UPDATING, which is just asking for trouble. What specifically is your concern here? I've been running portupgrade from cron for six years on a multitude of systems with great success. Yes, occasionally, things break, and reading UPDATING becomes a necessity, but I much prefer the nightly upgrade to running portupgrade by hand less frequently, especially when you have to do it on 20 or more machines. Note that most of these boxes have very limited SLAs, and dealing with the occasional breakage is much less work than regular manual maintainance. I decided to do this after I got bitten one too many times trying to upgrade ports after three to four months, and getting stuck in all kinds of bad dependencies. Daily upgrades usually means that I catch every single update by itself, so complex interdependencies are exactly what the committer tested. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Accessing tun devices from inside a Jail
Am 22.10.2011 um 01:19 schrieb Nikos Vassiliadis: On 10/21/2011 5:08 PM, Stefan Bethke wrote: - VIMAGE and mpd don't like each other, so VIMAGE was out as well Could you explain please? In my limited testing they seem to get along fine:) Sorry, I misremembered. The issue is actually pf and VIMAGE. A couple of years back, there were issues with VIMAGE and netgraph, but those seem to have been resolved. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Accessing tun devices from inside a Jail
Am 22.10.2011 um 14:04 schrieb Matthew Seaman: On 22/10/2011 12:49, Stefan Bethke wrote: Am 22.10.2011 um 01:19 schrieb Nikos Vassiliadis: On 10/21/2011 5:08 PM, Stefan Bethke wrote: - VIMAGE and mpd don't like each other, so VIMAGE was out as well Could you explain please? In my limited testing they seem to get along fine:) Sorry, I misremembered. The issue is actually pf and VIMAGE. A couple of years back, there were issues with VIMAGE and netgraph, but those seem to have been resolved. pf and VIMAGE seems to have been fixed in 9.0 Oh cool, I'll give it another shot then! Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Accessing tun devices from inside a Jail
Am 21.10.2011 um 04:02 schrieb Morgan Reed: Hi all, I'm currently attempting to setup, I suppose you'd call it a multi-VPN-tunnel gateway. Basically I have several OpenVPN Servers in different locations, I want to have various tunnels up to them and be able to choose an exit by way of pointing my browser at a particular instance of Squid running in a particular jail which routes via a particular tunnel (HTTP/S traffic is the primary concern at this point, though I might want to extend the concept to all traffic in future). I have a similar setup, but the OpenVPN endpoints are on OpenWrt, with tinyproxy running there. I have a central squid that knows which tiny proxy to use for which URL pattern, and that works quite well. First issue I ran into was routing tables, that was resolved by recompiling my kernel with option ROUTETABLES=10 and pointing each of my jails to their own FIB, however as it's not possible to configure route tables from inside the jail (as far as I'm aware anyway) I need to bring the OpenVPN tunnel up from the host and utilise a route-up script to configure the routing table for the jail (utilising setfib), I run into problems though, as even though the tun device is visible in the jail it does not appear to be configured (no IP addersses, etc) so the jail is unable to route traffic. All the stuff I've been able to find online has been geared to static addresses on each end of the tunnel, this is not the case with my VPN provider, tunnel addresses are dynamically assigned. I think that worst case I can probably use pf on the host to route traffic from a given jail via a particular interface or possibly cobble something up around VIMAGE, but I think I'd rather not have to go down those paths. I'm not sure if what I'm looking for is actually possible, any suggestions would be much appreciated. I was trying to enable a set of processes to use a separate DSL interface, with the FreeBSD box terminating the PPPoE connection. I've tried a couple of things: - I couldn't come up with pf rules that would allow certain processes (i. e. those in a specific jail, or running under a specific user id) to have seperate forwarding applied to them. I believe IPFW might be better suited, but I haven't tried. - VIMAGE and mpd don't like each other, so VIMAGE was out as well - VBox with the interface bridged to the DSL interface works fine, but has a lot of overhead. My OpenVPN hub server is running inside a jail, but the tun interface is preconfigured from outside; the config substitutes /bin/true for ifconfig and route. HTH, and please report back on any success, I'm definitely interested! Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: /usr/bin/script eating 100% cpu with portupgrade and xargs
Am 15.10.2011 um 09:36 schrieb Mikolaj Golub: On Fri, 14 Oct 2011 22:50:32 +0200 Stefan Bethke wrote: SB I finally figured out why my ports aren't updating anymore: when running portupgrade -a --batch from cron, stdin is /dev/null, and that produces the gobs of ^D in the output, as well as the script file that portupgrade creates. What's worse is that the upgrade never completes. SB You can easily see this for yourself: SB # portupgrade -a --batch /dev/null SB This is on 8-stable from October 5th. Could you please try the patch I attached to another my mail in this thread to see if it helps? Seems to do the trick, thanks! Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: unix browsers problem
Am 15.10.2011 um 12:34 schrieb kapral: When I connect with any freebsd 8.2 browsers like epithany konqueror firefox7.0.1 and under open bsd 4.9 with firefox 3.6.13 en i have strange connections too le100.net i checkt the ip and this is seedo in germany i also have other strange connections any idea what to do with this bug ? I think you need to be much more specific about what you're seeing, and why you think that it is a problem. I got curious, so I fired up a fresh Firefox, and indeed saw that I have open connections to a couple of IPs: $ netstat -anfinet Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp4 0 0 92.231.160.45.1494474.125.43.120.80 ESTABLISHED tcp4 0 0 92.231.160.45.6244174.125.43.104.80 ESTABLISHED tcp4 0 0 92.231.160.45.4171074.125.43.104.80 ESTABLISHED tcp4 0 0 92.231.160.45.56705195.95.193.85.80 ESTABLISHED tcp4 0 0 92.231.160.45.14474195.95.193.78.80 TIME_WAIT tcp4 0 0 92.231.160.45.64333195.95.193.78.80 ESTABLISHED tcp4 0 0 92.231.160.45.3619168.232.35.119.80 TIME_WAIT tcp4 0 0 92.231.160.45.4033963.245.217.43.443 TIME_WAIT tcp4 0 0 92.231.160.45.5178563.245.217.43.443 ESTABLISHED tcp4 0 0 92.231.160.45.5132174.125.43.190.443 ESTABLISHED The 74.125.43.* addresses do resolve to 1e100.net, as you're seeing: $ host 74.125.43.190 190.43.125.74.in-addr.arpa domain name pointer bw-in-f190.1e100.net. $ host 74.125.43.104 104.43.125.74.in-addr.arpa domain name pointer bw-in-f104.1e100.net. whois shows who's using them: $ whois 74.125.43.104 ... NetRange: 74.125.0.0 - 74.125.255.255 CIDR: 74.125.0.0/16 OriginAS: NetName:GOOGLE NetHandle: NET-74-125-0-0-1 Parent: NET-74-0-0-0-0 NetType:Direct Allocation RegDate:2007-03-13 Updated:2007-05-22 Ref:http://whois.arin.net/rest/net/NET-74-125-0-0-1 Considering that Firefox by default will open up the Firefox Google page, I don't find this surprising at all. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: /usr/bin/script eating 100% cpu with portupgrade and xargs
Am 14.10.2011 um 14:03 schrieb Jilles Tjoelker: On Wed, Oct 12, 2011 at 11:25:35PM +0100, Adrian Wontroba wrote: On Sat, Oct 08, 2011 at 01:27:07AM +0100, Adrian Wontroba wrote: I won't be in a position to create a simpler test case, raise a PR or try patches till Tuesday evening (UK) at the earliest. So far I have been unable to reproduce the problem with portupgrade (and will probably move to portmaster). I have however found a different but possibly related problem with the new version of script in RELENG_8, for which I have raised this PR: misc/161526: script outputs corrupt if input is not from a terminal Blast, should of course been bin/ The extra ^D\b\b are the EOF character being echoed. These EOF characters are being generated by the new script(1) to pass through the EOF condition on stdin. One fix would be to change the termios settings temporarily to disable the echoing but this may cause problems if the application is changing termios settings concurrently and generally feels bad. It may be best to remove writing EOF characters, perhaps adding an option to enable it again if there is a concrete use case for it. I finally figured out why my ports aren't updating anymore: when running portupgrade -a --batch from cron, stdin is /dev/null, and that produces the gobs of ^D in the output, as well as the script file that portupgrade creates. What's worse is that the upgrade never completes. You can easily see this for yourself: # portupgrade -a --batch /dev/null This is on 8-stable from October 5th. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: OS X Lion time machine = (afpd|iSCSI) = ZFS question
Am 21.07.2011 um 23:56 schrieb Bakul Shah: I am in no hurry to upgrade my MBP to OS X Lion but given Lion time machine and netatalk issues, I got wondering if iSCSI on FreeBSD is stable enough for time machine use. How much duct tape and baling wire are needed to make it work?! After having had odd behavior from TM on a netatalk volume, I've switched over to istgt and the globalSAN iSCSI initiator, using a ZVOL. I found the istgt configuration non-obvious, but I also have little background in iSCSI. Took me about an hour to get it up and running without authentication; haven't bothered since trying to get authentication to work. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Crashes with Promise controller
Am 13.06.2011 um 16:22 schrieb Christian Baer: I have to slightly explain the word crash here: I don't actually have to hard reset the system myself. My box just does a reboot by itself. No filesystem is unmounted cleanly and because the machine isn't really new and powerful fsck takes pretty long. I can't help you with your controllers, but anyone in a position to help will likely want to know if the box simply resets, or if the kernel panics. And if there are going to be any patches, you most certainly will want to get familiar with the debugger to help try stuff out. The handbook has information on how to enable crash dumps and getting the kernel debugger going. If you haven't done so already, try and get a serial console going, it helps tremendously to be able to cutpaste debugger info instead of trying to hand transcribe it. HTH, Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: gptzfsboot serial support
Am 01.06.2011 um 10:16 schrieb Arnaud Houdelette: Hi. I know that there is 2 versions of boot0 : With and Without serial support. boot0 and boot0sio are FreeBSD's version of the MBR; it's what shows the F1..F4 prompt. Is it the same with gptzfsboot ? How to build gptzfsboot with serial support, setting serial speed at 19200 baud ? Serial support is built by default for boot1/2, loader and it's variations. To change the default from video console to serial, or change the speed, see boot(8), and add the appropriate flags to /boot.config. If you only require loader(8) to interact with the serial console, you can set loader.conf(5) variables to pick the console and the speed. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: How to bind a static ether address to bridge?
Am 25.02.2011 um 07:56 schrieb Zhihao Yuan: My server is behind a DHCP-enabled router, and it has two network interfaces, wlan0 and bge0. I want to use them together, so I bind them, plus tap0 to bridge0. But bridge has a random MAC address for each time it was created, which makes me hard to reserve an IP for it (since I need to forward some ports to this server). So I set net.link.bridge.inherit_mac=1, which makes bridge0 to use bge0's MAC address, always. But this causes another problem: the packets sent to bridge0 is also sent to bge0, -- the packets are duplicated! The kernel have to drop half of them. So how can I bind a distinct MAC address to a bridge? This is in my router's rc.conf: ifconfig_bridge0=ether 02:00:00:00:00:01 addm tap0 addm vlan1 ifconfig_bridge0_alias0=inet 192.168.0.1/24 vlan1 is on em0; neither as an address assigned. And if you want to put IPv6 on there, you also have to add a link-local address to make rtadvd happy, something like: ipv6_network_interfaces=bridge0 gif0 ipv6_ifconfig_bridge0=fe80::21c:c0ff:fe7d:8c50%bridge0 ipv6_ifconfig_bridge0_alias0=2001:470:1f0b:::1 prefixlen 64 -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: bridge, ipv6 and rtadvd
Am 06.02.2011 um 13:23 schrieb Spil Oss: Hi All, Don't know if this is expected behaviour. My LAN (bge0) and WLAN (wlan0) are bridged in bridge0. I tried to run rtadvd on bridge0 but that didn't result in ipv6 addresses on my network. Tried running rtadvd directly /usr/sbin/rtadvd -c /etc/rtadvd.conf -f -D and saw the requests coming in from the client but that didn't result in a working ipv6 network. Wild guessing I tried loading it with /usr/sbin/rtadvd -f -D bge0 and I had a functional ipv6 network. Is this intended behaviour? Am I doing something wrong? It appears to be intentional; there was some discussion a couple years back, and the current behavior is for virtual interfaces to not receive link-local addresses. Since I prefer to have bridge0 as the main interface, I simply manually configured a link local address: ipv6_enable=YES ipv6_gateway_enable=YES ipv6_network_interfaces=bridge0 gif0 ipv6_ifconfig_bridge0=fe80::21c:c0ff:fe7d:8c50%bridge0 ipv6_ifconfig_bridge0_alias0=2001:470:1f0b:::1 prefixlen 64 ipv6_ifconfig_gif0=2001:470:1f0a:::2 2001:470:1f0a:::1 prefixlen 128 $ cat /etc/rtadvd.conf bridge0:\ :addrs#1:addr=2001:470:1f0b::::raflags#64: The IPv4 side of gif0 is brought up through a linkup script triggered by mpd when my DSL connection comes up; that also updates the endpoint address for the HE tunnel. Oh, this is on -stable from Dec 4. HTH, Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Abysmal re(4) performance under 8.1-STABLE (mid-August)
Am 06.11.2010 um 10:37 schrieb Ulrich Spörlein: On this new server, I cannot get more than ~280kByte/s up/downstream out of re(4) without any tweaking. re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC ether 00:21:85:63:74:34 inet6 fe80::221:85ff:fe63:7434%re0 prefixlen 64 scopeid 0x1 inet 46.4.12.147 netmask 0xffc0 broadcast 46.4.12.191 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: Ethernet autoselect (100baseTX half-duplex) status: active AOL: r...@pci0:1:0:0:class=0x02 card=0x82c61043 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'Gigabit Ethernet NIC(NDIS 6.0) (RTL8168/8111/8111c)' class = network subclass = ethernet re0: RealTek 8168/8111 B/C/CP/D/DP/E PCIe Gigabit Ethernet port 0xd800-0xd8ff mem 0xfdfff000-0xfdff,0xfdfe-0xfdfe irq 18 at device 0.0 on pci1 re0: Using 1 MSI messages re0: Chip rev. 0x3c00 re0: MAC rev. 0x0040 miibus0: MII bus on re0 rgephy0: RTL8169S/8110S/8211B media interface PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:26:18:d5:2c:23 re0: [FILTER] I believe that it was working properly some months ago, but reading Rick's thread over on -current I checked and transfer over NFS seems to be limited to a couple hundred KB as well. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Degraded zpool cannot detach old/bad drive
Am 29.10.2010 um 07:51 schrieb Rumen Telbizov: Thanks for your quick response. Unfortunately I already did try this approach. Applying -d /dev/gpt only limits the pool to the bare three remaining disks which turns pool completely unusable (no mfid devices). Maybe those labels are removed shortly they are being tried to be imported/accessed? What I don't understand is what exactly makes those gpt labels disappear when the pool is imported and otherwise are just fine?! Something to do with OpenSolaris ? On top of it all gpart show -l keeps showing all the labels right even while the pool is imported. Any other clues would be appreciated. The labels are removed by glabel as soon as something opens the underlying provider, i. e. the disk device, for writing. Since that process could change the part of the disk that the label information is extracted from, the label is removed. glabel will re-taste the provider once the process closes it again. Since you're using gpt labels, I would expect them to continue to be available, unless zpool import somehow opens the disk devices (instead of the partition devices). Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: ZFS write speed
Am 27.10.2010 um 22:51 schrieb S.N.Grigoriev: Hi list, I've got very low write speed using ZFS on a SATA disk. My HDD configuration is: ad4: 70911MB WDC WD740BLFS-01YBU0 04.04V01 at ata2-master UDMA100 SATA 3Gb/s ad6: 78532MB Hitachi HDS728080PLA380 PF2OA60A at ata3-master UDMA100 SATA 1.5Gb/s ad8: 1430799MB WDC WD15EARS-00MVWB0 51.0AB51 at ata4-master UDMA100 SATA 3Gb/s The EARS has 4k sectors, if I'm not mistaken. I don't recall the eventual outcome, but there was a long thread on stable or hackers on how to ensure proper alignment and (minimun) 4k-sized writes to make sure the disk doesn't have to do a read-modify-write cycle, so try and search the archives. ad4 and ad6 are single-slice disks (UFS2 with soft updates) ZFS configuration is following: zpool create Z ad8 zfs create Z/music zfs create Z/video All ZFS parameters are default. kern.maxvnodes = 100 To test my configuration I recursively copied from ad6 to ad8 two directories. The first one contains MP3 files (average size = 10MB). The second one contains AVI files (average size = 1GB). To compare performance I repeated above tests with ad8 using UFS2 with soft updates. 18GB of MP3 files required 10m35s to copy to UFS2 and 21m40s to copy to ZFS. 30GB of AVI files required 16m6s to copy to UFS2 and 1h2m39s to copy to ZFS. I used for tests FreeBSD 8.1R amd64. Amount of RAM on my machine is 6GB. Any tips? -- Regards, Serguey. ___ 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 -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Label question...why does ufs label vanish on mount?
Am 13.10.2010 um 06:56 schrieb Andrey V. Elsukov: On 12.10.2010 22:51, Kevin Oberman wrote: For some reason the /dev/ufs/label entry that geom creates for every UFS formatted partition is deleted when the device is mounted. This is not the case for other file systems, though I have not tried them all. It makes the drive much harder to deal with when you have to keep track of which physical drive contains the labeled media. It is a particular issue for hald and the tools which depend on it. Is there a good reason for this odd behavior of UFS? If there is not a good reason, could it be changed? When you are opening provider for writing (i.e. mount FS) GEOM(4) initiates SPOILING and all consumers that are attached to this provider except one will self-destroyed. When you are closing provider GEOM(4) initiates TASTING and consumers can return back. Look at man 4 geom for details. That explains the mechanism, but not the rationale. Or is it just an unintended consequence? And how is da2p1 different from ufs/mylabel? (Mount da2p1 and ufs/mylabel is removed, but not the other way around.) Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Label question...why does ufs label vanish on mount?
Am 13.10.2010 um 10:20 schrieb Pawel Jakub Dawidek: On Tue, Oct 12, 2010 at 11:33:11PM -0700, Jeremy Chadwick wrote: On Wed, Oct 13, 2010 at 08:29:06AM +0200, Stefan Bethke wrote: That explains the mechanism, but not the rationale. Or is it just an unintended consequence? And how is da2p1 different from ufs/mylabel? (Mount da2p1 and ufs/mylabel is removed, but not the other way around.) Pulling in pjd@ who can probably shed some light on this. The ufs/mylabel provider is based on da2p1, that's why opening da2p1 makes ufs/mylabel to be removed and not the other way around. The ufs/mylabel provider was created, because when da2p1 provider was created and LABEL class tasted it, it discovered that this provider contains UFS file system with 'mylabel' volume label, so the LABEL class created ufs/mylabel provider. Now when you open da2p1 for writing, the LABEL class destroys ufs/mylabel, because you may decide to change metadata on da2p1, for example you may choose to destroy UFS in there or change the volume label. When write open count on da2p1 goes down to zero, the LABEL class will be given da2p1 provider for tasting once again, so it can rediscover (possibly modified) volume label. The class may choose to ignore the spoil event from GEOM (it is send on first open for write), but if it isn't based on autodiscovering metadata. For example the NOP class ignores this event, because it doesn't care about metadata of provider it is based on. If we choose to ignore the spoil event in the LABEL class we will end up with stale info, eg. open da2p1 for writing, change its volume label and mount it and you will still have old label in /dev/ufs/. Thanks a lot (and also to Andrey), that really makes it clear to me! I just wish there was an easy way to keep the labels around even while someone has the provider open for writing, but I now understand that this requires some significant changes. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Label question...why does ufs label vanish on mount?
Am 12.10.2010 um 20:51 schrieb Kevin Oberman: For some reason the /dev/ufs/label entry that geom creates for every UFS formatted partition is deleted when the device is mounted. This is not the case for other file systems, though I have not tried them all. It makes the drive much harder to deal with when you have to keep track of which physical drive contains the labeled media. It is a particular issue for hald and the tools which depend on it. In 8, only the ones that are not mounted are removed; they are restored on unmount. So when you mount the filesystem via it's label, that entry continues to exist. And it's not limited to any particular label type, I've noticed the same with partitions that I used gmirror on. IIRC, in 7 only the device entry remained, and all label entries were removed on mount. Is there a good reason for this odd behavior of UFS? If there is not a good reason, could it be changed? I don't know, but I'm curious myself. When I asked this very question some time ago, I didn't get a response. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: need help with BElkin KVM and USB mouse problems.
Am 12.10.2010 um 20:17 schrieb Gary Kline: The USB keyboard works fine everywhere. But my USB mouse fails on the FreeBSD platforms when I try to run X11. I *have* managed to get the mouse working without X [i.e., in console mode]; and yes, the cursor and the buttons work fine. But once I launch X--even simple apps like twm or ctwm, the mouse pointer is dead. It doesn't sound like this issue is connected to your using a KVM at all, but rather your X configuration. If you have a second USB mouse, try plugging that in in addition to the KVM and see if there's any difference; I'm guessing not. Check you X config, and make sure dbus and hald are enabled in rc.conf and started. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Label question...why does ufs label vanish on mount?
Am 12.10.2010 um 22:19 schrieb Kevin Oberman: From: Stefan Bethke s...@lassitu.de Date: Tue, 12 Oct 2010 22:01:24 +0200 Am 12.10.2010 um 20:51 schrieb Kevin Oberman: For some reason the /dev/ufs/label entry that geom creates for every UFS formatted partition is deleted when the device is mounted. This is not the case for other file systems, though I have not tried them all. It makes the drive much harder to deal with when you have to keep track of which physical drive contains the labeled media. It is a particular issue for hald and the tools which depend on it. In 8, only the ones that are not mounted are removed; they are restored on unmount. So when you mount the filesystem via it's label, that entry continues to exist. And it's not limited to any particular label type, I've noticed the same with partitions that I used gmirror on. Sorry, but my experience in contrary to that. I mount /dev/ufs/aux and that device name is returned by df(1), but 'ls /dev/ufs' no longer contains 'aux'. This broke gnome-mount and required patching hald to ignore device created in /dev/ufs. Otherwise, when the device was removed, the /dev/ufs device was re-created, a devd creation event occurred and the partition was immediately re-mounted. It made it impossible to unplug the USB drive. Joe Marcus added a test of the created device to hald so the creation of /dev/ufs/aux would be ignored and the device always mounted by the hardware device name. This all works fine for msdosfs systems. The /dev/msdosfs entry does stay around when the device is mounted as /dev/msdosfs and all is well. I'd like to see consistent behavior before we get to making devicekit work with FreeBSD. (devicekit will replace hald some day.) This got me curious, so I fired up my -stable VM. I only tried UFS, but label entries do not reappear constently, at least in the quick test I did. And I still don't understand why they get removed in the first place. r...@freebsd8:~# uname -a FreeBSD freebsd8.lassitu.de 8.1-STABLE FreeBSD 8.1-STABLE #2 r212724: Thu Sep 16 15:22:34 UTC 2010 r...@freebsd8.lassitu.de:/usr/obj/usr/src/sys/MINIMAL amd64 Here's what I tried with a 1 gig stick that probes as: umass0: Kingston DataTraveler 2.0, class 0/0, rev 2.00/1.10, addr 2 on usbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI status: Check Condition (probe0:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready to ready change, medium may have changed) da2 at umass-sim0 bus 0 scbus1 target 0 lun 0 da2: Kingston DataTraveler 2.0 PMAP Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: 984MB (2015232 512 byte sectors: 64H 32S/T 984C) r...@freebsd8:~# gpart create -s gpt /dev/da2 da2 created r...@freebsd8:~# gpart add -s 256m -l ufs -t freebsd-ufs da2 da2p1 added r...@freebsd8:~# gpart list da2 Geom name: da2 fwheads: 64 fwsectors: 32 last: 2015198 first: 34 entries: 128 scheme: GPT Providers: 1. Name: da2p1 Mediasize: 268435456 (256M) Sectorsize: 512 Mode: r0w0e0 rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b label: ufs length: 268435456 offset: 17408 type: freebsd-ufs index: 1 end: 524321 start: 34 Consumers: 1. Name: da2 Mediasize: 1031798784 (984M) Sectorsize: 512 Mode: r0w0e0 r...@freebsd8:~# ls /dev/gpt ufs r...@freebsd8:~# ls /dev/gptid bba94c8e-d63f-11df-888c-000c295e330a r...@freebsd8:~# newfs -L ufslabel /dev/da2p1 /dev/da2p1: 256.0MB (524288 sectors) block size 16384, fragment size 2048 using 4 cylinder groups of 64.02MB, 4097 blks, 8256 inodes. super-block backups (for fsck -b #) at: 160, 131264, 262368, 393472 r...@freebsd8:~# mount /dev/da2p1 /mnt r...@freebsd8:~# ls /dev/gpt r...@freebsd8:~# ls /dev/ufs r...@freebsd8:~# ls /dev/gptid r...@freebsd8:~# umount /mnt r...@freebsd8:~# mount /dev/ufs/ufslabel /mnt r...@freebsd8:~# ls /dev/da2p1 /dev/da2p1 r...@freebsd8:~# ls /dev/gpt r...@freebsd8:~# ls /dev/ufs ufslabel r...@freebsd8:~# ls /dev/gptid r...@freebsd8:~# umount /mnt r...@freebsd8:~# ls -l /dev/da2p1 /dev/gpt /dev/gptid /dev/ufs crw-r- 1 root operator0, 103 Oct 12 20:34 /dev/da2p1 /dev/gpt: total 0 crw-r- 1 root operator0, 111 Oct 12 20:34 ufs /dev/gptid: total 0 crw-r- 1 root operator0, 112 Oct 12 20:34 bba94c8e-d63f-11df-888c-000c295e330a /dev/ufs: total 0 crw-r- 1 root operator0, 108 Oct 12 20:34 ufslabel I then unplugged and replugged the stick: r...@freebsd8:~# ls -l /dev/da2p1 /dev/gpt /dev/gptid /dev/ufs crw-r- 1 root operator0, 103 Oct 12 20:34 /dev/da2p1 /dev/gpt: total 0 crw-r- 1 root operator0, 111 Oct 12 20:34 ufs /dev/gptid: total 0 crw-r- 1 root operator0, 112 Oct 12 20:34 bba94c8e-d63f-11df-888c-000c295e330a /dev/ufs: total 0 crw-r- 1 root operator0, 108 Oct 12 20:34 ufslabel -- Stefan Bethke s...@lassitu.de
Re: How to predict drive number change for 7.3-8.1 upgrade?
Am 16.09.2010 um 11:05 schrieb Michael Sperber: I just upgraded my desktop system from 7.3 to 8.1, and the main hard drive, which was /dev/ad6 before is now /dev/ad10. Consequently, the initial boot failed when trying to mount the root file system from ad6. The desktop system is now fixed, but I also have a rented server with only a serial console, and I worry that the upgrade is going to leave me with a dead machine. Is there any way to predict how the drive number changes? (Why does it change at all?) If so, what's the proper way to tell the system the initial root device *before* rebooting? If you have a serial console, you can always enter the root device at the prompt, so you can recover there. If you can figure out the new device name, you can simply change the fstab entry for /; that's where loader picks up the root device that it hands to the kernel. Long-term, the best option is to label your filesystems or partitions, and use the label entries in fstab instead of the device names. I don't remember what 7.3 offers in terms of labels, but glabel should be available. Check tunefs if it offers the -L volname option, that's even better. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Serial console problems with stable/8
Am 12.09.2010 um 17:26 schrieb Oliver Fromme: I cannot even su(1) to root because it tries to print a message to the console, so it hangs, too. For the same reason I can't use shutdown(8) either. :-( This is what a hanging su(1) command looks like in ps -alxww: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 1533 1532 0 76 0 3392 3180 ttydcd I+ 00:00.05 su (zsh) Interestingly, the KDB sequences CR ~ ^B/^P/^R/ do work, which use the low-level console. So only the high-level console is frozen. Looking at the WCHAN, I'd speculate that it's waiting for DCD to become active. Are you using a proper cable with handshaking, or a three-wire cable? See what stty thinks the port is set to. It probably has clocal set, but shouldn't. See if you can unwedge it by setting -clocal with stty, then pick a proper cable or gettytab entry. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Serial console problems with stable/8
Am 13.09.2010 um 13:04 schrieb David Evans: I can confirm there is much weirdness with the uart on 8-STABLE. OTOH, I have real hardware where things are working just fine: $ grep uart /var/run/dmesg.boot uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 uart0: [FILTER] uart0: console (115200,n,8,1) $ grep ttyu0 /etc/ttys ttyu0 /usr/libexec/getty std.115200 vt100 on secure This is -stable from July 15th. The other end of the serial line is an uftdi USB adapter: uftdi0: usb serial converter on usbus0 Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Apparent dnsbl bug in Sendmail or m4
Am 22.08.2010 um 09:10 schrieb John Nielsen:
FEATURE(dnsbl, `bl.spamcop.net', `550 Mail from ${client_addr}
rejected, see http://spamcop.net/bl.shtml?; ${client_addr}')
On the FreeBSD 4.x server, this is the corresponding section in the .cf file:
# DNS based IP address spam list bl.spamcop.net
R$* $: ${client_addr}
R$-.$-.$-.$-$: ? $(dnsbl $4.$3.$2.$1.bl.spamcop.net. $: OK $)
R?OK $: OKSOFAR
R?$+TMP $: TMPOK
R?$+ $#error $@ 5.7.1 $: 550 Mail from ${client_addr}
rejected, s
ee http://spamcop.net/bl.shtml?; ${client_addr}
On the FreeBSD 8.x server, this is the corresponding section:
# DNS based IP address spam list bl.spamcop.net
R$* $: ${client_addr}
R$-.$-.$-.$-$: ? $(dnsbl $4.$3.$2.$1.bl.spamcop.net. $: OK $)
R?OK $: OKSOFAR
R?$+TMP $: TMPOK
I've got:
FEATURE(`dnsbl', `ix.dnsbl.manitu.net',`550 Rejected - see
http://www.heise.de/ix/nixspam/nixspam.blackmatches;')dnl
in my .mc, and get this in my .cf:
# DNS based IP address spam list ix.dnsbl.manitu.net
R$* $: ${client_addr}
R$-.$-.$-.$-$: ? $(dnsbl $4.$3.$2.$1.ix.dnsbl.manitu.net. $: OK $)
R?OK $: OKSOFAR
R?$+TMP $: TMPOK
R?$+ $#error $@ 5.7.1 $: 550 Rejected - see
http://www.heise.de/ix/nixspam/nixspam.blackmatches;
This is on 8.1 from July 15th. I just ran make all again, and it stays the
same.
Fired up my VMware image with a three-day old -stable, and put both mine and
yours in, and yours is missing the error line.
I experimented a bit, and it appears that the macro does not like having the
${client_addr} at the very end of the parameter. If I add , it starts
working. No idea how or why, but there you go :-)
FEATURE(`dnsbl', `bl.spamcop.net', `550 ${client_addr} foo
${client_addr} ')dnl
Stefan
--
Stefan Bethke s...@lassitu.de Fon +49 151 14070811
___
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: Apparent dnsbl bug in Sendmail or m4
Am 22.08.2010 um 10:00 schrieb Stefan Bethke:
FEATURE(`dnsbl', `bl.spamcop.net', `550 ${client_addr} foo
${client_addr} ')dnl
The real culprit is the comma. I believe the problem stems from unquoted use
of the arguments in some of the ifelses, where the comma turns the single
argument into two. Tracing the ifelses with -d aceq I see this for the last
ifelse in cf/feature/dnsbl.m4:
m4trace: -1- ifelse(`X550 Mail from ${client_addr} rejected', `see
http://spamcop.net/bl.shtml?; ${client_addr}', `Xquarantine', `R?$+
$#error $@ quarantine $: _DNSBL_SRV_', `X550 Mail from ${client_addr}
rejected', `
see http://spamcop.net/bl.shtml?; ${client_addr}', `Xdiscard', `R?$+
$#discard $: _DNSBL_SRV_', `R?$+ $#error $@ 5.7.1 $: _DNSBL_MSG_'
) - ???
m4trace: -1- ifelse(...) - `'
m4trace: -1- ifelse ...
I've never managed to really wrap my head around m4 quoting, but the easy fix
is to use some other character that has no meaning to m4.
Stefan
--
Stefan Bethke s...@lassitu.de Fon +49 151 14070811
___
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
ichwd causes freeze instead of reset
Hi, somewhat foolishly, I activated watchdogd and ichwd on a remote box, and while testing it (by suspending watchdogd), apparently the watchdog triggered. But instead of resetting, the machine does not react anymore on the serial console. I will have to wait until Monday to get physical access, so it might be hanging or just switched itself off; I have no way of telling right now. ichwd probes as: ichwd0: Intel ICH7 watchdog timer on isa0 ichwd0: Intel ICH7 watchdog timer (ICH7 or equivalent) ppc0: cannot reserve I/O port range (not sure why ppc0 is getting involved at that point.) FreeBSD lokschuppen.zs64.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #30: Thu Jul 15 12:58:20 UTC 2010 r...@lokschuppen.zs64.net:/usr/obj/usr/src/sys/EISENBOOT amd64 Once the box is up again, is it worthwile trying ichwd again, should I try and use SW_WATCHDOG, or forget about it? Thanks, Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: ichwd causes freeze instead of reset
Am 21.08.2010 um 23:02 schrieb Andriy Gapon: on 21/08/2010 23:33 Stefan Bethke said the following: Hi, somewhat foolishly, I activated watchdogd and ichwd on a remote box, and while testing it (by suspending watchdogd), apparently the watchdog triggered. But instead of resetting, the machine does not react anymore on the serial console. I will have to wait until Monday to get physical access, so it might be hanging or just switched itself off; I have no way of telling right now. ichwd probes as: ichwd0: Intel ICH7 watchdog timer on isa0 ichwd0: Intel ICH7 watchdog timer (ICH7 or equivalent) ppc0: cannot reserve I/O port range (not sure why ppc0 is getting involved at that point.) FreeBSD lokschuppen.zs64.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #30: Thu Jul 15 12:58:20 UTC 2010 r...@lokschuppen.zs64.net:/usr/obj/usr/src/sys/EISENBOOT amd64 Once the box is up again, is it worthwile trying ichwd again, should I try and use SW_WATCHDOG, or forget about it? Just test it more while having physical access before making any conclusions. There could be a number of radically different possibilities ranging from hardware peculiarities to configuration problems to pilot errors to etc. I guess what I'm looking for is some confirmation that ichwd is working properly on this particular hardware: Asus Pundit P4 P5G41 with a G41 chipset. Below are pciconv -lvb and dmesg: hos...@pci0:0:0:0: class=0x06 card=0x836d1043 chip=0x2e308086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI vgap...@pci0:0:2:0: class=0x03 card=0x836d1043 chip=0x2e328086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel G41 express graphics (PCIVEN_8086DEV_2E32SUBSYS_31031565REV_033115)' class = display subclass = VGA bar [10] = type Memory, range 64, base 0xfe40, size 4194304, enabled bar [18] = type Prefetchable Memory, range 64, base 0xe000, size 268435456, enabled bar [20] = type I/O Port, range 32, base 0xbc00, size 8, enabled vgap...@pci0:0:2:1: class=0x038000 card=0x836d1043 chip=0x2e338086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' class = display bar [10] = type Memory, range 64, base 0xfe80, size 1048576, enabled no...@pci0:0:27:0: class=0x040300 card=0x82fe1043 chip=0x27d88086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'IDT High Definition Audio Driver (BA101897)' class = multimedia subclass = HDA bar [10] = type Memory, range 64, base 0xfe3f8000, size 16384, enabled pc...@pci0:0:28:0: class=0x060400 card=0x81791043 chip=0x27d08086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) PCIe Root Port' class = bridge subclass = PCI-PCI pc...@pci0:0:28:2: class=0x060400 card=0x81791043 chip=0x27d48086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) PCIe Root Port' class = bridge subclass = PCI-PCI pc...@pci0:0:28:3: class=0x060400 card=0x81791043 chip=0x27d68086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) PCIe Root Port' class = bridge subclass = PCI-PCI uh...@pci0:0:29:0: class=0x0c0300 card=0x81791043 chip=0x27c88086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0xb400, size 32, enabled uh...@pci0:0:29:1: class=0x0c0300 card=0x81791043 chip=0x27c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0xb480, size 32, enabled uh...@pci0:0:29:2: class=0x0c0300 card=0x81791043 chip=0x27ca8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0xb800, size 32, enabled uh...@pci0:0:29:3: class=0x0c0300 card=0x81791043 chip=0x27cb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB bar [20] = type I/O Port, range 32, base 0xb880, size 32, enabled eh...@pci0:0:29:7: class=0x0c0320 card=0x81791043 chip=0x27cc8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xfe3f7c00, size 1024, enabled pc...@pci0:0:30:0: class=0x060401 card
Re: ichwd causes freeze instead of reset
Am 21.08.2010 um 23:24 schrieb Mike Tancsa: At 05:09 PM 8/21/2010, Stefan Bethke wrote: I guess what I'm looking for is some confirmation that ichwd is working properly on this particular hardware: Asus Pundit P4 P5G41 with a G41 chipset. Dont know about that particular MB implementation, but I have a number of various ICH7 based boards where ichwd works as expected. The freeze could some something as simple as the box is waiting for keyboard input at the BIOS prompt, or the BIOS option after a watchdog reset is to power off However, I have only seen that option in later boards. Thanks, I'll check that out Monday morning. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Inconsistent IO performance
Am 13.08.2010 um 18:01 schrieb Kevin Oberman: Note the dramatic differences even on the same kernel. For the December 6 kernel, for example, I see a maximum of 23,676,086 and a minimum of just 18,304,565. Are the disks still OK? If any sectors have been remapped between runs, additional seeks would be needed. I think it's unlikely, but checking with smartmontools should only take a few minutes. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: make world fails in usr.sbin/config?
Am 24.05.2010 um 19:49 schrieb Jeremy Chadwick: On Mon, May 24, 2010 at 09:24:00AM -0700, Jeremy Chadwick wrote: Builds are underway now (following /usr/src/Makefile method), I'll report back when those are done. I'm also adding time in front of the make buildXXX portions just to see now long things take. The build portions finished. Here are the numbers (quite high due to a combination of limited memory constraints (intentional) and the fact that VMware Workstation isn't the fastest thing on the planet. :-) ) For the record: I'm now running -stable as of last night, compiled without issue on ZFS filesystems throughout. No idea what caused the issue in the first place, and what made it disappear though, but updating to the correctly built -stable made the build on ZFS work again. (It also involved an accidential upgrade and downgrade via -current, since I checked out the wrong tag with csup. Yikes.) Thanks for all the support to all of you! Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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
make world fails in usr.sbin/config?
I have a feeling I screwed something up, but I can't find anything wrong
locally.
# uname -a
FreeBSD diesel.lassitu.de 8.0-STABLE FreeBSD 8.0-STABLE #9 r204100: Sat Feb 20
09:53:14 CET 2010 r...@diesel.lassitu.de:/usr/obj/usr/src/sys/DIESEL amd64
# svn info
Path: .
URL: svn://svn.freebsd.org/base/stable/8
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 208493
Node Kind: directory
Schedule: normal
Last Changed Author: mav
Last Changed Rev: 208492
Last Changed Date: 2010-05-24 13:01:56 +0200 (Mon, 24 May 2010)
[...]
=== usr.sbin/config (obj,depend,all,install)
/usr/obj/usr/src/tmp/usr/src/usr.sbin/config created for
/usr/src/usr.sbin/config
yacc -d /usr/src/usr.sbin/config/config.y
cp y.tab.c config.c
lex -t /usr/src/usr.sbin/config/lang.l lang.c
file2c 'char kernconfstr[] = {' ',0};' /usr/src/usr.sbin/config/kernconf.tmpl
kernconf.c
rm -f .depend
mkdep -f .depend -a-I. -I/usr/src/usr.sbin/config
-I/usr/obj/usr/src/tmp/legacy/usr/include config.c
/usr/src/usr.sbin/config/main.c lang.c /usr/src/usr.sbin/config/mkmakefile.c
/usr/src/usr.sbin/config/mkheaders.c /usr/src/usr.sbin/config/mkoptions.c
kernconf.c
echo config: /usr/lib/libc.a /usr/lib/libl.a /usr/lib/libsbuf.a
/usr/obj/usr/src/tmp/legacy/usr/lib/libegacy.a .depend
cc -O2 -pipe -I. -I/usr/src/usr.sbin/config
-I/usr/obj/usr/src/tmp/legacy/usr/include -c config.c
config.c:214: error: expected '=', ',', ';', 'asm' or '__attribute__' before
'*' token
config.c:215: error: expected '=', ',', ';', 'asm' or '__attribute__' before
'yyval'
config.c:216: error: expected '=', ',', ';', 'asm' or '__attribute__' before
'yylval'
config.c:219: error: expected '=', ',', ';', 'asm' or '__attribute__' before
'*' token
/usr/src/usr.sbin/config/config.y: In function 'yyerror':
/usr/src/usr.sbin/config/config.y:312: error: 'yyfile' undeclared (first use in
this function)
/usr/src/usr.sbin/config/config.y:312: error: (Each undeclared identifier is
reported only once
/usr/src/usr.sbin/config/config.y:312: error: for each function it appears in.)
/usr/src/usr.sbin/config/config.y:312: error: 'yyline' undeclared (first use in
this function)
/usr/src/usr.sbin/config/config.y: In function 'yywrap':
/usr/src/usr.sbin/config/config.y:318: error: 'found_defaults' undeclared
(first use in this function)
/usr/src/usr.sbin/config/config.y:319: error: 'PREFIX' undeclared (first use in
this function)
/usr/src/usr.sbin/config/config.y:319: error: 'stdin' undeclared (first use in
this function)
/usr/src/usr.sbin/config/config.y:319: warning: comparison between pointer and
integer
/usr/src/usr.sbin/config/config.y:321: error: 'yyfile' undeclared (first use in
this function)
/usr/src/usr.sbin/config/config.y:322: error: 'yyline' undeclared (first use in
this function)
/usr/src/usr.sbin/config/config.y: In function 'newfile':
/usr/src/usr.sbin/config/config.y:337: error: dereferencing pointer to
incomplete type
/usr/src/usr.sbin/config/config.y:340: error: dereferencing pointer to
incomplete type
/usr/src/usr.sbin/config/config.y:341: error: 'fntab' undeclared (first use in
this function)
/usr/src/usr.sbin/config/config.y:341: error: 'f_next' undeclared (first use in
this function)
/usr/src/usr.sbin/config/config.y: At top level:
/usr/src/usr.sbin/config/config.y:348: warning: 'struct device_head' declared
inside parameter list
e type
y.tab.c: In function 'yygrowstack':
y.tab.c:382: error: 'YYSTYPE' undeclared (first use in this function)
y.tab.c:382: error: 'newvs' undeclared (first use in this function)
y.tab.c:397: error: 'yyvs' undeclared (first use in this function)
y.tab.c:397: error: expected expression before ')' token
y.tab.c:402: error: 'yyvsp' undeclared (first use in this function)
y.tab.c: In function 'yyparse':
y.tab.c:456: error: 'yyvsp' undeclared (first use in this function)
y.tab.c:456: error: 'yyvs' undeclared (first use in this function)
y.tab.c:488: error: 'yylval' undeclared (first use in this function)
y.tab.c:569: error: 'yyval' undeclared (first use in this function)
*** Error code 1
Stop in /usr/src/usr.sbin/config.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
*** Error code 1
Stop in /usr/src.
--
Stefan Bethke s...@lassitu.de Fon +49 151 14070811
___
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
