Re: ECC memory driver in FreeBSD 10?

2012-04-07 Thread Nikolay Denev
On Apr 6, 2012, at 2:48 PM, O. Hartmann wrote: I'm looking for a way to force FreeBSD 10 to maintain/watch ECC errors reported by UEFI (or BIOS). Since ECC is said to be essential for server systems both in buisness and science and I do not question this, I was wondering if I can not report

Re: There is a known problem with MIPS tinderbox.

2012-04-07 Thread Jayachandran C.
2012/4/7 Stanislav Sedov s...@freebsd.org: On Fri, 6 Apr 2012 13:08:12 +0530 Jayachandran C. c.jayachand...@gmail.com mentioned: On Fri, Apr 6, 2012 at 12:01 PM, Stanislav Sedov s...@freebsd.org wrote: On Apr 5, 2012, at 11:08 PM, Jayachandran C. wrote: The asn1 library has a export

[head tinderbox] failure on mips/mips

2012-04-07 Thread FreeBSD Tinderbox
TB --- 2012-04-07 08:30:40 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-07 08:30:40 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

msk0: watchdog timeout in the HEAD

2012-04-07 Thread Subbsd
After updating kernel from 9-STABLE to 10-CURRENT (amd64) msk interfaces stop working with watchdog timout error. Watchdog arises at a traffic 100-300+ Kb, for example: make - C /usr/ports fetchindex (on the fresh boot) reaches 11-15% before watchdog coming pciconf -vl | grep -A4 ^msk

device_attach(9) and driver initialization

2012-04-07 Thread Konstantin Belousov
Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach method is executing, device is not fully initialized yet. Also the device state in the newbus part of the world is DS_ALIVE. There is definitely no shattering news in the statements, but

Re: device_attach(9) and driver initialization

2012-04-07 Thread Ian Lepore
On Sat, 2012-04-07 at 15:50 +0300, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach method is executing, device is not fully initialized yet. Also the device state in the newbus part of the world is

Re: device_attach(9) and driver initialization

2012-04-07 Thread Konstantin Belousov
On Sat, Apr 07, 2012 at 08:46:41AM -0600, Ian Lepore wrote: On Sat, 2012-04-07 at 15:50 +0300, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach method is executing, device is not fully initialized

Re: device_attach(9) and driver initialization

2012-04-07 Thread Nathan Whitehorn
On 04/07/12 07:50, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach method is executing, device is not fully initialized yet. Also the device state in the newbus part of the world is DS_ALIVE. There is

Re: device_attach(9) and driver initialization

2012-04-07 Thread Konstantin Belousov
On Sat, Apr 07, 2012 at 10:04:59AM -0500, Nathan Whitehorn wrote: On 04/07/12 07:50, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach method is executing, device is not fully initialized yet. Also the

Re: device_attach(9) and driver initialization

2012-04-07 Thread Nathan Whitehorn
On 04/07/12 10:15, Konstantin Belousov wrote: On Sat, Apr 07, 2012 at 10:04:59AM -0500, Nathan Whitehorn wrote: On 04/07/12 07:50, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach method is executing,

[head tinderbox] failure on mips/mips

2012-04-07 Thread FreeBSD Tinderbox
TB --- 2012-04-07 16:39:13 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-07 16:39:13 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

FreeBSD 10.0-CURRENT/amd r234000: Xorg/xdm startup failure when started via /etc/ttys

2012-04-07 Thread O. Hartmann
Since I recompiled this morning the sources of FreeBSD 10.0-CURRENT/amd64 (r234000), I have a very strange behaviour of xdm started via /etc/ttys. For a short moment the xdm login requester is shown on the screen and then the console is visible again. Well, I tried to investigate the problem and

Re: device_attach(9) and driver initialization

2012-04-07 Thread Julian Elischer
On 4/7/12 5:50 AM, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach method is executing, device is not fully initialized yet. Also the device state in the newbus part of the world is DS_ALIVE. There is

Re: device_attach(9) and driver initialization

2012-04-07 Thread Julian Elischer
On 4/7/12 8:15 AM, Konstantin Belousov wrote: On Sat, Apr 07, 2012 at 10:04:59AM -0500, Nathan Whitehorn wrote: On 04/07/12 07:50, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach method is executing,

[head tinderbox] failure on mips/mips

2012-04-07 Thread FreeBSD Tinderbox
TB --- 2012-04-08 00:37:11 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-04-08 00:37:11 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB ---

Re: device_attach(9) and driver initialization

2012-04-07 Thread Warner Losh
On Apr 7, 2012, at 8:46 AM, Ian Lepore wrote: On Sat, 2012-04-07 at 15:50 +0300, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach method is executing, device is not fully initialized yet. Also the

Re: device_attach(9) and driver initialization

2012-04-07 Thread Warner Losh
On Apr 7, 2012, at 9:04 AM, Nathan Whitehorn wrote: On 04/07/12 07:50, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach method is executing, device is not fully initialized yet. Also the device state

Re: device_attach(9) and driver initialization

2012-04-07 Thread Warner Losh
On Apr 7, 2012, at 8:57 AM, Konstantin Belousov wrote: On Sat, Apr 07, 2012 at 08:46:41AM -0600, Ian Lepore wrote: On Sat, 2012-04-07 at 15:50 +0300, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus. Basically, when device attach

Re: device_attach(9) and driver initialization

2012-04-07 Thread Warner Losh
On Apr 7, 2012, at 3:34 PM, Julian Elischer wrote: On 4/7/12 8:15 AM, Konstantin Belousov wrote: On Sat, Apr 07, 2012 at 10:04:59AM -0500, Nathan Whitehorn wrote: On 04/07/12 07:50, Konstantin Belousov wrote: Hello, there seems to be a problem with device attach sequence offered by newbus.

Re: device_attach(9) and driver initialization

2012-04-07 Thread Konstantin Belousov
On Sat, Apr 07, 2012 at 09:10:55PM -0600, Warner Losh wrote: On Apr 7, 2012, at 8:57 AM, Konstantin Belousov wrote: On Sat, Apr 07, 2012 at 08:46:41AM -0600, Ian Lepore wrote: On Sat, 2012-04-07 at 15:50 +0300, Konstantin Belousov wrote: Hello, there seems to be a problem with device