Julian Elischer wrote:
>
> I ported the code to allow gcc to report functions that use too much
> of our 3.4KB kernel stacks.
Very cool!
None of these are dangerous for the stuff I've done so far.
Someone else anticipated the question I was going to ask: thanks
for the patch, too!
-- Terry
T
Mike Smith wrote:
**
Takes self too seriously
>
> [Terry blathers]
Warning that uncivil posting will follow shortly
> > > Surprisingly, setting "vidconsole" in the SRM didn't make
> > > my TGA work in FreeBSD. 8-p.
>
> 'vidconsole' is the x86 loader console
Kazutaka YOKOTA wrote:
> While we are carrying out the reset/initialization sequence, the mouse
> pointer will be frozen on the screen. The keyboard input may not
> respond in a timely fasion because the PS/2 mouse and the AT keyboard
> share the same I/O port. Then, I suspect our user may feel un
Kazutaka YOKOTA wrote:
> Anyway, I am now considering the following experiment.
>
> - We make the psm driver count the number of the "out-of-sync" errors.
> - When the error is detected for the first time, the psm driver will
> throw few data bytes (up to entire packet size) and see if it can
>
In message <[EMAIL PROTECTED]>, Greg Lehey writes:
>On Wednesday, 15 August 2001 at 19:17:47 +0200, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, Ju
>> lian Elischer writes:
>>
>>> the lack of subdirectory support is a pitty.
>>
>> There is support for subdirectories:
>>
>> ls -
Ok, here is another topic for discussion.
>0x4000 is PSM_CONFIG_INITAFTERSUSPEND
>
>Under what circumstances would you _not_ want to call the
>function "reinitialize()" on the unit at resume time, such
>that this flag is not default?
To date, the flags PSM_CONFIG_HOOKRESUME and
PSM_COFIG_INITAFT
On Wed, 15 Aug 2001, Julian Elischer wrote:
>
> I put up a sorted list in order of severity
> http://people.freebsd.org/~julian/stack-hogs
> This one is from LINT and is more inclusive..
Wow, very interesting reading :)
--
Boris Popov
http://rbp.euro.ru
To Unsubscribe: send mail to
> > Too complicated?
>
>It sounds fine to me. I was thinking that if you are truly concerned
>about the amount of time that the disable/enable calls take, the way to
>solve that is a combination of counter and timer. Increment a counter
>when you take the disable/enable path to prevent recursive
I guess so, I started from the code that was on the gcc web page..
did you send me something new?
(I sent you a copy of the final version.. di you miss it?
I missed yours :-)
On Wed, 15 Aug 2001, David O'Brien wrote:
> On Wed, Aug 15, 2001 at 04:00:50PM -0700, Julian Elischer wrote:
> > I port
On Wed, Aug 15, 2001 at 04:00:50PM -0700, Julian Elischer wrote:
> I ported the code to allow gcc to report functions that use too much
> of our 3.4KB kernel stacks.
Actually I thought I did. :-) Is your final patch different from the
one I did and sent you?
To Unsubscribe: send mail to [EMAIL
# uname -a
FreeBSD phuong.nuxi.com 5.0-CURRENT FreeBSD 5.0-CURRENT #12: Sun Jul 15 19:07:45 PDT
2001 [EMAIL PROTECTED]:/files/Current/sys/alpha/compile/DS20 alpha
panic: mutex Giant not owned at ../../../kern/vfs_subr.c:2363
#0 0xfc3d5c80 in dumpsys () at ../../../kern/kern_shutdo
>Does it make sense to have a timeout (or perhaps just timestamps) in the
>driver, so that after some period of inactivity, you "know" that the
>next byte from the moust is the first of a multi-byte message?
>
>louie
I haven't thought about this. Yes, it may be possible. But, when the
mouse is m
>: Too complicated?
>
>I like this idea. It will allow mechanical KVM switches to "work"
>better than they do now (which is to say, not much at all). I also
>have one KVM switch that hits the out-of-sync problem when its power
>fails. Unfortunately, it has a horrible user interface: The power
>
the midway driver.. has the folowing comment.
855: #ifdef NBURST
856: /* be careful. kernel stack is only 8K */
857: u_int8_t buffer[BOUNDARY * 2 + 64 * (NBURSTS +
well, that may have been true on NetBSD where this came from, but not in
FreeBSD.. Su
[snip]
> And in general, can we stop the high incidence of mud-slinging we've
> seen on the lists lately?
Here, here!
Brandon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, 16 Aug 2001, Rex Luo wrote:
>
> May I ask where to get this utility?
> Thanks!
It's beeing added to gcc in -current..
here are my patches: WARNING..CUT_N_PASTE.. will not patch cleanly.
Index: calls.c
===
RCS file: /
I put up a sorted list in order of severity
http://people.freebsd.org/~julian/stack-hogs
This one is from LINT and is more inclusive..
please check if your favourites are there and even if you are not a
committer, send me fixes. If you ARE a committer of course, yuo know what
to do.. :-)
who o
May I ask where to get this utility?
Thanks!
Julian Elischer <[EMAIL PROTECTED]> said:
> I ported the code to allow gcc to report functions that use too much
> of our 3.4KB kernel stacks.
>
> I tried it ou ton a compile of GENERIC.
> it produced some 360 functions that allocate over 100 byte
On Wednesday, 15 August 2001 at 19:17:47 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Ju
> lian Elischer writes:
>
>> the lack of subdirectory support is a pitty.
>
> There is support for subdirectories:
>
> ls -la /dev/fd
What am I supposed to see there? I get three c
On 15-Aug-01 Michael Lucas wrote:
> On Wed, Aug 15, 2001 at 10:21:39AM +0930, Greg Lehey wrote:
>> To help localize this problem, could you please try this same thing on
>> a kernel without devfs? The dump you sent me did not look like a
>> Vinum bug, as I said in my reply.
>
> Sorry, it happen
I ported the code to allow gcc to report functions that use too much
of our 3.4KB kernel stacks.
I tried it ou ton a compile of GENERIC.
it produced some 360 functions that allocate over 100 bytes on the stack.
The list is available at:
http://people.freebsd.org/~julian/stack-hogs
It's quite in
On Wed, Aug 15, 2001 at 10:21:39AM +0930, Greg Lehey wrote:
> To help localize this problem, could you please try this same thing on
> a kernel without devfs? The dump you sent me did not look like a
> Vinum bug, as I said in my reply.
Sorry, it happens on a non-devfs kernel as well. Since it d
Kazutaka YOKOTA writes:
> Anyway, I am now considering the following experiment.
>
> - We make the psm driver count the number of the "out-of-sync" errors.
> - When the error is detected for the first time, the psm driver will
> throw few data bytes (up to entire packet size) and see if it
On 15-Aug-01 Mike Smith wrote:
>>
>> On 15-Aug-01 Mike Smith wrote:
>> >
>> > [Terry blathers]
>> >> > Surprisingly, setting "vidconsole" in the SRM didn't make
>> >> > my TGA work in FreeBSD. 8-p.
>> >
>> > 'vidconsole' is the x86 loader console driver. Under SRM, there are no
>> > console
In message <[EMAIL PROTECTED]>, Ju
lian Elischer writes:
>the lack of subdirectory support is a pitty.
There is support for subdirectories:
ls -la /dev/fd
>it was a primary design goal in the previous devfs and its
>disappearance caught me by surprise. (the support I mean)
The abilit
>
> On 15-Aug-01 Mike Smith wrote:
> >
> > [Terry blathers]
> >> > Surprisingly, setting "vidconsole" in the SRM didn't make
> >> > my TGA work in FreeBSD. 8-p.
> >
> > 'vidconsole' is the x86 loader console driver. Under SRM, there are no
> > console options (because the platform doesn't gi
the lack of subdirectory support is a pitty.
it was a primary design goal in the previous devfs and its
disappearance caught me by surprise. (the support I mean)
On Wed, 15 Aug 2001, Andrew Kenneth Milton wrote:
> +---[ Poul-Henning Kamp ]--
> | In message <[EMAIL PROTECT
One gets the first DMA buffer full, then the process hangs...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 15-Aug-01 Mike Smith wrote:
>
> [Terry blathers]
>> > Surprisingly, setting "vidconsole" in the SRM didn't make
>> > my TGA work in FreeBSD. 8-p.
>
> 'vidconsole' is the x86 loader console driver. Under SRM, there are no
> console options (because the platform doesn't give you any).
Errr
Hi all
I have a big commit planned for telnet(d).
You can see it at http://people.freebsd.org/~markm/patches/diff.cvs.gz
The main aims of the patch are to reduce the number of warnings
telnet(d) emits during compilation, and to properly merge the
differences between the "base" telnet and the cr
Does it make sense to have a timeout (or perhaps just timestamps) in the
driver, so that after some period of inactivity, you "know" that the
next byte from the moust is the first of a multi-byte message?
louie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
In message <[EMAIL PROTECTED]> Kazutaka YOKOTA
writes:
: Anyway, I am now considering the following experiment.
:
: - We make the psm driver count the number of the "out-of-sync" errors.
: - When the error is detected for the first time, the psm driver will
: throw few data bytes (up to entire
On Wed, Aug 15, 2001 at 20:15:21 +1000, Bruce Evans wrote:
> Something like:
>
> #define OFF_T_MAX 0x7FFF /* XXX */
> #define OFF_T_MIN (-0x7FFF - 1) /* XXX */
It seems that this defines often needed in many places. What about
+---[ Poul-Henning Kamp ]--
| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| writes:
| >+---[ Poul-Henning Kamp ]--
| >| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| >| writes:
| >|
| >| >The problem turns up most violently wit
On Wed, Aug 15, 2001 at 10:21:39AM +0930, Greg Lehey wrote:
> On Tuesday, 14 August 2001 at 19:26:09 -0400, Michael Lucas wrote:
> > Before I start generating crash dumps & etc., are there any gotchas
> > with Vinum & -current? I'm using devfs on a SMP system, upgraded 3
> > days ago. I get a pa
In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
writes:
>+---[ Poul-Henning Kamp ]--
>| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
>| writes:
>|
>| >The problem turns up most violently within the XFree86 DRI Module, since
>| >it now uses make_dev, and no
On Wed, 15 Aug 2001, Andrey A. Chernov wrote:
> The patch below adds both cases, i.e. disallow negative seeks for VREG,
> VDIR, VBLK and add off_t overflow checks.
>
> I plan to commit this, please review.
>
> --- vfs_syscalls.c.oldWed Aug 15 04:45:30 2001
> +++ vfs_syscalls.cWed Aug
+---[ Poul-Henning Kamp ]--
| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| writes:
|
| >The problem turns up most violently within the XFree86 DRI Module, since
| >it now uses make_dev, and not mknod as it used to.
| >
| >The DRI Module first attempts to mkdir
In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
writes:
>The problem turns up most violently within the XFree86 DRI Module, since
>it now uses make_dev, and not mknod as it used to.
>
>The DRI Module first attempts to mkdir /dev/dri/, and then for each card
>it supports attempts to use mak
+---[ Poul-Henning Kamp ]--
| In message <[EMAIL PROTECTED]>, Andrew Kenneth Milton
| writes:
| >+---[ Greg Lehey ]--
| >|
| >
| >[snip]
| >
| >| whether it's been fixed. Basically, devfs as supplied in CURRENT had
| >| a 16 character limit on devi
[Terry blathers]
> > Surprisingly, setting "vidconsole" in the SRM didn't make
> > my TGA work in FreeBSD. 8-p.
'vidconsole' is the x86 loader console driver. Under SRM, there are no
console options (because the platform doesn't give you any).
--
... every activity meets with opposition, ev
Ok, I am back.
There are so many issues to be explained and discussed. I will tackle
them one by one
- Flags 0x8000 for psm and "out-of-sync" error
As many people want to make it default, and my initial intent to make
it an option didn't work out well as a hindsight, we had better make
it
Here it is what POSIX says about lseek():
[EINVAL]
The whence argument is not a proper value, or the resulting file offset
would be negative for a regular file, block special file, or directory.
[EOVERFLOW]
The resulting file offset would be a value which cannot be represented
correctly i
On Wed, 15 Aug 2001, Ruslan Ermilov wrote:
> On Wed, Aug 15, 2001 at 12:40:19PM +1000, Bruce Evans wrote:
> > I agree (except the build-tools concept is a hack to work around
> > build-tools binaries not being buildable and installable in the usual
> > way (with 1 binary per Makefile)).
> >
> It
44 matches
Mail list logo
