In message <[EMAIL PROTECTED]> Soren Schmidt writes:
: Busspace is a joke, I'm perfectly fine with calling those macros
: in[bwl]/out[bwl] like they should be :)
You wouldn't say that if you've had to deal with all the oddities of a
mips box.
: Busdma, hmm, well I dont see that helping here eith
> > I'd hazard a guess that the presence of modules is causing the kernel
> > linker to run and pull all the sysctl hooks for modules it's finding.
> > I'm probably wrong, just a guess.
...
> I'll go look up cold usage, and see if it necessarily has to be done that
> early. I'll also investiga
> It seems Mike Smith wrote:
> > That's possible; it may be that the kernel linker is calling something
> > before you expect it to be called.
>
> Well, its rather that the delayed probe rutine I register with
> config_intrhook_establish() is called before interrupts are actually
> working, tha
On Thu, Feb 24, 2000 at 09:03:55AM +, Doug Rabson wrote:
[snip]
> Nick Hibma's machine at work shows this problem. Its an AMD Athlon FWIW.
> Nick spent a couple of hours looking at it without much success. I'll try
> some things today to see if the probe is being called with interrupts
> di
It seems Mike Smith wrote:
> >
> > That megapatch was only newbus patches and cosmetics around that, one
> > new item was cmd646 support but that is hardly the problem here.
>
> You didn't mention the 0xa5 test, and I forgot to tell you that I backed
> it out as well (no change).
yeah, cosmeti
> It seems Mike Smith wrote:
> > > Forgive me if I'm beating a dead horse... I'm still having the following
> > > problem if I load any modules from /boot/loader.conf:
> >
> > I've reproduced this here, and narrowed it down to Soren's ATA megacommit
> > on the 18th. Unfortunately, the newbus pa
Soren Schmidt wrote:
>
> It seems Mike Smith wrote:
> > > Forgive me if I'm beating a dead horse... I'm still having the following
> > > problem if I load any modules from /boot/loader.conf:
> >
> > I've reproduced this here, and narrowed it down to Soren's ATA megacommit
> > on the 18th. Unfort
I'm also
experiencing this under current since the Mega Patch, I'm running on Celeron
500. Asus P99B Board (2 IDE, 128MB Ram, 4.3 GB Hard Disk). But if I don't load
any modules, it works fine.
It seems Doug Rabson wrote:
> >
> > That megapatch was only newbus patches and cosmetics around that, one
> > new item was cmd646 support but that is hardly the problem here.
> >
> > > Soren - this is somewhat of a showstopper. Can you reproduce it there?
> >
> > Nope, I've tried several machi
It seems Mike Smith wrote:
> > Forgive me if I'm beating a dead horse... I'm still having the following
> > problem if I load any modules from /boot/loader.conf:
>
> I've reproduced this here, and narrowed it down to Soren's ATA megacommit
> on the 18th. Unfortunately, the newbus patches (teste
> Forgive me if I'm beating a dead horse... I'm still having the following
> problem if I load any modules from /boot/loader.conf:
I've reproduced this here, and narrowed it down to Soren's ATA megacommit
on the 18th. Unfortunately, the newbus patches (tested) and the other
gunk (untested) end
Forgive me if I'm beating a dead horse... I'm still having the following
problem if I load any modules from /boot/loader.conf:
ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_INTR
ata0-slave: ata_command: timeout waiting for intr
ata0-slave: identify failed
no devsw (majdev=0 bootdev=0xa040)
M
> > > > > I've yesterday sent a post on this list (from my work email) about the
> > > > > impossibility of loading the if_xl and miibus modules with the loader
> > > > > (it works well with kldload, afterwards)
> > > >
> > > > This is a known problem with modules that have dependancies; if you lo
Mike Smith wrote:
>
> > > > I've yesterday sent a post on this list (from my work email) about the
> > > > impossibility of loading the if_xl and miibus modules with the loader
> > > > (it works well with kldload, afterwards)
> > >
> > > This is a known problem with modules that have dependancies
> > > I've yesterday sent a post on this list (from my work email) about the
> > > impossibility of loading the if_xl and miibus modules with the loader
> > > (it works well with kldload, afterwards)
> >
> > This is a known problem with modules that have dependancies; if you load
> > the miibus m
Mike Smith wrote:
>
> > Hello,
> >
> > I've yesterday sent a post on this list (from my work email) about the
> > impossibility of loading the if_xl and miibus modules with the loader
> > (it works well with kldload, afterwards)
>
> This is a known problem with modules that have dependancies; if
> Hello,
>
> I've yesterday sent a post on this list (from my work email) about the
> impossibility of loading the if_xl and miibus modules with the loader
> (it works well with kldload, afterwards)
This is a known problem with modules that have dependancies; if you load
the miibus module first
Hello,
I've yesterday sent a post on this list (from my work email) about the
impossibility of loading the if_xl and miibus modules with the loader
(it works well with kldload, afterwards)
This is with 4.0 - RC1.
TfH
(The loader loops trying to load the miibus module)
Mike Smith wrote
> Vladimir Kushnir wrote:
> >
> > Hello,
> > I dont't know if this is some HW problem, but after the last update system
> > became unbootable if I load modules by /boot/loader rather them kldload.
> That seems to be a bug -- I'd just load the modules via /etc/rc.conf for
> now. Other people h
Vladimir Kushnir wrote:
>
> Hello,
> I dont't know if this is some HW problem, but after the last update system
> became unbootable if I load modules by /boot/loader rather them kldload.
That seems to be a bug -- I'd just load the modules via /etc/rc.conf for
now. Other people have reported p
Hello,
I dont't know if this is some HW problem, but after the last update system
became unbootable if I load modules by /boot/loader rather them kldload.
> sos 2000/02/18 12:57:33 PST
>
> Modified files:
> sys/alpha/includemd_var.h
> sys/alpha/pcipcibus.c
>
21 matches
Mail list logo
