On Wed, Oct 19, 2005 at 03:18:00AM +0100, Chris wrote:
> On 17/10/05, Joerg Pernfuss <[EMAIL PROTECTED]> wrote:
> > On Mon, 17 Oct 2005 22:11:07 +0300
> > Toomas Aas <[EMAIL PROTECTED]> wrote:
> >
> >
> > > grep -i giant /var/run/dmesg.boot comes up blank on all my FreeBSD 5.4
> > > machines: the t
On 17/10/05, Joerg Pernfuss <[EMAIL PROTECTED]> wrote:
> On Mon, 17 Oct 2005 22:11:07 +0300
> Toomas Aas <[EMAIL PROTECTED]> wrote:
>
>
> > grep -i giant /var/run/dmesg.boot comes up blank on all my FreeBSD 5.4
> > machines: the two RELENG_5_4 servers I've just upgraded and my home
> > RELENG_5 box
On Mon, 17 Oct 2005 22:11:07 +0300
Toomas Aas <[EMAIL PROTECTED]> wrote:
> grep -i giant /var/run/dmesg.boot comes up blank on all my FreeBSD 5.4
> machines: the two RELENG_5_4 servers I've just upgraded and my home
> RELENG_5 box.
Choose the "Boot with verbose dmesg" option to get the [MP-SAF
On Mon, Oct 17, 2005 at 10:11:07PM +0300, Toomas Aas wrote:
> Kris Kennaway wrote:
>
> >On Mon, Oct 17, 2005 at 09:28:56PM +0300, Toomas Aas wrote:
> >
> >>Hello!
>
> ...
>
> >>With FreeBSD 5.3, several devices (for example: ips, ahc,
> >>atkbd) had a note similar to this in dmesg:
> >>
> >>ips
Kris Kennaway wrote:
On Mon, Oct 17, 2005 at 09:28:56PM +0300, Toomas Aas wrote:
Hello!
...
With FreeBSD 5.3, several devices (for example: ips, ahc,
atkbd) had a note similar to this in dmesg:
ips0: port 0x2000-0x20ff mem
0xfeb0-0xfebf irq 9 at device 1.0
On Mon, Oct 17, 2005 at 09:28:56PM +0300, Toomas Aas wrote:
> Hello!
>
> I'm in a process of upgrading our FreeBSD 5.3 servers to 5.4. Two done,
> one to go. I noticed that the Giant lock is no longer mentioned in dmesg
> during boot. With FreeBSD 5.3, several devices (for example: ips, ahc,
>
Hello!
I'm in a process of upgrading our FreeBSD 5.3 servers to 5.4. Two done,
one to go. I noticed that the Giant lock is no longer mentioned in dmesg
during boot. With FreeBSD 5.3, several devices (for example: ips, ahc,
atkbd) had a note similar to this in dmesg:
ips0: port 0x2000-0x20ff