Re: I think that "Damn Small Linux" has another problem; I need further testing with Knoppix before I can say if it is the same problem... 

Is "pcibissort" a typo for pcibios_sort?

Were there any error/warning messages before this kernel fault?

Can you boot any Linux kernel on this system?  If so, please provide output
from 'lspci -v'.
 

* yes, its a typo ;-)
* I think so. 
* I run Linux in a VM under Windows sucessfully, but I don't think that that helps. Any other Linux kernel seems to do not work. If I can do so, I'll provide the requested data later. 

Please try to provide full & complete answers.
a.  What is the typo-ed function name supposed to be?
b.  what messages came before the kernel fault?
c.  thank you.

What is the typo-ed function name supposed to be?
a) "pcibis_sort" rather than "pcibiossort"; I've double checked the rest and couldn't find any other error. 

hat messages came before the kernel fault?
b) In case of LFS: 
 [Splash Screen Image]
 This is the official LFS Live CD, Version: x86-6.3-r2052
 Press [Enter] to boot, F1 - F4 for available options
 boot: _
 Loading Linux..................................
 Loading initramfs_data_cpio.gz...............................................
 .............................................................................
 ...................DONE

The next thing that is visible is "EIP: 0060:[<c00f0488>] Not tainted VLI". There are no other statements. 

btw: I've tried it with Knoppix; it is resulting in a black screen on default and resulting in almost the same error in debug mode. In debug mode there is more to read, but its to fast to write it down on paper. 

Is there any way to scroll through the error page-by-page like using the 'more' command? Some changes in the source of the bootstrap code might help doing so. I think that its not possible to save a protocol on HDD. Afaik the HDD driver don't loads in this early stage. 

