Hi all,
I might be completely off here, but since I did a
update/buildkernel/buildworld yesterday evening, NFS seems to act up. I
can mount a remote NFS resource locally and access it, but when I try to
access a subdirectory it seems to hang and never return. I currently
have two zombie mc-process
Hi,
I've now finally managed to test this, a bit later than I anticipated.
It does help the situation quite a lot, but I still have sound problems.
They are much less audible now, as I cannot hear any crackles and pops.
However in music with a steady rythm I notice that every now and then it
must
Matthew D. Fuller wrote:
On Wed, Nov 05, 2003 at 11:28:50AM +0100 I heard the voice of
Eirik Oeverby, and lo! it spake thus:
The second is that mouse messages are actually *lost*, or bogus ones are
being generated. I guess it's the first, making moused or X misinterpret
the messages it
Sheldon Hearn wrote:
On (2003/11/04 15:46), Jeff Roberson wrote:
The thing is, I'm using 4BSD, not ULE, so I wouldn't trouble Jeff to
look for a cause for that specific problem in ULE.
How long have you been seeing this? Are you using a usb mouse? Can you
try with PS/2 if you are?
Since my la
Alex Wilkinson wrote:
On Wed, Nov 05, 2003 at 12:27:04AM +0100, Eirik Oeverby wrote:
Just for those interested:
I do *not* get any messages at all from the kernel (or elsewhere) when
my mouse goes haywire. And it's an absolute truth (just tested back and
forth 8 times) that it
Eirik Oeverby wrote:
Eirik Oeverby wrote:
Just for those interested:
I do *not* get any messages at all from the kernel (or elsewhere) when
my mouse goes haywire. And it's an absolute truth (just tested back
and forth 8 times) that it *only* happens with SCHED_ULE and *only*
with old ver
Eirik Oeverby wrote:
Just for those interested:
I do *not* get any messages at all from the kernel (or elsewhere) when
my mouse goes haywire. And it's an absolute truth (just tested back and
forth 8 times) that it *only* happens with SCHED_ULE and *only* with old
versions (~1.50) and the
SCHED_ULE and some signal/message/interrupt handling causing messages
to get lost along the way. Because that's exactly how it feels...
Greetings,
/Eirik
Morten Johansen wrote:
On Tue, 4 Nov 2003, Sheldon Hearn wrote:
On (2003/11/04 09:29), Eirik Oeverby wrote:
> The problem is two part
Sheldon Hearn wrote:
On (2003/11/04 09:29), Eirik Oeverby wrote:
The problem is two parts: The mouse tends to 'lock up' for brief moments
when the system is under load, in particular during heavy UI operations
or when doing compile jobs and such.
The second part of the problem is relat
Jeff Roberson wrote:
On Mon, 3 Nov 2003, Eirik Oeverby wrote:
Hi,
Just recompiled yesterday, running sched_ule.c 1.75. It seems to have
re-introduced the bogus mouse events I talked about earlier, after a
period of having no problems with it. The change happened between 1.69
and 1.75, and
John Baldwin wrote:
I'm committing the new i386 interrupt and SMP code, so buckle your
seat belts. :) I'll be intentionally breaking the kernel build at
the start and re-enable it with the last commit when I am done.
Is this *only* for SMP systems, or will the interrupt code also affect
UNIprocess
Hi,
Just recompiled yesterday, running sched_ule.c 1.75. It seems to have
re-introduced the bogus mouse events I talked about earlier, after a
period of having no problems with it. The change happened between 1.69
and 1.75, and there's also the occational glitch in keyboard input.
If you need
Hi,
Jeff Roberson wrote:
On Mon, 27 Oct 2003, Jonathan Fosburgh wrote:
On Monday 27 October 2003 12:06 pm, Arjan van Leeuwen wrote:
Hi,
I just cvsupped and built a new kernel that includes sched_ule.c 1.67. I'm
getting a page fault when working in Mozilla Firebird. It happens pretty
soon, afte
Thanks.
I should have known =)
/Eirik
Maxime Henrion wrote:
Eirik Oeverby wrote:
As a side note/question:
Is there any way to figure out which ULE version I'm running in a
precompiled kernel? I just nuked my src tree by accident, and am not
sure if i'm on 1.65 or something older..
I
As a side note/question:
Is there any way to figure out which ULE version I'm running in a
precompiled kernel? I just nuked my src tree by accident, and am not
sure if i'm on 1.65 or something older..
If there is no way, is this perhaps an idea?
Thanks,
/Eirik
Jeff Roberson wrote:
On Fri, 17 Oc
Jeff Roberson wrote:
On Thu, 16 Oct 2003, Eirik Oeverby wrote:
Jeff Roberson wrote:
On Wed, 15 Oct 2003, Eirik Oeverby wrote:
Eirik Oeverby wrote:
Jeff Roberson wrote:
I fixed two bugs that were exposed due to more of the kernel running
outside of Giant. ULE had some issues with
Jeff Roberson wrote:
On Wed, 15 Oct 2003, Eirik Oeverby wrote:
Eirik Oeverby wrote:
Jeff Roberson wrote:
I fixed two bugs that were exposed due to more of the kernel running
outside of Giant. ULE had some issues with priority propagation that
stopped it from working very well.
Things should
Eirik Oeverby wrote:
Jeff Roberson wrote:
I fixed two bugs that were exposed due to more of the kernel running
outside of Giant. ULE had some issues with priority propagation that
stopped it from working very well.
Things should be much improved. Feedback, as always, is welcome. I'd
li
Jeff Roberson wrote:
I fixed two bugs that were exposed due to more of the kernel running
outside of Giant. ULE had some issues with priority propagation that
stopped it from working very well.
Things should be much improved. Feedback, as always, is welcome. I'd
like to look into making this the
Thanks for this update,
I've been trying to make a SCHED_ULE enabled kernel work here for a few
days now, thinking it would be about time to test it again (last time
was ~2 months ago), but ata issues have kept me from booting it
successfully. Now I know for sure I can give it atleast another week
Hi,
Can someone tell me what is needed to play with the new scheduler these
days? I seem to be completely unable to compile my kernel with it
enabled, getting lots of undefined references to sched_*.
Have I missed some critical information?
/Eirik
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To all the english speaking on this list, I'm sorry for this small
internal joke - but when I observe two danes thinking they are the only
ones to understand their language, I need to remind them otherwise ;)
Si for all del ikke noe dritt om meg, for
any other
OS (tested OS/2, BeOS, Linux, winXX).
Anyone? :)
/Eirik
On Wed, 27 Aug 2003 11:03:54 +0200
Eirik Oeverby <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Since I upgraded from 4.8 to 5.1, I've been following the -CURRENT
> branch, doing a new kernel/world roughly
listed
below.
If anyone has a clue, I'd appreciate whatever hints to get rid of these
distortions. Apart from them, audio works fine - no instabilities or
anything.
Best regards,
Eirik Oeverby
[EMAIL PROTECTED] ~$ pciconf -l -v
[EMAIL PROTECTED]:0:0: class=0x06 card=0x chip=0x7
Hi,
Then I shall provide what I possibly can.
When using dhclient to configure my wi-driven lucent card (latest
firmware), it will work for a while (varying number of minutes - up to
30 or so) and then stop working, while spitting out messages like:
wi0: bad alloc 55c != 2a2, cur 0 nxt 0
wi0: de
Hi,
I've just compiled ATAng into my kernel, and I'm currently running it -
but I had to rip out my CD-ROM to make it work. I wasn't able to grab
the exact wording of the error, but it was something along the lines of
a failure to identify ata1-slave - which I suppose is my CD-ROM player.
It then
Hi,
Is this going to cure the cases where using DHCP results in my network
link going dead about ~30 minutes after getting a lease? At that point
it starts spitting out timeout errors and stuff, and i have to
unplug/replug the card and re-start dhclient to get connectivity again..
Thanks for the
"Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes:
> >>
> >>> On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote:
> >>>>
> >>>> Oh and btw.. Get the *latest* firmware onto all your cards. That
> >
Hi,
Agree fully.
I have the same problem on my ThinkPad T21 - as reported on this list
earlier. Running without ACPI is no problem.
Another problem when running with ACPI is that suspend mode doesn't turn
the display off. Pretty annoying, and besides it will never come back
from suspend either :)
Hi,
Are you sure? I believe the Win2k driver is still at the same level as
the XP driver - you probably just need to download a newer one.. Correct
me if I'm wrong. But I have a Sony Vaio thingie here with Win2k, and
I've used that one to upgrade all my cards (Lucent, Orinoco and Avaya
labelled -
Hey,
I have a few Orinoco cards, and they 'work' in both ad-hoc and
infrastructure mode. However with dhclient it gets tricky, because it
will only work the first time dhclient assigns an address to the card.
Whenever it tries to refresh it or whatever, I start getting those
timeout and busy bit e
It would be great if this could be sorted out ASAP. With the patches
floating around and (seemingly) working (not that I have tested any of
them), they add enough extra functionality and flexibility to be very
valuable.. The multi-IP, process injection and the SysV stuff is (from
where I stand) the
Hi,
Can you be a bit more specific as to which other problems it fixes? I
would love to try, because I have had some pretty nasty ACPI problems in
the past, but I only have this one box to test on (my workstation) so I
don't feel like going through the compile/install/fail/restore process
if there
Thanks. I'll be keeping my eyes wide open for this one.
/Eirik
On Mon, 30 Jun 2003 15:30:06 -0500
"Alan L. Cox" <[EMAIL PROTECTED]> wrote:
> Peter Holm wrote:
> >
> > On Mon, Jun 30, 2003 at 03:26:13PM +0200, Eirik Oeverby wrote:
> > > Hi,
k it up. Perhaps creating/using the
> filesystem snapshots was triggering the lockup.
>
> -jre
>
> On Mon, Jun 30, 2003 at 03:42:58PM +0200, Eirik Oeverby wrote:
> > Hi,
> >
> > Kernel from 27.06 has same behaviour. I would prefer not to have to
> > in
t 03:26:13PM +0200, Eirik Oeverby wrote:
> > Hi,
> >
> > Good to see I'm not the only one.
> > I'm currently going back to a kernel dated 2003.06.27.12.00.00, and
> > I'll test again with that one.
Hi,
Good to see I'm not the only one.
I'm currently going back to a kernel dated 2003.06.27.12.00.00, and I'll test
again with that one.
/Eirik
On Mon, 30 Jun 2003, Peter Holm wrote:
> On Mon, Jun 30, 2003 at 01:42:15PM +0200, Eirik Oeverby wrote:
> > Hi folks,
>
Hi,
Reinstalling what? VMWare or FreeBSD?
/Eirik
On Mon, 30 Jun 2003, Lutz Bichler wrote:
> I got the same problem/message and "solved" it by reinstalling ;-)
>
> Lutz
>
> --
> Lutz Bichler
> Institute for Software Technology, Department of Computer Science
> Univ. of the Fed. Armed Forces Muni
Hi,
As of yesterday (I think), VMWare 3.2.1 is no longer working on my
5-CURRENT box. When I try to start it, I get
=
[EMAIL PROTECTED] ~$ vmware
Setting TMPDIR=/var/tmp.
VMware Workstation Err
VMware Workstation Error:
Version mismatch with vmmon module: expecting
Hi folks,
I am having some very weird problems on my laptop, which I at first
thought were due to a failing drive. However after a lot of testing and
trial and error I've concluded that it must be a software problem - I'm
smelling filesystem issues or something.
Whenever I transfer large files to
Hi,
> My suspicion is that there are problems with current (as well with
> 5.1 and probably 5.0) with power management that will result in
> overheating, which will then look like a hardware problem.
YES!!! Finally someone seeing something that could explain my problems!!
My machine, after insta
"1"
. Does this make a difference?)
/Eirik
On Mon, 23 Jun 2003 22:40:40 +0200
Eirik Oeverby <[EMAIL PROTECTED]> wrote:
> Hi again,
>
> No workie. No difference in behaviour whatsoever.
> Sorry :(
>
> /Eirik
>
> On Mon, 23 Jun 2003 13:43:14 -0400
> Je
Hi again,
No workie. No difference in behaviour whatsoever.
Sorry :(
/Eirik
On Mon, 23 Jun 2003 13:43:14 -0400
Jesse Guardiani <[EMAIL PROTECTED]> wrote:
> Eirik Oeverby wrote:
>
> > On Mon, 23 Jun 2003 10:53:32 -0400
> > Jesse Guardiani <[EMAIL PROTECTED]> wr
Hi,
this is exactly the problem I have with my wi-driven card aswell. I have
a pretty standard Lucent card (Orinoco Silver, 64bit), PCMCIA, in my
ThinkPad T21 (see another thread specifically about that machine and its
issues with 5.1). It will work for a while, then start spitting out
error messa
On Mon, 23 Jun 2003 10:53:32 -0400
Jesse Guardiani <[EMAIL PROTECTED]> wrote:
> > And with ACPI disabled, the machine refuses totally to
> > boot, it hangs at 'Mounting root from ...'. If I undock the machine,
> > I can boot with and without ACPI, with the latter option being the
> > only usable (
Hi,
> > doesn't work for several models.. Including Inspiron 7500.
> > WHo knows enough about this to be able to look at debug info
> > I have?
>
> John Baldwin has posted a patch which worked for me on my Thinkpad
> 600X with the same "ACPI-0340" error.
I tried this patch, and while it does get
Hi,
I'm seeing similiar things on my setup - both the ACPI Global Lock
messages and the wi0 issues. In fact, the wi driver seems to be
incredibly unstable - Every half hour or so I need to remove and
re-insert the card to regain network connectivity (and ofcourse killall
dhclient ; ifconfig wi0 ..
Hi,
Your language is not the problem, I think everyone here understands what
you're saying, just not what you mean.
I assume you want to give people e-mail accounts and nothing more. No
SSH, no FTP, nothing. In that case, creating a full-blown system account
is not only a waste of resources, it's
Stijn Hoop wrote:
> On Thu, Jun 19, 2003 at 09:33:41AM +0200, Eirik Oeverby wrote:
>
>>- When booted with ACPI enabled (docked), the machine will at some point
>>simply power itself off. I have seen people complaining about similiar
>>machines powering themselves *on* a
Stijn Hoop wrote:
On Thu, Jun 19, 2003 at 09:33:41AM +0200, Eirik Oeverby wrote:
- When booted with ACPI enabled (docked), the machine will at some point
simply power itself off. I have seen people complaining about similiar
machines powering themselves *on* after a power-off, but in my case
cked.
If anyone wants to look more into this, I'll be happy to provide
whatever information is necessary. Please let me know. The system is
running at the latest firmware level. There are no 'firmwares' for the
docking station, so there is nothing I can do there.
/Eirik Oev
51 matches
Mail list logo