Professional Web Applications Themes

freebsd-questions Digest, Vol 91, Issue 29 - FreeBSD

> From: Jason Henson <rr.com>  > > FreeBSD is very robust with power failures, but that was a reset > button. Do you have acpi on? When I hit my power button every once in > a while my system shuts down properly. Try booting into single user > mode and do a manual mount and fsck. > > And just to help you out: > > $ sysctl -ad | grep pipekva > kern.ipc.maxpipekva: Pipe KVA limit > kern.ipc.pipekva: Pipe KVA usage > $ sysctl -a | grep pipekva > kern.ipc.maxpipekva: 8634368 > kern.ipc.pipekva: 344064 >[/ref] Thank you Jason. ...

  1. #1

    Default Re: freebsd-questions Digest, Vol 91, Issue 29

    > From: Jason Henson <rr.com> 
    >
    > FreeBSD is very robust with power failures, but that was a reset
    > button. Do you have acpi on? When I hit my power button every once in
    > a while my system shuts down properly. Try booting into single user
    > mode and do a manual mount and fsck.
    >
    > And just to help you out:
    >
    > $ sysctl -ad | grep pipekva
    > kern.ipc.maxpipekva: Pipe KVA limit
    > kern.ipc.pipekva: Pipe KVA usage
    > $ sysctl -a | grep pipekva
    > kern.ipc.maxpipekva: 8634368
    > kern.ipc.pipekva: 344064
    >[/ref]
    Thank you Jason. I do have ACPI on. I believe booting into -s mode,
    manually mounting and fsck-ing the slices, and adding the two kernel
    paramenters to /boot/loader.conf as you suggsted has sorted me (or, at
    least, alleviated the system of kernel errors). I used your parameters
    ver batim; I will need to understand how the values relate to physical
    memory (only 320MB) before I tinker with them.

    Thanks again,
    ~John
    John Guest

  2. #2

    Default Re: kern.maxpipekva exceeded, please see tuning(7)

    > From: Jason Henson <rr.com> 
    >
    > FreeBSD is very robust with power failures, but that was a reset
    > button. Do you have acpi on? When I hit my power button every once in
    > a while my system shuts down properly. Try booting into single user
    > mode and do a manual mount and fsck.
    >
    > And just to help you out:
    >
    > $ sysctl -ad | grep pipekva
    > kern.ipc.maxpipekva: Pipe KVA limit
    > kern.ipc.pipekva: Pipe KVA usage
    > $ sysctl -a | grep pipekva
    > kern.ipc.maxpipekva: 8634368
    > kern.ipc.pipekva: 344064
    >[/ref]
    Thanks to Jason's instructions, I was able to boot into -s mode,
    manually mount and fsck the slices, and add the two kernel
    paramenters to /boot/loader.conf, using his maxpipekva and pipekva
    parameters and values
    ver batim; and this seemed to get me back up and running.

    Howver, whenever I now try to perform any intensive operations, such
    as cvsup or makeworld, the errors come right back and do not desist
    unless I reboot the machine.

    Is there a recommended value for these parameters if I've got a total
    of 340MB RAM, or another way of solving this problem?

    Thank you,
    ~John
    John Guest

  3. #3

    Default Re: kern.maxpipekva exceeded, please see tuning(7)

    On Sat, 19 Mar 2005 14:17:33 -0500, John DeStefano
    <com> wrote: 
    > >
    > > FreeBSD is very robust with power failures, but that was a reset
    > > button. Do you have acpi on? When I hit my power button every once in
    > > a while my system shuts down properly. Try booting into single user
    > > mode and do a manual mount and fsck.
    > >
    > > And just to help you out:
    > >
    > > $ sysctl -ad | grep pipekva
    > > kern.ipc.maxpipekva: Pipe KVA limit
    > > kern.ipc.pipekva: Pipe KVA usage
    > > $ sysctl -a | grep pipekva
    > > kern.ipc.maxpipekva: 8634368
    > > kern.ipc.pipekva: 344064
    > >[/ref]
    > Thanks to Jason's instructions, I was able to boot into -s mode,
    > manually mount and fsck the slices, and add the two kernel
    > paramenters to /boot/loader.conf, using his maxpipekva and pipekva
    > parameters and values
    > ver batim; and this seemed to get me back up and running.
    >
    > Howver, whenever I now try to perform any intensive operations, such
    > as cvsup or makeworld, the errors come right back and do not desist
    > unless I reboot the machine.
    >
    > Is there a recommended value for these parameters if I've got a total
    > of 340MB RAM, or another way of solving this problem?
    >
    > Thank you,
    > ~John
    >[/ref]

    Hi again folks,

    In addition to the above, cron is now dumping signal 11 cores on me
    every two minutes. I had one suggestion to check the value of
    "openfiles" in /etc/login.conf, but that's already set to "unlimited".

    Any and all ideas would be appreciated.

    Thanks.
    ~John
    John Guest

Similar Threads

  1. freebsd-questions Digest, Vol 89, Issue 20
    By Geoff Glasson in forum FreeBSD
    Replies: 0
    Last Post: February 25th, 05:38 AM
  2. freebsd-questions Digest, Vol 88, Issue 68
    By Matt Rechkemmer in forum FreeBSD
    Replies: 0
    Last Post: February 20th, 12:39 AM
  3. rubynet-announce Digest, Vol 6, Issue 4
    By rubynet-announce-request@lists.rubynet.org in forum Ruby
    Replies: 0
    Last Post: August 16th, 07:00 PM
  4. rubynet-announce Digest, Vol 5, Issue 2
    By rubynet-announce-request@lists.rubynet.org in forum Ruby
    Replies: 0
    Last Post: July 5th, 07:00 PM
  5. rubynet-announce Digest, Vol 5, Issue 1
    By rubynet-announce-request@lists.rubynet.org in forum Ruby
    Replies: 0
    Last Post: July 2nd, 07:00 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139