Date: Sat, 8 Aug 2009 14:12:24 -0500 (CDT) From: Greg Rivers <gcr+freebsd-current@tharned.org> To: Attilio Rao <attilio@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: hald broken with USB drives since 8.0-BETA2 Message-ID: <alpine.BSF.2.00.0908081405280.1298@blue.tharned.org> In-Reply-To: <3bbf2fe10908081201g3378b8q479b8836d69f636b@mail.gmail.com> References: <alpine.BSF.2.00.0908081254050.1298@blue.tharned.org> <3bbf2fe10908081116q384da0dcp1f41554dea0b0b95@mail.gmail.com> <alpine.BSF.2.00.0908081320130.1298@blue.tharned.org> <3bbf2fe10908081151o35a9141dhcea06fcaa5b6838e@mail.gmail.com> <Pine.GSO.4.64.0908081457130.3821@sea.ntplx.net> <3bbf2fe10908081201g3378b8q479b8836d69f636b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 8 Aug 2009, Attilio Rao wrote: > 2009/8/8 Daniel Eischen <deischen@freebsd.org>: >> On Sat, 8 Aug 2009, Attilio Rao wrote: >> >>> 2009/8/8 Greg Rivers <gcr+freebsd-current@tharned.org>: >>>> >>>> On Sat, 8 Aug 2009, Attilio Rao wrote: >>>> >>>>> 2009/8/8 Greg Rivers <gcr+freebsd-current@tharned.org>: >>>>>> >>>>>> I've had to disable hald on my Acer One netbook since 8.0-BETA2. >>>>>> Now hald seems to work only the first time a USB drive is attached. >>>>>> The drive is detected and mounted, and can be unmounted and >>>>>> remounted via kde3's media interface. >>>>>> >>>>>> But if I unmount the drive and detach it, hald wedges the USB buss. >>>>>> No further USB connections (any device, not just disks) are >>>>>> detected, and hald becomes unkillable. >>>>>> >>>>>> Has anyone else experienced this? Any suggestions for >>>>>> troubleshooting? >>>>> >>>>> After installing BETA2 did you further update to -CURRENT or simply >>>>> used BETA2 system? >>>>> >>>> >>>> I've been tracking -CURRENT. I last rebuilt kernel and world on >>>> August 2nd. Sorry for not being clear about that. >>>> >>>> I removed and rebuilt all ports from source after the July 19 shared >>>> library version bump, and I rebuilt hald and dbus after the August >>>> 2nd kernel/world update. >>> >>> Did you include r196037? >>> If you did, can you try remove it and rebuild anything and experience >>> the problem again? >> >> You can also see this thread from June: >> >> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1494406+0+archive/2009/freebsd-current/20090607.freebsd-current > > Oh, so it should not be the newbus locking patch. > Right, r196037 was committed on August 2nd, and I've seen this problem since ~July 20. -- Greg Rivers
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0908081405280.1298>