Hi Guenter,
> > Only when you set the .parent field in the watchdog_device data you will
> > get the
> > referal in the /sys/class/... tree. In iTCO_wdt.c you have the following
> > code
> > that does that: iTCO_wdt_watchdog_dev.parent = dev->dev.parent;
> >
> > From the watchdog-kernel-api doc
Hi Guenter,
> > Only when you set the .parent field in the watchdog_device data you will
> > get the
> > referal in the /sys/class/... tree. In iTCO_wdt.c you have the following
> > code
> > that does that: iTCO_wdt_watchdog_dev.parent = dev->dev.parent;
> >
> > From the watchdog-kernel-api doc
On Mon, May 27, 2013 at 09:16:18PM +0200, Wim Van Sebroeck wrote:
> Hi Guenter,
>
> > > Hi Guenter,
> > >
> > > Is there an easy way to determine which driver is loaded for each
> > > /dev/watchdogN device (from a script perspective).
> > >
> > > Basically, I wanted to determine the module that
On Mon, May 27, 2013 at 09:16:18PM +0200, Wim Van Sebroeck wrote:
> Hi Guenter,
>
> > > Hi Guenter,
> > >
> > > Is there an easy way to determine which driver is loaded for each
> > > /dev/watchdogN device (from a script perspective).
> > >
> > > Basically, I wanted to determine the module that
Hi Guenter,
> > Hi Guenter,
> >
> > Is there an easy way to determine which driver is loaded for each
> > /dev/watchdogN device (from a script perspective).
> >
> > Basically, I wanted to determine the module that needs to be included in
> > the kdump initrd image.
> >
> Sometimes. For example
On Wed, Apr 24, 2013 at 10:42:26AM -0400, Don Zickus wrote:
> On Thu, Apr 18, 2013 at 07:54:13AM -0700, Guenter Roeck wrote:
> > > No, that will probably work. It is my misunderstanding. Is there a
> > > common way to check the timeout length and the ping frequency?
> > >
> > Usually it is confi
On Thu, Apr 18, 2013 at 07:54:13AM -0700, Guenter Roeck wrote:
> > No, that will probably work. It is my misunderstanding. Is there a
> > common way to check the timeout length and the ping frequency?
> >
> Usually it is configured in /etc/watchdog.conf if the watchdog package
> is installed. Th
Don Zickus writes:
> On Thu, Apr 18, 2013 at 09:35:05AM -0700, Eric W. Biederman wrote:
>> Don Zickus writes:
>>
>> > 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.
>
On Thu, Apr 18, 2013 at 09:35:05AM -0700, Eric W. Biederman wrote:
> Don Zickus writes:
>
> > 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 c
Don Zickus writes:
> 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 up a hook to put i
On Thu, Apr 18, 2013 at 09:52:57AM -0400, Don Zickus wrote:
> On Thu, Apr 18, 2013 at 06:49:04AM -0700, Guenter Roeck wrote:
> > On Thu, Apr 18, 2013 at 09:00:09AM -0400, Don Zickus wrote:
> > > On Wed, Apr 17, 2013 at 02:49:59PM -0700, Eric W. Biederman wrote:
> > > > Don Zickus writes:
> > > >
On Thu, Apr 18, 2013 at 06:49:04AM -0700, Guenter Roeck wrote:
> On Thu, Apr 18, 2013 at 09:00:09AM -0400, Don Zickus wrote:
> > On Wed, Apr 17, 2013 at 02:49:59PM -0700, Eric W. Biederman wrote:
> > > Don Zickus writes:
> > >
> > > > A common problem with kdump is that during the boot up of the
On Thu, Apr 18, 2013 at 09:00:09AM -0400, Don Zickus wrote:
> On Wed, Apr 17, 2013 at 02:49:59PM -0700, Eric W. Biederman wrote:
> > Don Zickus writes:
> >
> > > A common problem with kdump is that during the boot up of the
> > > second kernel, the hardware watchdog times out and reboots the
> >
On Wed, Apr 17, 2013 at 02:49:59PM -0700, Eric W. Biederman wrote:
> Don Zickus writes:
>
> > 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 c
On Wed, Apr 17, 2013 at 02:49:59PM -0700, Eric W. Biederman wrote:
> Don Zickus writes:
>
> > 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 c
Don Zickus writes:
> 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 up a hook to put i
On Wed, Apr 17, 2013 at 05:19:56PM -0400, 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 watchd
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 up a hook to put in the kdump path that provides
o
18 matches
Mail list logo
