On Mon, Apr 15, 2013 at 04:55:04PM -0400, Don Zickus wrote:
> On Fri, Apr 12, 2013 at 02:30:24PM -0700, Guenter Roeck wrote:
> > On Fri, Apr 12, 2013 at 05:16:27PM -0400, Don Zickus wrote:
> > > On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
> > > > > have no idea how to even find
On Fri, Apr 12, 2013 at 02:30:24PM -0700, Guenter Roeck wrote:
> On Fri, Apr 12, 2013 at 05:16:27PM -0400, Don Zickus wrote:
> > On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
> > > > have no idea how to even find out if multiple watchdogs are open on the
> > > > system. Is there
On Fri, Apr 12, 2013 at 02:30:24PM -0700, Guenter Roeck wrote:
On Fri, Apr 12, 2013 at 05:16:27PM -0400, Don Zickus wrote:
On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
have no idea how to even find out if multiple watchdogs are open on the
system. Is there a list I
On Mon, Apr 15, 2013 at 04:55:04PM -0400, Don Zickus wrote:
On Fri, Apr 12, 2013 at 02:30:24PM -0700, Guenter Roeck wrote:
On Fri, Apr 12, 2013 at 05:16:27PM -0400, Don Zickus wrote:
On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
have no idea how to even find out if
On Fri, Apr 12, 2013 at 05:16:27PM -0400, Don Zickus wrote:
> On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
> > > have no idea how to even find out if multiple watchdogs are open on the
> > > system. Is there a list I could walk? And with regard to 'watchdog is
> >
> > /* the
On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
> > have no idea how to even find out if multiple watchdogs are open on the
> > system. Is there a list I could walk? And with regard to 'watchdog is
>
> /* the dev_t structure to store the dynamically allocated watchdog devices */
On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
have no idea how to even find out if multiple watchdogs are open on the
system. Is there a list I could walk? And with regard to 'watchdog is
/* the dev_t structure to store the dynamically allocated watchdog devices */
On Fri, Apr 12, 2013 at 05:16:27PM -0400, Don Zickus wrote:
On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
have no idea how to even find out if multiple watchdogs are open on the
system. Is there a list I could walk? And with regard to 'watchdog is
/* the dev_t
On Wed, Apr 10, 2013 at 12:49:14PM -0400, David Teigland wrote:
> On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
> > However, we still have the problem that if the machine panics and we want
> > to jump into the kdump kernel, we need to 'kick' the watchdog one more
> > time. This
On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
> However, we still have the problem that if the machine panics and we want
> to jump into the kdump kernel, we need to 'kick' the watchdog one more
> time. This provides us a sane sync point for determining how long we have
> to load
On Wed, Apr 10, 2013 at 12:17:39PM -0400, Don Zickus wrote:
> On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
> > On Wed, Apr 10, 2013 at 10:20:55AM -0400, Don Zickus wrote:
> > > On Wed, Apr 10, 2013 at 06:51:23AM -0700, Guenter Roeck wrote:
> > > > On Wed, Apr 10, 2013 at
On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
> On Wed, Apr 10, 2013 at 10:20:55AM -0400, Don Zickus wrote:
> > On Wed, Apr 10, 2013 at 06:51:23AM -0700, Guenter Roeck wrote:
> > > On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
> > > > On Tue, Apr 09, 2013 at
On Wed, Apr 10, 2013 at 10:20:55AM -0400, Don Zickus wrote:
> On Wed, Apr 10, 2013 at 06:51:23AM -0700, Guenter Roeck wrote:
> > On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
> > > On Tue, Apr 09, 2013 at 09:07:58AM -0700, Guenter Roeck wrote:
> > > > > > Just look for the use of
On Wed, Apr 10, 2013 at 06:51:23AM -0700, Guenter Roeck wrote:
> On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
> > On Tue, Apr 09, 2013 at 09:07:58AM -0700, Guenter Roeck wrote:
> > > > > Just look for the use of mod_timer in the watchdog directory.
> > > >
> > > > So looking at the
On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
> On Tue, Apr 09, 2013 at 09:07:58AM -0700, Guenter Roeck wrote:
> > > > Just look for the use of mod_timer in the watchdog directory.
> > >
> > > So looking at the mod_timer logic in various drivers, it seems regardless
> > > if the
On Tue, Apr 09, 2013 at 09:07:58AM -0700, Guenter Roeck wrote:
> > > Just look for the use of mod_timer in the watchdog directory.
> >
> > So looking at the mod_timer logic in various drivers, it seems regardless
> > if the /dev/watchdog device is opened or not, if it is running, it will
> >
On Tue, Apr 09, 2013 at 09:07:58AM -0700, Guenter Roeck wrote:
Just look for the use of mod_timer in the watchdog directory.
So looking at the mod_timer logic in various drivers, it seems regardless
if the /dev/watchdog device is opened or not, if it is running, it will
automagically
On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
On Tue, Apr 09, 2013 at 09:07:58AM -0700, Guenter Roeck wrote:
Just look for the use of mod_timer in the watchdog directory.
So looking at the mod_timer logic in various drivers, it seems regardless
if the /dev/watchdog
On Wed, Apr 10, 2013 at 10:20:55AM -0400, Don Zickus wrote:
On Wed, Apr 10, 2013 at 06:51:23AM -0700, Guenter Roeck wrote:
On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
On Tue, Apr 09, 2013 at 09:07:58AM -0700, Guenter Roeck wrote:
Just look for the use of mod_timer in
On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
On Wed, Apr 10, 2013 at 10:20:55AM -0400, Don Zickus wrote:
On Wed, Apr 10, 2013 at 06:51:23AM -0700, Guenter Roeck wrote:
On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
On Tue, Apr 09, 2013 at 09:07:58AM -0700,
On Wed, Apr 10, 2013 at 12:17:39PM -0400, Don Zickus wrote:
On Wed, Apr 10, 2013 at 08:10:41AM -0700, Guenter Roeck wrote:
On Wed, Apr 10, 2013 at 10:20:55AM -0400, Don Zickus wrote:
On Wed, Apr 10, 2013 at 06:51:23AM -0700, Guenter Roeck wrote:
On Wed, Apr 10, 2013 at 09:40:39AM -0400,
On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
However, we still have the problem that if the machine panics and we want
to jump into the kdump kernel, we need to 'kick' the watchdog one more
time. This provides us a sane sync point for determining how long we have
to load the
On Wed, Apr 10, 2013 at 12:49:14PM -0400, David Teigland wrote:
On Wed, Apr 10, 2013 at 09:40:39AM -0400, Don Zickus wrote:
However, we still have the problem that if the machine panics and we want
to jump into the kdump kernel, we need to 'kick' the watchdog one more
time. This provides
On Tue, Apr 09, 2013 at 11:14:23AM -0400, Don Zickus wrote:
> On Tue, Apr 09, 2013 at 07:52:28AM -0700, Guenter Roeck wrote:
> > On Tue, Apr 09, 2013 at 10:44:31AM -0400, Don Zickus wrote:
> > > On Mon, Apr 08, 2013 at 08:15:09AM -0700, Guenter Roeck wrote:
> > > > On Mon, Apr 08, 2013 at
On Tue, Apr 09, 2013 at 07:52:28AM -0700, Guenter Roeck wrote:
> On Tue, Apr 09, 2013 at 10:44:31AM -0400, Don Zickus wrote:
> > On Mon, Apr 08, 2013 at 08:15:09AM -0700, Guenter Roeck wrote:
> > > On Mon, Apr 08, 2013 at 08:48:58AM -0400, Don Zickus wrote:
> > > > On Mon, Apr 08, 2013 at
On Tue, Apr 09, 2013 at 10:44:31AM -0400, Don Zickus wrote:
> On Mon, Apr 08, 2013 at 08:15:09AM -0700, Guenter Roeck wrote:
> > On Mon, Apr 08, 2013 at 08:48:58AM -0400, Don Zickus wrote:
> > > On Mon, Apr 08, 2013 at 01:46:58PM +0800, Dave Young wrote:
> > > > On 04/06/2013 04:16 AM, Don Zickus
On Mon, Apr 08, 2013 at 08:15:09AM -0700, Guenter Roeck wrote:
> On Mon, Apr 08, 2013 at 08:48:58AM -0400, Don Zickus wrote:
> > On Mon, Apr 08, 2013 at 01:46:58PM +0800, Dave Young wrote:
> > > On 04/06/2013 04:16 AM, Don Zickus wrote:
> > > > A common problem with kdump is that during the boot
On Mon, Apr 08, 2013 at 08:15:09AM -0700, Guenter Roeck wrote:
On Mon, Apr 08, 2013 at 08:48:58AM -0400, Don Zickus wrote:
On Mon, Apr 08, 2013 at 01:46:58PM +0800, Dave Young wrote:
On 04/06/2013 04:16 AM, Don Zickus wrote:
A common problem with kdump is that during the boot up of the
On Tue, Apr 09, 2013 at 10:44:31AM -0400, Don Zickus wrote:
On Mon, Apr 08, 2013 at 08:15:09AM -0700, Guenter Roeck wrote:
On Mon, Apr 08, 2013 at 08:48:58AM -0400, Don Zickus wrote:
On Mon, Apr 08, 2013 at 01:46:58PM +0800, Dave Young wrote:
On 04/06/2013 04:16 AM, Don Zickus wrote:
On Tue, Apr 09, 2013 at 07:52:28AM -0700, Guenter Roeck wrote:
On Tue, Apr 09, 2013 at 10:44:31AM -0400, Don Zickus wrote:
On Mon, Apr 08, 2013 at 08:15:09AM -0700, Guenter Roeck wrote:
On Mon, Apr 08, 2013 at 08:48:58AM -0400, Don Zickus wrote:
On Mon, Apr 08, 2013 at 01:46:58PM +0800,
On Tue, Apr 09, 2013 at 11:14:23AM -0400, Don Zickus wrote:
On Tue, Apr 09, 2013 at 07:52:28AM -0700, Guenter Roeck wrote:
On Tue, Apr 09, 2013 at 10:44:31AM -0400, Don Zickus wrote:
On Mon, Apr 08, 2013 at 08:15:09AM -0700, Guenter Roeck wrote:
On Mon, Apr 08, 2013 at 08:48:58AM -0400,
On Mon, Apr 08, 2013 at 08:48:58AM -0400, Don Zickus wrote:
> On Mon, Apr 08, 2013 at 01:46:58PM +0800, Dave Young wrote:
> > On 04/06/2013 04:16 AM, Don Zickus wrote:
> > > A common problem with kdump is that during the boot up of the
> > > second kernel, the hardware watchdog times out and
On Mon, Apr 08, 2013 at 01:46:58PM +0800, Dave Young wrote:
> On 04/06/2013 04:16 AM, Don Zickus wrote:
> > A common problem with kdump is that during the boot up of the
> > second kernel, the hardware watchdog times out and reboots the
> > machine before a vmcore can be captured.
> >
> > Instead
On Mon, Apr 08, 2013 at 01:46:58PM +0800, Dave Young wrote:
On 04/06/2013 04:16 AM, Don Zickus wrote:
A common problem with kdump is that during the boot up of the
second kernel, the hardware watchdog times out and reboots the
machine before a vmcore can be captured.
Instead of
On Mon, Apr 08, 2013 at 08:48:58AM -0400, Don Zickus wrote:
On Mon, Apr 08, 2013 at 01:46:58PM +0800, Dave Young wrote:
On 04/06/2013 04:16 AM, Don Zickus wrote:
A common problem with kdump is that during the boot up of the
second kernel, the hardware watchdog times out and reboots the
On 04/06/2013 04:16 AM, Don Zickus wrote:
> A common problem with kdump is that during the boot up of the
> second kernel, the hardware watchdog times out and reboots the
> machine before a vmcore can be captured.
>
> Instead of tellling customers to disable their hardware watchdog
> timers, I
On 04/06/2013 04:16 AM, Don Zickus wrote:
A common problem with kdump is that during the boot up of the
second kernel, the hardware watchdog times out and reboots the
machine before a vmcore can be captured.
Instead of tellling customers to disable their hardware watchdog
timers, I hacked
37 matches
Mail list logo
