It seem this is relevant.
Here is the output of "python test_select.py":
Traceback (innermost last):
File "test_select.py", line 63, in ?
test()
File "test_select.py", line 47, in test
rfd, wfd, xfd = select.select([p], [], [], tout)
select.error: (4, 'Interrupted system call')
--
On Tue, Dec 21, 1999 at 01:23:05PM -0800, Matthew Dillon wrote:
> I just rebooted both machines and it didn't fix the problem. I did a
> packet trace on both boxes and there does indeed appear to be packet loss.
Sorry if this is stating the obvious, but I've seen more than one
clueful pe
The new `sym' (Symbios) driver has been turned on in GENERIC. There is a
subset of NCR chipsets which both `sym' and the `ncr' driver can own.
For those controllers the `sym' driver will win out. This behavior may
be changed by using the "SYM_SETUP_LP_PROBE_MAP" kernel config option.
It is desc
On Tue, 21 Dec 1999, Soren Schmidt wrote:
> It probably because I relaxed the requirements for doing WDMA on disks
> that doesn't bother to tell whihc verson of the ATA spec they conform to.
> I think your case is the more seldom one, but I'm this close to
> blacklisting all WD/Maxtor drives, tha
On Tue, 21 Dec 1999, Andrey A. Chernov wrote:
> With latest ppp I hear no phone numbers dial sounds at the stage:
> Phase: Phone: N
> ppp does _nothing_ until timeout occurse, then redial happens
> with the same unsuccessful result.
I'm seeing the exact same thing. It appears that the ph
With latest ppp I hear no phone numbers dial sounds at the stage:
Phase: Phone: N
ppp does _nothing_ until timeout occurse, then redial happens
with the same unsuccessful result.
--
Andrey A. Chernov
http://nagual.pp.ru/~ache/
MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y
> Hi,
>
>I tried to install a SNAP which I built early this morning
> and ran into some trouble (4.0-19991220-SNAP).
I accepted some changes to libdisk which, in retrospect,
were too draconian. I'll back 'em out.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe f
>
> I can't seem to boot from wd1s3a. When I run the loader, and set
> currdev=disk2s3a, it won't ls, and when I try to lsdev, it says there
> is a bad partition table on wd1.
That's pretty categoric; if the loader doesn't like your partition table,
you're not going to have much luck.
> I fo
On Tue, Dec 21, 1999 at 11:22:12PM +0100, Thierry Herbelot wrote:
> Let's start a thread on the BP6 ? (the release of the board was
> carefully synchronized with stable SMP releases of FreeBSD : kudos to
> the FreeBSD release engineering team ;-))
I second that! Running -current since October and
On Tuesday, 21 December 1999 at 10:07:28 +0100, Wilko Bulte wrote:
> On Mon, Dec 20, 1999 at 05:08:27PM -0800, Matthew Dillon wrote:
>>> It's possible you might be on to something. I've been running iostat
>>> at 1 second intervals, and during the last hang I saw:
>>>
>>> ttyad2
Mike Smith wrote:
>
> Hmm. The "right" answer would appear to be in a 'loader.rc.local', but
> that's obviously not implemented at this point. The loader.rc file isn't
> typically overwritten after installation, so either inserting it there or
> sourcing another file at that point would be the
John Polstra wrote:
>
> I'm trying to figure out how all these loader scripts fit together,
> and I have some questions. First, my understanding is that the
> scripts are included like this (indentation signifies nesting):
>
> /boot/loader.rc
> /boot/loader.4th
> /boot/support
Let's start a thread on the BP6 ? (the release of the board was
carefully synchronized with stable SMP releases of FreeBSD : kudos to
the FreeBSD release engineering team ;-))
I've also got one of these babies (dual 460 @ 2.1V) and I'm wondering if
I should buy a new PSU (300W, instead of the pre
On Dec 12, 1999 at 04:00:00PM -0500, Garrett Wollman wrote:
> <<[EMAIL PROTECTED]> said:
>
> > I have NOT tested this fix yet, so I don't know if it works, but I
> > believe the problem is that on high speed networks the milliscond round
> > trip delay is short enough that you can get
It seems Matthew Dillon wrote:
>
> The thread 'vm_page_remove panic' that Tamiji Homma initiated may be
> related. She is getting a panic in the buffer cache subsystem while
> using the new ATA driver with softupdates + NFS exported filesystems.
>
> I do not know if it is relat
It seems Peter Wemm wrote:
>
> Same here, but with a toshiba laptop disk. I have to comment out a version
> test in ata-disk.c to get it to work.
I've just a few hours ago committed a change that does this...
>
> --- ata-disk.c 1999/12/18 20:06:30 1.46
> +++ ata-disk.c 1999/12/21 21:48:2
:> it broke again as I recompiled my system yesterday (This was the first
:> time after it had been fixed, so I don't know when exactly it broke).
:>
:> Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
:>Western Digital Caviar (2.5 GB), DMA-33.
:> Mainboard: Asus P5A-B Super7
:
Theo van Klaveren wrote:
>
> When installing the 08-dec-1999 snapshot (before ATA went in GENERIC),
> a recompile from the kernel with the ATA driver instead of the WD
> driver resulted in an unbootable system because of the following
> error (approx.):
>
> mounting root /dev/ad0s1a
> ata-mast
:>
:>Hmmm. I thought we agreed that 200 msec was the minimum reasonable
:>RTO. That code doesn't seem to have made it in.
:
:I assume you mean 20 msec (= 2 tick @ 100 Hz ) ? 200 msec is enough
:to get halfway around the globe...
:
:--
:Poul-Henning Kamp FreeBSD coreteam member
I
< said:
>> Hmmm. I thought we agreed that 200 msec was the minimum reasonable
>> RTO. That code doesn't seem to have made it in.
> I assume you mean 20 msec (= 2 tick @ 100 Hz ) ? 200 msec is enough
> to get halfway around the globe...
No, I mean 200 msec. If you make the RTO be any shorter
In message <[EMAIL PROTECTED]>, Garrett Wollman write
s:
><<[EMAIL PROTECTED]> said:
>
>> I have NOT tested this fix yet, so I don't know if it works, but I
>> believe the problem is that on high speed networks the milliscond round
>> trip delay is short enough that you can get 1-tick
Try turning off UDMA operation on your IDE disks. It should be in the
kernel configuration somewhere, but the IDE driver has changed so often
I have no idea which one you are using.
-Matt
Matthew Dillon
< said:
> I have NOT tested this fix yet, so I don't know if it works, but I
> believe the problem is that on high speed networks the milliscond round
> trip delay is short enough that you can get 1-tick timeouts.
Hmmm. I thought we agreed that 200 msec was the minimum reasonable
RT
On 21-Dec-99 John W. DeBoskey said:
|
|Before I start debugging the boot floppy (actually I use the
| 2.88 image burned onto a CD) code, has anyone else run into this
| yet, and/or is a fix being looked at?
|
Yes, see my message "error with install" from yesterday. It broke s
> I'm trying to figure out how all these loader scripts fit together,
> and I have some questions. First, my understanding is that the
> scripts are included like this (indentation signifies nesting):
>
> /boot/loader.rc
> /boot/loader.4th
> /boot/support.4th
> ["start" com
I think this may be due to the timing changes. While typing over a
TCP connection, running a remote X client (such as netscape), and so
forth I sometimes see momentary 1/10 second hangs, even on a clean,
empty network.
For a while I thought it was packet loss, but then I real
:
:On 1999-Dec-21 12:08:27 +1100, Matthew Dillon <[EMAIL PROTECTED]> wrote:
:>Tape drives may:
:>* Not support disconnection ...
:>* Implement a crappy SCSI command stack ...
:>* Not properly terminate the SCSI bus ...
:>* Introduce too much noise onto the SCSI bus due to bad
Hi,
I tried to install a SNAP which I built early this morning
and ran into some trouble (4.0-19991220-SNAP).
After running through sysinstall and configuring everything,
the following message pops up:
Unable to make device node for /dev/ad0s1b in /dev!
The creation of filesystems will be
Today Oliver Fromme wrote:
> The comment in LINT about AUTO_EOI_2 sounds pretty suspicous,
> so I never even tried it: "it works for some clones and some
> integrated versions." That sounds to me like "it works on a
> very limited set of hardware (and if you're lucky)."
I've only got one out o
On Tue, Dec 21, 1999 at 09:37:14AM -0800, John Polstra wrote:
> I'm trying to figure out how all these loader scripts fit together,
> and I have some questions. First, my understanding is that the
...
> 4. Shouldn't these scripts installed on the Alpha too? Currently,
> none of them are.
FICL (
On Tue, 21 Dec 1999 17:13:20 +0100, D. Rock wrote:
>Oliver Fromme schrieb:
>> Doug White wrote in list.freebsd-current:
>> > On Tue, 21 Dec 1999, Soren Schmidt wrote:
>> > > It seems Dieter Rothacker wrote:
>> > > > The solution for me was to recompile the kernel without AUTO_EOI1 and
>> > >
On Tue, 21 Dec 1999, Edwin Culp wrote:
> My ESS1869 is now repeating the very end of the sound file being played
> six or seven times. It is as if the last buffer is being written and
> rewritten to the device at the end without finding the EOF. These laptops
> are current as of 9 am PST today.
On Tue, 21 Dec 1999, John Polstra wrote:
> I'm trying to figure out how all these loader scripts fit together,
> and I have some questions. First, my understanding is that the
> scripts are included like this (indentation signifies nesting):
>
> /boot/loader.rc
> /boot/loader.4th
>
I'm trying to figure out how all these loader scripts fit together,
and I have some questions. First, my understanding is that the
scripts are included like this (indentation signifies nesting):
/boot/loader.rc
/boot/loader.4th
/boot/support.4th
["start" command executes]
Oliver Fromme schrieb:
>
> Doug White wrote in list.freebsd-current:
> > On Tue, 21 Dec 1999, Soren Schmidt wrote:
> > > It seems Dieter Rothacker wrote:
> > > > The solution for me was to recompile the kernel without AUTO_EOI1 and
> > > > AUTO_EOI2.
> > >
> > > Those options newer worked (
It seems Doug White wrote:
> >
> > It probably because I relaxed the requirements for doing WDMA on disks
> > that doesn't bother to tell whihc verson of the ATA spec they conform to.
> > I think your case is the more seldom one, but I'm this close to
> > blacklisting all WD/Maxtor drives, that w
Doug White wrote in list.freebsd-current:
> On Tue, 21 Dec 1999, Soren Schmidt wrote:
> > It seems Dieter Rothacker wrote:
> > > The solution for me was to recompile the kernel without AUTO_EOI1 and
> > > AUTO_EOI2.
> >
> > Those options newer worked (for me at least) reliably with anything
Cameron,
Thanks for fixing the regenerative feedback problem between the mic and
the speakers.
My ESS1869 is now repeating the very end of the sound file being played
six or seven times. It is as if the last buffer is being written and
rewritten to the device at the end without finding the EOF.
On Tue, 21 Dec 1999, Soren Schmidt wrote:
> > Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
> >Western Digital Caviar (2.5 GB), DMA-33.
> > Mainboard: Asus P5A-B Super7
> > Chipset: ALi Aladdin V AGPset
>
> It probably because I relaxed the requirements for doing WDMA on di
Soren Schmidt writes:
> It seems Theo van Klaveren wrote:
> > On Tue, 21 Dec 1999, Soren Schmidt wrote:
> >
> > > > Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
> > > >Western Digital Caviar (2.5 GB), DMA-33.
> > > > Mainboard: Asus P5A-B Super7
> > > > Chipset: ALi
On Tue, 21 Dec 1999, Soren Schmidt wrote:
> It seems Dieter Rothacker wrote:
> >
> > Using the new board, I get "waiting for interrupt" errors, and the system
> > freezes while trying to mount the disks (with kernel from 12/03) or the
> > system freeezes before being able to detect the drives (w
Out of da blue John Polstra aka ([EMAIL PROTECTED]) said:
> In article <[EMAIL PROTECTED]>,
> Bush Doctor I <[EMAIL PROTECTED]> wrote:
> > What's the latest on building modula 3 and cvsup on -current systems?
>
> It probably doesn't work right yet -- I'm not sure. I've been too
> busy and there
>What's your filesystem configuration? Do a 'df'. Are any of the
>filesystems non-standard?
/usr/src on /dev/ad0s2f
/usr/obj on /dev/ad2f
/usr/home/ncvs on /dev/ad0s2f
I think that swap is 256MB.
Thanks
Tammy
Filesystem 1K-blocks UsedAvail Capacity Mounted on
/
It seems Theo van Klaveren wrote:
> On Tue, 21 Dec 1999, Soren Schmidt wrote:
>
> > > Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
> > >Western Digital Caviar (2.5 GB), DMA-33.
> > > Mainboard: Asus P5A-B Super7
> > > Chipset: ALi Aladdin V AGPset
> >
> > It probably becau
Hi.
Now we have pthread_cancel in FreeBSD-current(Thanks alfred).
So I ported xmovie (QuickTime Movie Player). It use pthread_cancel
function. But It can't play correctly.
Sorry, I don't have enough skill and time to solve this problem.
I hope to someone help this problem.
Current sta
Fritz Heinrichmeyer wrote:
>
> with todays freebsd-current, pythons "test_select.py" fails. Is this harmful?
>
Hmm, is this using libc_r?
I just found and fixed (not committed yet) a bug that may cause errant wakeups
due to SIGCHLD for threads in wrapped system calls (select included).
Dan Ei
>i suggest that you try and find a committer which can do appropriate
>tests.
Huum, at first, I will merge 3-stable rc.diskless1 into 4-current.
And I will test and post patch here.
>BTW -- i attach to this msg a small script (/etc/diskless/clone_root,
>whatever it should go e.g. /usr/share/ex
On Mon, Dec 20, 1999 at 05:08:27PM -0800, Matthew Dillon wrote:
> :It's possible you might be on to something. I've been running iostat
> :at 1 second intervals, and during the last hang I saw:
> :
> : ttyad2 da1 sa1 cpu
> : tin tout KB/t tp
On Tue, 21 Dec 1999, Soren Schmidt wrote:
> > Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
> >Western Digital Caviar (2.5 GB), DMA-33.
> > Mainboard: Asus P5A-B Super7
> > Chipset: ALi Aladdin V AGPset
>
> It probably because I relaxed the requirements for doing WDMA on di
> [/etc/rc.diskless1 was broken]
...
> From CVS log of src/etc/rc.diskless1, I think someone forgot to
> commit newer and sophisticated code in 4-current and only committed
> in 3-stable by Luigi.
it is not something i forgot --
the problem is, i don't have the resources to run a 4.0 machine,
a
It seems Theo van Klaveren wrote:
>
> When installing the 08-dec-1999 snapshot (before ATA went in GENERIC),
> a recompile from the kernel with the ATA driver instead of the WD
> driver resulted in an unbootable system because of the following
> error (approx.):
>
> mounting root /dev/ad0s1a
>
When installing the 08-dec-1999 snapshot (before ATA went in GENERIC),
a recompile from the kernel with the ATA driver instead of the WD
driver resulted in an unbootable system because of the following
error (approx.):
mounting root /dev/ad0s1a
ata-master: lost disk contact
ata: resetting devi
[/etc/rc.diskless1 was broken]
I setup File server under 4-current for diskless machine,
``/etc/rc.diskless1'' for diskless machine was different from
3-stable and broken .
If I replace rc.diskless1 to 3-stable version, it is fine and
no-trouble under 4-current diskless client.
From CVS
[snip]
>> What is the rating of your Power supply ?
>
>Not quite high enough :-(
>It's a 300 Watt power supply.
>
Hehe - I'm running dual 540's (2.2V) on a BP6 (I'm guessing around 30 Watts
per CPU), extra case fan, big CPU fans, CD, TNT and an IDE drive (I've had
three hooked up once) - on a 23
with todays freebsd-current, pythons "test_select.py" fails. Is this harmful?
--
Fritz Heinrichmeyer mailto:[EMAIL PROTECTED]
FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany)
tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh
To Unsubscribe: send mail to [EMAIL PROTECTE
It seems Dieter Rothacker wrote:
>
> Using the new board, I get "waiting for interrupt" errors, and the system
> freezes while trying to mount the disks (with kernel from 12/03) or the
> system freeezes before being able to detect the drives (with kernel from
> 12/20).
>
> The solution for me wa
Hi,
I do not know if this issue has already been solved, but I cannot remember
having read something about it.
ATA errors directly after booting the kernel seem to be related to the usage
of the fast IRQ tuning parameter "AUTO_EOI".
Last night I migrated from my
GA586DX (Dualboard, 430HX chipse
> I've got a ESS1879 as well. Try the following patch, Cameron sent me.
i commited an equivalent fix this morning.
- cameron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> > # mount -tmsdos /dev/fd0 /mnt
> > msdos: vfsload(msdos): Exec format error
> > Disk works in windows.
Check
tail /var/log/messages
as well. It might make remarks about unknown variables in
there. Recompile your kernel and modules in any case.
Nick
> >
>
> Your /modules/msdos.ko
I've got a ESS1879 as well. Try the following patch, Cameron sent me.
Index: sb.c
===
RCS file: /home/ncvs/src/sys/dev/sound/isa/sb.c,v
retrieving revision 1.41
diff -u -r1.41 sb.c
--- sb.c1999/12/19 22:25:26 1.41
+++ sb.
On Mon, 20 Dec 1999, Cameron Grant wrote:
> > On Sat, 18 Dec 1999, Donn Miller wrote:
> >
> > > I just rebuilt my kernel from a recent cvsup. Of course, I have
> > >
> > > device pcm0
> > > device sbc0
> > >
> > > in my kernel config file. When I try to play a realaudio clip
>
61 matches
Mail list logo
