Hi all,
I have posted this email for [EMAIL PROTECTED] but I didn't got any answer.
I am running FreeBSD 3.3 Release on one laptop Toshiba and as XServer the
Accelerated X 5.0.2. I am curious about one fact. Everytime when I exit
from XServer I 've got:
> pid 8971 (Xaccel): trap 12 with interr
On Mon, 13 Dec 1999, Alfred Perlstein wrote:
>
> On Sun, 12 Dec 1999, Julian Elischer wrote:
>
> > On Mon, 13 Dec 1999, Chris Costello wrote:
> >
> > > On Mon, Dec 13, 1999, Ilia Chipitsine wrote:
> > > > Is it called once an year or 50 times a second ?
> > > > Is there a way how can I d
It seems Karl Denninger wrote:
> Hi folks,
>
> Well, I'm in for it now ;-)
>
> I'm going to have to start supporting ATAPI tape drives on FreeBSD for some
> business associates - they're too cheap to go SCSI.
>
> Some of these (if not all) require formatting, right? This leads to the
> obvious
On Sun, 12 Dec 1999, Julian Elischer wrote:
> On Mon, 13 Dec 1999, Chris Costello wrote:
>
> > On Mon, Dec 13, 1999, Ilia Chipitsine wrote:
> > > Is it called once an year or 50 times a second ?
> > > Is there a way how can I determine it by myself ?
> >
> >Add a statement like
> >
>
You can compile the kernel with -p -g and use the profiling.
On Mon, 13 Dec 1999, Chris Costello wrote:
> On Mon, Dec 13, 1999, Ilia Chipitsine wrote:
> > Is it called once an year or 50 times a second ?
> > Is there a way how can I determine it by myself ?
>
>Add a statement like
>
It seems like using gprof would be a little bit more useful than
potentially having something print to the screen 50k times. I guess printf
would be fine if you only care if something is called a lot or not at all.
-Kip
On Mon, 13 Dec 199
On Mon, Dec 13, 1999, Ilia Chipitsine wrote:
> Is it called once an year or 50 times a second ?
> Is there a way how can I determine it by myself ?
Add a statement like
printf("somefunc() being called!\n");
to the top of the function you want to 'measure'.
--
|Chris Costello
-BEGIN PGP SIGNED MESSAGE-
Dear hackers,
How can I find how often is particular routine (say wdintr()) called.
Is it called once an year or 50 times a second ?
Is there a way how can I determine it by myself ?
Regards, (îÁÉÌÕÞÛÉÅ ÐÏÖÅÌÁÎÉÑ)
Ilia Chipitsine (éÌØÑ ûÉÐÉÃÉÎ)
-BE
Hi, in PR kern/15452 I have sent in patches to make getfh always be in
the system call table. Details are also included in the PR. Any
thoughts/comments/flames?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Attention, all FreeBSD, OpenBSD and NetBSD developers..
This is a chance we cannot ignore.. Please form up a development team
with a central tram leader and get signed up for this offer. The
Documentation personnel should sign up for the Contributors link to
add BSD's voice in setting the guide
>Submitter-Id: current-users
>Originator: Frank Mayhar
>Organization: Subversive Atheists -R- Us
>Confidential: no
>Synopsis: The name of the tagfile is left in the path.
>Severity: serious
>Priority: high
>Category: bin
>Release:FreeBSD 3.4-RC i386
>Clas
From: Wilko Bulte [mailto:[EMAIL PROTECTED]]
>Charles Randall wrote:
>> ... It also notes that
>> this is, "Derived from Issue 1 of the SVID."
>
>SVID == System V Interface Definition.
Interesting, my Solaris 2.6 box defines timezone as the global variable (in
accordance with the Single Unix Spec
> > > I thought rootdev was fixed a long time back. If it's not, please tell
> > > me and I'll fix it again. 8)
> >
> > Alright I finally got around testing this with a later kern.flp
> > (3.3-R actually), and it still didn't work. ...
>
> Well i played with this once more yesterday and now
Julian Elischer wrote:
>
>
> On Sun, 12 Dec 1999, Gergely EGERVARY wrote:
>
> > > what kind of disk to you have? and the chipset? (this may seem irrelevant
> > > but misconfigured DMA devices can block the cpu for long enough to cause
> > > this sort of thing in some cases). ALSO check systat -
On Sun, Dec 12, 1999 at 12:40:06PM -0700, Charles Randall wrote:
> On my FreeBSD 3.3R system, /usr/include/time.h includes a prototype for the
> timezone() function. The timezone(3) manual page indicates that this
> function is for compatibility purposes only and notes that the timezone()
> functi
On Sun, 12 Dec 1999, Gergely EGERVARY wrote:
> > what kind of disk to you have? and the chipset? (this may seem irrelevant
> > but misconfigured DMA devices can block the cpu for long enough to cause
> > this sort of thing in some cases). ALSO check systat -vmstat while this
> > is happenning a
Karl Denninger wrote:
>
> Can I ask why the makefiles for the world don't build in this order?
>
> 1. Build the "basic" GNU kit necessary to compile things.
> 2. Build the LIBRARIES necessary to LINK things.
> 3. Rebuild the gnu kid using (2); you now have a self-consistent
>
On Mon, Dec 13, 1999 at 05:31:17AM +0800, Peter Wemm wrote:
> Karl Denninger wrote:
> > Hi folks,
> >
> > Just something to keep in mind
> >
> > I am trying to update from a Juneish -CURRENT to a current -CURRENT.
> >
> > I've run into two instances (the latest being the use of "colldef" in
Karl Denninger wrote:
> Hi folks,
>
> Just something to keep in mind
>
> I am trying to update from a Juneish -CURRENT to a current -CURRENT.
>
> I've run into two instances (the latest being the use of "colldef" in
> /usr/src/share/colldef) where older binaries are INCOMPATIBLE with the ne
Hi folks,
Just something to keep in mind
I am trying to update from a Juneish -CURRENT to a current -CURRENT.
I've run into two instances (the latest being the use of "colldef" in
/usr/src/share/colldef) where older binaries are INCOMPATIBLE with the newer
files they are processing, AND the
> what kind of disk to you have? and the chipset? (this may seem irrelevant
> but misconfigured DMA devices can block the cpu for long enough to cause
> this sort of thing in some cases). ALSO check systat -vmstat while this
> is happenning and check that you don't have a source of spurious
> inte
what kind of disk to you have? and the chipset? (this may seem irrelevant
but misconfigured DMA devices can block the cpu for long enough to cause
this sort of thing in some cases). ALSO check systat -vmstat while this is
happenning and check that you don't have a source of spurious interrupts.
J
Alexander Prohorenko wrote,
> Hello,
>
> I've got some problem and I need your help to solve it.
>
> uname -mrs
> FreeBSD 3.3-STABLE i386
>
> dmesg output:
>
> wdc1: unit 1 (atapi): , removable, accel, iordy
>
> I've added such strings to kernel configuration file:
>
> options ATAPI
> device
Hi folks,
Well, I'm in for it now ;-)
I'm going to have to start supporting ATAPI tape drives on FreeBSD for some
business associates - they're too cheap to go SCSI.
Some of these (if not all) require formatting, right? This leads to the
obvious question:
How do you format a tape for
It seems Alexander Prohorenko wrote:
> Hello,
>
> I've got some problem and I need your help to solve it.
>
> uname -mrs
> FreeBSD 3.3-STABLE i386
>
> dmesg output:
>
> wdc1: unit 1 (atapi): , removable, accel, iordy
Hmm, I've gotten a failure report on one of these before, I'm afraid
we dont
hy,
i still can't get rid of silo overflows :(
3.3-STABLE, a simple pentium2 system w/ external 33.6 rockwell modem
attached to sio0. i see nothing special. and the overflows just still come
:(
what should i check/ look after?
--mauzi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "un
On my FreeBSD 3.3R system, /usr/include/time.h includes a prototype for the
timezone() function. The timezone(3) manual page indicates that this
function is for compatibility purposes only and notes that the timezone()
function first appeared in AT&T Unix V7.
Version 2 of the Single Unix Specific
Hello,
I've got some problem and I need your help to solve it.
uname -mrs
FreeBSD 3.3-STABLE i386
dmesg output:
wdc1: unit 1 (atapi): , removable, accel, iordy
I've added such strings to kernel configuration file:
options ATAPI
device wst0
Of course, I did:
cd /dev
./MAKEDEV wst0
ls -al /
(Cc'd to -hackers because, well, it contains hacks...)
On Thu, Nov 11, 1999 at 10:47:30PM +0100, nox wrote:
> On Sun, Nov 07, 1999 at 11:57:26AM -0800, Mike Smith wrote:
> > > > Rootdev ought to work, actually. But if you get it wrong, the loader
> > > > will fall back to using currdev.
> > >
> Can anyone interpret this for me:
>
> HARDWARE FAILURE asc:0,4
>
> What does it mean?
>
> It this just the numeric code for ``Buy another tape drive''?
> :-)
Yes.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
30 matches
Mail list logo
