Ok, I reproduce the problem and attached several lspci log here
--- Stephen Hemminger <[EMAIL PROTECTED]> wrote: > On Tue, 30 Aug 2005 13:18:57 -0700 > Jesse Brandeburg <[EMAIL PROTECTED]> wrote: > > > on 2.6.11/12 when it isn't working maybe you > should send us the output > > of lspci -vvv > > > > just a hint, I'm guessing its power management > related, and / or > > something to do with the pci bus code. > > Also, the dmesg output with skge driver will show > chip version and revision. > The problem is obviously some of the chip > initialization that is complex > with the Marvell chips. Something is probably > missing. There was a fix > in the latest 2.6.13 that is probably related: > > > http://www.mail-archive.com/netdev@vger.kernel.org/msg00438.html > S.KIEU ____________________________________________________ Do you Yahoo!? The New Yahoo! Movies: Check out the Latest Trailers, Premiere Photos and full Actor Database. http://au.movies.yahoo.com
dmesg-2.6.12-nowork.log.gz
Description: 2772971102-dmesg-2.6.12-nowork.log.gz
dmesg-2613.log.gz
Description: 3668832883-dmesg-2613.log.gz
lspci-2612-nowork.log.gz
Description: 3470857198-lspci-2612-nowork.log.gz
lspci-2613.log.gz
Description: 1122749440-lspci-2613.log.gz
lspci-2612-work.log.gz
Description: 267994485-lspci-2612-work.log.gz
