Check the return code of intr_setaffinity() and log any errors
it returns. When a qid is not located, log an error before returning
failure.
Details
- Reviewers
sbruno - Commits
- rS323879: Improved logging of gtaskqueue failues
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
sys/kern/subr_gtaskqueue.c | ||
---|---|---|
793 ↗ | (On Diff #33271) | pedantic nit. Do you want to explicitly put the function name in the printf() calls here or should we use func ? Basically, all these printf() calls should be one way or the other. |
Hi Stephen,
Just wanted to mention that this patch is causing warning messages with bnxt driver during load.
If there is any thing missing in bnxt driver, we will implement. kindly let me know.
bnxt0: using 12 rx queues 12 tx queues
bnxt0: Using MSIX interrupts with 13 vectors
taskqgroup_attach_cpu: setaffinity failed: 3
taskqgroup_attach_cpu: setaffinity failed: 3
taskqgroup_attach_cpu: setaffinity failed: 3
taskqgroup_attach_cpu: setaffinity failed: 3
taskqgroup_attach_cpu: setaffinity failed: 3
taskqgroup_attach_cpu: setaffinity failed: 3
taskqgroup_attach_cpu: setaffinity failed: 3
taskqgroup_attach_cpu: setaffinity failed: 3
taskqgroup_attach: setaffinity failed: 3
taskqgroup_attach: setaffinity failed: 3
taskqgroup_attach: setaffinity failed: 3
taskqgroup_attach: setaffinity failed: 3
taskqgroup_attach: setaffinity failed: 3
taskqgroup_attach: setaffinity failed: 3
taskqgroup_attach: setaffinity failed: 3
taskqgroup_attach: setaffinity failed: 3
bnxt0: Ethernet address: 00:0a:f7:c4:b2:c0
Thanks,
Chenna.
I should have a patch that fixes these issues today or tomorrow. It appears the rid parameter does not actually expect an rid.
Thanks for the heads-up.