On Fri, 28 Feb 2003, Kris Kennaway wrote:
On Fri, Feb 28, 2003 at 11:24:53AM -0800, James Satterfield wrote:
First off, I found SCHED_ULE to be very slow. More importantly, the two
times that I rebooted while running it, shutdown failed to sync the
disks. On the second reboot, I had just
It seems Shizuka Kudo wrote:
--- Bruce Cran [EMAIL PROTECTED] wrote:
Just to add to this, when I run the above 'dd' command, I see top reporting 35-40%
interrupt
usage on the drive on the RAID controller, while it's
3-5% for the drive on the VIA controller, and the drive itself is:
It seems Akinori MUSHA wrote:
Hi,
Using the latest CURRENT on my box, the ata driver fails to enable
UDMA for the ATA133 disks connected to an on-board HPT372 controller.
Besides, UDMA is not enabled for the CD/DVD-ROM drive which is capable
of UDMA4 either, but this may be a feature or a
At Sat, 1 Mar 2003 10:34:50 +0100 (CET),
Soeren Schmidt wrote:
Using the latest CURRENT on my box, the ata driver fails to enable
UDMA for the ATA133 disks connected to an on-board HPT372 controller.
Besides, UDMA is not enabled for the CD/DVD-ROM drive which is capable
of UDMA4 either,
I still havn't yet got my wireless lan working after upgrade to 5.0-current
I applied a wi timeout patch of yesterday but the kernel message
is still there (tx failed).
I disabled all firewalling for the moment to have nothing in the way
that might occlude the problem.
The control lights at
On Fri, 28 Feb 2003, Maksim Yevmenkin wrote:
[About creeping bitrot:]
so = soalloc(p != 0);
--
so = soalloc(td != 0);
--
so = soalloc(M_NOWAIT);
[and proposed fixes:]
--
so = soalloc(0);
or --
so = soalloc(1);
I see, however I
On Sat, Mar 01, 2003 at 12:03:12PM +0100, Christoph Kukulies wrote:
I still havn't yet got my wireless lan working after upgrade to 5.0-current
I applied a wi timeout patch of yesterday but the kernel message
is still there (tx failed).
The patch is unrelated to the tx failed message.
On
--- Soeren Schmidt [EMAIL PROTECTED] wrote:
It seems Shizuka Kudo wrote:
I have sysctl -a showing hw.ata.ata_dma: 1, but atacontrol mode showing
PIO4 for the
drives attached to HP370A. Setting them to mode udma6 was just ignored.
Fixed!
-Søren
Søren,
Thanks, my drives are
I'm adding IPF to a set of 5.0 boxen, and I'm sure to have questions.
Anyone who's done this please drop me a note, I'm on list, but in
digest mode, and Saturday is a work-day-from-home.
Has anyone noticed a persistent reset-from-peer problem with 5.0?
I'm behind on reading -CURRENT...
Eric
To
Hi,
At 21:06 28/2/03, M. Warner Losh wrote:
[...] We have some a few embedded systems coming back
from the field soon and I plan on trying some tests on them (they are
amd 386, so might not be good for you). [etc]
IIRC AMD had a mask deal with Intel for the 386, so should be OK.
--
Bob Bishop
In message: [EMAIL PROTECTED]
Marcel Moolenaar [EMAIL PROTECTED] writes:
: status: no carrier
: ssid 1:
:
: Did you do `wicontrol -i wi0 -p 1'?
I've found that the new driver really really really hates the old
wicontrol interface when the commands are also present in the ifconfig
On Thu, Feb 27, 2003 at 05:05:43PM -0500, John Baldwin wrote:
On 27-Feb-2003 Mike Barcroft wrote:
John Baldwin [EMAIL PROTECTED] writes:
Fixed. Apparently people don't compile kernels for 80386's very often.
Maybe LINT should be building I386 instead of more modern processors.
That
On Fri, 28 Feb 2003, Poul-Henning Kamp wrote:
My main concern would be if the chips have the necessary umphf
to actually do a real-world job once they're done running all the
overhead of 5.0-R. The lack of cmpxchg8 makes the locking horribly
expensive.
Actually, the lack of cmpxchg8 only
Bruce Evans wrote:
On Fri, 28 Feb 2003, Maksim Yevmenkin wrote:
sonewconn() calls soalloc(0).
tcp_input() is a critical caller of sonewconn() and it obviously shouldn't
sleep. But sonewconn() is called from process context elsewhere.
sonewconn() has used a no-wait malloc() since at least
Eric Brunner-Williams in Portland Maine wrote:
I'm adding IPF to a set of 5.0 boxen, and I'm sure to have questions.
Anyone who's done this please drop me a note, I'm on list, but in
digest mode, and Saturday is a work-day-from-home.
Has anyone noticed a persistent reset-from-peer problem
Bob Bishop wrote:
At 21:06 28/2/03, M. Warner Losh wrote:
[...] We have some a few embedded systems coming back
from the field soon and I plan on trying some tests on them (they are
amd 386, so might not be good for you). [etc]
IIRC AMD had a mask deal with Intel for the 386, so should be
On Sat, Mar 01, 2003 at 03:18:49AM -0800, Marcel Moolenaar wrote:
On Sat, Mar 01, 2003 at 12:03:12PM +0100, Christoph Kukulies wrote:
I still havn't yet got my wireless lan working after upgrade to 5.0-current
I applied a wi timeout patch of yesterday but the kernel message
is still
Sorry for resending (3rd time), but I've found a small typo in the patch
of sbin/atm/ilmid/ilmid.c
Jens
--- sbin/atm/ilmid/ilmid.c.orig Wed Jan 1 18:48:45 2003
+++ sbin/atm/ilmid/ilmid.c Sat Mar 1 13:29:05 2003
@@ -162,7 +162,7 @@
union {
int ival;
Hi,
I just tried using my FreeBSD laptop to unload pictures off of a 340MB IBM
microdrive (Model: DMDM-10340, P/N: 22L0046) using the IBM PC Card adapter
(P/N: 31L9315). The laptop in question is a stock Dell Latitude C800 with
a 1Ghz P3, 512MB of RAM and a 20GB ATA66 drive.
I got a double page
On Sat, Mar 01, 2003 at 06:08:27AM -0700, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Marcel Moolenaar [EMAIL PROTECTED] writes:
: status: no carrier
: ssid 1:
:
: Did you do `wicontrol -i wi0 -p 1'?
As already said, I did that and the wicontrol output between the
In message: [EMAIL PROTECTED]
Christoph P. Kukulies [EMAIL PROTECTED] writes:
: Warner, I applied the patch and no change.
marcel's patch, or my patch?
: How does one specify the commands in the ifconfig interface?
: This is what I used to invoke from /etc/rc.local:
:
:
On Thu, Feb 27, 2003 at 11:53:02AM +0200, Vallo Kallaste vallo wrote:
The vinum R5 and system as a whole were stable without
softupdates. Only one problem remained after disabling softupdates,
while being online and user I/O going on, rebuilding of failed disk
corrupt the R5 volume
On Fri, Feb 28, 2003 at 05:52:59PM -0800, Terry Lambert wrote:
I have seen this as well, using -O2 -march=athlon-xp.
The generated assembler tried to stuff -129 into a single byte.
What about just trying -march=athlon? The only difference is the SSE
support, which is quite new
On Sat, Mar 01, 2003 at 11:35:37AM -0700, M. Warner Losh wrote:
Not sure whether I group replied, so maybe you will be
receiving two similar sounding answers, Warner.
In message: [EMAIL PROTECTED]
Christoph P. Kukulies [EMAIL PROTECTED] writes:
: Warner, I applied the patch and no
On Sat, Mar 01, 2003 at 08:08:36PM +0100, Christoph P. Kukulies wrote:
On Sat, Mar 01, 2003 at 11:35:37AM -0700, M. Warner Losh wrote:
It works!
Packets started flowing right after I typed in the above line.
and
ifconfig wi0 192.168.254.2 netmask 255.255.255.0 ssid kuku
On Sat, Mar 01, 2003 at 06:08:27AM -0700, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Marcel Moolenaar [EMAIL PROTECTED] writes:
: status: no carrier
: ssid 1:
:
: Did you do `wicontrol -i wi0 -p 1'?
I've found that the new driver really really really hates the old
In message: [EMAIL PROTECTED]
Marcel Moolenaar [EMAIL PROTECTED] writes:
: BTW: Shouldn't we obsolete wicontrol then or strip functionality?
: It appears we have 2 ways in which we can do things now...
I'm planning on doing that soonish. However, I think that hacking wi
to make it
Does anyone know if someone is working on WiFi drivers for cards based
on the TI chipset running at 22Mbps (ie. D-link DWL-650+ pcmcia card)?
Regards,
Suneel.
**
A disclaimer applies to all email sent from
On Sat, Mar 01, 2003 at 12:23:22PM -0700, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Marcel Moolenaar [EMAIL PROTECTED] writes:
: BTW: Shouldn't we obsolete wicontrol then or strip functionality?
: It appears we have 2 ways in which we can do things now...
I'm planning
With my three days old 5.0-current I had a kernel panic this afternoon
while I had wi0 in promiscous mode (FWIW).
Message was:
panic: headlocked should be 0
--
Chris Christoph P. U. Kukulies [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in
Hugo
Having 'device pcm' in the kernel is all you should need for you VT82C686
(kldload'ing sound drivers requires pcm support not be compiled into the
kernel.
The are two portions to the sound h/w you have, the pcm component, ie the
VT82C686, and the AC97 codec that controls the mixer and
Hello,
I encounter a strange problem with an old rs-232 serial pccard on current (just
cvsup'ed).
The card works quite well on 5.0-RELEASE, but it it is detected as a wlan
card on current, and the system attempts to run the wi driver. This calls ther
debugger, and the (continue) command reboot
Juli Mallett wrote:
* De: Jens Rehsack [EMAIL PROTECTED] [ Data: 2003-03-01 ]
[ Subjecte: Re: PATCH: type errors in src-tree ]
Sorry for resending (3rd time), but I've found a small typo in the patch
of sbin/atm/ilmid/ilmid.c
- u_char **bufp;
- Objid *objid;
+
Date: Sat, 1 Mar 2003
With my three days old 5.0-current
panic: headlocked should be 0
Try updating to rev 1.198 of tcp_input.c which was committed on Feb 26,
around 3 days ago.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the
Juli Mallett wrote:
* De: Jens Rehsack [EMAIL PROTECTED] [ Data: 2003-03-01 ]
[ Subjecte: Re: PATCH: type errors in src-tree ]
caddr_t is discouraged, with preference of writing an actual type. caddr_t
is just an obfuscation. I'm unclear what it gains in your context.
Okay, sorry for
On Sat, Mar 01, 2003 at 11:09:03PM +0100, Jens Rehsack wrote:
...
- u_char **bufp;
+ caddr_t *bufp;
...
Of course. Very often in ilmid.c the type caddr_t was used, and nearly
the same count of 'const char *'s was used. I've searched the include
files for caddr_t (core
Barney Wolff wrote:
On Sat, Mar 01, 2003 at 11:09:03PM +0100, Jens Rehsack wrote:
Shouldn't we care about u_char vs char? On some machines it matters,
and on all machines compilers tend to notice and generate warnings.
Yes, usually we should. But I reviewed the code and didn't found a
reason
Barney Wolff wrote:
On Sat, Mar 01, 2003 at 11:09:03PM +0100, Jens Rehsack wrote:
Shouldn't we care about u_char vs char? On some machines it matters,
and on all machines compilers tend to notice and generate warnings.
Just another question: I turned on '-ansi' and got some warning about a
* De: Jens Rehsack [EMAIL PROTECTED] [ Data: 2003-03-01 ]
[ Subjecte: Re: PATCH: type errors in src-tree ]
Barney Wolff wrote:
On Sat, Mar 01, 2003 at 11:09:03PM +0100, Jens Rehsack wrote:
Shouldn't we care about u_char vs char? On some machines it matters,
and on all machines
In message: [EMAIL PROTECTED]
Suneel Jhangiani [EMAIL PROTECTED] writes:
: Does anyone know if someone is working on WiFi drivers for cards based
: on the TI chipset running at 22Mbps (ie. D-link DWL-650+ pcmcia card)?
22Mbps isn't WiFi. It is Ti's own proprietary thing that 802.11g
Juli Mallett wrote:
* De: Jens Rehsack [EMAIL PROTECTED] [ Data: 2003-03-01 ]
[ Subjecte: Re: PATCH: type errors in src-tree ]
Barney Wolff wrote:
On Sat, Mar 01, 2003 at 11:09:03PM +0100, Jens Rehsack wrote:
Shouldn't we care about u_char vs char? On some machines it matters,
and on
Juli Mallett wrote:
ANSI is preferred, but mixing style with functional changes is discouraged.
I get the impression your change to width-specified values has a real
correlation to what things need to use, and thus it might fix brokenness
with systems not ILP32.
Sorry, it's getting late here -
This is an example of what I was pointing out:
On Sun, Mar 02, 2003 at 01:53:33AM +0100, Jens Rehsack wrote:
...
@@ -1444,22 +1420,19 @@
* none- response sent
*
*/
-void
-send_resp ( intf, Hdr, resp )
- int intf;
- Snmp_Header *Hdr;
- u_char
Barney Wolff wrote:
This is an example of what I was pointing out:
On Sun, Mar 02, 2003 at 01:53:33AM +0100, Jens Rehsack wrote:
...
@@ -1444,22 +1420,19 @@
* none- response sent
*
*/
-void
-send_resp ( intf, Hdr, resp )
- int intf;
- Snmp_Header *Hdr;
-
Barney Wolff wrote:
This is an example of what I was pointing out:
On Sun, Mar 02, 2003 at 01:53:33AM +0100, Jens Rehsack wrote:
...
@@ -1444,22 +1420,19 @@
* none- response sent
*
*/
-void
-send_resp ( intf, Hdr, resp )
- int intf;
- Snmp_Header *Hdr;
-
On Sun, Mar 02, 2003 at 02:33:55AM +0100, Jens Rehsack wrote:
...
+ n = write ( ilmi_fd[intf], resp+1, resp[0] );
Here's a case where it matters whether something is u_char or char.
write(2) takes a size_t as its third arg, and extension of a char to
that may not be the same as for
Hello.
Just as the topic says, do you think this patch is good enough, or gets
even close to it? I have tested the patch, and it seems to do it's job
in the right way. Some might call it hackery, but it's better than
nothing I would suppose.
Before:
FreeBSD/SMP: Multiprocessor System
* De: Hiten Pandya [EMAIL PROTECTED] [ Data: 2003-03-01 ]
[ Subjecte: Possible patch for limiting APs at startup ]
Hello.
Just as the topic says, do you think this patch is good enough, or gets
even close to it? I have tested the patch, and it seems to do it's job
in the right way.
Blue Lightning was an i486 core in a i386SX/DX compatible package (usually
SX). AMD's i386DX's predate Blue Lightning by about 5 years.
Adam
- Original Message -
From: Terry Lambert [EMAIL PROTECTED]
To: Bob Bishop [EMAIL PROTECTED]
Cc: M. Warner Losh [EMAIL PROTECTED]; [EMAIL
panic: bwrite: buffer is not busy???
panic messages:
---
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x20
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01b2036
stack pointer = 0x10:0xcd32da90
frame pointer
Hi All,
I am adding some new feature to the kgdb. I am not sure why the libkvm doesn't
implement reading from memory space when checking core dump. Who can give
some comments on this? If it is possible, I will try to implement it.
I found kgdb is not easy to use when checking a core dump. And
51 matches
Mail list logo
