Unable to boot recent -stable with MSI/MSIX enabled
jfvogel at gmail.com
Fri Oct 12 20:19:07 PDT 2007
A suggestion, take the relevant files from my em driver and put
them back into the kernel tree that was working on 10/1, it should
be compatible. Then see if it breaks that kernel. Or if you'd prefer
I can just email the tar ball for the Intel version of 6.6.6, you can
disable the in-kernel em driver, and build the other and use that
with the 10/1 kernel.
Let me know what you'd prefer.
On 10/12/07, Alson van der Meulen <alson+ml at alm.flutnet.org> wrote:
> * Jack Vogel <jfvogel at gmail.com> [2007-10-13 01:30]:
> > Hmmm, so am I correct in understanding that this root is remote, so its
> > really coming in over the the em driver?
> No, the root is local: gmirror of two SATA disks on ATA (AHCI)
> controller, this host has no remote filesystems. em is not needed for
> mounting the root fs. I'm not 100% sure if em is to blame, but:
> - The em merge is the only remotely related commit to RELENG_6 that I
> could find between October 1 and October 10.
> - Disabling MSI/MSIX fixes it, and em is the only MSI user as far as I
> can see in the dmesg.
> It's possible that the use of MSI by em triggers a bug in the PCI/ATA
> driver. It's even possible that the chipset has broken MSI support (see
> previous mail for dmesgs).
> Friday morning (local time, CEST), it did boot up with the new kernel
> and mounted its root FS successfully, but when I attempted to log in a
> few hours later, none of the network interfaces (em and fxp) worked. fxp
> is not even on a PCIe link, but a PCI card, so it appears to break
> any PCI/PCIe device. Logging in via the console gave this error:
> getty: /usr/bin/login: Exec format error
> Probably because it couldn't properly access /usr (which is on ATA
> disks) anymore.
> The system appears to have worked initially, but started to fail when my
> workstation, which is directly connected to the em interface, was turned
> on. I also saw a watchdog timeout on the em interface about ten minutes
> after the link went up. After my workstation was turned on this box lost
> all network connections. Unplugging the cable to the em interface might
> prevent the problem to occur, this also points at the em driver as the
> trigger. I'll try to verify this.
> Below is a list of files in /usr/src/sys changed since the last working
> kernel of 2007-10-01. I don't see any PCI changes relevant to amd64, so
> it appears to be at least triggered by the em driver.
> freebsd-stable at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
More information about the freebsd-stable