[SLUG] System freeze - how to diagnose?
The power light was on, but no-one home. Nothing responding, no ping. Other machines on the same UPS are running fine. I rebooted and got a "30 times mounted" forced disk check - no problem there. Everything came up fine. Nothing in syslog or anywhere else I can think of. The only thing notable was that the activity light on a USB webcam I'm messing with was still on, which makes me suspicious it might have to do with that. [1] I was testing an image capture script that's cpu intensive, and I left it running over-night, for over 12 hours - over heating perhaps? Any suggestions where/how to start investigating this? Nothing obvious on Google that I can find. Ubuntu 6.10, btw. many thanks... David. [1] [17179602.072000] drivers/media/video/spca5xx/spca5xx-main.c: USB SPCA5XX camera found. Logitech QC Communicate STX [17179602.372000] usbcore: registered new driver spca5xx [17179602.372000] drivers/media/video/spca5xx/spca5xx-main.c: spca5xx driver 00.57.08 registered -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] System freeze - how to diagnose?
On Mon, Jan 22, 2007 at 09:13:24AM +1100, david wrote: > The power light was on, but no-one home. Nothing responding, no ping. > Other machines on the same UPS are running fine. > > I rebooted and got a "30 times mounted" forced disk check - no problem > there. Everything came up fine. Nothing in syslog or anywhere else I can > think of. > > The only thing notable was that the activity light on a USB webcam I'm > messing with was still on, which makes me suspicious it might have to do > with that. [1] I was testing an image capture script that's cpu > intensive, and I left it running over-night, for over 12 hours - over > heating perhaps? > > Any suggestions where/how to start investigating this? Nothing obvious > on Google that I can find. Ubuntu 6.10, btw. > > many thanks... if you have another machine, connect the 2 together by serial cable and send your console out the serial cable. Start up minicom on the 2nd box and what for it to crash. Also did you try alt+sysrq magic key combo ? > > David. > > > [1] > [17179602.072000] drivers/media/video/spca5xx/spca5xx-main.c: USB > SPCA5XX camera found. Logitech QC Communicate STX > [17179602.372000] usbcore: registered new driver spca5xx > [17179602.372000] drivers/media/video/spca5xx/spca5xx-main.c: spca5xx > driver 00.57.08 registered > > > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > signature.asc Description: Digital signature -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] System freeze - how to diagnose?
On Mon, 2007-01-22 at 13:46 +1100, Alex Samad wrote: > On Mon, Jan 22, 2007 at 09:13:24AM +1100, david wrote: > > The power light was on, but no-one home. Nothing responding, no ping. > > Other machines on the same UPS are running fine. > > > > I rebooted and got a "30 times mounted" forced disk check - no problem > > there. Everything came up fine. Nothing in syslog or anywhere else I can > > think of. > > > > The only thing notable was that the activity light on a USB webcam I'm > > messing with was still on, which makes me suspicious it might have to do > > with that. [1] I was testing an image capture script that's cpu > > intensive, and I left it running over-night, for over 12 hours - over > > heating perhaps? > > > > Any suggestions where/how to start investigating this? Nothing obvious > > on Google that I can find. Ubuntu 6.10, btw. > > > > many thanks... > > if you have another machine, connect the 2 together by serial cable and send > your console out the serial cable. Start up minicom on the 2nd box and what > for it to crash. > sounds reasonable ;-) sounds like I need to run it overnight again and try to reproduce the problem. > Also did you try alt+sysrq magic key combo ? > I hadn't heard of this, but it looks like it only works from console, not from a Gnome terminal. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] System freeze - how to diagnose?
On Mon, Jan 22, 2007 at 02:30:13PM +1100, david wrote: > On Mon, 2007-01-22 at 13:46 +1100, Alex Samad wrote: > > On Mon, Jan 22, 2007 at 09:13:24AM +1100, david wrote: > > > The power light was on, but no-one home. Nothing responding, no ping. > > > Other machines on the same UPS are running fine. > > > > > > I rebooted and got a "30 times mounted" forced disk check - no problem > > > there. Everything came up fine. Nothing in syslog or anywhere else I can > > > think of. > > > > > > The only thing notable was that the activity light on a USB webcam I'm > > > messing with was still on, which makes me suspicious it might have to do > > > with that. [1] I was testing an image capture script that's cpu > > > intensive, and I left it running over-night, for over 12 hours - over > > > heating perhaps? > > > > > > Any suggestions where/how to start investigating this? Nothing obvious > > > on Google that I can find. Ubuntu 6.10, btw. > > > > > > many thanks... > > > > if you have another machine, connect the 2 together by serial cable and send > > your console out the serial cable. Start up minicom on the 2nd box and what > > for it to crash. > > > > sounds reasonable ;-) sounds like I need to run it overnight again and > try to reproduce the problem. > > > Also did you try alt+sysrq magic key combo ? > > > > I hadn't heard of this, but it looks like it only works from console, > not from a Gnome terminal. yep you need console access, there is some way of doing it across a serial connection, but . It is worth knowing about, has saved me a few times > > > signature.asc Description: Digital signature -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] System freeze - how to diagnose?
For the record, this was a disk I/O error, which I discovered by leaving the job running over night logged into a console rather than Gnome. I'm guessing something is overheating, since it's a job that's very processor/harddrive intensive. I'm also assuming (!) that it wasn't logged because the system couldn't write to disk ? David. On Mon, 2007-01-22 at 22:22 +1100, Alex Samad wrote: > On Mon, Jan 22, 2007 at 02:30:13PM +1100, david wrote: > > On Mon, 2007-01-22 at 13:46 +1100, Alex Samad wrote: > > > On Mon, Jan 22, 2007 at 09:13:24AM +1100, david wrote: > > > > The power light was on, but no-one home. Nothing responding, no ping. > > > > Other machines on the same UPS are running fine. > > > > > > > > I rebooted and got a "30 times mounted" forced disk check - no problem > > > > there. Everything came up fine. Nothing in syslog or anywhere else I can > > > > think of. > > > > > > > > The only thing notable was that the activity light on a USB webcam I'm > > > > messing with was still on, which makes me suspicious it might have to do > > > > with that. [1] I was testing an image capture script that's cpu > > > > intensive, and I left it running over-night, for over 12 hours - over > > > > heating perhaps? > > > > > > > > Any suggestions where/how to start investigating this? Nothing obvious > > > > on Google that I can find. Ubuntu 6.10, btw. > > > > > > > > many thanks... > > > > > > if you have another machine, connect the 2 together by serial cable and > > > send > > > your console out the serial cable. Start up minicom on the 2nd box and > > > what > > > for it to crash. > > > > > > > sounds reasonable ;-) sounds like I need to run it overnight again and > > try to reproduce the problem. > > > > > Also did you try alt+sysrq magic key combo ? > > > > > > > I hadn't heard of this, but it looks like it only works from console, > > not from a Gnome terminal. > yep you need console access, there is some way of doing it across a serial > connection, but . > > It is worth knowing about, has saved me a few times > > > > > > > > > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] System freeze - how to diagnose?
On Tue, Jan 23, 2007 at 11:33:42AM +1100, david wrote: > For the record, this was a disk I/O error, which I discovered by leaving > the job running over night logged into a console rather than Gnome. > > I'm guessing something is overheating, since it's a job that's very > processor/harddrive intensive. I'm also assuming (!) that it wasn't > logged because the system couldn't write to disk ? smartmon or smarttools is your friend > > David. > > > On Mon, 2007-01-22 at 22:22 +1100, Alex Samad wrote: > > On Mon, Jan 22, 2007 at 02:30:13PM +1100, david wrote: > > > On Mon, 2007-01-22 at 13:46 +1100, Alex Samad wrote: > > > > On Mon, Jan 22, 2007 at 09:13:24AM +1100, david wrote: > > > > > The power light was on, but no-one home. Nothing responding, no ping. > > > > > Other machines on the same UPS are running fine. > > > > > > > > > > I rebooted and got a "30 times mounted" forced disk check - no problem > > > > > there. Everything came up fine. Nothing in syslog or anywhere else I > > > > > can > > > > > think of. > > > > > > > > > > The only thing notable was that the activity light on a USB webcam I'm > > > > > messing with was still on, which makes me suspicious it might have to > > > > > do > > > > > with that. [1] I was testing an image capture script that's cpu > > > > > intensive, and I left it running over-night, for over 12 hours - over > > > > > heating perhaps? > > > > > > > > > > Any suggestions where/how to start investigating this? Nothing obvious > > > > > on Google that I can find. Ubuntu 6.10, btw. > > > > > > > > > > many thanks... > > > > > > > > if you have another machine, connect the 2 together by serial cable and > > > > send > > > > your console out the serial cable. Start up minicom on the 2nd box and > > > > what > > > > for it to crash. > > > > > > > > > > sounds reasonable ;-) sounds like I need to run it overnight again and > > > try to reproduce the problem. > > > > > > > Also did you try alt+sysrq magic key combo ? > > > > > > > > > > I hadn't heard of this, but it looks like it only works from console, > > > not from a Gnome terminal. > > yep you need console access, there is some way of doing it across a serial > > connection, but . > > > > It is worth knowing about, has saved me a few times > > > > > > > > > > > > > > > -- > > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > signature.asc Description: Digital signature -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
