Hey Christian, Intel proposed change [1]
which is targeting this problem and based on our testing in fact it solves the
problem.
This change is currently added to Ubuntu Kernels.
I'm also keeping an eye on [2] but right now I don't yet see "business need" to
incorporate it to Ubuntu Kernel.
This
Fix already included in 6.8
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
Intel E810-XXV - NETD
Switching status for Noble to In Progress.
Target release for Noble is 6.8 (which includes fix) but it's not out yet,
status will be changed once 6.8 will be introduced.
** Changed in: linux (Ubuntu Noble)
Status: Invalid => In Progress
--
You received this bug notification because you a
roviding incorrect
credentials, which might
confuse users.
* Attaching tcpdump pcaps with SMB operations from 5.15 Kernel with and
without patch.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Robert Malz (rmalz)
Status: New
** Affects: linux (Ubuntu Focal)
Im
Attaching tcpdump output without patch
** Attachment added: "base_5_15_104_filtered.pcap"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+attachment/5766752/+files/base_5_15_104_filtered.pcap
--
You received this bug notification because you are a member of Kernel
Packages, whi
Attaching tcpdump output with patch
** Attachment added: "base_5_15_104_with_patch_filtered.pcap"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061986/+attachment/5766753/+files/base_5_15_104_with_patch_filtered.pcap
--
You received this bug notification because you are a member of
Jammy update:
Due to lack of reproduction environment I have been performing following
regression test:
1. Setup:
nic: 2port E810-XXV
both interfaces set up in bonding
kernel: 5.15.0-100-generic
2. Test cases:
0) verified that code from the change is used during driver init
a)
Hi Roxana,
Mantic verification is still not finished.
I did some touch tests without stress traffic.
I'm trying to get my hands on E810 device to finish testing, I'll update ticket
once it's done.
Wishful ETA EOW 09.
--
You received this bug notification because you are a member of Kernel
Packag
LP update:
Mantic update:
Due to lack of reproduction environment I have been performing following
regression test:
1. Setup:
nic: 2port E810-C
both interfaces set up in bonding
kernel: 6.5.0-25-generic
2. Test cases:
0) verified that code from the change is used during driver in
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-done-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036239
Title:
Intel E810-XXV - NETDEV WATC
** Description changed:
+ [Impact]
+ * Issue is causing transmit hang on E810 ports with bonding enabled.
+ * Based on the provided logs, TX hang can last for even a couple of
minutes, but in most scenarios, the network will be recovered after the ice
driver performs a PF reset (TX
Script to verify AQ 0x000A capabilities
** Attachment added: "parse_aq_0xA.py"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2036239/+attachment/5736421/+files/parse_aq_0xA.py
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
@Christian,
Can you verify your device capabilities returned from 0x000A looking for SRIOV
lag?
I have attached a script "parse_aq_0xA.py" you need to load driver with
dyndbg=+p and replace a buffer in script.
Note: buffer has to come from CQ CMD: opcode 0x000A
Expected result:
(...)
resp cap: 0x
Hey @Christian,
1a) No need, AQ 0x000A returns NVM capabilities regardless of configuration
applied (it's done during driver init)
1b) That's the point, I noticed you upgraded to 4.3 which I currently don't
have access to and I wanted to verify capabilities on 4.3. NVM caps should be
similar on
attaching apic.dsl files
** Attachment added: "clean_apic.dsl"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097455/+attachment/5855116/+files/clean_apic.dsl
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Public bug reported:
[ Impact ]
* In Kernels with commit ec9aedb2aa1a (6.7) CPUs can be enumerated in the order
which violates ACPI specification that states:
"OSPM should initialize processors in the order that they appear in the
MADT"
* The problematic commit parses all LAPIC ent
modified apic.dsl
** Attachment added: "modified_apic.dsl"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2097455/+attachment/5855117/+files/modified_apic.dsl
** Summary changed:
- Fix LAPIC/x2APIC parsing order
+ Incorrect LAPIC/x2APIC parsing order
--
You received this bug notifica
Tested CPU ordering on both 6.11.0-21-generic 6.8.0-56-generic with modified
ACPI tables.
Everything looks correct:
Linux rmalz 6.11.0-19-generic #19~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Feb 17
11:51:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
NUMA node(s): 2
NUMA node0 CP
18 matches
Mail list logo
