[no subject]

15eb37d@crater_reader.dragonflybsd.org> <ea7b9c170906042002i522bd90cjcd6df636b12db20@mail.gmail.com>
From: Johannes Hofmann <Johannes.Hofmann@gmx.de>
Subject: Re: can't mount root disk with ACPI enabled
Date: Fri, 5 Jun 2009 09:32:35 +0200
BestServHost: crater.dragonflybsd.org
List-Post: <mailto:bugs@crater.dragonflybsd.org>
List-Subscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=subscribe>
List-Unsubscribe: <mailto:bugs-request@crater.dragonflybsd.org?body=unsubscribe>
List-Help: <mailto:bugs-request@crater.dragonflybsd.org?body=help>
List-Owner: <mailto:owner-bugs@crater.dragonflybsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ea7b9c170906042002i522bd90cjcd6df636b12db20@mail.gmail.com>
Sender: bugs-errors@crater.dragonflybsd.org
Errors-To: bugs-errors@crater.dragonflybsd.org
Lines: 75
NNTP-Posting-Host: 216.240.41.25
X-Trace: 1244187617 crater_reader.dragonflybsd.org 880 216.240.41.25
Xref: crater_reader.dragonflybsd.org dragonfly.bugs:10244

On Fri, Jun 05, 2009 at 11:02:02AM +0800, Sepherosa Ziehau wrote:
> On Thu, Jun 4, 2009 at 10:54 PM, Johannes
> Hofmann<johannes.hofmann@gmx.de> wrote:
> > Johannes Hofmann <johannes.hofmann@gmx.de> wrote:
> >> Sepherosa Ziehau <sepherosa@gmail.com> wrote:
> >>> On Thu, Jun 4, 2009 at 6:59 PM, Johannes Hofmann
> >>> <johannes.hofmann@gmx.de> wrote:
> >>>> Sepherosa Ziehau <sepherosa@gmail.com> wrote:
> >>>>> On Thu, Jun 4, 2009 at 2:28 PM, Johannes Hofmann
> >>>>> <johannes.hofmann@gmx.de> wrote:
> >>>>>> Sepherosa Ziehau <sepherosa@gmail.com> wrote:
> >>>>>>>>
> >>>>>>>> Just noticed that even with revision
> >>>>>>>> 7e7d17cb48838b48389fb990950f2959b9635e63
> >>>>>>>> I still can't mount the root disk iff I load usb modules (usb, ehci,
> >>>>>>>> umass) during boot via /boot/loader.conf - which I normally don't to
> >>>>>>>> allow CPU to enter C3 state.
> >>>>>>>
> >>>>>>> You box is UP, so only i8254 is used.  C3 does not affect the i8254
> >>>>>>> interrupt timer.
> >>>>>>
> >>>>>> Right, but usb modules prevent the CPU from entering C3 generally
> >>>>>> (As far as I know it's a bus mastering DMA thing).
> >>>>>>
> >>>>>>>
> >>>>>>>>
> >>>>>>>> So maybe this is just some sort of timing problem?
> >>>>>>>> Is anyone else seeing this? I guess thinkpads are quite common here.
> >>>>>>>
> >>>>>>> This looks very strange, could you give me the bootverbose dmesgs:
> >>>>>>> w/ ACPI, w/o usb modules
> >>>>>>
> >>>>>> http://leaf.dragonflybsd.org/~hofmann/acpi_nousb.dmesg
> >>>>>>
> >>>>>>> w/o ACPI, w/ usb modules
> >>>>>>
> >>>>>> http://leaf.dragonflybsd.org/~hofmann/noacpi_usb.dmesg
> >>>>>>
> >>>>>>> I think using these two combinition, your box is booting?
> >>>>>
> >>>>> Is ad0 detected w/ ACPI and w/ usb modules?
> >>>>
> >>>> Ah, just noticed that it's detected as ad1 in that case:
> >>>>
> >>>> http://leaf.dragonflybsd.org/~hofmann/acpi_usb.dmesg
> >>>
> >>> It looks very strange to me, do you have ATA_STATIC_ID in your kernel
> >>> config file?
> >>
> >> Yes, I do. Nevertheless I'm currently compiling GENERIC to check whether
> >> that makes a difference.
> >
> > Well it does: The problem occurs with GENERIC only if I comment out
> > all USB support, add
> >
> > device          drm
> > device          radeondrm
> >
> > and load usb, ehci, umass from /boot/loader.conf
> >
> > Very weird indeed...
> 
> Comment out:
> kern.do_async_attach="1"
> in your /boot/loader.conf

I also noticed this and started to get embarrassed that I forgot
about it :-)
But commenting out this line doesn't fix the problem.
Instead I noticed that the problem starts with the DRM update in
b3705d716ab5621c5cac8741394ad6cab7e5c99b
It's a rather huge changeset unfortunately...

Best Regards,
Johannes