It was <2023-10-31 wto 22:52>, when James Seo wrote: > On Tue, Oct 31, 2023 at 10:07:26PM +0100, Lukasz Stelmach wrote: >> It was <2023-10-31 wto 12:28>, when Guenter Roeck wrote: >>> On 10/31/23 12:07, Lukasz Stelmach wrote: [...] >>>> My solution would be to add a module option, let's name it `quirks` and >>>> make it a bit field for future use, that enables the workaound. Plus an >>>> additional error message when probe fails to suggest user to add the >>>> option to kernel command line or whatever file that contains module >>>> options. A nice touch would be to detect if the workaround is still >>>> required. >>>> >>> >>> Please no module option. Use DMI data or similar. >> >> DMI data is fine when can you identify broken systems upfront. In this >> case we don't know which systems are or will be affected by this bug. > > This particular bug seems extremely rare in general, which means I'm further > inclined towards treating it as a one-off. As Günter said, we can always add > more later. > > Can you provide the output of `dmidecode -s baseboard-product-name` for now? --8<---------------cut here---------------start------------->8--- # dmidecode -s baseboard-product-name 870C --8<---------------cut here---------------end--------------->8--- -- Łukasz Stelmach Samsung R&D Institute Poland Samsung Electronics
Attachment:
signature.asc
Description: PGP signature
