Public bug reported:

Currently the Ubuntu kernels ship with CONFIG_EISA_VLB_PRIMING=y.  This
doesn't match the upstream default (n) and this is the help text:

          Activate this option if your system contains a Vesa Local
          Bus (VLB) card that identify itself as an EISA card (such as
          the Adaptec AHA-284x).

          When in doubt, say N.

I noticed this actually changes the kernel behavior such that it forces
the probing code to probe EISA slots even when it cannot find an EISA
compliant mainboard.

This manifests in a collection of warnings on every boot.

[    0.985127] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    0.985845] platform eisa.0: Cannot allocate resource for EISA slot 1
[    0.986526] platform eisa.0: Cannot allocate resource for EISA slot 2
[    0.987213] platform eisa.0: Cannot allocate resource for EISA slot 3
[    0.987899] platform eisa.0: Cannot allocate resource for EISA slot 4
[    0.988586] platform eisa.0: Cannot allocate resource for EISA slot 5
[    0.989273] platform eisa.0: Cannot allocate resource for EISA slot 6
[    0.989961] platform eisa.0: Cannot allocate resource for EISA slot 7
[    0.990646] platform eisa.0: Cannot allocate resource for EISA slot 8

I think this config option should be changed to match upstream default
for Ubuntu kernels.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
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/2009759

Title:
  Change default of CONFIG_EISA_VLB_PRIMING

Status in linux package in Ubuntu:
  New

Bug description:
  Currently the Ubuntu kernels ship with CONFIG_EISA_VLB_PRIMING=y.
  This doesn't match the upstream default (n) and this is the help text:

          Activate this option if your system contains a Vesa Local
          Bus (VLB) card that identify itself as an EISA card (such as
          the Adaptec AHA-284x).

            When in doubt, say N.

  I noticed this actually changes the kernel behavior such that it
  forces the probing code to probe EISA slots even when it cannot find
  an EISA compliant mainboard.

  This manifests in a collection of warnings on every boot.

  [    0.985127] platform eisa.0: EISA: Cannot allocate resource for mainboard
  [    0.985845] platform eisa.0: Cannot allocate resource for EISA slot 1
  [    0.986526] platform eisa.0: Cannot allocate resource for EISA slot 2
  [    0.987213] platform eisa.0: Cannot allocate resource for EISA slot 3
  [    0.987899] platform eisa.0: Cannot allocate resource for EISA slot 4
  [    0.988586] platform eisa.0: Cannot allocate resource for EISA slot 5
  [    0.989273] platform eisa.0: Cannot allocate resource for EISA slot 6
  [    0.989961] platform eisa.0: Cannot allocate resource for EISA slot 7
  [    0.990646] platform eisa.0: Cannot allocate resource for EISA slot 8

  I think this config option should be changed to match upstream default
  for Ubuntu kernels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009759/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to