Yes, thank you. I updated just a few minutes ago, works like a charm.
On 6/22/06, Scott Robbins <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 22, 2006 at 08:42:57AM -0600, Scott Long wrote:
> Doug Poland wrote:
> >I am following the handbook's "The Cano
On Friday 23 June 2006 14:39, M. Warner Losh wrote:
> However, unless you have 'nodevice isa' in your kernel config file,
> the conf/DEFAULTS file will pull in the isa bus.
Ahh..
> If the serial port works, then ignore the warning... It is there to
> indicate a possible problem, not necessarily
On Friday 23 June 2006 14:44, M. Warner Losh wrote:
> : I think a better option would be to remove the test in sio.c for the
> : AMD64 case since isa_irq_pending() won't do anything.
>
> I hate #ifdef __amd64__ code. It is evil and should be avoided.
> Maybe the right answer is to have a separate
On Friday 23 June 2006 14:34, M. Warner Losh wrote:
> isa_irq_pending can only really be called on isa bus attachments...
>
> Why don't you have ISA in your kernel. I thought it was still required.
It's not in GENERIC on 6.1.
atpic has isa_irq_pending, however if you don't have atpic in your ker
In message: <[EMAIL PROTECTED]>
"Daniel O'Connor" <[EMAIL PROTECTED]> writes:
: I think a better option would be to remove the test in sio.c for the AMD64
: case since isa_irq_pending() won't do anything.
I hate #ifdef __amd64__ code. It is evil and should be avoided.
Maybe the right
In message: <[EMAIL PROTECTED]>
Pieter de Goeje <[EMAIL PROTECTED]> writes:
: > Hmm actually I just looked through the code.. It appears that this happens
: > because isa_irq_pending() is a noop unless isa is in the kernel, and it
: > isn't in GENERIC. Perhaps those tests in sio.c shoul
In message: <[EMAIL PROTECTED]>
"Daniel O'Connor" <[EMAIL PROTECTED]> writes:
: I have 2 Asus A8V motherboards running FreeBSD 6.0 and 6.1 (amd64) and I see
: the following in dmesg..
:
: sio0: configured irq 3 not in bitmap of probed irqs 0
: sio0: port may not be enabled
: sio0: <16
In message: <[EMAIL PROTECTED]>
Gavin Atkinson <[EMAIL PROTECTED]> writes:
: On Mon, 2006-06-19 at 02:56 +0400, Dmitry Morozovsky wrote:
: > Dear colelagues,
: >
: > playing with puc compatible MOXA card I found that it's rather useless with
: > contemporary DEFAULT kernel:
: >
: >
Are there any known problems with FreeBSD 6.x and Dual PIII motherboards?
My source tree is from May 25th ...
I just noticed something while looking around my server, and there is no
CPU1 running, only CPU0 ... I definitely have SMP enabled in my kernel:
# strings /boot/kernel/kernel | grep
On Fri, 23 Jun 2006, Konstantin Belousov wrote:
For reporting kernel deadlocks, see
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html
The problem (ie. nightmare) is that I don't have access to the console
(remote server), so DDB debugging isn't an
In the last episode (Jun 23), Marc G. Fournier said:
> On Fri, 23 Jun 2006, Konstantin Belousov wrote:
> >What exactly happens ? Are you sure that the _system_ freezes ?
> >Could it be that only your application has some troubles ?
>
> Nothing works ... I can ping the server, and that is about it
On Fri, 23 Jun 2006, Konstantin Belousov wrote:
What exactly happens ? Are you sure that the _system_ freezes ? Could it
be that only your application has some troubles ?
Nothing works ... I can ping the server, and that is about it ... the last
time it happened, I had a vmstat process runnin
On Thu, Jun 22, 2006 at 05:12:22PM -0300, Marc G. Fournier wrote:
>
> 'k, I was thinking / hoping it was just maxpipekva causing me issues, but
> apparently that isn't it ... it just froze up again with only 40 out of
> 60M of allocated space used:
>
> ==
> kern.ipc.
'k, I was thinking / hoping it was just maxpipekva causing me issues, but
apparently that isn't it ... it just froze up again with only 40 out of
60M of allocated space used:
==
kern.ipc.maxpipekva: 67108864 - kern.ipc.pipekva: 39272448
running processes: 1631
On Thursday 22 June 2006 20:53, Pieter de Goeje wrote:
> > The ports are enabled in the BIOS and do seem to work.. mostly. I have
> > had odd problems trying to talk to stuff connected to the on occasion
> > though.
>
> Never had any problems with it. I use it for a serial console at 115200
> baud.
Scot Hetzel wrote:
On 6/20/06, Patrick Bowen <[EMAIL PROTECTED]> wrote:
Pyun YongHyeon wrote:
>On Tue, Jun 20, 2006 at 04:04:52PM -0500, Patrick Bowen wrote:
> > Hello:
> >
> >I have two questions.
> >
> >The first regards support for the Broadcom BCM94318 wireless LAN
> > adapter. Wh
Scot Hetzel wrote:
On 6/20/06, Patrick Bowen <[EMAIL PROTECTED]> wrote:
Pyun YongHyeon wrote:
>On Tue, Jun 20, 2006 at 04:04:52PM -0500, Patrick Bowen wrote:
> > Hello:
> >
> >I have two questions.
> >
> >The first regards support for the Broadcom BCM94318 wireless LAN
> > adapter. Wh
Hi,
Unfortunaltly I get this with the debug kernel.
Does one have to boot with the debug.kernel itself
to get a trace which is usable ?
Sigh. A recompile helped !
(kgdb) where
#0 doadump () at pcpu.h:165
#1 0xc066355e in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc0663
On śro, cze 21, 2006 at 07:43:15 +0100, Robert Watson wrote:
> On Wed, 21 Jun 2006, Martin Blapp wrote:
>
> >I just upgraded from 5.5 (stable btw.) to 6.1 and after 10 hours I got a
> >nice panic. Does this look like some tty problem ?
>
> It looks like a tty or devfs problem.
>
> >This is the
On Thu, 22 Jun 2006, Chuck Swiger wrote:
Marc G. Fournier wrote:
[ ... ]
Figuring that the last time I checked, I was using something like 7000
pipes, @ 16k each, I should be setting it closer to 128M, and that is
assuming no 64k pipes ...
So, is there an 'upper max' that it won't allow me t
On 6/20/06, Patrick Bowen <[EMAIL PROTECTED]> wrote:
Pyun YongHyeon wrote:
>On Tue, Jun 20, 2006 at 04:04:52PM -0500, Patrick Bowen wrote:
> > Hello:
> >
> >I have two questions.
> >
> >The first regards support for the Broadcom BCM94318 wireless LAN
> > adapter. When trying to compile t
On 22 jun 2006, at 18.45, Dan Nelson wrote:
In the last episode (Jun 22), Johan Strm said:
On 22 jun 2006, at 17.42, Dan Nelson wrote:
If it ever happens again, you can drop to the debugger with
Ctrl-Alt-ESC and run "ps" to get a list of running processes. You
might even be able to recover b
In the last episode (Jun 22), Johan Strm said:
> On 22 jun 2006, at 17.42, Dan Nelson wrote:
> > If it ever happens again, you can drop to the debugger with
> > Ctrl-Alt-ESC and run "ps" to get a list of running processes. You
> > might even be able to recover by killing some offending processes
>
Marc G. Fournier wrote:
[ ... ]
Figuring that the last time I checked, I was using something like 7000
pipes, @ 16k each, I should be setting it closer to 128M, and that is
assuming no 64k pipes ...
So, is there an 'upper max' that it won't allow me to set it past?
Read "man tuning" about KV
On 22 jun 2006, at 17.42, Dan Nelson wrote:
If it ever happens again, you can drop to the debugger with
Ctrl-Alt-ESC and run "ps" to get a list of running processes. You
might even be able to recover by killing some offending processes with
"kill 9 ", then continue with "c".
Hm, I
On Thu, 22 Jun 2006, Dan Nelson wrote:
In the last episode (Jun 22), Johan Strm said:
On 22 jun 2006, at 09.57, [LoN]Kamikaze wrote:
Johan Str??m wrote:
Anyway.. I'm using default login.conf, which have unlimited for all
resource limits.. So wtf is this?
Look at
# sysctl kern.maxproc
Oka
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jun 22, 2006 at 08:42:57AM -0600, Scott Long wrote:
> Doug Poland wrote:
> >I am following the handbook's "The Canonical Way to Update Your System"
> >and have sucessfully cvsup'd RELENG_6 and run make buildworld.
> >The problem I'm having is
On Tue, Jun 20, 2006, M.Hirsch wrote:
> As stated in my initial post, I used "BEFORE: rcconf" up to and
> including 6.0.
>
> So what is an "appropriate BEFORE entry" for 6-STABLE?
This might be a crude hack but _should_ (untested) work. What about
wrapping rcorder like this ...
/usr/local/sbin
In the last episode (Jun 22), Marcin Koziej said:
> I use FreeBSD 6.1-STABLE #0: Mon Jun 12 18:00:56 CEST 2006 for a
> desktop (Launch several apps at the start and mostly nothing else,
> except when compiling). I've got 512 MB of ram.
>
> From some time, I've noticed poor swapping performance --
In the last episode (Jun 22), Johan Strm said:
> On 22 jun 2006, at 09.57, [LoN]Kamikaze wrote:
> >Johan Ström wrote:
> >>Anyway.. I'm using default login.conf, which have unlimited for all
> >>resource limits.. So wtf is this?
> >
> >Look at
> >
> ># sysctl kern.maxproc
>
> Okay, 4096 procs... Bu
I've read the comments in /usr/src/sys/kern/sys_pipe.c, but couldn't see
anything in there ... I'm up to 32M (as set through /boot/loader.conf) and
am still hitting the max after a period of time (latest was 7 hours) ...
Figuring that the last time I checked, I was using something like 7000
Doug Poland wrote:
Hello,
I'm in the middle of an attempt to upgrade an i386 box from 5.5-STABLE
to 6.1-STABLE. Just in case it's apropos, the box was recently upgraded
from 5.2.1-RELEASE to 5.5-STABLE.
I am following the handbook's "The Canonical Way to Update Your System"
and have sucessfull
Hello,
I use FreeBSD 6.1-STABLE #0: Mon Jun 12 18:00:56 CEST 2006
for a desktop (Launch several apps at the start and mostly nothing else,
except when compiling). I've got 512 MB of ram.
From some time, I've noticed poor swapping performance -- this can be
very annoying when memory needs to b
Hi,
Yesterday I've installed 6.1. After rebooting, I got the beastie
loader screen. I've typed 8 (reboot) to get into the
raid bios again, but then the server freezed. Does this happen
only to me or is it a common problem ?
The server affected is a IBM 346 X-Series server with 2 CPUS.
Martin
On Thursday 22 June 2006 06:54, Daniel O'Connor wrote:
> I have 2 Asus A8V motherboards running FreeBSD 6.0 and 6.1 (amd64) and I
> see the following in dmesg..
>
> sio0: configured irq 3 not in bitmap of probed irqs 0
> sio0: port may not be enabled
> sio0: <16550A-compatible COM port> port 0x2f8-
Johan Ström wrote:
> Anyway.. I'm using default login.conf, which have unlimited for all
> resource limits.. So wtf is this?
Look at
# sysctl kern.maxproc
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stab
On 22 jun 2006, at 09.57, [LoN]Kamikaze wrote:
Johan Ström wrote:
Anyway.. I'm using default login.conf, which have unlimited for all
resource limits.. So wtf is this?
Look at
# sysctl kern.maxproc
Okay, 4096 procs... But what was those 4k procs...On my newly booted
i got 127... Well I
Hi
Today I woke up and was not able to log in to my system (ssh). Some
stuff worked (DNS for example, this box runs bind), altough the IMAP
server didnt work to well...
Anyway, I checked out local console:
maxproc limit exceeded by uid 0, please see tuning(7) and login.conf(5).
Repeated 23
38 matches
Mail list logo
