On Fri, Feb 24, 2012 at 12:22:36PM -0500, John Baldwin wrote:
> Try this for fixing the panic. New-bus was not clearing the description
> if a device's attach routine failed.
Thanks, this patch indeed fixes the panic.
./danfe
___
freebsd-current@freebs
On Thursday, February 23, 2012 9:41:16 am Alexey Dokuchaev wrote:
> On Thu, Feb 23, 2012 at 08:28:47AM -0500, John Baldwin wrote:
> > Hmm, can you see what 'dev->nameunit' is? Maybe just do 'p *dev' actually
> > and reply with that.
>
> (kgdb) p *dev
> $1 = {ops = 0xc50de000, link = {tqe_next = 0
On Thu, Feb 23, 2012 at 08:28:47AM -0500, John Baldwin wrote:
> Hmm, can you see what 'dev->nameunit' is? Maybe just do 'p *dev' actually
> and reply with that.
(kgdb) p *dev
$1 = {ops = 0xc50de000, link = {tqe_next = 0xc5271380, tqe_prev =
0xc5271184},
devlink = {tqe_next = 0xc5271380, tqe_pre
On Thursday, February 23, 2012 1:44:49 am Alexey Dokuchaev wrote:
> On Wed, Jan 19, 2011 at 08:14:19AM -0500, John Baldwin wrote:
> > On Wednesday, January 19, 2011 5:08:10 am Bruce Cran wrote:
> > > On Tue, 18 Jan 2011 11:25:38 -0500
> > > John Baldwin wrote:
> > >
> > > > Oh, the uart[01] devic
On Wed, Jan 19, 2011 at 08:14:19AM -0500, John Baldwin wrote:
> On Wednesday, January 19, 2011 5:08:10 am Bruce Cran wrote:
> > On Tue, 18 Jan 2011 11:25:38 -0500
> > John Baldwin wrote:
> >
> > > Oh, the uart[01] devices already exist. I suspect if you removed the
> > > hints from /boot/device.
On Wednesday, January 19, 2011 5:08:10 am Bruce Cran wrote:
> On Tue, 18 Jan 2011 11:25:38 -0500
> John Baldwin wrote:
>
> > Oh, the uart[01] devices already exist. I suspect if you removed the
> > hints from /boot/device.hints and then kldloaded uart you would be
> > ok. I think this is an "ol
On Tue, 18 Jan 2011 11:25:38 -0500
John Baldwin wrote:
> Oh, the uart[01] devices already exist. I suspect if you removed the
> hints from /boot/device.hints and then kldloaded uart you would be
> ok. I think this is an "old" bug that might also be in 8.x.
I'm running -CURRENT from a couple of
On Saturday, January 15, 2011 2:14:25 pm Bruce Cran wrote:
> On Mon, 10 Jan 2011 14:46:06 -0500
> John Baldwin wrote:
> > Can you get devinfo -rv output before you try to kldload uart?
>
> I've attached the devinfo output.
Oh, the uart[01] devices already exist. I suspect if you removed the hin
On Mon, 10 Jan 2011 14:46:06 -0500
John Baldwin wrote:
> Can you get devinfo -rv output before you try to kldload uart?
I've attached the devinfo output.
--
Bruce Crannexus0
cryptosoft0
padlock0
npx0
ram0
I/O memory addresses:
0x0-0x9fbff
0x9fc00-0x9
On Sunday, January 09, 2011 9:02:15 am Bruce Cran wrote:
> Hi,
>
> I removed uart from my kernel configuration - when I tried to load it
> later as a module I got the following error:
>
> acpi_timer0: couldn't allocate resource (port 0x4008)
> driver bug: Unable to set devclass (devname: (null))
Hi,
I removed uart from my kernel configuration - when I tried to load it
later as a module I got the following error:
acpi_timer0: couldn't allocate resource (port 0x4008)
driver bug: Unable to set devclass (devname: (null))
--
Bruce Cran
___
freebsd
11 matches
Mail list logo