On Fri, Oct 03, 2003 at 11:36:29PM +0200, Bernd Walter wrote:
> > > The modem coild also be something proprietary for which there is no
> > > driver available.
> > >
> > > > When I run getty (or mgetty) on that port or when I do a cu -l /dev/cuaa0
> > > > the system freezes.
> > >
> > > Why do yo
On Sat, Oct 04, 2003 at 10:25:48AM +0200, Christoph P. Kukulies wrote:
> On Fri, Oct 03, 2003 at 11:36:29PM +0200, Bernd Walter wrote:
> > You can't expect anything reliable from a device which is broken.
> > The kernel already warned you that something seems to be questionable.
> > In the same way
On Fri, Oct 03, 2003 at 05:04:22PM -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Bernd Walter <[EMAIL PROTECTED]> writes:
> : You need a different driver for your PCI one - e.g. puc.
>
> actually, puc still uses sio/uart. puc just manages the bus
> resources.
So pu
Hello Andrei,
I'm now having the same problem as you deed with my ISA sound card
(CMI8330). It does not work.
Already I've recompiled the kernel with the following lines added to the
kernel configuration file:
device pcm
device sbc
as stated on the freeBSD.org site.
If you solved your pr
On Mon, 29 Sep 2003, Dan Langille wrote:
>
> All our testing on this patch has been successful. I'm going to do a
> few more tests on different hardware under 4.8-stable.
>
> What's the next step? Commit it? Get others to test with it first?
It's already in -current. You'll have to wait f
I need some startup help in moving my new systems. Sure would appreciate
it if I could get a pointer here on a couple of matters. My new
physical location has really improved things, but my mail isn't
working yet, right, and my keyboard is also going wrong.
My mail has to come first, here the se
On 4 Oct 2003 at 10:17, Daniel Eischen wrote:
> On Mon, 29 Sep 2003, Dan Langille wrote:
> >
> > All our testing on this patch has been successful. I'm going to do a
> > few more tests on different hardware under 4.8-stable.
> >
> > What's the next step? Commit it? Get others to test with it
Hi
I installed FreeBSD 4.9RC1 on P4 3GHz with hyperthreading and I see
drastic slowdown when kernel with hyperthreading is booted. For example
program compilation took this time:
hyperthreading kernel, make -j 1 --- 1:09
hyperthreading kernel, make -j 2 --- 0:42
singlethreading kernel, make -j
On Sat, 4 Oct 2003, Brian Fundakowski Feldman wrote:
> I keep getting these panics on my SMP box (no backtrace or DDB or crash
> dump of course, because panic() == hang to FreeBSD these days): panic:
> receive: m == 0 so->so_rcv.sb_cc == 52 From what I can tell, all sorts
> of socket-related cal
On Friday 03 October 2003 10:38 pm, Brian Fundakowski Feldman wrote:
> I keep getting these panics on my SMP box (no backtrace or DDB or crash
> dump of course, because panic() == hang to FreeBSD these days):
> panic: receive: m == 0 so->so_rcv.sb_cc == 52
> From what I can tell, all sorts of socke
On Sat, Oct 04, 2003 at 04:39:03PM +0200, Mikulas Patocka wrote:
> Hi
>
> I installed FreeBSD 4.9RC1 on P4 3GHz with hyperthreading and I see
> drastic slowdown when kernel with hyperthreading is booted. For example
> program compilation took this time:
>
> hyperthreading kernel, make -j 1 --- 1
Kris Kennaway wrote:
On Sat, Oct 04, 2003 at 04:39:03PM +0200, Mikulas Patocka wrote:
I installed FreeBSD 4.9RC1 on P4 3GHz with hyperthreading and I see
drastic slowdown when kernel with hyperthreading is booted. For example
program compilation took this time:
hyperthreading kernel, make -j 1 ---
On Sat, Oct 04, 2003 at 03:20:03PM -0400, Richard Coleman wrote:
> Kris Kennaway wrote:
> >On Sat, Oct 04, 2003 at 04:39:03PM +0200, Mikulas Patocka wrote:
> >>I installed FreeBSD 4.9RC1 on P4 3GHz with hyperthreading and I see
> >>drastic slowdown when kernel with hyperthreading is booted. For exa
Kris Kennaway wrote:
On Sat, Oct 04, 2003 at 03:20:03PM -0400, Richard Coleman wrote:
Kris Kennaway wrote:
On Sat, Oct 04, 2003 at 04:39:03PM +0200, Mikulas Patocka wrote:
I installed FreeBSD 4.9RC1 on P4 3GHz with hyperthreading and I see
drastic slowdown when kernel with hyperthreading is boot
In message <[EMAIL PROTECTED]>, Kris Kennaway writes:
>Yes, that's because (as discussed in the archives) the kernel treats
>it like an extra, completely decoupled physical CPU and schedules
>processes on it without further consideration. This is presumably the
>cause of the slowdown, because it's
Sam Leffler <[EMAIL PROTECTED]> wrote:
> On Friday 03 October 2003 10:38 pm, Brian Fundakowski Feldman wrote:
> > I keep getting these panics on my SMP box (no backtrace or DDB or crash
> > dump of course, because panic() == hang to FreeBSD these days):
> > panic: receive: m == 0 so->so_rcv.sb_cc =
I'm considering options for a new project, and I think I've discovered
what I think is the best idea, but I don't think current software
supports the config. I'd like to get some confirmation, and comments on
if it would be hard to implement.
Consider:
ISP #1---\
\
On Saturday 04 October 2003 11:39 am, Sam Leffler wrote:
> On Friday 03 October 2003 10:38 pm, Brian Fundakowski Feldman wrote:
> > I keep getting these panics on my SMP box (no backtrace or DDB or
> > crash dump of course, because panic() == hang to FreeBSD these days):
> > panic: receive: m == 0
On Sat, Oct 04, 2003 at 05:54:45PM -0400, Richard Coleman wrote:
> hyperthreading kernel, make -j 1 --- 1:09
> hyperthreading kernel, make -j 2 --- 0:42
> singlethreading kernel, make -j 1 --- 0:45
> singlethreading kernel, make -j 2 --- 0:41
[snip]
> >Yes, that's because (as di
Richard Coleman wrote:
Kris Kennaway wrote:
On Sat, Oct 04, 2003 at 03:20:03PM -0400, Richard Coleman wrote:
Kris Kennaway wrote:
On Sat, Oct 04, 2003 at 04:39:03PM +0200, Mikulas Patocka wrote:
I installed FreeBSD 4.9RC1 on P4 3GHz with hyperthreading and I see
drastic slowdown when kernel wit
> In message <[EMAIL PROTECTED]>, Kris Kennaway writes:
> >Yes, that's because (as discussed in the archives) the kernel treats
> >it like an extra, completely decoupled physical CPU and schedules
> >processes on it without further consideration. This is presumably the
> >cause of the slowdown, be
21 matches
Mail list logo
