Bug 8595
Summary: | Problem with PCI resource assignment and device discovery with some buggy BIOSes | ||
---|---|---|---|
Product: | Drivers | Reporter: | Martin Drab (martin.drab) |
Component: | PCI | Assignee: | Alan (alan) |
Status: | REJECTED INVALID | ||
Severity: | normal | ||
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.21 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 7883 | ||
Attachments: |
Output of the dmidecode for the ASUS A8Js
dmesg output on kernel with the quick and dirty patch dmesg output on kernel without the quick and dirty patch lspci -vvxxx on kernel with the quick and dirty patch lspci -vvxxx on kernel without the quick and dirty patch |
Description
Martin Drab
2007-06-06 15:46:09 UTC
Created attachment 11695 [details]
Output of the dmidecode for the ASUS A8Js
Created attachment 11696 [details]
dmesg output on kernel with the quick and dirty patch
Created attachment 11697 [details]
dmesg output on kernel without the quick and dirty patch
Created attachment 11698 [details]
lspci -vvxxx on kernel with the quick and dirty patch
Created attachment 11699 [details]
lspci -vvxxx on kernel without the quick and dirty patch
Hmm, this is odd. Now it seems that the 04:00.0 device beyond the bridge
actually does get discovered even without the patch. Strange. Why would I be
doing and using those quick and dirty patches if everything would have worked?
Is it possible I've just been under the wrong impression that it was not
working? I'd better get some disk to attach to that SATA controller and test it
all again thoroughly before anyone seriously tries to do something about this
bug. Hold on, I'll be back. ;)
OK, I did some testing and it seems that I was really wrong. It works even without the patches with the current PCI code. So I'm closing this bug as invalid. Sorry for bothering. (Though it doesn't change the fact that the ASUS BIOS is buggy. If anyone of ASUS ever reads this, please fix it anyway.) |