In /etc/rc, there is a "swapfile" feature, to configure a file to use
swap device. Here is a script for that.
# Add additional swapfile, if configured.
#
case ${swapfile} in
[Nn][Oo] | '')
;;
*)
if [ -w "${swapfile}" -a -c /dev/mdctl ]; then
echo "Adding ${swapf
In message <[EMAIL PROTECTED]> Andy Sparrow writes:
: > Gotta love one problem report hitting 5 problems all at once :-)
:
: You do? :-/
Yes, and I wasn't even counting your sound problems :-)
hopefully I can resolve at least the interrupt routing issue soonish.
Would you be game to be a guinee
hi all,
sorry for running -current.. but i am an enthusiastic
and challenging man...(boy)...
anyways.. whats a mutex and a lock order reversal...
if you could point to some good manual on these
subjects... thanks...
help is appreciated...
thanks again...
=
regards,
Hiten Pandya
<[EMAIL PR
On Thu, 22 Nov 2001, Warner Losh wrote:
> Gotta add scsi system stuff too:
Yeah, I just pooched it and had dropped the scbus device, had the rest. Just
kept overlooking it.
Thanks for the reply.
Darren Henderson
i think I saw the same problem. I was trying to do a
make buiildworld and the system hung early in the build
process (while it was rm /usr/obj and cleaning dirs).
I froze hard; no ctl-alt-del, no nothing. I had to remove
the battery to reboot it (it's a laptop).
I rebooted the old kernel and
Hiten Pandya wrote:
> MH> The lock order verification is not part of the mtx
> MH> API. It's debugging
> MH> stuff activated by default in -CURRENT. If you do
> MH> not want to see these
> MH> warnings, remove ``options WITNESS'' from your
> MH> kernel conf or patch the
> MH> code to solve the p
MH> The lock order verification is not part of the mtx
MH> API. It's debugging
MH> stuff activated by default in -CURRENT. If you do
MH> not want to see these
MH> warnings, remove ``options WITNESS'' from your
MH> kernel conf or patch the
MH> code to solve the problem :-)
hi,
i know that bit..
Hiten Pandya wrote:
> hi all,
> sorry for running -current.. but i am an enthusiastic
> and challenging man...(boy)...
>
> anyways.. whats a mutex and a lock order reversal...
> if you could point to some good manual on these
> subjects... thanks...
>
> help is appreciated...
>
> thanks again..
Hiten Pandya wrote:
> one more question... if there is a lock order
> reversal.. is there a way that can be solved.. for
> e.g. by using on of the MTX_XX things...
The lock order verification is not part of the mtx API. It's debugging
stuff activated by default in -CURRENT. If you do not want t
hi maxime...
thanks very very much.. now i get it...,
its like.. a mutex is a lock, which is used when
things are done in parralel and to avoid corruption of
the data which is being processed... i took an example
of the way i used to lock files in PERL, in order to
avoid multiple writes at the sam
> OK. Here we see the confluance of two problems. First, irq 0 is
> bogus and likely illegal per the pci spec for devices that do
> interrupt. Even if it isn't illegal, it is wrong wrong wrong wrong,
> but lots of people do it. I have a patch for -stable, but not for
> current.
Well, the car
In message <[EMAIL PROTECTED]> Andy Sparrow writes:
: pci_cfgintr_search: linked (62) to configured irq 0 at 0:31:0
: pci_cfgintr: 0:30 INTC routed to irq 0
: pcib2: routed slot 5 INTA to irq 0
: pcic0: irq 0 at device 5.0 on pci2
: pcib2: device pcic0 requested unsupported memory range 0x440
I was trying to view a VCD with mtv, which is a linux binary.
Mtv starts mtvp to do the actual rendering. I made quite a few
attempts with various combinations of options with no success.
That's not the problem. I just noticed, some 10 hours later,
that there are 34 zombied mtvp processes layi
Hi DES,
- realitexpire, td);
+ realitexpire, td->td_proc);
Fixes the panic 100%.
Thanks a lot !
Martin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Martin Blapp <[EMAIL PROTECTED]> writes:
> kernel trap 12 with interrupts disabled
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0x123423bd
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc024d74a
> stack pointer
On Sat, Nov 24, 2001 at 11:51:26AM +0100, Anders Andersson wrote:
> On Fri, Nov 23, 2001 at 09:42:53PM -0600, David W. Chapman Jr. wrote:
> > I am running -current and trying to remove a directory and every time
> > I try it hardlocks the computer. Its a -current as of noon central
> > time. I
On Sat, Nov 24, 2001 at 02:37:01AM -0800, Hiten Pandya wrote:
> hi david...
> if you are running current.. please give more
> information on what it does after it locks out your
> drive...
>
I really don't know what else to give you. Any type of large file
i/o and the computer hard locks. Befo
17 matches
Mail list logo