Re: Samsung T7 external SSD support?

2025-04-04 Thread Poul-Henning Kamp
Steve Kargl writes: > which is what I expected. So, the extension cable seems to be an issue. USB-C is objectively an amazing feat of data transmission, and there is no margin for shoddy cables. This is the insides of a USB-C cable: https://opencircuitsbook.com/#outtake-28 (

Re: Samsung T7 external SSD support?

2025-04-04 Thread Steve Kargl
On 4/4/25 19:44, Steve Kargl wrote: On 4/4/25 19:28, Alexander Motin wrote: On 04.04.2025 21:45, Steve Kargl wrote: Anyone using a Samsung T7 external SSD with FreeBSD current? If I plug the drive into a USB 2.0 port, I see usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage dev

UPDATE: pkg 2.1.0 looks to be making official bulk builds of packages take much longer

2025-04-04 Thread Mark Millard
[This is an update of earlier notes, now that I've noticed what is different for the contexts that not seeing larger time frames in the Mar-29/Apr-01 bulk build starts of official package builds.] The context here is the official bulk builds started 2025-Mar-29 (beefy 17 and beefy18) or 2025-Apr-0

Re: FYI: main-armv64-default bulk build times (ampere2) look to have grown significantly [...]; 142amd64-default (beefy22) as well

2025-04-04 Thread Mark Millard
On Apr 4, 2025, at 09:04, Mark Millard wrote: > Longest ever prior bulk build of main-arm64-default (HHH:MM:SS): 171:50:51 > (Host OSVERSION: 1500019) > > On going bulk build: Built 11348 Remaining 23676(HHH:MM:SS): 85:57:28 > > This suggests possibly more like 230+ Hrs for the completed

Re: FYI: main-armv64-default bulk build times (ampere2) look to have grown significantly [...]; 142amd64-default (beefy22) as well; more, including 72 hrs+ longer for main-amd64-default (beefy18)

2025-04-04 Thread Mark Millard
[Note: The new main-amd64 (beefy18) example reported is still building but has taken over 72 hrs longer than any other prior example. There is a major performance change involved compared to builds started before April. Slower hardware makes that more obvious than the fastest hardware does.] On Ap

Re: Samsung T7 external SSD support?

2025-04-04 Thread Steve Kargl
On 4/4/25 19:28, Alexander Motin wrote: On 04.04.2025 21:45, Steve Kargl wrote: Anyone using a Samsung T7 external SSD with FreeBSD current? If I plug the drive into a USB 2.0 port, I see usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device Samsung PSSD T7 Shield (0x04e8:0x

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Rick Macklem
On Fri, Apr 4, 2025 at 6:36 PM Shawn Webb wrote: > > On Sat, Apr 05, 2025 at 01:27:17AM +, Shawn Webb wrote: > > On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote: > > > On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote: > > > > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Rick Macklem
On Fri, Apr 4, 2025 at 6:27 PM Shawn Webb wrote: > > On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote: > > On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote: > > > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb > > > wrote: > > > > > > > > On Thu, Apr 03, 2025 at 06:12:59PM -070

Re: Samsung T7 external SSD support?

2025-04-04 Thread Alexander Motin
On 04.04.2025 21:45, Steve Kargl wrote: Anyone using a Samsung T7 external SSD with FreeBSD current? If I plug the drive into a USB 2.0 port, I see usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device Samsung PSSD T7 Shield (0x04e8:0x61fb) ugen0.2: at usbus0 umass0 on uhub

Samsung T7 external SSD support?

2025-04-04 Thread Steve Kargl
Anyone using a Samsung T7 external SSD with FreeBSD current? If I plug the drive into a USB 2.0 port, I see usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device Samsung PSSD T7 Shield (0x04e8:0x61fb) ugen0.2: at usbus0 umass0 on uhub1 umass0: on usbus0 umass0: SCSI over

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Shawn Webb
On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote: > On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote: > > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb > > wrote: > > > > > > On Thu, Apr 03, 2025 at 06:12:59PM -0700, Rick Macklem wrote: > > > > On Thu, Apr 3, 2025 at 4:52 PM Sh

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Shawn Webb
On Sat, Apr 05, 2025 at 01:27:17AM +, Shawn Webb wrote: > On Sat, Apr 05, 2025 at 01:04:25AM +, Shawn Webb wrote: > > On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote: > > > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb > > > wrote: > > > > > > > > On Thu, Apr 03, 2025 at 06:12:5

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Shawn Webb
On Fri, Apr 04, 2025 at 05:40:21PM -0700, Rick Macklem wrote: > On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb wrote: > > > > On Thu, Apr 03, 2025 at 06:12:59PM -0700, Rick Macklem wrote: > > > On Thu, Apr 3, 2025 at 4:52 PM Shawn Webb > > > wrote: > > > > > > > > On Wed, Apr 02, 2025 at 01:51:26PM

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Rick Macklem
On Fri, Apr 4, 2025 at 10:50 AM Shawn Webb wrote: > > On Thu, Apr 03, 2025 at 06:12:59PM -0700, Rick Macklem wrote: > > On Thu, Apr 3, 2025 at 4:52 PM Shawn Webb > > wrote: > > > > > > On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote: > > > > The commit 2ec2ba7e232d just hit main. I

Re: Possible video driver issue after main-n275966-d2a55e6a9348 -> main-n275975-5963423232e8

2025-04-04 Thread Mark Johnston
On Fri, Mar 21, 2025 at 02:50:58AM -0700, Gleb Smirnoff wrote: > On Fri, Mar 21, 2025 at 05:34:16AM -0400, Mark Johnston wrote: > M> On Fri, Mar 21, 2025 at 01:56:01AM -0700, Gleb Smirnoff wrote: > M> > On Thu, Mar 20, 2025 at 07:52:19PM +, Bjoern A. Zeeb wrote: > M> > B> He's hitting a ... som

Re: March 2025 stabilization week

2025-04-04 Thread Tomoaki AOKI
On Wed, 26 Mar 2025 19:02:35 +0100 Olivier Certner wrote: > Hi, > > Commit 2619c5ccfe1f7889f0241916bd17d06340142b05 you mentioned is not a > functional prerequisite (but it may prevent applying the patch straight away). > > Please find attached the straightforward MFC to stable/14 I've been us

Re: March 2025 stabilization week

2025-04-04 Thread Gleb Smirnoff
On Mon, Mar 24, 2025 at 01:00:11AM -0700, Gleb Smirnoff wrote: T> This is an automated email to inform you that the March 2025 stabilization week T> started with FreeBSD/main at main-n276073-67c1c4dfd1cc, which was tagged as T> main-stabweek-2025-Mar. At Netflix testing we didn't find any stabili

Re: Possible video driver issue after main-n275966-d2a55e6a9348 -> main-n275975-5963423232e8

2025-04-04 Thread Mark Johnston
On Fri, Mar 21, 2025 at 01:56:01AM -0700, Gleb Smirnoff wrote: > On Thu, Mar 20, 2025 at 07:52:19PM +, Bjoern A. Zeeb wrote: > B> He's hitting a ... somewhere in i915kms.ko (here's the two instances I > B> have): > B> REDZONE: Buffer underflow detected. 16 bytes corrupted before > 0xfe089b

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Shawn Webb
On Thu, Apr 03, 2025 at 06:12:59PM -0700, Rick Macklem wrote: > On Thu, Apr 3, 2025 at 4:52 PM Shawn Webb wrote: > > > > On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote: > > > The commit 2ec2ba7e232d just hit main. I do not think it will > > > cause problems, but it is fairly large.

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Dennis Clarke
On 4/4/25 10:25, Rick Macklem wrote: On Fri, Apr 4, 2025 at 6:37 AM Rick Macklem wrote: On Fri, Apr 4, 2025 at 1:48 AM Dennis Clarke wrote: . . . well ooops what was the idea here again ?? Well, this has nothing to do with my recent commit. Thus ooops. ZFS has always suppor

FYI: main-armv64-default bulk build times (ampere2) look to have grown significantly with Host OSVERSION: 1500035 instead of prior Host OSVERSION: 1500028

2025-04-04 Thread Mark Millard
Longest ever prior bulk build of main-arm64-default (HHH:MM:SS): 171:50:51 (Host OSVERSION: 1500019) On going bulk build: Built 11348 Remaining 23676(HHH:MM:SS): 85:57:28 This suggests possibly more like 230+ Hrs for the completed build. Now (0n going bulk build, first such): Host OSV

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Rick Macklem
On Fri, Apr 4, 2025 at 6:37 AM Rick Macklem wrote: > > On Fri, Apr 4, 2025 at 1:48 AM Dennis Clarke wrote: > > > > On 4/3/25 19:52, Shawn Webb wrote: > > > On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote: > > >> The commit 2ec2ba7e232d just hit main. I do not think it will > > >> ca

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Rick Macklem
On Fri, Apr 4, 2025 at 1:48 AM Dennis Clarke wrote: > > On 4/3/25 19:52, Shawn Webb wrote: > > On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote: > >> The commit 2ec2ba7e232d just hit main. I do not think it will > >> cause problems, but it is fairly large. > >> > >> Man page updates w

Re: Heads Up: commit 2ec2ba7e232d just hit main

2025-04-04 Thread Dennis Clarke
On 4/3/25 19:52, Shawn Webb wrote: On Wed, Apr 02, 2025 at 01:51:26PM -0700, Rick Macklem wrote: The commit 2ec2ba7e232d just hit main. I do not think it will cause problems, but it is fairly large. Man page updates will be done as separate commits. Hopefully this will not cause grief, rick