Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Dec 2005 22:04:33 +0100
From:      Melvyn Sopacua <freebsd.stable@melvyn.homeunix.org>
To:        freebsd-stable@freebsd.org
Subject:   Re: HEADS UP: Release schedule for 2006
Message-ID:  <200512162204.34400.freebsd.stable@melvyn.homeunix.org>
In-Reply-To: <20051216204503.GR77268@cirb503493.alcatel.com.au>
References:  <20051216105005.68898.qmail@web36212.mail.mud.yahoo.com> <200512162120.45053.freebsd.stable@melvyn.homeunix.org> <20051216204503.GR77268@cirb503493.alcatel.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 16 December 2005 21:45, Peter Jeremy wrote:

> EST - Enhanced SpeedStep
> TM2 - Thermal Monitor 2

Hm, guess I'll play with mbmon to see if this shows more then one monitor 
(assuming the 2 is the number of, not the protocol version).

> >-pci0: <serial bus, USB> at device 29.7 (no driver attached)
> >+ehci0: <Intel 82801DB/DBL/DBM (ICH4) USB 2.0 controller> mem
> >0xf4fffc00-0xf4ffffff irq 11 at device 29.7 on pci0
> >+ehci0: [GIANT-LOCKED]
> >
> >Kudos!
>
> I'm still trying to get my USB2 to do anything more than probe :-(

Ouch, well guess I'll have to find that memory stick I should have around here 
somewhere.

> >-Timecounter "TSC" frequency 1398819442 Hz quality 800
> >-Timecounters tick every 10.000 msec
> >+Timecounter "TSC" frequency 1398819606 Hz quality 800
> >+Timecounters tick every 1.000 msec
> >
> >Q: This is a big scarey difference :p This isn't a printf bug I presume?
>
> Which bit?  The TSC is notoriously unstable and a relative change of
> 1.2e-7 can be ignored.  If you look at kern.clockrate, you'll see that
> hz now defaults to 1000.

Ah! That explains why rtc was complaining on 5.x but magically stopped doing 
that on 6.

> >-acd0: CDRW <HL-DT-STCD-RW/DVD-ROM GCC-4241N/A100> at ata1-master PIO4
> >+acd0: CDRW <HL-DT-STCD-RW/DVD-ROM GCC-4241N/A100> at ata1-master UDMA33
> >
> >That's *very* nice!
>
> Again, that's just a change in defaults.  Problems were found with DMA to
> ATAPI devices so the decision was made to default to PIO4 in 5.x.  You can
> set hw.ata.atapi_dma to 1 in 5.x if you want to (see acd(4)).

Problems as in long waits on `burncd blank` and subsequent i/o errors and 
unmountable disks that disappear after reboot?
-- 
Melvyn Sopacua
freebsd.stable@melvyn.homeunix.org

FreeBSD 6.0-STABLE
Qt: 3.3.5
KDE: 3.4.3



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200512162204.34400.freebsd.stable>