ith "unsubscribe freebsd-current" in the body of the message
>
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
the handler itself
> might be messed up. If you do a hexdump of the first argument to
> ithread_remove_handler() that should give you a dump of the struct intrhand,
> and you can then see if that looks valid, esp. the ithread pointer. If the
> ithread pointer is valid then you can st
0,6db000,6dbc00,6db000,0) at initclocks+0x1c
mi_startup() at mi_startup+0xb5
begin() at begin+0x2c
db>
_mtx_lock_flags+0x43 -> sys/kern/kern_mutex.c:324
ithread_remove_handler+0x53 -> sys/kern/kern_intr.c:314
inthand_remove+0x11 -> sys/i386/isa/intr_machdep.c:705
cpu_initclocks+0x327
I'm quite certain this was discussed recently, but I can't find it in
the mailing list archives.
I'm getting a few "fxp0: device timeout" on my supermicro 6010H (dual
1GHz PIII with onboard fxp). Was this resolved?
thanks,
dave c
--
Dave Cornejo @ Dogwood Media,
0F PCI ethernet card"
wiif_wi 2 network "Lucent WaveLAN/IEEE 802.11 PCMCIA card"
- wxif_wx 2 network "Intel Gigabit Ethernet (82452) card"
xlif_xl 2 network "3COM 3c90x / 3c90xB PCI ethernet card"
--- 54
e left on device
*** Error code 1
Stop in /usr/src/release.
*** Error code 1
Stop in /usr/src/release.
*** Error code 1
Stop in /usr/src/release.
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren't any monkeys chasing us..." - Xochi
To Uns
ion so I'll keep plugging and if I get some time this
weekend and they still are doing this, then I'll try and get more
info.
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
you wrote:
> And just for the record: PERL is right out (of space) for this purpose...
as I assume emacs would be too? :-(
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: s
- but no other apparent side effects.
The corrupted line shows up in many different places and users, and
the exact contents vary, but there's always a "(csh)" at the end.
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren'
quot;Waiting 15 seconds.." message comes out.
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
.000MHz, offset 63, 16bit), Tagged Queueing Enabled
da1: 17501MB (35843671 512 byte sectors: 255H 63S/T 2231C)
Mounting root from ufs:/dev/da0s1a
SMP: AP CPU #1 Launched!
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
oblem have been introduced
when support was added?
thanks,
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
thing from
that (provided nothing is broken).
thanks,
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
atch the command completions? which routine is best
to do this in?
btw, thanks very much for your help!
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
en the system hangs.
I have gone back to a SMP kernel from April 15th - using a GENERIC
kernel with SMP enabled it exhibits the same problem. Will work my
way back to -stable and see if anything changes...
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
&qu
the trace buffer
besides what appears to be normal process rescheduling (?) which is
mostly idle task time...
Do think there's any use to rolling my source tree back a ways and
compiling a kernel?
thanks,
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTE
ExtINT active-hiedge3 02550
NMI active-hiedge0 0:A2551
=======
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL
place to start (like a routine to start
tracing), or is there anything I can do that might get more info for
the people that know what is going on?
thanks!
dave c
--
Dave Cornejo @ Dogwood Media, Fremont, California (also [EMAIL PROTECTED])
"There aren't any monkeys chasing us...
Dave Cornejo -
From: Dave Cornejo <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Subject: SuperMicro 6010H SCSI Problems
To: [EMAIL PROTECTED]
Date: Sun, 17 Jun 2001 00:20:47 -0700 (PDT)
X-Mailer: ELM [version 2.4ME+ PL88 (25)]
I finally got a make release done (a heartfelt
__GTHREAD_MUTEX_INIT_FUNCTION(m)=pthread_mutex_init(m, NULL)'
>
> .include "../libgcc/Makefile"
>
>
>
--
Dave Cornejo @ Dogwood Media, Fremont, California
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
from /usr/libexec/ld-elf.so.1
(gdb) quit
The program is running. Exit anyway? (y or n) y
juneau#
The system is a dual PIII-600 w/512M RAM if that helps...
--
Dave Cornejo @ Dogwood Media, Fremont, California
"There aren't any monkeys chasing us..." - Xochi
To Unsubscribe: send
PROTECTED]
the latest fetch sends this:
USER [EMAIL PROTECTED]@21
which fwtk apparently interprets as username "[EMAIL PROTECTED]"
at IP address "0.0.0.21"
What is incorrect here? Should FWTK understand this or is fetch
wrong?
dave
--
Dave Cornejo @ Dogwood Me
not longer. If you want v6, run current, don't make the people
waiting for 4.0 wait longer. This is much more likely to cause lost
users than no v6.
--
Dave Cornejo - Dogwood Media, Fremont, California
General Magician & Registered Be Developer
To Unsubscribe: send mail to [EMAIL PROT
23 matches
Mail list logo