* From: Brian Fundakowski Feldman [EMAIL PROTECTED]
* Cool idea! Let's just limit it to the committer birthdays and not
* pets' birthdays too (sorry Asami's hamster and Jordan's cats, but it
Why not? Discrimination! I've committed things too!
-fifi
To Unsubscribe: send mail to [EMAIL
Leif Neland wrote:
I would appreciate it if people running -current would run a "vmstat -s"
and tell me if they see a NON-ZERO value for copy-on-write optimized
faults. About six months ago, I implemented a simpler and more general
optimization at an earlier "fork in the road". (In
I switched to the 'new' atapi driver and I am having trouble with my cdrom
which worked fine using the old wd driver.
I have the following in my config file :
controller ata0
device atadisk0
device atapicd0
The device exists:
$ ls -l /dev/acd0*
On Sun, 31 Oct 1999, Paul van der Zwan wrote:
I switched to the 'new' atapi driver and I am having trouble with my cdrom
which worked fine using the old wd driver.
I have the following in my config file :
controller ata0
device atadisk0
device atapicd0
I get high numbers too:
FreeBSD mailtoaster1.pipeline.ch 3.2-STABLE FreeBSD 3.2-STABLE #3: Sun
Jun 13 20:31:43 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys
/compile/mailtoaster1 i386
Read the original message. It says:
I would appreciate it if people running -current would run a
I run pre-signal-change-current on my
gateway-apache-squid-imap-sendmail-mysql-roxen server and
post-signal-change-current on my other box.
I have compiled a new kernel on the post-signal-change machine, and
installed it (as kernel.new) on the old machine.
But I get a panic, trap 12 while in
current, cvsupped around 3:00 GMT 31 oct.
When trying to boot a new kernel, the machine simply hangs.
I have narrowed it down to ed0, by removing other devices with visual
config at boot. However, nothing is shown regarding ed0, so the hang
probably occurs early in the probing.
Therefore I see
[EMAIL PROTECTED] wrote:
I get high numbers too:
FreeBSD mailtoaster1.pipeline.ch 3.2-STABLE FreeBSD 3.2-STABLE #3: Sun
Jun 13 20:31:43 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys
/compile/mailtoaster1 i386
Read the original message. It says:
I would appreciate it if people
* From: [EMAIL PROTECTED] (fifi -- hamster of Satoshi)
* Why not? Discrimination! I've committed things too!
*
* -fifi
Oops, I left the cage door open! Sorry folks!
No, I honestly have no idea what fifi was talking about. I've never
let her commit things. Ok, not without me watching
Hi,
At 12:33 pm +0100 31/10/99, Leif Neland wrote:
current, cvsupped around 3:00 GMT 31 oct.
When trying to boot a new kernel, the machine simply hangs.
I have narrowed it down to ed0[etc]
The LinkSys probe code (in particular the checksum at the start of
ed_get_Linksys()) causes my no-name
In message [EMAIL PROTECTED], Paul van der Zwan wrote:
I switched to the 'new' atapi driver and I am having trouble with my cdrom
which worked fine using the old wd driver.
I have the following in my config file :
controller ata0
device atadisk0
device atapicd0
Vincent Poy wrote:
I have always read the -current mailing list but you have to
remember that by the time I do the update, the known problem should
already have been gone.
I assume you have a lousy way of expressing yourself (in this case) and
that you don't actually mean what you
[Redirecting to -chat]
On Sun, Oct 31, 1999 at 02:05:14AM -0700, fifi -- hamster of Satoshi wrote:
* From: Brian Fundakowski Feldman [EMAIL PROTECTED]
* Cool idea! Let's just limit it to the committer birthdays and not
* pets' birthdays too (sorry Asami's hamster and Jordan's cats, but
On Sun, 31 Oct 1999, Bob Bishop wrote:
Hi,
At 12:33 pm +0100 31/10/99, Leif Neland wrote:
current, cvsupped around 3:00 GMT 31 oct.
When trying to boot a new kernel, the machine simply hangs.
I have narrowed it down to ed0[etc]
The LinkSys probe code (in particular the checksum at
Hi,
At 2:56 pm +0100 31/10/99, Leif Neland wrote:
[...]If ed_get_linksys was called later than my card was
detected...
I guess it's an ordering thing, but I don't have a LinkSys card here for
testing.
--
Bob Bishop (0118) 977 4017 international code +44 118
[EMAIL PROTECTED]
The LinkSys probe code (in particular the checksum at the start of
ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine
up. I guess you have the same problem.
ouch! not goodwhat is the ethernet address of your ne2000
clone?
jmb
To Unsubscribe: send
And my mine... I get zero COW optimized faults.
louie@whizzo[20] $ vmstat -s
47312081 cpu context switches
89421468 device interrupts
30438305 software interrupts
16214761 traps
244593116 system calls
1546 swap pager pageins
5124 swap pager pages paged in
4185 swap pager
Hi,
At 7:03 am -0800 31/10/99, Jonathan M. Bresler wrote:
The LinkSys probe code (in particular the checksum at the start of
ed_get_Linksys()) causes my no-name ISA NE2000 clone to lock the machine
up. I guess you have the same problem.
ouch! not goodwhat is the ethernet
Have you either tried disabling DMA on the drive? This is easily achieved
by the following (whitespace mangled):
--- atapi-all.c 1999/10/10 18:08:38 1.19
+++ atapi-all.c 1999/10/23 16:51:12
@@ -135,7 +135,8 @@
udmamode(atp-atapi_parm),
On Sun, 31 Oct 1999, Brian Fundakowski Feldman wrote:
Have you either tried disabling DMA on the drive? This is easily achieved
by the following (whitespace mangled):
I'll try it on Monday.
--
Doug Rabson Mail: [EMAIL PROTECTED]
Nonlinear Systems Ltd.
It seems Doug Rabson wrote:
On Sun, 31 Oct 1999, Brian Fundakowski Feldman wrote:
Have you either tried disabling DMA on the drive? This is easily achieved
by the following (whitespace mangled):
I'll try it on Monday.
Hmm, as well as DMA might be the reason, it only applies to
I have the same problem with my NE2000 clone, so for now I have to use
an old kernel that I made 2 weeks ago.
My NE2000-clone uses port 300, irq 11
Yes, I added a return(0) at the beginning of ed_get_linksys(); and now I'm
up. But now is the question how to fix if_ed permanently... Perhaps a
I also get this lock up on a machine with a ISA NE2000 clone:
ed0 at 0x300-0x31f irq 9 on isa
ed0: address 00:40:33:23:6b:c1, type NE2000 (16 bit)
I have every other NIC driver removed, but a -CURRENT kernel with ed0
enabled on it will cause it to lock hard. Disabling the device in the
kernel
According to Satoshi - Ports Wraith - Asami:
let her commit things. Ok, not without me watching over her shoulder
Experience shows that even this is not enough to prevent accidents (Hi Greg!).
:-)
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD
okay i have changed the order in which we test for NE1000, NE2000, and
the Linksys (dl10016c ? ethernet controller).
pleazse test and let me know how this patch does.
hopefully the problem will be solved.
does *ANYONE* have an NE1000, the can test?
before adding in teh Linksys we tested:
In message [EMAIL PROTECTED], Brian Fun
dakowski Feldman wrote:
Have you either tried disabling DMA on the drive? This is easily achieved
by the following (whitespace mangled):
--- atapi-all.c 1999/10/10 18:08:38 1.19
+++ atapi-all.c 1999/10/23 16:51:12
@@ -135,7 +135,8 @@
I am going to try host the following discussions on -arch over the next
week.
1/ which direction (maybe multiple) are we going with threads.
2/ SMP. how to go about it from here..
3/ In what ways should the VFS and the filesystems be changed/cleaned-up
4/ what about posix extensions such
On Sun, 31 Oct 1999, Louis A. Mamakos wrote:
And my mine... I get zero COW optimized faults.
THE E-MAIL EXPLICITLY SAID ONLY TO POST IF YOU HAVE MORE THEN 0 FAULTS
I hope one day the people who don't read this list carefully miss something
really important and it eats your system as a result.
I am not that really interested on threads..
Is there a possibility of having an async call gate for which the kernel
can do the scheduling whether be for a uni processor or a multi processor
enviroment.
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
yes it is a possibility..
see terry's thread model (coming up soon).
(at least lurk)
On Sun, 31 Oct 1999, Amancio Hasty wrote:
I am not that really interested on threads..
Is there a possibility of having an async call gate for which the kernel
can do the scheduling whether be for a
p.s. this should not be in -current but in -arch
On Sun, 31 Oct 1999, Julian Elischer wrote:
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, 31 Oct 1999, Jonathan M. Bresler wrote:
okay i have changed the order in which we test for NE1000, NE2000, and
the Linksys (dl10016c ? ethernet controller).
pleazse test and let me know how this patch does.
hopefully the problem will be solved.
I tried it, I could boot, and
I believe the ESS drivers weren't committed to 4.0-current yet. When I
grep ' ESS ' in /sys/i386/isa/sound, the only thing I can come up with is
the ESS support that was in the old voxware sound code. Sanpei, who is
developing the ESS sound drivers, says they were committed to the newpcm
Hi,
At 10:52 am -0800 31/10/99, Jonathan M. Bresler wrote:
okay i have changed the order in which we test for NE1000, NE2000, and
the Linksys (dl10016c ? ethernet controller).
pleazse test and let me know how this patch does.[etc]
OK the patch fixes the problem here. [Thanks for the context
Today Jonathan M. Bresler wrote:
okay i have changed the order in which we test for NE1000, NE2000, and
the Linksys (dl10016c ? ethernet controller).
pleazse test and let me know how this patch does.
hopefully the problem will be solved.
Works with my NE2000 clone. Thanks Jonathan.
My box has got three ata disks and one atapi cdrom drive(on secondary slave).
Since a few weeks ago the cdrom drive does not get probed.
dmesg
Oct 30 19:31:46 silver /kernel: ata-pci0: Intel PIIX4 IDE controller at device 4.1
on pci0
Oct 30 19:31:46 silver /kernel: ata-pci0: Busmastering DMA
ohci0: OPTi 82C861 (FireLink) USB controller irq 9 at device 11.0 on pci0
+ohci_waitintr: timeout
IRQ 9 is shared with the VGA controller. Perhaps calling the VESA
BIOS caused it to do something strange that interfered with the
delivery of this interrupt on your motherboard.
No, this
On Sun, Oct 31, 1999 at 09:39:33PM -0700, Nick Hibma wrote:
ohci0: OPTi 82C861 (FireLink) USB controller irq 9 at device 11.0 on pci0
+ohci_waitintr: timeout
IRQ 9 is shared with the VGA controller. Perhaps calling the VESA
BIOS caused it to do something strange that interfered
On Sat, Oct 30, 1999 at 02:43:47PM -0700, Vincent Poy wrote:
Yes, I am still running -current. I read the -current mailing
list on a more regular basis than most of the people out there.
By what measure? I think you've shown the opposite.
I have always read the -current
On Sun, 31 Oct 1999, David O'Brien wrote:
On Sat, Oct 30, 1999 at 02:43:47PM -0700, Vincent Poy wrote:
Yes, I am still running -current. I read the -current mailing
list on a more regular basis than most of the people out there.
By what measure? I think you've shown the
40 matches
Mail list logo
