Re: incorrect subclass?
"Karsten W. Rohrbach" wrote: > > Matthew Jacob([EMAIL PROTECTED])@2001.04.09 16:42:05 +: > > FBSD-I-I do not think you should do that. > > FBSD-W-Do not do that again. > > FBSD-E-I told you not to do that. > > FBSD-F-panic, freeing free identifier of known type > > > when you implemted it, remind me to get a stack of blank punhcards to > create a boot stack for /boot/loader and /kernel ;-) No, no, no, that's a VAXism, so you will want to load your kernel, or perhaps even microcode, from a DECtape. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: incorrect subclass?
Matthew Jacob([EMAIL PROTECTED])@2001.04.09 16:42:05 +: > FBSD-I-I do not think you should do that. > FBSD-W-Do not do that again. > FBSD-E-I told you not to do that. > FBSD-F-panic, freeing free identifier of known type > when you implemted it, remind me to get a stack of blank punhcards to create a boot stack for /boot/loader and /kernel ;-) /k -- > cd /pub; more beer KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: incorrect subclass?
On Mon, 9 Apr 2001, Mike Smith wrote: > > > > This showed up recently on my PC164: > > > > > > > > PCI-ISA bridge with incorrect subclass 0x0 > ... > > Oh, if it's not a problem, it's not a problem. > > No, it's not a problem. We probably need a mechanism for identifying > the various classes of diagnostics we print... 8) FBSD-I-I do not think you should do that. FBSD-W-Do not do that again. FBSD-E-I told you not to do that. FBSD-F-panic, freeing free identifier of known type To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: incorrect subclass?
> > > This showed up recently on my PC164: > > > > > > PCI-ISA bridge with incorrect subclass 0x0 ... > Oh, if it's not a problem, it's not a problem. No, it's not a problem. We probably need a mechanism for identifying the various classes of diagnostics we print... 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: incorrect subclass?
On Mon, 9 Apr 2001, Mike Smith wrote: > > > > This showed up recently on my PC164: > > > > PCI-ISA bridge with incorrect subclass 0x0 > > PCI-ISA bridge with incorrect subclass 0x0 > > This is a bootverbose thing; I meant for it to assist in making sure that > the list of PCI:ISA bridges we had was accurately tuned. If it's > bothering you, feel free to either nuke the printf (I don't intend on > trimming the list, after all) or to mark the chipset(s) in question as > known to be buggy so that someone *else* trimming the list doesn't cut > them out by accident. Oh, if it's not a problem, it's not a problem. Thurber wrote of saying pointing a quivering finger at a dial on his car dashboard and saying to the mechanic, "Say- that isn't supposed to be that high, is it??". The mechanic responded with a pitying, "Look, Pal, all it is is that you've got your radio tuned to WOR" (Or something like this..) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: incorrect subclass?
> > This showed up recently on my PC164: > > PCI-ISA bridge with incorrect subclass 0x0 > PCI-ISA bridge with incorrect subclass 0x0 This is a bootverbose thing; I meant for it to assist in making sure that the list of PCI:ISA bridges we had was accurately tuned. If it's bothering you, feel free to either nuke the printf (I don't intend on trimming the list, after all) or to mark the chipset(s) in question as known to be buggy so that someone *else* trimming the list doesn't cut them out by accident. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
