John Baldwin wrote:
>
> > SUMMARY:
> > The boot disk (ad0 in attachment) is not the problem.
> > There are two other IBM SCSI disks attached to two Adaptec cards.
> > Its these other two SCSI disks-da0,da1 which are empty and
> > whose disklabels I played with. These cause a BTX error if
> > the
Mike,
Mike Smith wrote:
> The only real solution is to hot-plug
> the disks, camcontrol rescan, then dd zeroes over the heads of the disks
> and then re-lable them safely.
Yep, that method works for now.
I was hoping its easy enough to crack this myself (with some online
tips & references)
I changed the disklabels on a few SCSI disks and now
I keep getting these "BTX halted" messages every time
I reboot.
They dont occur if I disconnect those disks. They occur
even after I rewrite those labels. Its not dedicated mode
or whatever now..
I am currently running 4.4-REL.
I am wil
I am seeing strange behaviour with a kld module
which prints out the curproc->p_pid of the caller.
Here are the details :
Configuration :
---
Uniprocessor kernel/Single i686 CPU
4.3-RELEASE
kernel config = GENERIC + {DUMMYNET, BREAK_TO_DEBUGGER}
Setup :
---
(a) I have a kl
Ron,
This may be of interest...
http://citeseer.nj.nec.com/stone00when.html
When The CRC and TCP Checksum Disagree
Jonathan Stone, Craig Partridge SIGCOMM
-Sandeep
On Thu, 27 Sep 2001, Ronald G Minnich wrote:
>
> I have a question on the checksum offloading. Has anyone measured any
> in
I believe the functions you need are in kern/uipc_socket.c
(socreate, sosend, soreceive, soclose, sosetopt..)
Alternately, you could also do as follows, for each
of the above functions
so->so_proto->pr_usrreqs->pru_sosend(so, 0, uio, 0, 0, 0,
uio->uio_procp)
I am not
Matt
Ok I see..the interlock is a lock on a collection (e.g
on vfs mount list) and it can be released once the simple
lock within the to-be-locked object has been acquired.
These are really spin locks, now that I saw simplelock.s
One more clarification if you will.. :-)
What is the purpose of
Hi there,
I need some mechanism to hold long-term locks (across
context switches) while using kernel threads (kthread_*)
and lockmgr() looked like the right thing to use.
I am running FreeBSD 4.1 on a uniprocessor (..the questions
are similar with 4.3)
Looking at kern_lock.c, I see that lockmg
8 matches
Mail list logo
