Rodney W. Grimes wrote:
[stuff snipped]
>Daniel Ebdrup Jensen wrote:
>> Hi Rick,
>>
>> If I understand your plans correctly, you're not going to be making
>> it so that minorversion=N complains?
>
>Ah, I think that if you specify a minorversion and the server
>does not support that mino
On 2021-May-14, at 13:48, Rodney W. Grimes
wrote:
>>
>> On 2021-May-14, at 05:52, Rodney W. Grimes > gndrsh.dnsmgr.net> wrote:
>>
Note: The context was using a non-debug main build
from mid-2021-Mar. (More details identified
later.)
The issue happend while att
>
> On 2021-May-14, at 05:52, Rodney W. Grimes gndrsh.dnsmgr.net> wrote:
>
> >> Note: The context was using a non-debug main build
> >> from mid-2021-Mar. (More details identified
> >> later.)
> >>
> >> The issue happend while attempting a:
> >>
> >> # zfs send -R zpold@for-copy | zf
I vote for this.
+1
- Peter
> On 14 May 2021, at 01:02, Rick Macklem wrote:
>
> Hi,
>
> I believe that NFSv4.1 and NFSv4.2 are now mature in freebsd-current/main.
> I also believe that NFSv4.1/4.2 is a better protocol than NFSv4.0.
> (In particular, the sessions mechanism for "exactly once R
On 2021-May-14, at 05:52, Rodney W. Grimes
wrote:
>> Note: The context was using a non-debug main build
>> from mid-2021-Mar. (More details identified
>> later.)
>>
>> The issue happend while attempting a:
>>
>> # zfs send -R zpold@for-copy | zfs recv -Fdv zpnew
>>
>> where the dr
On Fri, May 14, 2021, 11:03 AM Marc Veldman wrote:
>
>
> > On 14 May 2021, at 17:29, Henri Hennebert wrote:
> >
> > On 5/14/21 5:05 PM, Marc Veldman wrote:
> >>> On 14 May 2021, at 16:48, Gary Jennejohn wrote:
> >>>
> >>> On Fri, 14 May 2021 16:21:05 +0200
> >>> Marc Veldman wrote:
> >>>
> >>>
> On 14 May 2021, at 17:29, Henri Hennebert wrote:
>
> On 5/14/21 5:05 PM, Marc Veldman wrote:
>>> On 14 May 2021, at 16:48, Gary Jennejohn wrote:
>>>
>>> On Fri, 14 May 2021 16:21:05 +0200
>>> Marc Veldman wrote:
>>>
> On 14 May 2021, at 10:22, Henri Hennebert wrote:
>
>
>>
On 5/14/21 5:05 PM, Marc Veldman wrote:
On 14 May 2021, at 16:48, Gary Jennejohn wrote:
On Fri, 14 May 2021 16:21:05 +0200
Marc Veldman wrote:
On 14 May 2021, at 10:22, Henri Hennebert wrote:
Please test the 2.0h version from GitHub.
On my Lenovo P50s:
Cold boot with card not insert
On 13/05/2021 16:09, Lev Serebryakov wrote:
It doesn't panic, boots and works more than 500 seconds :-)
The Power To Serve
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send a
On 14.05.2021 18:05, Marc Veldman wrote:
I removed the flag, and it works now.Thanks!
What is it in the trace that indicated that the inversion flag is not needed?
THIS:
Insert card after boot, no crash, but the message
seems weird:
May 14 16:01:27 supernovo kernel: rtsx0: Interrupt card i
> On 14 May 2021, at 16:48, Gary Jennejohn wrote:
>
> On Fri, 14 May 2021 16:21:05 +0200
> Marc Veldman wrote:
>
>>> On 14 May 2021, at 10:22, Henri Hennebert wrote:
>>>
>>>
>>> Please test the 2.0h version from GitHub.
>>>
>>
>> On my Lenovo P50s:
>>
>> Cold boot with card not inserted
On Fri, 14 May 2021 16:21:05 +0200
Marc Veldman wrote:
> > On 14 May 2021, at 10:22, Henri Hennebert wrote:
> >
> >
> > Please test the 2.0h version from GitHub.
> >
>
> On my Lenovo P50s:
>
> Cold boot with card not inserted: OK
> Insert card after boot, no crash, but the message
> seems
On Thu, May 13, 2021 at 5:02 PM Rick Macklem wrote:
> Hi,
>
> I believe that NFSv4.1 and NFSv4.2 are now mature in freebsd-current/main.
> I also believe that NFSv4.1/4.2 is a better protocol than NFSv4.0.
> (In particular, the sessions mechanism for "exactly once RPC semantics"
> is a significa
Daniel Ebdrup Jensen wrote:
>On Thu, May 13, 2021 at 11:02:35PM +, Rick Macklem wrote:
>>Hi,
>>
>>I believe that NFSv4.1 and NFSv4.2 are now mature in freebsd-current/main.
>>I also believe that NFSv4.1/4.2 is a better protocol than NFSv4.0.
>>(In particular, the sessions mechanism for "exactly
> On 14 May 2021, at 10:22, Henri Hennebert wrote:
>
>
> Please test the 2.0h version from GitHub.
>
On my Lenovo P50s:
Cold boot with card not inserted: OK
Insert card after boot, no crash, but the message
seems weird:
May 14 16:01:27 supernovo kernel: rtsx0: Interrupt card inserted/remo
> On Thu, May 13, 2021 at 11:02:35PM +, Rick Macklem wrote:
> >Hi,
> >
> >I believe that NFSv4.1 and NFSv4.2 are now mature in freebsd-current/main.
> >I also believe that NFSv4.1/4.2 is a better protocol than NFSv4.0.
> >(In particular, the sessions mechanism for "exactly once RPC semantics"
>
> On 5/13/21 9:00 PM, Rodney W. Grimes wrote:
> >> On 12.05.2021 21:01, Marc Veldman wrote:
> >>
> >>> I?m not sure if this is an interesting data point or not,
> >>> but a warm boot without the card inserted succeeds after
> >>> a cold boot with the card inserted.
> >>
> >>It could explain, wh
> Note: The context was using a non-debug main build
> from mid-2021-Mar. (More details identified
> later.)
>
> The issue happend while attempting a:
>
> # zfs send -R zpold@for-copy | zfs recv -Fdv zpnew
>
> where the drives involved in the command were:
>
> zpold: a USB3 SSD, usi
On 5/13/21 9:00 PM, Rodney W. Grimes wrote:
On 12.05.2021 21:01, Marc Veldman wrote:
I?m not sure if this is an interesting data point or not,
but a warm boot without the card inserted succeeds after
a cold boot with the card inserted.
It could explain, why my tests with "same code path" g
On 14.05.2021 11:22, Henri Hennebert wrote:
Please test the 2.0h version from GitHub.
Cold Boot with card: OK
Card removal after boot: OK
Cold Boot without card:OK
Card insertion after boot: OK
It is with 14-CURRENT n246524-95a74ab4fb0
--
// Lev Serebryakov
_
On May 14, 2021 5:59:48 AM UTC, Mark Millard via freebsd-current
wrote:
>The [usb{usbus2}] process eventually got stuck-busy, no
>more I/O:
>
>
>The system was a MACCHIATObin Double Shot.
I've noticed USB issues on the mcbin too.
In my experience uaudio was the most likely thing to freeze: so
On Thu, May 13, 2021 at 11:02:35PM +, Rick Macklem wrote:
Hi,
I believe that NFSv4.1 and NFSv4.2 are now mature in freebsd-current/main.
I also believe that NFSv4.1/4.2 is a better protocol than NFSv4.0.
(In particular, the sessions mechanism for "exactly once RPC semantics"
is a significant
On 5/13/21 7:55 PM, Lev Serebryakov wrote:
On 13.05.2021 18:56, Henri Hennebert wrote:
So if I understand correctly, your problem is solved.
Stupid me. I didn't check card insertion/removal after boot.
Card REMOVAL when boot was WITH CARD:
Instant panic:
rtsx0: Interrupt card inserted/re
On 5/13/21 7:25 PM, Marc Veldman wrote:
On 13 May 2021, at 17:56, Henri Hennebert wrote:
On 5/13/21 5:51 PM, Lev Serebryakov wrote:
On 13.05.2021 18:38, Henri Hennebert via freebsd-current wrote:
This seems a good news.
Can you replace sys/dev/rtsx.c by the latest version (2.0g) from
http
jake h writes:
> > What about adding a new flag to enable strtoul behavior?
> I have had a look at the available flag options for a potential strtoul
> flag, and a flag that makes sense to me is [-s] / [--strtoul]. [-s] is not
> currently being used in i2c, if we wanted to use it.
-s is
25 matches
Mail list logo
