Is a BAD BAR something to worry about?

[Tilman Linneweh]

Hi,

With todays CURRENT my ata controllers are a bit more verbose:

atapci1: <VIA 6420 SATA150 controller> port 0xd000-0xd0ff,0xd400-0xd40f,0xd800-0xd803,0xe000-0xe007,0xe400-0xe403,0xe800-0xe807 irq 20 at device 15.0 on pci0
atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xd400
atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xe800
atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xe400
ata5: at 0xe800 on atapci1
atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0xe000
atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xd800
ata6: at 0xe000 on atapci1
atapci2: <VIA 8237 UDMA133 controller> port 0xfc00-0xfc0f at device 15.1 on pci0
atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfc00
atapci2: BAD BAR: skipping checks
atapci2: Lazy allocation of 0x8 bytes rid 0x10 type 4 at 0x1f0
atapci2: BAD BAR: skipping checks
atapci2: Lazy allocation of 0x4 bytes rid 0x14 type 4 at 0x3f4
ata0: at 0x1f0 irq 14 on atapci2
atapci2: BAD BAR: skipping checks
atapci2: Lazy allocation of 0x8 bytes rid 0x18 type 4 at 0x170
atapci2: BAD BAR: skipping checks
atapci2: Lazy allocation of 0x4 bytes rid 0x1c type 4 at 0x374
ata1: at 0x170 irq 15 on atapci2

Everything seems to work normal............