> mpintrenable: multiple botch irq 11, tbdf 5000000, lo 00000068, n 00000068 > mpintrenable: out of choices eisa -1 isa 22 tbdf 0xc00d100 irq 11 > intrenable: couldn't enable irq 11, tbdf 0xC00D100 for usbuhci > mpintrenable: multiple botch irq 11, tbdf 5000000, lo 00000068, n 00000068 > mpintrenable: out of choices eisa -1 isa 22 tbdf 0xc00e900 irq 11 > intrenable: couldn't enable irq 11, tbdf 0xC00E900 for usbuhci > mpintrenable: multiple botch irq 11, tbdf 5000000, lo 00000068, n 00000068 > mpintrenable: out of choices eisa -1 isa 22 tbdf 0xc00ea00 irq 11 > intrenable: couldn't enable irq 11, tbdf 0xC00EA00 for usbuhci > mpintrenable: multiple botch irq 11, tbdf 5000000, lo 00000068, n 00000068 > mpintrenable: out of choices eisa -1 isa 22 tbdf 0xc00d700 irq 11 > intrenable: couldn't enable irq 11, tbdf 0xC00D700 for usbehci > mpintrenable: multiple botch irq 11, tbdf 5000000, lo 00000068, n 00000068 > mpintrenable: out of choices eisa -1 isa 22 tbdf 0xc00ef00 irq 11 > intrenable: couldn't enable irq 11, tbdf 0xC00EF00 for usbehci 3063M memory: > 148M kernel data, 2915M user, 3540M swap
what's going on with this? it looks like the same device is being considered with various tbdfs. - erik
