RELENG_7 hangs on boot w/Gigabyte MA78GM-S2H MB

Jeremy Chadwick koitsu at
Sat Sep 20 14:05:04 UTC 2008

On Sat, Sep 20, 2008 at 08:24:29AM -0500, Bob Willcox wrote:
> > 1) It would be helpful to know if you installed i386 or amd64 FreeBSD,
> This is amd64 on this particular machine.
> > 2) With regards to the lock-up after "mount root", if you press NumLock
> > or CapsLock, do the keyboard LEDs turn on/off?
> Nope, no keys do anything. You must either push reset or pull the plug.

Is it possible to get the output when booting in verbose mode?  If not,
what are the last few lines before the machine locks up when booting

> > 3) Many others have seen the hanging/lock-up after "mount root".  I
> > believe one found a workaround by setting ATA_STATIC_ID in their kernel
> > configuration.  I realise this is a problem when you can't get the
> > system up to a point of building a kernel; chicken-and-egg problem,
> Well, I can build a kernel if I run the 7.0-release kernel. That's how I
> got to 7-stable on the machine in the first place. I used "sneaker net"
> to copy it to this one via a CD (as I mentioned, the 7.0 kernel boots
> but the Realtek ethernet device is not recognized).

So the problem is that 7.0-RELEASE works fine for you, but after
upgrading your RELENG_7 source (to what is now 7.1-BETA), the machine
hangs after printing the mount root message.  Is this correct?

Here's another question: does booting into single-user exhibit the same
problem as multi-user?

> > 4) The Realtek NIC on that motherboard is probably too new to be
> > supported under RELENG_7.  Realtek has a history of releasing different
> > sub-revisions of the same NIC/PHY, and the internal changes are severe
> > enough to cause the NIC to not work correctly (under any OS) without
> > full driver support for that specific sub-revision.
> That's what I suspected. The values displayed when doing a "pciconf -lv"
> are similar as for this system I'm using to type this, but now that
> I look closer and make a direct comparison, the failing device has a
> rev=0x02 vs. rev=0x01 for the working one. The pciconf -lv output for
> the failing mb is:
> none3 at pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x02 hdr=0x00
>     vendor     = 'Realtek Semiconductor'
>     device     = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
>     class      = network
>     subclass   = ethernet

Regarding the Realtek issue: I've CC'd PYUN Yong-Hyeon (surname in
caps), who maintains the re(4) driver for FreeBSD.  He might have a
patch available for you to try, or help determine how to get this NIC
working on FreeBSD.  He'll probably need more than just pciconf -lv
output, but should be able to work with you.


| Jeremy Chadwick                                jdc at |
| Parodius Networking              |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |

More information about the freebsd-stable mailing list