• BugBusting
• Commonly_reported_issues

Commonly reported FreeBSD issues

This is a list of the most commonly reported FreeBSD issues on the mailing lists. There is some overlap with the Well-Known PRs list and the PRs recommended for committer evaluation by the bugbusting team.

Items marked with are of a severe (non-trivial) nature. Users should be very concerned with those items.

(this article needs a new maintainer. MarkLinimon notes that as of 20120122, some of the entries are stale.)

ATA/SATA

• Please see my ATA/SATA issues and troubleshooting methods page for ATA/SATA-related things

SCSI/SAS, iSCSI

• mpt(4) unable to check the status of a RAID-1 array

  • Reference: http://lists.freebsd.org/pipermail/freebsd-hackers/2008-March/023763.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-hackers/2008-March/023765.html

• mfi(4) problems on Dell PowerEdge PERC6/i controllers

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2007-December/038755.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039568.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039574.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039660.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039675.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039791.html

• ciss(4) breaks with filesystems larger than 2TB

  • Reference: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/ciss/ciss.c

  • Fix: Applied to RELENG_6 and RELENG_7 on May 16th, 2008; see above commit

• iSCSI: Timeouts (30 sec) induced by race condition; result is odd behaviour or bad performance

  • Reference: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html

  • Patch: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html

ZFS

• Heavy I/O between ZFS pool and UFS filesystem results in deadlocked system

  • Reference: ZFSKnownProblems

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/040047.html

• After a failure (checksum or drive failure) + reboot occurs, ZFS can resilver unexpectedly

  • Reference: http://lists.freebsd.org/pipermail/freebsd-fs/2008-January/004241.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-fs/2008-March/004561.html

• After booting into single-user and doing ZFS-related commands, then going back into multi-user, ZFS cannot find any pools to mount (zfs list returns no datasets available)

  • Workaround (confirmed): While in single-user, run /etc/rc.d/hostid start then /etc/rc.d/zfs start

  • Workaround: Once back in multi-user, use zpool import -a to re-import all known ZFS pools. You should only have to do this once

GEOM

• Inability to boot off of gvinum(8) volumes

  • Reference: http://lists.freebsd.org/pipermail/freebsd-geom/2007-August/002513.html

• After making a gstripe(8), using newfs -U on the new stripe causes bad things to happen

dump/restore

• dump process frequently hangs

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2007-January/031882.html

  • Open PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/121684

  • Possible patch (untested): http://lists.freebsd.org/pipermail/freebsd-stable/2007-January/032250.html

  • Possible workaround: use dump without the -L flag. Be aware of the risks, however

• UFS2 snapshot generation (mksnap_ffs, dump -L) takes too long; system is unusable during this time

  • Reference (explanation): http://lists.freebsd.org/pipermail/freebsd-hackers/2007-October/021985.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-fs/2005-July/001216.html

• Filesystems not cleanly shut down if reboot performed while dump(8) still running

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2007-September/036916.html

Kernel

• System locks up after printing Trying to mount root from ufs:/whatever/device

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045161.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-current/2005-August/054879.html

• Intel SpeedStep (EIST) incompatibilities with some motherboards

  • Symptom: kernel says things like calcru: negative runtime of -XXXXX usec for pid XX

  • Symptom: kernel says things like calcru: runtime went backwards from XXXXX usec to XXXXX usec for pid XX

  • Reference: http://lists.freebsd.org/pipermail/freebsd-questions/2006-October/133253.html

  • Workaround: Disable the EIST feature in the BIOS. You can still achieve ACPI-based processor frequency throttling by using powerd(8)

• RELENG_7 jerky mouse and skipping sound

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039599.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-February/040793.html

