should be concerned with?
I just got this setup running as my MBE.
Everything seems to work great
This is from the Syslog on the MSI K8N neo4.

Jan 1 14:33:45 mythtv kernel: PCI: Setting latency timer of device 0000:00:0b.0 to 64
Jan 1 14:33:45 mythtv kernel: pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
Jan 1 14:33:45 mythtv kernel: assign_interrupt_mode Found MSI capability
Jan 1 14:33:45 mythtv kernel: Allocate Port Service[pcie00]
Jan 1 14:33:45 mythtv kernel: Allocate Port Service[pcie03]
Jan 1 14:33:45 mythtv kernel: PCI: Setting latency timer of device 0000:00:0c.0 to 64
Jan 1 14:33:45 mythtv kernel: pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
Jan 1 14:33:45 mythtv kernel: assign_interrupt_mode Found MSI capability
Jan 1 14:33:45 mythtv kernel: Allocate Port Service[pcie00]
Jan 1 14:33:45 mythtv kernel: Allocate Port Service[pcie03]
Jan 1 14:33:45 mythtv kernel: PCI: Setting latency timer of device 0000:00:0d.0 to 64
Jan 1 14:33:45 mythtv kernel: pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
Jan 1 14:33:45 mythtv kernel: assign_interrupt_mode Found MSI capability
Jan 1 14:33:45 mythtv kernel: Allocate Port Service[pcie00]
Jan 1 14:33:45 mythtv kernel: Allocate Port Service[pcie03]
Jan 1 14:33:45 mythtv kernel: PCI: Setting latency timer of device 0000:00:0e.0 to 64
Jan 1 14:33:45 mythtv kernel: pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
Jan 1 14:33:45 mythtv kernel: assign_interrupt_mode Found MSI capability
Jan 1 14:33:45 mythtv kernel: Allocate Port Service[pcie00]
Jan 1 14:33:45 mythtv kernel: Allocate Port Service[pcie03]
Jan 1 14:33:45 mythtv kernel: isapnp: Scanning for PnP cards...
Jan 1 14:33:45 mythtv kernel: isapnp: No Plug & Play device found
Jan 1 14:33:45 mythtv kernel: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Jan 1 14:33:45 mythtv kernel: PNP: PS/2 controller doesn't have AUX irq; using default 12
Jan 1 14:33:45 mythtv kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Jan 1 14:33:45 mythtv kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jan 1 14:33:45 mythtv kernel: FDC 0 is a post-1991 82077
Jan 1 14:33:45 mythtv kernel: RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Jan 1 14:33:45 mythtv kernel: loop: loaded (max 8 devices)
Jan 1 14:33:45 mythtv kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Jan 1 14:33:45 mythtv kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Jan 1 14:33:45 mythtv kernel: NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
Jan 1 14:33:45 mythtv kernel: NFORCE-CK804: chipset revision 242
Jan 1 14:33:45 mythtv kernel: NFORCE-CK804: not 100%% native mode: will probe irqs later
Jan 1 14:33:45 mythtv kernel: NFORCE-CK804: 0000:00:06.0 (rev f2) UDMA133 controller

Searching around I find nothing in here, and only references to this same issue on the Web.

Is it something I should try to clear up? Anyone have any ideas?

TIA.

Andy

_________________
KnoppMyth R5.5
MBE: AMD64 3400+, K8N Neo4 Plat., 1Gig, Asus Extreme N6200, 320G pata, 2x320Gsata, 750Gsata, PVR-150 Retail w/Blaster
SBE: AMD XP2000, GA 7ZMMH, 1 Gig, XFX 256M 6200, 20 Gig, PVR-150 Retail w/Blaster
SBE: AMD Dur1800, 512M, PVR500

What exactly are you worried about there? It all looks pretty normal to me.

Well I am mostly just wondering if this is something I should be trying to fix? I know the system is working really good and having only built two of these the First one which was demoted to an SBE and now the new MBE which is throwing this log file.

2 things would seem to raise a flag for me if I was having problems. It all seems to work well just trying to get familar with the logs in the event something changes, I don't know though.

1) pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS I believe these are related to the PCI Express video. Not sure.

2) PCI: Setting latency timer of device 0000:00:0b.0 to 64 I see this in there but I also see later on ivtv where it says "unreasonable low latency setting to 64" Is there a timing issue here that might need an update somewhere. Does a newer version of Linux(KM version) address this?

I mean if these are normal then I will just chalk it up to something to not really care about.

Thanks for the reply.