Conversation

Support daily routine: given there's a regression in the networking code on SMP, suggest running a reproducer with taskset pinning it to a single CPU, or booting with nr_cpus=1 so that the issue is not reproducible any more, and present this as a workaround to the customer.

Who said SMP was a mistake?..

2
0
2
@oleksandr more i've used 6.11 in fedora more i feel like that kernel release was a mistake ;-) random crashes, wifi not working etc. no time to write bug reports all the time...
2
0
1

@jarkko …with a difference that this is an enterprise kernel I'm talking about :).

1
0
2
@jarkko @oleksandr haha well then just wait for 6.12 that's gonna be legendary
2
1
2
@oleksandr @jarkko I've heard "enterprise kernels" are buggy and vulnerable due to missing backported fixes!
1
0
2

HAMMER SMASHED FILESYSTEM πŸ‡ΊπŸ‡¦

@ljs @oleksandr sir did

2
0
1

HAMMER SMASHED FILESYSTEM πŸ‡ΊπŸ‡¦

@ljs @oleksandr ^C hail sir
HAIL SIR! πŸ”

1
1
1

HAMMER SMASHED FILESYSTEM πŸ‡ΊπŸ‡¦

@ljs @oleksandr ^🐟 HAIL SIR

1
1
1

HAMMER SMASHED FILESYSTEM πŸ‡ΊπŸ‡¦

@ljs @oleksandr 🌊πŸͺ“πŸŸ

PRAISE MESSIEUR

1
1
1

HAMMER SMASHED FILESYSTEM πŸ‡ΊπŸ‡¦

@ljs @oleksandr @vbabka βœ”οΈ die shot
βœ”οΈ sir
βœ”οΈ fish
wait, the thumb... *squint* βœ”οΈ not opposable

0
1
1

@vbabka @jarkko Because of @ljs contributions I suppose.

1
1
2

@vbabka @jarkko I cannot state anything wrong against my company, but SUSE kernels are surely buggy ;).

0
0
1

@vbabka @oleksandr @jarkko i'm hyped for it because of asus vivobook changes!

0
0
1

@oleksandr @ljs yes and the other sir is babka
cc @vbabka

1
1
2
@lkundrak @oleksandr @vbabka a babka? GIVE THE BABKA A SEAT ON THE TRAM IMMEDIATELY
0
0
2

@oleksandr @vbabka @jarkko @ljs Phew. Glad I haven't contributed anything this time.

0
1
3