Today I updated my 9.0-CURRENT system (amd64) to revision 199506: After
rebooting I get the following messages two times per second in an
endless run:
-
...
Jan 14 09:37:47 krabat kernel: (sg1:umass-sim0:0:0:0):
cam_periph_release_locked: release
After looking around I had been able to localise the cause for the
described messages, see below:
On 14.01.2011 10:07 (UTC+1), Rainer Hurling wrote:
Today I updated my 9.0-CURRENT system (amd64) to revision 199506: After
rebooting I get the following messages two times per second in an
endless
This is just a heads up that I've committed some changes to how the scheduler
handles realtime thread priorities. Please let me know of any issues you
encounter with nice, rtprio, or idprio. Note that as a result of these
changes, rtprio threads will no longer share priorities with
On Fri, 14 Jan 2011, John Baldwin wrote:
This is just a heads up that I've committed some changes to how the scheduler
handles realtime thread priorities. Please let me know of any issues you
encounter with nice, rtprio, or idprio. Note that as a result of these
changes, rtprio threads will
On Friday, January 14, 2011 12:22:18 pm Daniel Eischen wrote:
On Fri, 14 Jan 2011, John Baldwin wrote:
This is just a heads up that I've committed some changes to how the
scheduler
handles realtime thread priorities. Please let me know of any issues you
encounter with nice, rtprio, or
engineering team. This should provide a sufficient testing period before
9.0 and allow a maximal number of bugs to be discovered and solved
before the release is shipped.
Demo ISO for i386:
http://people.freebsd.org/~nwhitehorn/bsdinstall-i386-20110114.iso.bz2
SVN repository: svn://svn.freebsd.org/base
2011/1/14 John Baldwin j...@freebsd.org:
Note that as a result of these
changes, rtprio threads will no longer share priorities with interactive
timeshare threads. Instead, rtprio threads are now always more important than
non-rt threads.
Great!
I was thinking about the split of timesharing
Marcus,
Can you have a look at this?
--HPS
On Friday 14 January 2011 16:21:00 Rainer Hurling wrote:
After looking around I had been able to localise the cause for the
described messages, see below:
On 14.01.2011 10:07 (UTC+1), Rainer Hurling wrote:
Today I updated my 9.0-CURRENT system
On Thursday, January 13, 2011 11:26:46 am Michael Jung wrote:
Links to crash info below.
http://216.26.153.6/msgbuf.txt
This might be a hardware problem. The panic you got is a should never
happen panic. Note that in the code line sourced, the second argument to
mtx_assert() is MA_OWNED.
On Jan 13, 2011, at 23:05 , Steve Kargl wrote:
On Thu, Jan 13, 2011 at 10:08:30PM -0500, Ryan Stone wrote:
I would suggest using hwpmc for profiling:
# kldload hwpmc
# pmcstat -S unhalted-cycles -O /tmp/samples.out ../penetration
# pmcstat -R /tmp/samples.out -G /tmp/penetration.txt
John:
Thanks, I actually didn¹t see the MCA errors on the screen as the system has
reloaded but noted them in the ddb.txt file last night.
The Motherboard, CPU, Memory and PS were replaced today. I¹ll post back if
this has or not corrected the problem but I suspect you are on target in
that the
On Jan 14, 2011, at 10:26 AM, Nathan Whitehorn wrote:
The final architecture on which we use sysinstall, ia64, is currently
unsupported, because I don't know how to set up booting on those systems --
patches to solve this are very much welcome.
Don't let this stop you. I'll work with you
TB --- 2011-01-15 01:10:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-01-15 01:10:00 - starting HEAD tinderbox run for i386/pc98
TB --- 2011-01-15 01:10:00 - cleaning the object tree
TB --- 2011-01-15 01:10:22 - cvsupping the source tree
TB --- 2011-01-15 01:10:22 -
TB --- 2011-01-15 01:10:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-01-15 01:10:00 - starting HEAD tinderbox run for i386/i386
TB --- 2011-01-15 01:10:00 - cleaning the object tree
TB --- 2011-01-15 01:10:26 - cvsupping the source tree
TB --- 2011-01-15 01:10:26 -
TB --- 2011-01-15 01:10:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2011-01-15 01:10:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2011-01-15 01:10:00 - cleaning the object tree
TB --- 2011-01-15 01:10:26 - cvsupping the source tree
TB --- 2011-01-15 01:10:26 -
On Fri, Jan 14, 2011 at 03:40:46PM -0500, George Neville-Neil wrote:
On Jan 13, 2011, at 23:05 , Steve Kargl wrote:
On Thu, Jan 13, 2011 at 10:08:30PM -0500, Ryan Stone wrote:
I would suggest using hwpmc for profiling:
# kldload hwpmc
# pmcstat -S unhalted-cycles -O
On Fri, Jan 14, 2011 at 10:10 PM, Steve Kargl
s...@troutmask.apl.washington.edu wrote:
On Fri, Jan 14, 2011 at 03:40:46PM -0500, George Neville-Neil wrote:
On Jan 13, 2011, at 23:05 , Steve Kargl wrote:
On Thu, Jan 13, 2011 at 10:08:30PM -0500, Ryan Stone wrote:
I would suggest using hwpmc
On Jan 14, 2011, at 19:31 , Marcel Moolenaar wrote:
On Jan 14, 2011, at 10:26 AM, Nathan Whitehorn wrote:
The final architecture on which we use sysinstall, ia64, is currently
unsupported, because I don't know how to set up booting on those systems --
patches to solve this are very much
18 matches
Mail list logo
