Bus scan is too chatty
DPDK EAL needs to be less verbose for non-existent buses. Most users won't have embedded devices, and messages like:
EAL: Scan for (fslmc) bus failed.
will be confusing.
10/11/2024 20:17, Stephen Hemminger:
Quoted 6 lines
DPDK EAL needs to be less verbose for non-existent buses. Most users won't have embedded devices, and messages like:
EAL: Scan for (fslmc) bus failed.
will be confusing.
When merging the recent fslmc patches, I've reduced the verbosity of some fslmc logs appearing at the cleanup stage.
This log is from EAL because fslmc scan fails.
It should not return an error if there is no bus or no environment variable.
Sachin, Hemant, please could you fix it?
Quoted 19 lines
-----Original Message-----
From: Thomas Monjalon <[email protected]>
Sent: Monday, November 11, 2024 3:02 PM
To: Stephen Hemminger <[email protected]>; Gagandeep Singh <[email protected]>; Sachin Saxena (OSS) <[email protected]>; Hemant Agrawal <[email protected]>
Cc: [email protected]
Subject: Re: Bus scan is too chatty
Importance: High10/11/2024 20:17, Stephen Hemminger:
Quoted 6 lines
DPDK EAL needs to be less verbose for non-existent buses. Most users won't have embedded devices, and messages like:
EAL: Scan for (fslmc) bus failed.
will be confusing.
Quoted 8 lines
When merging the recent fslmc patches, I've reduced the verbosity of some fslmc logs appearing at the cleanup stage.
This log is from EAL because fslmc scan fails.
It should not return an error if there is no bus or no environment variable.Sachin, Hemant, please could you fix it?
[Hemant] yes, let me have a look and provide a fix.
Hello,
I'm noting here that the compressdev test failures reported over the weekend for the Community Lab are related to this, as the DTS compressdev tests fail if EAL contains "failed." So, these patchseries failures can be ignored by maintainers.
I see the fix from Hemant was merged by Thomas. It looks like some of the recent failures are from series applied to next-net, so I'm guessing that branch need to be rebased on main.
Thanks.
Quoted 30 lines · Hemant Agrawal
Quoted 17 lines
-----Original Message-----
From: Thomas Monjalon <[email protected]>
Sent: Monday, November 11, 2024 3:02 PM
To: Stephen Hemminger <[email protected]>; Gagandeep Singh <[email protected]>; Sachin Saxena (OSS) <[email protected]>; Hemant Agrawal <[email protected]>
Cc: [email protected]
Subject: Re: Bus scan is too chatty
Importance: High10/11/2024 20:17, Stephen Hemminger:
Quoted 5 lines
DPDK EAL needs to be less verbose for non-existent buses. Most users won't have embedded devices, and messages like:
EAL: Scan for (fslmc) bus failed.
Quoted 7 lines
Quoted 1 line
will be confusing.
When merging the recent fslmc patches, I've reduced the verbosity of some fslmc logs appearing at the cleanup stage.
This log is from EAL because fslmc scan fails.
It should not return an error if there is no bus or no environmentvariable.
Quoted 3 lines
Sachin, Hemant, please could you fix it?
[Hemant] yes, let me have a look and provide a fix.
Quoted 11 lines · Patrick Robb
Hello,
I'm noting here that the compressdev test failures reported over the weekend for the Community Lab are related to this, as the DTS compressdev tests fail if EAL contains "failed." So, these patchseries failures can be ignored by maintainers.
I see the fix from Hemant was merged by Thomas. It looks like some of the recent failures are from series applied to next-net, so I'm guessing that branch need to be rebased on main.
Hi Patrick,
I am not clear with problem, but I rebased next-net on -rc2, will this fix the issue for you?
Quoted 40 lines
Thanks.
Quoted 2 lines · On Mon, Nov 11, 2024 at 4:36 AM Hemant Agrawal <[email protected]…
-----Original Message-----
From: Thomas Monjalon <[email protected]<mailto:[email protected]>>
> Sent: Monday, November 11, 2024 3:02 PM
> To: Stephen Hemminger <[email protected] <mailto:[email protected]>>; Gagandeep Singh
> <[email protected] <mailto:[email protected]>>; Sachin Saxena (OSS) <[email protected] <mailto:[email protected]>>; > Hemant Agrawal <[email protected] <mailto:[email protected]>>
> Cc: [email protected] <mailto:[email protected]>
> Subject: Re: Bus scan is too chatty
> Importance: High
>
> 10/11/2024 20:17, Stephen Hemminger:
> > DPDK EAL needs to be less verbose for non-existent buses. > > Most users won't have embedded devices, and messages like:
> >
> > EAL: Scan for (fslmc) bus failed.
> >
> > will be confusing.
>
> When merging the recent fslmc patches, I've reduced the verbosity of some
> fslmc logs appearing at the cleanup stage.
>
> This log is from EAL because fslmc scan fails.
> It should not return an error if there is no bus or no environment variable.
>
> Sachin, Hemant, please could you fix it?
>
[Hemant] yes, let me have a look and provide a fix.
No worries Ferruh, the reason is not very interesting so you can stop here. :) Thanks for rebasing on rc2. But for the record, the cause is the EAL message:
"EAL: Scan for (fslmc) bus failed."
Which I believe is now removed with this commit which is now in next-net:
https://git.dpdk.org/next/dpdk-next-net/commit/?id=b472c50aeee1ca4f3a86be0580d31474653dfd8f
Cheers.