Re: kernel debugging: seeing swap issues in 7.0
On Fri, May 23, 2008 at 10:12:17PM -0700, paul beard wrote: On Fri, May 23, 2008 at 2:08 PM, Kris Kennaway [EMAIL PROTECTED] wrote: You can try increasing the timeout by editing the relevant kernel source, but if it's failing to reply to the I/O after 30 seconds then something is drastically overloaded on your system. Well, not much is running, and I have recently built a new kernel and world in less time than it takes to get this one port upgraded. I think there is something else amiss. Should this really be soaking up 100Mb of RAM? Yes, that is quite normal. PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 32272 root 1 -200 101M 70340K swread 3:04 0.93% cc1 I have filed a bug against gcc, per instructions. There seems to be an issue somewhere in py-gtk that is exacerbated by the low resources on this system. There is no bug in gcc. Your system does not have enough memory to run the compilation job, so you are thrashing it severely. Try turning down the CFLAGS optimization level, or use a precompiled package from the FTP site or built on another machine. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel debugging: seeing swap issues in 7.0
On Sat, May 24, 2008 at 1:28 AM, Kris Kennaway [EMAIL PROTECTED] wrote: There is no bug in gcc. Your system does not have enough memory to run the compilation job, so you are thrashing it severely. Try turning down the CFLAGS optimization level, or use a precompiled package from the FTP site or built on another machine. That's as may be, but the initial warning/error message was that the gcc folks wanted a big filed. If there is a package for this, I'll go that route. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel debugging: seeing swap issues in 7.0
paul beard wrote: On Sat, May 24, 2008 at 1:28 AM, Kris Kennaway [EMAIL PROTECTED] wrote: There is no bug in gcc. Your system does not have enough memory to run the compilation job, so you are thrashing it severely. Try turning down the CFLAGS optimization level, or use a precompiled package from the FTP site or built on another machine. That's as may be, but the initial warning/error message was that the gcc folks wanted a big filed. If there is a package for this, I'll go that route. The gcc message is a secondary failure from the process being killed at an unexpected point when your system ran out of memory. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel debugging: seeing swap issues in 7.0
I see a lot of these as my system grinds to a halt. It never crashes (I reboot it when it gets really boggy . . . May 23 11:41:13 stinky kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 49155, size: 4096 May 23 11:41:21 stinky kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 48905, size: 4096 This is the top of the kernel debug Unread portion of the kernel message buffer: 118May 23 12:48:46 stinky syslogd: exiting on signal 15 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...1 0 0 done All buffers synced. swap_pager: I/O error - pagein failed; blkno 35668,size 4096, error 5 panic: swap_pager_force_pagein: read from swap failed Uptime: 14h20m56s Physical memory: 115 MB Dumping 37 MB: 22 6 #0 doadump () at pcpu.h:195 195 __asm __volatile(movl %%fs:0,%0 : =r (td)); I have partition-based swap and swap files I set up after gcc was running out of memory. Device: 1048576-blocks Used: /dev/ad0s2b 139 0 /dev/md0 128 0 Any ideas what I can do (besides buy more hardware)? -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel debugging: seeing swap issues in 7.0
On Fri, May 23, 2008 at 01:02:35PM -0700, paul beard wrote: I see a lot of these as my system grinds to a halt. It never crashes (I reboot it when it gets really boggy . . . May 23 11:41:13 stinky kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 49155, size: 4096 May 23 11:41:21 stinky kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 48905, size: 4096 This is the top of the kernel debug Unread portion of the kernel message buffer: 118May 23 12:48:46 stinky syslogd: exiting on signal 15 Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...1 0 0 done All buffers synced. swap_pager: I/O error - pagein failed; blkno 35668,size 4096, error 5 panic: swap_pager_force_pagein: read from swap failed Uptime: 14h20m56s Physical memory: 115 MB Dumping 37 MB: 22 6 #0 doadump () at pcpu.h:195 195 __asm __volatile(movl %%fs:0,%0 : =r (td)); I have partition-based swap and swap files I set up after gcc was running out of memory. Device: 1048576-blocks Used: /dev/ad0s2b 139 0 /dev/md0 128 0 Any ideas what I can do (besides buy more hardware)? You can try increasing the timeout by editing the relevant kernel source, but if it's failing to reply to the I/O after 30 seconds then something is drastically overloaded on your system. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel debugging: seeing swap issues in 7.0
On Fri, May 23, 2008 at 2:08 PM, Kris Kennaway [EMAIL PROTECTED] wrote: You can try increasing the timeout by editing the relevant kernel source, but if it's failing to reply to the I/O after 30 seconds then something is drastically overloaded on your system. Well, not much is running, and I have recently built a new kernel and world in less time than it takes to get this one port upgraded. I think there is something else amiss. Should this really be soaking up 100Mb of RAM? PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 32272 root 1 -200 101M 70340K swread 3:04 0.93% cc1 I have filed a bug against gcc, per instructions. There seems to be an issue somewhere in py-gtk that is exacerbated by the low resources on this system. Thanks. -- Paul Beard / www.paulbeard.org/ [EMAIL PROTECTED]/[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
