| 1 |
On March 14, 2012 at 2:41 PM "ZHANG, Le" <r0bertz@g.o> wrote: |
| 2 |
|
| 3 |
> On Wed, Mar 14, 2012 at 11:23 AM, Jarry <mr.jarry@×××××.com> wrote: |
| 4 |
> |
| 5 |
> > Hi, |
| 6 |
> > |
| 7 |
> > my question might seem silly, but I have reason for it: |
| 8 |
> > I have heard there is way to auto-reboot linux after kernel |
| 9 |
> > panic using "kernel.panic=<time>" in /etc/sysctl.conf. |
| 10 |
> > |
| 11 |
> > This might come handy as my server is far from me and I do |
| 12 |
> > not have any remote console. But I would like to test it |
| 13 |
> > and see if it works (first on my desktop). |
| 14 |
> > |
| 15 |
> > So my question is: Can I somehow deliberately trigger |
| 16 |
> > "kernel panic" (or "kernel oops")? |
| 17 |
> |
| 18 |
> |
| 19 |
> For panic, echo c > /proc/sysrq-trigger |
| 20 |
> |
| 21 |
> -- |
| 22 |
> Zhang Le, Robert |
| 23 |
> Gentoo/Loongson(龙芯) Developer |
| 24 |
> http://zhangle.is-a-geek.org |
| 25 |
|
| 26 |
|
| 27 |
Nasty way to do it, but I thought that should be: |
| 28 |
|
| 29 |
echo b > / proc / sysrq-trigger |
| 30 |
|
| 31 |
Isn't b for reboot? |
| 32 |
-- |
| 33 |
Happy Penguin Computers >`) |
| 34 |
126 Fenco Drive ( \ |
| 35 |
Tupelo, MS 38801 ^^ |
| 36 |
662-269-2706; 662-491-8613 |
| 37 |
support at happypenguincomputers dot com |
| 38 |
http://www.happypenguincomputers.com |
Archives