• Scrambled or garbled kernel output, such as:

  • SdMaP0::  AP1 6C0P.U0 0#0M1B /Lsa utnrcahnesdf!e
    da0: <SSMEPA:G AATPE  CSPTU3 3#617 5L3auLnWc hHePdS!3> 

    Sep  5 00:34:38 test kernel: Waiting (max 60
    Sep  5 00:34:38 test kernel: seScyonncdisn)g  fdoirs kssy,s tvenmo dperso
    creesmsa i`nsiynngc.e.r.' to3  stop...0 0 done
    Sep  5 00:34:38 test kernel: All buffers synced. 

  • Reference: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078145.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-current/2007-November/079130.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2007-December/038727.html

  • Workaround (partial): Use options PRINTF_BUFR_SIZE=256 in your kernel configuration. This will decrease the amount of interspersed output, but does not solve issue entirely

• Panic occurs when a mounted device (USB, SATA, local image file, etc.) is removed

  • Workaround: Be sure to umount all filesystems before removing the physical device
  • Partial fix: Committed to CURRENT (8.0) on/prior to 2008/02/21

  • There is ongoing work to fully fix this problem, ETA 2009/02

• Panic occurs when vm.kmem_size or vm.kmem_size_max set to values larger than 1536M

  • Kernel will panic with a message that looks very similar to either of the following:

    • panic: kmem_malloc(4096): kmem_map too small: 1073741824 total allocated
      kmem_suballoc(): bad status return of 3 

  • Limit is caused by a 2GB limit for kmem
  • Affects i386 and amd64, regardless of how much physical memory is installed
  • Greatly impacts ZFS stability

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042764.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-hackers/2008-May/024708.html

  • Fix: Committed to CURRENT (8.0); expands limitation to 512GB. MFC of fix is very unlikely
• System does not automatically reboot after a kernel panic

  • System reboots fine using shutdown -r or reboot

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042250.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-June/043011.html

ACPI

• NULL (\0) characters in ACPI namespace results in kernel panic

  • Affects some MSI motherboards

  • Reference: http://bsd.haofood.net/2005/11/21/work-around-for-busted-rs-acpi-long/

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-April/041789.html

• Some FreeBSD devices do not work, functionality is limited, or kernel panics early during boot stage; system works with ACPI disabled.

  • Check dmesg(8) to see if the kernel spits out any ACPI errors on boot

  • Workaround: Check motherboard vendor's website for an updated BIOS, which may/may not fix applicable ACPI tables

Firewall (pf, ipfilter, ipfw)

• pf(4): "modulate state" appears to function oddly/incorrectly on FreeBSD

  • Reference: http://lists.freebsd.org/pipermail/freebsd-pf/2008-March/004223.html

  • Workaround (confirmed): Use "keep state" instead

• pf(4): State mismatches can occur when a TCP port is re-used before the state table entry is removed

  • Confirmed to exist on OpenBSD 4.2 as well; fixed in OpenBSD 4.3

  • Open PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/125261

  • Reference: http://www.openbsd.org/plus43.html

  • Fix: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/contrib/pf/net/pf.c

  • Fix: Committed to CURRENT on 2008/08/04
  • Fix: Committed to RELENG_7 on 2008/08/11

Networking (IP stack and friends)

• Changing the IP address of an interface causes loss of routing table information, including default route

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-November/046620.html

  • Confirmation: http://lists.freebsd.org/pipermail/freebsd-stable/2008-November/046624.html

  • Open PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=128954

Networking (hardware and drivers)

• Atheros AR5418, AR9160, AR9281 unsupported

  • Reference: http://lists.freebsd.org/pipermail/freebsd-questions/2008-November/186578.html

  • Linux device driver

  • Support for AR5416, AR5418, AR9130, AR9160, AR9280, AR9281, AR9283, AR9285, AR9287 is present in at least -8 and later. Perhaps later -7 systems included some AR5416/AR5418 spuport.
  • Most stable support SHOULD be in -9/-HEAD.

  • More information: dev/ath_hal(4)/HardwareSupport

• Atheros AR8121/AR8113/AR8114 unsupported
  • Mainly used by Asus P5Q-series motherboards, and the Asus EeePC
  • Otherwise known at Attansic L1E (AR8121) and Attansic L2E (AR8113/AR8114)

  • Significantly different than the Atheros L1 predecessor; not compatible with age(4)

  • Sent Yong-Hyeon PYUN an Asus P5Q SE motherboard for driver development

  • Fix: ale(4) driver committed to CURRENT on 2008/11/12

• Marvel 88E8040 unsupported

  • There is a patch available from Yong-Hyeon PYUN that adds support for this NIC. However, there are numerous problems which should be noted:

    • Ethernet link establishment does not work with this patch, severely limiting its usability

    • A lack of documentation for this NIC makes driver development difficult

    • At present, in the US market, only two computers use this NIC: the Dell Inspiron 1525 and Dell XPS M1530. There are no consumer network cards which use this chip. This limits the ability for one to send hardware to Yong-Hyeon for development.
    • Linux was able to get driver support by Marvell sending the driver authors development/test PCI boards; if only we could get them to do that for FreeBSD...

• em(4) watchdog timeouts on Intel 82573 NICs

  • Reference: http://e1000.sourceforge.net/doku.php?id=known_issues#v_l_e_tx_unit_hang_messages

  • Fix: DOS-based EEPROM patcher from Intel

  • Fix: Boot Linux, install ethtool(8), and follow this procedure

  • Troubleshooting: when using em(4) driver 6.7.3 or later, you can dump the contents of the EEPROM by doing sysctl dev.em.X.debug=2 (0=em0, 1=em1, etc.). You'll see something like this from the kernel:

    • Interface EEPROM Dump:
      Offset
      0x0000  3000 8f48 d903 0d20 f746 0057 ffff ffff
      0x0010  ffff ffff 026b 109a 15d9 109a 8086 80df
      0x0020  0000 2000 7e54 0000 1000 00da 0004 2700
      0x0030  6cc9 3150 0732 040b 2984 0000 c000 0706 

  • Since the above code prints things in little-endian-stored words, you need to look at the value at offset 0x1f (and not 0x1e like Linux ethtool!), which in the above example is value 0xdf. Bit 0 should be set (1), which disables the power-saving feature that causes the problem. In the above example, the bit is set, which means that the above NIC is not succeptable to the bug

• em(4) watchdog timeouts on other NICs

  • Open PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=122928

USB

• Removal of a mounted USB device without umount'ing first results in a kernel panic
  • See above, re: "Kernel - Panic occurs when a mounted device (USB, SATA, local image file, etc.) is removed"
• Keyboard LEDs do not work
• F-Lock key on Microsoft Natural Ergonomic Keyboard does not function on RELENG_7

  • Reference: http://lists.freebsd.org/pipermail/freebsd-usb/2007-July/003806.html

  • Patch: http://sonic.net/~artemb/freebsd/usb-hid.patch.gz

• Modifier keys (Control/Alt/Shift) act as if they are stuck

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-March/041426.html

Bootstraps (BTX, boot2, and loader)

• Cannot boot FreeBSD from a USB device (flash, disk, etc.)

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-March/041112.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-stable/2008-March/041287.html

• Loading of gzip'd mfsroot from pxeboot(8) causes loader reload/reset

  • Open PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/120127

• BTX crashes on start (screen continually scrolls registers or dumps registers then reboots)

  • Some systems behave badly when executing BIOS interrupts while in virtual 86 mode. Use real mode instead

  • Reference: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/boot/i386/btx/btx/Makefile - see revision 1.19.10.1

  • Workaround: Download a snapshot ISO from http://pub.allbsd.org/FreeBSD-snapshots/

  • Fix: John Baldwin committed fixes to RELENG_[467] on March 18th, 2008

• loader version 1.02 hangs, or prints

  • Can't work out which disk we are booting from.
    Guessed BIOS device 0xffffffff not found by probes, defaulting to disk0 

  • Problem #1: v86 structure not initialised prior to being called
  • Problem #2: eflags register not initialised prior to vm86 requests (interrupts randomly disabled/enabled)

  • Reference #1: http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042650.html

  • Reference #2: http://lists.freebsd.org/pipermail/freebsd-stable/2008-August/044204.html

  • Fix #1: Committed to HEAD on 2008/03/10. Revision 1.46
  • Fix #1: Committed to RELENG_[67] on 2008/03/18. Revisions 1.38.2.3 and 1.44.2.1
  • Fix #2: Committed to HEAD on 2008/08/08. Revision 1.47
  • Fix #2: Committed to RELENG_[67] on 2008/08/15. Revisions 1.38.2.4 and 1.44.2.2

PPP

• LuizSouza is interested in testing and fixing problems on ppp. Here are his notes:

  • I have fixed the route handling on ppp. This fixes kern/125079 and kern/122068 (same problem on both) and probably bin/126892 but I think it should be reviewed by an experienced developer. Here is the patch.

  • My experience is from the "server side" using ppp as a pppoe concentrator or as a vpn server. From there I know that the "proxy arp" option is not working at all - my second target.

  • I'm also interested in checking bin/115951 (which has a copy in bin/108895), bin/122519, and others (there are a lot of simple fixes waiting for someone to review and commit).

Other

• When switching consoles (e.g. Alt-F2 to switch to ttyv1), a 2-3 second delay is experienced

  • Often seen when using a USB keyboard on the VGA console, and with atkbd/atkbdc/psm enabled in the kernel. But, can still happen even for people using native PS/2 keyboards

  • Doesn't matter if "USB Legacy" is enabled in the BIOS or not

  • Reference: http://lists.freebsd.org/pipermail/freebsd-hackers/2006-March/015724.html

  • Reference: http://lists.freebsd.org/pipermail/freebsd-hackers/2008-May/024647.html

  • Workarounds (try one or the other, not both):

    • Disable kbdmux -- use hint.kbdmux.0.disabled="1" in loader.conf

    • Disable atkbd and atkbc -- use hint.atkbd.0.disabled="1" and hint.atkbdc.0.disabled="1" in loader.conf