[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1032271: marked as done (Module advansys fails to load on amd64)

Your message dated Thu, 01 May 2025 17:22:34 +0200 (CEST)
with message-id <20250501152234.BE50CBE2DE0@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1032271,
regarding Module advansys fails to load on amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1032271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032271
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:linux
Version: 5.10.162-1
Severity: normal

Dear maintainer,

Loading the 'advansys' module fails with any -amd64 kernel:

# modprobe advansys
modprobe: ERROR: could not insert 'advansys': No such device

The module loads successfully with any -686 or -686-pae kernel.
I observed the same behaviour with any stable Debian kernel from 4.9 to 6.1 I have, regardless of whether the supported device and required firmware are present or not.
After adding a few printk() in the module code, it appears that the reason is because calls to isa_register_driver() in advansys_init() fail. The failure may be related with some ISA-related config option missing in amd64 kernels. A quick comparison shows that the following options are enabled in -686 config but not in -amd64 config: 

CONFIG_ISA=y
CONFIG_ISA_BUS_API=y
CONFIG_ISAPNP=y
However I believe a better solution would be to have the module not fail if ISA is disabled, as it also support EISA and PCI devices.
--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .

If you can reproduce your issue with

- the current version in unstable/testing
- the latest kernel from backports

or, if it was a feature addition/wishlist and still consider it
relevant, then:

Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.

Regards,
Salvatore

--- End Message ---
Reply to: