Date: Mon, 31 Jul 2006 22:52:28 +0200 (CEST) From: "Frank W. Josellis" <frank@dynamical-systems.org> To: FreeBSD-gnats-submit@FreeBSD.org Cc: jylefort@FreeBSD.org Subject: ports/101124: sysutils/mbmon - fatal problem with SMB support Message-ID: <200607312052.k6VKqRnR002763@pollux.senax.net> Resent-Message-ID: <200607312100.k6VL0Yds009510@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 101124 >Category: ports >Synopsis: sysutils/mbmon - fatal problem with SMB support >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jul 31 21:00:33 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Frank W. Josellis >Release: FreeBSD 5.5-STABLE i386 >Organization: >Environment: System: FreeBSD pollux.senax.net 5.5-STABLE FreeBSD 5.5-STABLE #7: Sun May 28 19:03:10 CEST 2006 root@pollux.senax.net:/usr/obj/usr/src/sys/POLLUX i386 >Description: Configuring mbmon-205_3 with the default setting "WITH_SMB=true" may cause trouble on some boards. For example, the Asus A7V8X makes use of the SMBus for hardware monitoring: $ mbmon -dA Summary of Detection: * SMB monitor(s)[VT8233/A/8235/8237(KT266/333/400/600/880)]: ** Asus Chip ASB100(Bach) found at slave address: 0x5A. The above config option seems to be a natural choice here, but has unexpected consequences. With 6.1-STABLE the program hangs and causes rapidly increasing CPU load. With 5.5-STABLE it's even worse, as invoking mbmon will instantly freeze the entire system, enforcing a RESET. >How-To-Repeat: >Fix: No fix, just a workaround. Choose "WITHOUT_SMB=true" and everything is still fine. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607312052.k6VKqRnR002763>