Re: patch-008 missing in CVS repo
ckeader wrote: > Brian Conway writes: > [...] > > >> I see similar results when I try pulling from a couple anoncvs mirrors. > > >> Perhaps a bug or oops in the CVS update process? > > > > > > Keep waiting while more of Canada wakes up and it will likely get > > > resolved. > > > In the meantime you could fetch the patch from the errata page and apply > > > it locally. > > > > Looks resolved now, thanks all. > > Sorry I'm late to the party, but this patch single-handedly broke two of > my machines. I don't have a complete dmesg now but ends roughly like > this: > > > scsibus3 at softraid0: 256 targets > root on sd0a (e524655a9f058e3f.a) swap on sd0b dump on sd0b > Process (pid 1) got signal 31 > Process (pid 1) got signal 12 > Process (pid 1) got signal 12 > Process (pid 1) got signal 12 > Process (pid 1) got signal 12 > > The above made me think of a disk related problem, and that's probably > close to the mark for one of the boxes (SSD dead - no longer detected > when tested in different machines). But the second server, completely > different hw, was recoverable with the 7.3 release kernel. > > That was a first in decades of OBSD use. You are probably holding it wrong.
Re: Allwinner D1 riscv64 mango pi SBC
Peter I understand losing the "warm and fuzzy" feeling. I lost mine too in mid-June when I spent 12 days in hospital and have no recollection of the first 4 days in hospital, but that is a story for another day. :-) I just sent an email to several OpenBSD developers to ping them regarding interest in MangoPi h/w. 73 diana KI5PGJ On Thu, Jul 20, 2023 at 2:42 AM Peter J. Philipp wrote: > > Hi all, > > Just so we don't lose the warm fuzzy feelings around this. Diana do you > want to give me your paypal address so I can transfer the 30 EUR to > you? I'm very excited about this, particularily because the mango pi > comes out of china. > > Here is some interesting read I googled the other day: > https://www.hpcwire.com/2023/07/19/how-china-is-building-an-open-national-chip-plan-around-risc-v/ > > Risc-v is really taking off! I do hope that sifive can give us > something of value, because I heard about this Milk-V computer giving > Intel/Sifive a run for their products. > > https://liliputing.com/milk-v-computers-feature-up-to-64-risc-v-cpu-cores/ > > That said I'm hoping on invest in another risc-v computer by next year. > Support for it will probably lack and I'll run linux on it for a while > perhaps. > > Best Regards, > > -peter > > On 7/19/23 03:40, deich...@placebonol.com wrote: > > I'm going to reach out to a few folks who I see are doing riscv64 > > specific development. I realize they might not want to take on yet > > another h/w design. > > > > g.day > > > > > > On July 18, 2023 3:14:18 PM MDT, Mike Larkin wrote: > > > > On Tue, Jul 18, 2023 at 02:02:45PM -0600, deich...@placebonol.com > > wrote: > > > > Hi Mike I've volunteered to coordinate a purchase of Mango Pi > > to get them into OpenBSD developers working on riscv64 > > platform. It has been awhile but I used to facilitate getting > > h/w into OpenBSD developers hands on a semi-regular basis. diana > > > > Great. I don't know who would be interested, so I'd wait to let > > them speak up before ordering anything. -ml > > > > On July 16, 2023 1:13:02 PM MDT, "Peter J. Philipp" > > wrote: > > > > On Sun, Jul 16, 2023 at 06:25:50PM +, Mike Larkin wrote: > > > > On Sun, Jul 16, 2023 at 11:56:51AM +0200, Peter J. > > Philipp wrote: > > > > Hi *, I'm back for the moment. I was wondering who > > has a Allwinner D1 riscv64 SBC? This is the Mango > > Pi SBC. I have one which has linux on it currently > > but I'm trying to boot OpenBSD on it. But I'm > > fairly lazy and haven't done much with this > > lately. I can get to the riscv64 loader but when > > it loads the kernel, it goes blind. So there is > > more than just getting the GPIO pins configured > > which I think I have been able to adjust. I use a > > QEMU-based riscv64 emulation to compile kernels > > which is slow but this SBC isn't much faster > > either (1000 Mhz it claims). I use this u-boot > > directive to get into the boot loader: setenv > > bootobsd 'load mmc 0:1 0x4FA0 > > > > /boot/dtbs/5.19.0-1009-allwinner/allwinner/sun20i-d1-nezha-memory.dtb > > ; load mmc 0:f 0x4008 > > /EFI/OpenBSD/BOOTRISCV64.EFI ; bootefi 0x4008 > > 0x4FA0' followed by a: run bootobsd I am > > unsure how to save this though in the u-boot > > itself. Any hints would be appreciated. I think we > > need a specific riscv mailing list for this sort > > of stuff perhaps it's too technical for misc. > > Regarding to the nostradamus stuff of someone from > > chicago (Re: A couple of Questions) , check out > > "1st wave" and "cade foster" on youtube (reruns), > > this will feed you more ideas. my personal opinion > > is that time travel of information is possible, > > contributing to major headaches when events get > > changed (for the prometheus seers). Back to > > "reality" I'm looking for a group of people to > > help getting the mango pi working. I'm hampered by > > pride to ask knowledged people and these people > > have their own directions and I don't want to > > bother their efforts. The more we are the more we > > could possibly get something done. > > > > The best way to get that done is to get hardware in > > the hands of developer(s). Wishing on misc@ is
Re: patch-008 missing in CVS repo
Brian Conway writes: [...] > >> I see similar results when I try pulling from a couple anoncvs mirrors. > >> Perhaps a bug or oops in the CVS update process? > > > > Keep waiting while more of Canada wakes up and it will likely get resolved. > > In the meantime you could fetch the patch from the errata page and apply > > it locally. > > Looks resolved now, thanks all. Sorry I'm late to the party, but this patch single-handedly broke two of my machines. I don't have a complete dmesg now but ends roughly like this: scsibus3 at softraid0: 256 targets root on sd0a (e524655a9f058e3f.a) swap on sd0b dump on sd0b Process (pid 1) got signal 31 Process (pid 1) got signal 12 Process (pid 1) got signal 12 Process (pid 1) got signal 12 Process (pid 1) got signal 12 The above made me think of a disk related problem, and that's probably close to the mark for one of the boxes (SSD dead - no longer detected when tested in different machines). But the second server, completely different hw, was recoverable with the 7.3 release kernel. That was a first in decades of OBSD use.
Re: PF rate limiting options valid for UDP?
On Thu, Jul 20, 2023 at 05:52:07PM +, mabi wrote:
> --- Original Message ---
> On Wednesday, July 19th, 2023 at 10:58 PM, Stuart Henderson
> wrote:
>
> > For rules that pass traffic to your authoritative DNS servers,
> > I don't think you need much longer than the time taken to answer a
> > query. So could be quite a bit less.
>
> Right good point, I will add custom state timeouts for this specific UDP pass
> rule on port 53.
>
> > Usually carp/ospf will enter the state table before the machines start
> > seeing large amounts of packets and stay there, which is what you would
> > normally want. If the state table is full, you have more problem
> > opening new connections that require state to be added than you do
> > maintaining existing ones.
> >
> > fwiw I typically use this on ospf+carp machines, "pass quick proto
> > {carp, ospf} keep state (no-sync) set prio 7"
>
> That's very interesting, I never realized there was a simple priority system
> ready to use in PF without the need of setting up any queues. Probably the
> "set prio 7" option on OSPF+CARP pass rules will juts do the trick and I will
> definitely also implement this.
>
> > DNS server software is written with this type of traffic in mind, and
> > has more information available (from inside the DNS request packet)
> > to make a decision about what to do with it, than is available in a
> > general-purpose packet filter like PF.
> >
> > Also it stores the tracking information in data structures that have
> > been chosen to make sense for this use (and common DNS servers default
> > to masking on common subnet sizes, reducing the amount they have to
> > store compared to tracking the full IP address).
> >
> > http://man.openbsd.org/nsd.conf#rrl
> > https://bind9.readthedocs.io/en/latest/reference.html#response-rate-limiting
> > https://www.knot-dns.cz/docs/2.4/html/reference.html#module-rrl
>
> Too bad I use PowereDNS, it does not seem to offer much parameters related to
> rate-limiting for UDP but for TCP I found at least max-tcp-connections. Maybe
> it's time for a change as Gabor mentions his tests in his reply (thanks
> btw!)...
>
In a typical PowerDNS setup the task of rate limiting is done by dnsdist.
-Otto
Re: PF rate limiting options valid for UDP?
--- Original Message ---
On Wednesday, July 19th, 2023 at 10:58 PM, Stuart Henderson
wrote:
> For rules that pass traffic to your authoritative DNS servers,
> I don't think you need much longer than the time taken to answer a
> query. So could be quite a bit less.
Right good point, I will add custom state timeouts for this specific UDP pass
rule on port 53.
> Usually carp/ospf will enter the state table before the machines start
> seeing large amounts of packets and stay there, which is what you would
> normally want. If the state table is full, you have more problem
> opening new connections that require state to be added than you do
> maintaining existing ones.
>
> fwiw I typically use this on ospf+carp machines, "pass quick proto
> {carp, ospf} keep state (no-sync) set prio 7"
That's very interesting, I never realized there was a simple priority system
ready to use in PF without the need of setting up any queues. Probably the "set
prio 7" option on OSPF+CARP pass rules will juts do the trick and I will
definitely also implement this.
> DNS server software is written with this type of traffic in mind, and
> has more information available (from inside the DNS request packet)
> to make a decision about what to do with it, than is available in a
> general-purpose packet filter like PF.
>
> Also it stores the tracking information in data structures that have
> been chosen to make sense for this use (and common DNS servers default
> to masking on common subnet sizes, reducing the amount they have to
> store compared to tracking the full IP address).
>
> http://man.openbsd.org/nsd.conf#rrl
> https://bind9.readthedocs.io/en/latest/reference.html#response-rate-limiting
> https://www.knot-dns.cz/docs/2.4/html/reference.html#module-rrl
Too bad I use PowerDNS, it does not seem to offer much parameters related to
rate-limiting for UDP but for TCP I found at least max-tcp-connections. Maybe
it's time for a change as Gabor mentions his tests in his reply (thanks btw!)...
Re: Allwinner D1 riscv64 mango pi SBC
Hi Peter, I got a VisionFive2 SBC laying arround, so if this is of interest for the devs too I can ship it somewhere. cheers Markus Am 20.07.2023 um 10:32 schrieb Peter J. Philipp: Hi all, Just so we don't lose the warm fuzzy feelings around this. Diana do you want to give me your paypal address so I can transfer the 30 EUR to you? I'm very excited about this, particularily because the mango pi comes out of china. Here is some interesting read I googled the other day: https://www.hpcwire.com/2023/07/19/how-china-is-building-an-open-national-chip-plan-around-risc-v/ Risc-v is really taking off! I do hope that sifive can give us something of value, because I heard about this Milk-V computer giving Intel/Sifive a run for their products. https://liliputing.com/milk-v-computers-feature-up-to-64-risc-v-cpu-cores/ That said I'm hoping on invest in another risc-v computer by next year. Support for it will probably lack and I'll run linux on it for a while perhaps. Best Regards, -peter On 7/19/23 03:40, deich...@placebonol.com wrote: I'm going to reach out to a few folks who I see are doing riscv64 specific development. I realize they might not want to take on yet another h/w design. g.day On July 18, 2023 3:14:18 PM MDT, Mike Larkin wrote: On Tue, Jul 18, 2023 at 02:02:45PM -0600, deich...@placebonol.com wrote: Hi Mike I've volunteered to coordinate a purchase of Mango Pi to get them into OpenBSD developers working on riscv64 platform. It has been awhile but I used to facilitate getting h/w into OpenBSD developers hands on a semi-regular basis. diana Great. I don't know who would be interested, so I'd wait to let them speak up before ordering anything. -ml On July 16, 2023 1:13:02 PM MDT, "Peter J. Philipp" wrote: On Sun, Jul 16, 2023 at 06:25:50PM +, Mike Larkin wrote: On Sun, Jul 16, 2023 at 11:56:51AM +0200, Peter J. Philipp wrote: Hi *, I'm back for the moment. I was wondering who has a Allwinner D1 riscv64 SBC? This is the Mango Pi SBC. I have one which has linux on it currently but I'm trying to boot OpenBSD on it. But I'm fairly lazy and haven't done much with this lately. I can get to the riscv64 loader but when it loads the kernel, it goes blind. So there is more than just getting the GPIO pins configured which I think I have been able to adjust. I use a QEMU-based riscv64 emulation to compile kernels which is slow but this SBC isn't much faster either (1000 Mhz it claims). I use this u-boot directive to get into the boot loader: setenv bootobsd 'load mmc 0:1 0x4FA0 /boot/dtbs/5.19.0-1009-allwinner/allwinner/sun20i-d1-nezha-memory.dtb ; load mmc 0:f 0x4008 /EFI/OpenBSD/BOOTRISCV64.EFI ; bootefi 0x4008 0x4FA0' followed by a: run bootobsd I am unsure how to save this though in the u-boot itself. Any hints would be appreciated. I think we need a specific riscv mailing list for this sort of stuff perhaps it's too technical for misc. Regarding to the nostradamus stuff of someone from chicago (Re: A couple of Questions) , check out "1st wave" and "cade foster" on youtube (reruns), this will feed you more ideas. my personal opinion is that time travel of information is possible, contributing to major headaches when events get changed (for the prometheus seers). Back to "reality" I'm looking for a group of people to help getting the mango pi working. I'm hampered by pride to ask knowledged people and these people have their own directions and I don't want to bother their efforts. The more we are the more we could possibly get something done. The best way to get that done is to get hardware in the hands of developer(s). Wishing on misc@ is likely not going to get anyone interested. Check the commit logs for people working in this area, reach out to them, and see if they are interested in helping. -ml Hi Mike, Thanks. This will take a bit, I'm in talks to get a new job soon, which will put extra money in my pocket. Then I may be able to get a handful of these perhaps. Do you still keep tabs on Shivam, Mars, Brian, and Wenyan? Are
Re: Allwinner D1 riscv64 mango pi SBC
Hi all, Just so we don't lose the warm fuzzy feelings around this. Diana do you want to give me your paypal address so I can transfer the 30 EUR to you? I'm very excited about this, particularily because the mango pi comes out of china. Here is some interesting read I googled the other day: https://www.hpcwire.com/2023/07/19/how-china-is-building-an-open-national-chip-plan-around-risc-v/ Risc-v is really taking off! I do hope that sifive can give us something of value, because I heard about this Milk-V computer giving Intel/Sifive a run for their products. https://liliputing.com/milk-v-computers-feature-up-to-64-risc-v-cpu-cores/ That said I'm hoping on invest in another risc-v computer by next year. Support for it will probably lack and I'll run linux on it for a while perhaps. Best Regards, -peter On 7/19/23 03:40, deich...@placebonol.com wrote: I'm going to reach out to a few folks who I see are doing riscv64 specific development. I realize they might not want to take on yet another h/w design. g.day On July 18, 2023 3:14:18 PM MDT, Mike Larkin wrote: On Tue, Jul 18, 2023 at 02:02:45PM -0600, deich...@placebonol.com wrote: Hi Mike I've volunteered to coordinate a purchase of Mango Pi to get them into OpenBSD developers working on riscv64 platform. It has been awhile but I used to facilitate getting h/w into OpenBSD developers hands on a semi-regular basis. diana Great. I don't know who would be interested, so I'd wait to let them speak up before ordering anything. -ml On July 16, 2023 1:13:02 PM MDT, "Peter J. Philipp" wrote: On Sun, Jul 16, 2023 at 06:25:50PM +, Mike Larkin wrote: On Sun, Jul 16, 2023 at 11:56:51AM +0200, Peter J. Philipp wrote: Hi *, I'm back for the moment. I was wondering who has a Allwinner D1 riscv64 SBC? This is the Mango Pi SBC. I have one which has linux on it currently but I'm trying to boot OpenBSD on it. But I'm fairly lazy and haven't done much with this lately. I can get to the riscv64 loader but when it loads the kernel, it goes blind. So there is more than just getting the GPIO pins configured which I think I have been able to adjust. I use a QEMU-based riscv64 emulation to compile kernels which is slow but this SBC isn't much faster either (1000 Mhz it claims). I use this u-boot directive to get into the boot loader: setenv bootobsd 'load mmc 0:1 0x4FA0 /boot/dtbs/5.19.0-1009-allwinner/allwinner/sun20i-d1-nezha-memory.dtb ; load mmc 0:f 0x4008 /EFI/OpenBSD/BOOTRISCV64.EFI ; bootefi 0x4008 0x4FA0' followed by a: run bootobsd I am unsure how to save this though in the u-boot itself. Any hints would be appreciated. I think we need a specific riscv mailing list for this sort of stuff perhaps it's too technical for misc. Regarding to the nostradamus stuff of someone from chicago (Re: A couple of Questions) , check out "1st wave" and "cade foster" on youtube (reruns), this will feed you more ideas. my personal opinion is that time travel of information is possible, contributing to major headaches when events get changed (for the prometheus seers). Back to "reality" I'm looking for a group of people to help getting the mango pi working. I'm hampered by pride to ask knowledged people and these people have their own directions and I don't want to bother their efforts. The more we are the more we could possibly get something done. The best way to get that done is to get hardware in the hands of developer(s). Wishing on misc@ is likely not going to get anyone interested. Check the commit logs for people working in this area, reach out to them, and see if they are interested in helping. -ml Hi Mike, Thanks. This will take a bit, I'm in talks to get a new job soon, which will put extra money in my pocket. Then I may be able to get a handful of these perhaps. Do you still keep tabs on Shivam, Mars, Brian, and Wenyan? Are they still interested in riscv64 after the initial port with yours and Dales guidance? I think I paid something like 30 EUR for a Mango Pi
