Date: Sat, 3 Sep 2011 12:24:22 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Daniel Eischen <deischen@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: ath0 no longer attaches, cardbus problems? Message-ID: <CAJ-Vmo=k14BTrrUJ4L4=83mjwPPgM7m=ik%2BhSzNEU4A8Dn%2BQFQ@mail.gmail.com> In-Reply-To: <Pine.GSO.4.64.1109021226010.9560@sea.ntplx.net> References: <Pine.GSO.4.64.1108242007100.23746@sea.ntplx.net> <201108250940.44847.jhb@freebsd.org> <Pine.GSO.4.64.1108251313130.28322@sea.ntplx.net> <Pine.GSO.4.64.1109021226010.9560@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, The most direct way to fix this is to find the exact commit which introduced the break. Thanks, Adrian On 3 September 2011 00:27, Daniel Eischen <deischen@freebsd.org> wrote: > On Thu, 25 Aug 2011, Daniel Eischen wrote: > >> On Thu, 25 Aug 2011, John Baldwin wrote: >> >>> On Wednesday, August 24, 2011 8:19:42 pm Daniel Eischen wrote: >>>> >>>> Hello, >>>> >>>> I have an older Dell 4150 laptop that takes forever to build >>>> world, so I don't update it that often. =A0The last time I >>>> updated it was March 1, 2010. =A0I just updated the system >>>> yesterday and ath0 (a Linksys PCCard) no longer attaches. >>>> >>>> The interesting thing is that ath0 is detected at different >>>> addresses between the working kernel and the non-working >>>> kernel: >>>> >>>> =A0 March 1, 2010 kernel >>>> =A0 -------------------- >>>> =A0 ath0: <Atheros 5212> mem 0x88000000-0x8800ffff irq 11 >>>> =A0 =A0 =A0 at device 0.0 on =A0cardbus0 >>>> =A0 ath0: [ITHREAD] >>>> =A0 ath0: AR5212 mac 5.9 RF5112 phy 4.3 >>>> >>>> >>>> =A0 Aug 23, 2011 kernel >>>> =A0 ------------------- >>>> =A0 ath0: <Atheros 5212> mem 0xf8f10000-0xf8f1ffff irq 11 >>>> =A0 =A0 =A0 at device 0.0 on =A0cardbus0 >>>> >>>> >>>> I've tried forcing successful returns from >>>> ar5212SetPowerModeAwake() and ar5212SetResetReg() >>>> but it doesn't help (diffs below). >>>> >>>> Any suggestions on how to get this to work? >>>> Full dmesg from working and non-working kernels at >>>> >>>> =A0 http://people.freebsd.org/~deischen/ath/ath.dmesg >>> >>> You can try setting 'debug.acpi.disable=3Dhostres' at the loader prompt= as >>> a >>> test. =A0If that doesn't work, a verbose dmesg from the broken case as = well >>> as >>> devinfo -u and devinfo -r output from the working and broken cases woul= d >>> be >>> most useful. >> >> Setting debug.acpi.disable=3Dhostres did not work. =A0Strange thing is >> that ath0 is now at mem 0x88000000-0x8800ffff for both working >> and non-working kernels (with and without debug.acpi.disable=3Dhostres). >> ath0 still doesn't attach, but it seems funny that the memory >> address changes. =A0These are all soft reboots, not hard reboots, >> after a working kernel. >> >> All the information you requested is here: >> >> =A0http://people.freebsd.org/~deischen/ath/ >> >> There are verbose boots and devinfo -u/-r output for the >> working kernel and the non-working kernel (with and without >> debug.acpi.disable=3Dhostres). >> >> Anything else you'd like me to try? > > Any hopes of getting this cardbus problem fixed? > > -- > DE > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=k14BTrrUJ4L4=83mjwPPgM7m=ik%2BhSzNEU4A8Dn%2BQFQ>