Date: Wed, 22 Aug 2007 17:19:38 -0300 From: "William Grzybowski" <william88@gmail.com> To: "Nate Lawson" <nate@root.org> Cc: freebsd-acpi@freebsd.org Subject: Re: msk dev problem with acpi Message-ID: <632825b40708221319jbdd6391u19d3172d2b58485f@mail.gmail.com> In-Reply-To: <632825b40708211116g1c11612aj86163495e6a32e97@mail.gmail.com> References: <632825b40708210457r50b22cf9xd55fa88b569e3b5b@mail.gmail.com> <46CB2097.5000706@miralink.com> <46CB28AF.5080506@root.org> <632825b40708211116g1c11612aj86163495e6a32e97@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/21/07, William Grzybowski <william88@gmail.com> wrote: > > On 8/21/07, Nate Lawson <nate@root.org> wrote: > > > > Sean Bruno wrote: > > > William Grzybowski wrote: > > >> Hi! > > >> > > >> I'm having a problem with my marvell yukon ethernet when i boot my > > >> -CURRENT > > >> with the ACPI enable, it goes fine when acpi is off... > > >> I already tried to talk with the msk driver developer and he has now > > idea > > >> why it is happening and told me to try something here... > > >> > > >> dmesg error: > > >> mskc0: <Marvell Yukon 88E8038 Gigabit Ethernet> irq 16 at device 0.0 > > >> on pci2 > > >> mskc0: 0x4000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). > > >> mskc0: unknown device: id=0x00, rev=0x00 > > >> device_attach: mskc0 attach returned 6 > > >> > > >> the card: > > >> mskc0@pci2:0:0: class=0x020000 card=0x01101025 chip=0x435211ab > > rev=0x14 > > >> hdr=0x00 > > >> vendor = 'Marvell Semiconductor (Was: Galileo Technology > > Ltd)' > > >> device = 'Yukon 88E8038 PCI-E Fast Ethernet Controller' > > >> class = network > > >> subclass = ethernet > > >> > > >> I am also attaching the acpidump and dmesg , > > >> If it can't be a apci isue, please, let me know. > > >> > > > I don't see any attachments in this email. Can you try resending to > > the > > > list? > > > > > > > Attachments that are too big are stripped. Please post a URL to the > > acpidump instead. > > > > -Nate > > > > It has just ~30kb, anyway, i am posting the links... > http://www.inf.ufpr.br/wg06/acpi.gz > http://www.inf.ufpr.br/wg06/dmesg.gz Hi, i was testing a verbose boot with acpi and without acpi, i noted a "requested unsupported memory range" with acpi... verbose dmesg with acpi: mskc0: <Marvell Yukon 88E8038 Gigabit Ethernet> irq 16 at device 0.0 on pci2 pcib1: mskc0 requested unsupported memory range 0-0xffffffff (decoding 0-0, 0-0) mskc0: 0x4000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). mskc0: Lazy allocation of 0x4 bytes rid 0x14 type 4 at 0x1000 mskc0: unknown device: id=0xff, rev=0x0f and without acpi: mskc0: <Marvell Yukon 88E8038 Gigabit Ethernet> port 0x2000-0x20ff mem 0xd0100000-0xd0103fff irq 16 at device 0.0 on pci2 mskc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xd0100000 mskc0: MSI count : 2 mskc0: attempting to allocate 2 MSI vectors (2 supported) Is that relevant? Maybe a issue in the msk driver allocation and not in acpi? Should I send all the verbose boots with and without acpi? Thanks, bye. Thanks > > -- > William Grzybowski > ------------------------------------------ > Jabber: william88 at gmail dot com > Msn: william.grz at hotmail dot com > Curitiba/PR > -- William Grzybowski ------------------------------------------ Jabber: william88 at gmail dot com Msn: william.grz at hotmail dot com Curitiba/PR
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?632825b40708221319jbdd6391u19d3172d2b58485f>