Re: Udev-165 (apparently) System Crash

2011-01-11 Thread alupu
On Thu Jan 6 2011 09:24 PM, William Immendorf wrote: Intriguing. This is something that you should report to both LKML and linux-hotplug (the Udev list). Also, be sure to provide the kdump of that kernel, the log, and the hardware that you think is causing the Udev issue. Hi William, First,

Re: Udev-165 (apparently) System Crash

2011-01-08 Thread alupu
On Thu, 2011-01-06 at 02:08 AM, Simon Geard wrote: ... udevd supports a couple of options that might help, --debug and --debug-trace. 1. FWIW, udevd-165 does not (no-longer?) have a --debug-trace option. Maybe it's undocumented now (shades of Undocumented DOS of yore :) Please see 'man

Re: Udev-165 (apparently) System Crash

2011-01-08 Thread Neal Murphy
On Saturday 08 January 2011 13:44:23 al...@verizon.net wrote: On Thu, 2011-01-06 at 02:08 AM, Simon Geard wrote: ... udevd supports a couple of options that might help, --debug and --debug-trace. 1. FWIW, udevd-165 does not (no-longer?) have a --debug-trace option. Maybe it's

Re: Udev-165 (apparently) System Crash

2011-01-08 Thread alupu
On Saturday 08 January 2011 02:48 PM Neal Murphy wrote: While I was integrating udev into my test/dev version of Smoothwall ... Hi Neal, This is only to acknowledge and thank you for your detailed comments. I haven't had time to go into any depth at all, what with the NFL playoffs and all, but

Re: Udev-165 (apparently) System Crash

2011-01-06 Thread alupu
On Thu, 2011-01-06 at 02:08:45 AM, Simon Geard wrote ... if the system is completely frozen, it may be hardware related ...Hi Simon,Very good points, overall.When it crashes it's frozen all right (i.e. a crash crash).No hardware changes as of late.Seems some old hardware the latest Udev iteration

Re: Udev-165 (apparently) System Crash

2011-01-06 Thread William Immendorf
On Thu, Jan 6, 2011 at 6:36 PM, al...@verizon.net wrote: If I correctly read the frozen screen, and taking into account the Udev step where the crash occurs, seems an IRQ conflict of some sort. I'll dig into it. Intriguing. This is something that you should report to both LKML and

Re: Udev-165 (apparently) System Crash

2011-01-06 Thread Simon Geard
On Thu, 2011-01-06 at 18:36 -0600, al...@verizon.net wrote: The important thing for me is you appear to support me, even if indirectly, in my attempt to avoid kdump in my troubleshoot, if at all possible :) Happy to help. Simon. signature.asc Description: This is a digitally signed message

Udev-165 (apparently) System Crash

2011-01-05 Thread alupu
Hello, Hardware: ASUS P4S533-MX, Intel Pentium 4, 3.06 GHz, 1 GB, PATA Software: i686-pc-linux-gnu, (B)LFS, 2.6.36.2, ext2, udev-165 PROBLEM System started crashing on boot-up recently, about 50% of the time. Softly, i.e. after reboot, fsck returns 1 (errors found and corrected). In the Udev

Re: Udev-165 (apparently) System Crash

2011-01-05 Thread Simon Geard
On Wed, 2011-01-05 at 20:12 -0600, al...@verizon.net wrote: QUESTION Is there a simple way of analyzing the crash, maybe with help of the specialists here, as opposed to formally reporting it? Never tried, myself, but udevd supports a couple of options that might help, --debug and