GIANT lock in 5.4
Kris Kennaway
kris at obsecurity.org
Mon Oct 17 12:20:51 PDT 2005
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: <IBM ServeRAID Adapter> port 0x2000-0x20ff mem
> >> 0xfeb00000-0xfebfffff 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20051017/2333fd9e/attachment.bin
More information about the freebsd-questions
mailing list