On Wed, Apr 03, 2013 at 08:50:26AM -0700, Guenter Roeck wrote:
> On Wed, Apr 03, 2013 at 08:06:59AM -0700, Tony Chung wrote:
> > On Tue, Apr 2, 2013 at 9:21 PM, Guenter Roeck wrote:
> >
> > >
> > >
> > > What is the exact chip type in your system ? I want to have a look into
> > > the
> > >
On Wed, Apr 03, 2013 at 08:06:59AM -0700, Tony Chung wrote:
> On Tue, Apr 2, 2013 at 9:21 PM, Guenter Roeck wrote:
>
> >
> >
> > What is the exact chip type in your system ? I want to have a look into the
> > datasheet; maybe I can find out how it can trigger without causing a reset.
>
>
On Tue, Apr 2, 2013 at 9:21 PM, Guenter Roeck wrote:
>
>
> What is the exact chip type in your system ? I want to have a look into the
> datasheet; maybe I can find out how it can trigger without causing a reset.
Winbond 83627HF chip
I believe BIOS has watchdog disabled otherwise it would have
On Tue, Apr 2, 2013 at 9:21 PM, Guenter Roeck li...@roeck-us.net wrote:
What is the exact chip type in your system ? I want to have a look into the
datasheet; maybe I can find out how it can trigger without causing a reset.
Winbond 83627HF chip
I believe BIOS has watchdog disabled otherwise
On Wed, Apr 03, 2013 at 08:06:59AM -0700, Tony Chung wrote:
On Tue, Apr 2, 2013 at 9:21 PM, Guenter Roeck li...@roeck-us.net wrote:
What is the exact chip type in your system ? I want to have a look into the
datasheet; maybe I can find out how it can trigger without causing a reset.
On Wed, Apr 03, 2013 at 08:50:26AM -0700, Guenter Roeck wrote:
On Wed, Apr 03, 2013 at 08:06:59AM -0700, Tony Chung wrote:
On Tue, Apr 2, 2013 at 9:21 PM, Guenter Roeck li...@roeck-us.net wrote:
What is the exact chip type in your system ? I want to have a look into
the
On Mon, Apr 01, 2013 at 09:59:00PM -0700, Tony Chung wrote:
> Thanks Guenter!
> I agree with you. My first reaction was also about a small watchdog
> server that will start in early boot process. There are pros and
> cons. For example, there are many types of watchdog devices such as
>
On Mon, Apr 01, 2013 at 09:59:00PM -0700, Tony Chung wrote:
Thanks Guenter!
I agree with you. My first reaction was also about a small watchdog
server that will start in early boot process. There are pros and
cons. For example, there are many types of watchdog devices such as
Thanks Guenter!
I agree with you. My first reaction was also about a small watchdog
server that will start in early boot process. There are pros and
cons. For example, there are many types of watchdog devices such as
ipmi_watchdog which can accept more than 255 seconds for timeout. So
you
On Sun, Mar 31, 2013 at 10:59:32PM -0700, Tony Chung wrote:
> Observed that the w83627hf watchdog timer start counting during reboot.
> If the system load the driver after 5 minutes, it rebooted immediately
> because of timer expired.
> For example, fsck took more than 5 minutes to run, then the
Observed that the w83627hf watchdog timer start counting during reboot.
If the system load the driver after 5 minutes, it rebooted immediately because
of timer expired.
For example, fsck took more than 5 minutes to run, then the computer reboot as
soon as the driver was loaded.
Signed-off-by:
Observed that the w83627hf watchdog timer start counting during reboot.
If the system load the driver after 5 minutes, it rebooted immediately because
of timer expired.
For example, fsck took more than 5 minutes to run, then the computer reboot as
soon as the driver was loaded.
Signed-off-by:
On Sun, Mar 31, 2013 at 10:59:32PM -0700, Tony Chung wrote:
Observed that the w83627hf watchdog timer start counting during reboot.
If the system load the driver after 5 minutes, it rebooted immediately
because of timer expired.
For example, fsck took more than 5 minutes to run, then the
Thanks Guenter!
I agree with you. My first reaction was also about a small watchdog
server that will start in early boot process. There are pros and
cons. For example, there are many types of watchdog devices such as
ipmi_watchdog which can accept more than 255 seconds for timeout. So
you
14 matches
Mail list logo
