On Sat, 7 Apr 2007 10:30:24 -0700 "Tom London" <selinux@xxxxxxxxx> wrote: > Noticed this in last kernel build report: > > kernel-2.6.20-1.3045.fc7 > ------------------------ > * Wed Apr 04 2007 Dave Jones <davej@xxxxxxxxxx> > - 2.6.21-rc5-git12 > > * Wed Apr 04 2007 Dave Jones <davej@xxxxxxxxxx> > - Silence noisy power management printk's > > * Wed Apr 04 2007 Dave Jones <davej@xxxxxxxxxx> > - Disable PCI MSI and MMCONFIG by default (cebbert) > > And I now get > Apr 7 09:55:55 localhost kernel: assign_interrupt_mode Found MSI > capability Apr 7 09:55:56 localhost kernel: e1000: eth1: > e1000_request_irq: Unable to allocate MSI interrupt Error: -22 > Apr 7 09:56:09 localhost kernel: e1000: eth1: e1000_request_irq: > Unable to allocate MSI interrupt Error: -22 These are expected, harmless error messages. Chuck Ebbert (wisely, IMHO) disabled MSI by default (as you aptly noted from the changelog), but your driver was written to use MSI by default, if possible. It tries, fails, falls back to IRQ, and you get the error spew. You can explicitly set the pci=msi boot option to override Chuck's default. -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list