GIANT lock in 5.4
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 mem 0xfeb0-0xfebf irq 9 at device 1.0 on pci0 ips0: [GIANT-LOCKED] With FreeBSD 5.4, the [GIANT-LOCKED] message no longer appears. Does that mean that Giant lock has been removed from all those drivers, or is the message simply not printed? --- ... You have, of course, just begun reading the sentence that you have just finished reading. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GIANT lock in 5.4
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 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-SAFE] or > > [GIANT-LOCKED] outputs on 5.4. > > > > Joerg > > How to do this when no console access? thanks. See boot(8). Kris pgpaA9PceUTRj.pgp Description: PGP signature
Re: GIANT lock in 5.4
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, > atkbd) had a note similar to this in dmesg: > > ips0: port 0x2000-0x20ff mem > 0xfeb0-0xfebf irq 9 at device 1.0 on pci0 > ips0: [GIANT-LOCKED] > > With FreeBSD 5.4, the [GIANT-LOCKED] message no longer appears. > > Does that mean that Giant lock has been removed from all those drivers, > or is the message simply not printed? Do you still see it on some other drivers? If so, the former. Kris pgpotk6bqopDW.pgp Description: PGP signature
Re: GIANT lock in 5.4
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 pci0 ips0: [GIANT-LOCKED] With FreeBSD 5.4, the [GIANT-LOCKED] message no longer appears. Does that mean that Giant lock has been removed from all those drivers, or is the message simply not printed? Do you still see it on some other drivers? If so, the former. 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. --- ... I spilled spot remover on my dog. Now he's gone. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GIANT lock in 5.4
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: > >> > >>ips0: port 0x2000-0x20ff mem > >>0xfeb0-0xfebf irq 9 at device 1.0 on pci0 > >>ips0: [GIANT-LOCKED] > >> > >>With FreeBSD 5.4, the [GIANT-LOCKED] message no longer appears. > >> > >>Does that mean that Giant lock has been removed from all those drivers, > >>or is the message simply not printed? > > > >Do you still see it on some other drivers? If so, the former. > > 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. The message was surpressed, then. It did generate a lot of confusion from users who didn't realise that "Giant locked" was the state of the *entire kernel* in 4.x and thought that this was a regression in 5.x. Kris pgp8bLCoOoDmk.pgp Description: PGP signature
Re: GIANT lock in 5.4
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-SAFE] or [GIANT-LOCKED] outputs on 5.4. Joerg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GIANT lock in 5.4
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. > > Choose the "Boot with verbose dmesg" option to get the [MP-SAFE] or > [GIANT-LOCKED] outputs on 5.4. > > Joerg How to do this when no console access? thanks. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
