It is also a descendant of Oberon, which was used very much successfully at ETHZ during the 90's.
Every time I have this argument I wish some PhD student bothers to rewrite Native Oberon in Go.
Also you should educate yourself, a small list of GC enabled systems programming language is:
Lisp, Algol-68RS, Mesa/Cedar, Modula-2+, Modula-3, Oberon, Oberon-2, Active Oberon, Component Pascal, Sing#, SystemC#, D.
There are plenty of ACM, SIGPLAN, digital archive papers from the OS written in those languages.
Far as Go, it's designed to recreate the Oberon-2 experience of Pike. It's basically a modified Oberon. If Oberon can do OS's, then Go can do OS's with some modifications to runtime or something.
https://github.com/jjyr/bootgo
http://wiki.osdev.org/Go_Bare_Bones
Although the Wiki author doesn't seem to understand how to use the unsafe.Pointer type, and makes use of external Assembly instead, but the bootgo does it properly.
I just sent the Github author an email suggesting it as his next project. Plus a little praise for giving us the needed ammo. :)
If the whole OS stack can be implemented in the language, ignoring the Assembly help that even C requires, it is a systems language regardless if it has a GC for heap management or not.