I didn't make to install any linux. At least no one with a 2.6.xx Kernel. Finally I've managed to install FreeBSD (this took me some time because as Windows user I'm not familar with Unix). Because Randy asked for the "lspci -v", I'm providing Informations from "pciconf -ls", which does afaik (almost) the same. I hope that helps. So here it is: 


hostb0@pci0:0:0:	class=0x060000 card=0x70281462 chip=0x25808086 rev=0x04 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82915G/GV/GL/P/PL/GL Grantsdale Host Bridge/DRAM Controller'
    class    = bridge
    subclass = HOST-PCI
pcib1@pci0:1:0:	class=0x060400 card=0x00000088 chip=0x25818086 rev=0x04 hdr=0x01
    vendor   = 'Intel Corporation'
    device   = '82915G/P/PL Grantsdale Host-PCI Express Graphics Bridge'
    class    = bridge
    subclass = PCI-PCI
none0@pci0:27:0:	class=0x040300 card=0x70281462 chip=0x26688086 rev=0x03 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801FB/FR/FW/FRW Intel High DefiNition Audio Controller'
    class    = multimedia
pcib2@pci0:28:0:	class=0x060400 card=0x00000040 chip=0x26608086 rev=0x03 hdr=0x01
    vendor   = 'Intel Corporation'
    device   = '82801FB/FR/FW/FRW PCI Express Port 1'
    class    = bridge
    subclass = PCI-PCI
pcib3@pci0:28:2:	class=0x060400 card=0x00000040 chip=0x26648086 rev=0x03 hdr=0x01
    vendor   = 'Intel Corporation'
    device   = '82801FB/FR/FW/FRW PCI Express Port 3'
    class    = bridge
    subclass = PCI-PCI
uhci0@pci0:29:0:	class=0x0c0300 card=0x70281462 chip=0x26588086 rev=0x03 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801FB/FR/FW/FRW USB UHCI Controller'
    class    = serial bus
    subclass = USB
uhci1@pci0:29:1:	class=0x0c0300 card=0x70281462 chip=0x26598086 rev=0x03 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801FB/FR/FW/FRW USB UHCI Controller'
    class    = serial bus
    subclass = USB
uhci2@pci0:29:2:	class=0x0c0300 card=0x70281462 chip=0x265a8086 rev=0x03 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801FB/FR/FW/FRW USB UHCI Controller'
    class    = serial bus
    subclass = USB
uhci3@pci0:29:3:	class=0x0c0300 card=0x70281462 chip=0x265b8086 rev=0x03 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801FB/FR/FW/FRW USB UHCI Controller'
    class    = serial bus
    subclass = USB
ehci0@pci0:29:7:	class=0x0c0320 card=0x70281462 chip=0x265c8086 rev=0x03 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801FB/FR/FW/FRW USB 2.0 EHCI Controller'
    class    = serial bus
    subclass = USB
pcib4@pci0:30:0:	class=0x060401 card=0x00000050 chip=0x244e8086 rev=0xd3 hdr=0x01
    vendor   = 'Intel Corporation'
    device   = '82801BA/CA/DB/DBL/EB/ER/FB (ICH2/3/4/4/5/5/6), 6300ESB Hub Interface to PCI Bridge'
    class    = bridge
    subclass = PCI-PCI
isab0@pci0:31:0:	class=0x060100 card=0x70281462 chip=0x26408086 rev=0x03 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801FB/FR ICH6/ICH6R LPC Interface Bridge'
    class    = bridge
    subclass = PCI-ISA
atapci0@pci0:31:1:	class=0x01018a card=0x70281462 chip=0x266f8086 rev=0x03 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801FB/FBM Ultra ATA Storage Controllers - 266F'
    class    = mass storage
    subclass = ATA
atapci1@pci0:31:2:	class=0x01018f card=0x70281462 chip=0x26528086 rev=0x03 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801FR/FRW ICH6R/ICH6RW SATA Controller'
    class    = mass storage
    subclass = ATA
none1@pci0:31:3:	class=0x0c0500 card=0x70281462 chip=0x266a8086 rev=0x03 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = '82801FB/FR/FW/FRW SMBus Controller'
    class    = serial bus
    subclass = SMBus
none2@pci1:0:0:	class=0x030000 card=0x06121462 chip=0x3e501002 rev=0x00 hdr=0x00
    vendor   = 'ATI Technologies Inc'
    device   = 'Radeon X600 Series'
    class    = display
    subclass = VGA
none3@pci1:0:1:	class=0x038000 card=0x06131462 chip=0x3e701002 rev=0x00 hdr=0x00
    vendor   = 'ATI Technologies Inc'
    device   = 'Radeon X600 Series Secondary'
    class    = display
bge0@pci3:0:0:	class=0x020000 card=0x028c1462 chip=0x167714e4 rev=0x01 hdr=0x00
    vendor   = 'Broadcom Corporation'
    device   = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express'
    class    = network
    subclass = ethernet

On Linux kernels, you could also try some of the kernel command-line boot
options, such as:  pci=nosort
or:  pci=bfsort
or:  pci=nobfsort
to see if they have any effect on the PCI device sorting problem.

I'll take a look at the PCI devices list, thanks.

Or take the PCI BIOS out of the picture complete by booting with:
  pci=nobios
since the crash looks a bit like the PCI BIOS is flaky.

Thank you Randy! 
I'm not experiencing any problems with "pci=nosort" and "pci=nobios"; with "pci=bfsort" and "pci=nobfsort" I still get the Kernel Panic. You might be right that its the PCI BIOS that makes me headache. 

Do you think its better to contact the Mainboard vendor or to handle this issue in the sorting procedure (or changing nothing at all because there is a hack available)? 

Question:  do any earlier versions of Linux work for you on this system?
It says above:
  Most recent kernel where this bug did not occur: 2.6.22.5
Is that correct?

To answer your question, I think that you'll need to continue using
"pci=nosort" or "pci=nobios" to boot.  You can try contacting the system
board vendor and explain to them that PCI BIOS indirect calls with a
function code of PCI_FIND_DEVICE are failing to return to the caller,
but I have doubts about how responsive they would be.

Re: Most recent kernel where this bug did not occur

It is not correct, because I've misread the sentence - I'm not that kind of good english speaker, sorry. 
I have tried it with some older kernels. But they either have that problem or are not capable of detecting all the hardware (at least with 2.4.xx Kernels). I think the problem was introduced with the 2.6.0 Kernel, but it would take probably to much wasted CDs and time to test that. (I have already dozends of Linux-CDs here for which I have no use anymore; also it took me weeks on learning how linux works without ever installing it)
=========================
Re: you'll need to continue using "pci=nosort" or "pci=nobios" to boot

Its not an issue for me because I know that now. But it might be a good thing if the kernel will get some error recovery code in future releases. It would help other linux newbies, because common peoples will mostly not report problems but instead stick to windows. 
=========================
Re: I have doubts about how responsive they would be

I think that too. Because the Mainboard is probably outdated now, the vendor will not really work on it. 

Any update on this bug? Is the workaround a sufficient solution? Sounds like nothing else can be done, is it correct Randy. I'd say this bug can be marked resolved.

Resolved would be OK with me, but it only says CODE_FIX or PATCH_ALREADY_AVAILABLE.  Actually this is still an incomplete bug report:
we don't have the function name where the current EIP is.

movgp0: can you provide us with a System.map file for the kernel that failed here
so that we can try to see where the kernel actually faulted?  Which distribution
and version number is it?  Do you recall that information?

Sorry. I do not recall. Instead I can try to test my distributions one-by-one until I get a match. But I need some time for doing so.