Re: updating from r231158 to 234465: mounting from ufs:/dev/ad4s1a failed with error 19

From: John Baldwin <jhb_at_freebsd.org>
Date: Wed, 30 May 2012 12:00:08 -0400
On Tuesday, May 29, 2012 7:17:01 pm Anton Shterenlikht wrote:
> On Mon, May 21, 2012 at 01:08:24PM -0400, John Baldwin wrote:
> > On Monday, May 21, 2012 5:45:19 am Anton Shterenlikht wrote:
> > > On Mon, May 21, 2012 at 09:42:17AM +0100, Anton Shterenlikht wrote:
> > > > On Sun, May 20, 2012 at 09:54:51AM +0100, Anton Shterenlikht wrote:
> > > > > On Fri, May 18, 2012 at 10:48:52AM -0400, John Baldwin wrote:
> > > > > > On Wednesday, May 16, 2012 11:30:19 am Anton Shterenlikht wrote:
> > > > > > > er.. yes, of course it helped.
> > > > > > > 
> > > > > > > My problem was that I couldn't boot.
> > > > > > > So, I presumed the very existence of dmesg.boot
> > > > > > > showed that your patches (both of them) work fine.
> > > > > > > But, sorry, I could've been more explicit.
> > > > > > > All seems to work, including sound and wireless.
> > > > > > 
> > > > > > Hmm.  Can you try one more thing.  Can you boot an unmodified 
kernel 
> > (no 
> > > > > > patches) but set 'hw.pci.enable_io_modes=0' from the loader?
> > > > > 
> > > > > That works too, see dmesg.boot below.
> > > > 
> > > > I might have misled you on this,
> > > 
> > > Yes, sorry, looking at the dmesg I sent you,
> > > I obviously booted the patched kernel.
> > > 
> > > So, no, 'hw.pci.enable_io_modes=0' in /boot/loader.conf
> > > doesn't help to boot an unmodified kernel.
> > 
> > Ok, I'll work on getting this fix into the tree in some fashion.
> 
> Just to let you know.
> I'm on 2³6024 now, with your patch.
> 
> I've lost sound.
> 
> Commands like:
> 
> % ls > /dev/dsp0.0
> % mixer vol 100
> 
> give lots of 
> 
> hðãc0: ©ømmãnð timeøut øn ãððress 0
> hðãc0: ©ømmãnð timeøut øn ãððress 0
> hðãc0: ©ømmãnð timeøut øn ãððress 0
> 
> on the console.
> 
> Just wanted to check with you if you
> think this has anything to do with the
> patch, or whether you think it's a completely
> different issue.

It could be related perhaps, though I thought on your system the only BAR that 
was disabled was the VGA framebuffer.

-- 
John Baldwin
Received on Wed May 30 2012 - 17:36:17 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:27 UTC