| To: | Thomas Duffy <tduffy@xxxxxxxxx> |
|---|---|
| Subject: | Re: kernel panic (corruption of task struct) |
| From: | Stephen Lord <lord@xxxxxxx> |
| Date: | Mon, 11 Feb 2002 10:52:55 -0600 |
| Cc: | Linux Mailing List <linux-xfs@xxxxxxxxxxx> |
| References: | <1013222059.2794.35.camel@xxxxxxxxxxxxxxxxxxxx> <3C657C70.9050300@xxxxxxx> <1013313171.26982.4.camel@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011226 |
Thomas Duffy wrote: Should this actually be stack overflow, the tricky part is that the crash usually happens long after the overflow - when the corrupted task struct is accessed.On Sat, 2002-02-09 at 11:45, Stephen Lord wrote:Stack overflow looks likely here. I don't know of any in xfs, but xfs in combination with other things might cause problems. We had one case in LVM snapshotting where LVM was putting large chunks of stuff on the stack. That code should not be in yourkernel though, unless you added it.This is a stock xfs kernel rpm 1.0.2 from sgi. No recompile, no addons -- we are not using lvm on this machine, anyways. Any suggestions on how to figure out what is going on here? Cause this is on a critical machine and having it go down every few days is not good... If it goes down again, is there anything I can do in kdb to help narrow down where this is happening? Thanks! -tduffy The one of these we found in LVM took a long time to locate. All I can suggest right now is updating your kernel. Steve |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | best kernel version to use with XFS+LVM+MD, mai99bxd |
|---|---|
| Next by Date: | TAKE - merge up to 2.5.4, Steve Lord |
| Previous by Thread: | Re: kernel panic (corruption of task struct), Thomas Duffy |
| Next by Thread: | How to undelete a file?, Friedrisch Muller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |