On Sat, 4 Jun 2005, Andreas Koch wrote: > > Actually, I tried that already. But I didn't get any usable info from > the oops and GDB (`list *pci_setup_bridge+0x1a2' shows an include file, > not a line in the function) . I'll make another attempt tomorrow when > I am more awake :-) Usually the easiest way to match up things is to just do x/10i pci_setup_bridge+0x1a2 and match it up with "make drivers/pci/setup-bus.s". Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
- From: Andreas Koch <[email protected]>
- Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
- References:
- PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
- From: Andreas Koch <[email protected]>
- Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
- From: Linus Torvalds <[email protected]>
- Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
- From: Andreas Koch <[email protected]>
- Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
- From: Linus Torvalds <[email protected]>
- Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
- From: Andreas Koch <[email protected]>
- PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
- Prev by Date: [PATCH] libata: shelved ioctl-get-identity patch
- Next by Date: [PATCH scsi-misc 1/2] megaraid_sas: LSI Logic MegaRAID SAS RAID D river
- Previous by thread: Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
- Next by thread: Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
- Index(es):