Topic: Kernal Panic Error

[sal1504]

The last couple of mornings the smeserver has had an error on the screen. The error is:
 
Kernal_panic - not syncing:fs/jbd/transaction.c:980 spin_lock (fs/jbd/journal.c:f7e94f74) already locked by fs/jbd/comintit.c /249

Hardware configuration is Intel e5200 processor with 4gb of ram, three - 250gb hard drives in a raid 1 with spare - two 10/100 nics, Quantum AIT tape drive. Smeserver 7.4 running in a server/gateway mode. Standard Smeserver with Sarg running. There is also a windows 2008 server attached to the network backing up to the smeserver.
 

Anyone know what this means? I am not sure which log I would find more information in.

Sal

[CharlieBrady]

The last couple of mornings the smeserver has had an error on the screen. The error is:
 
Kernal_panic - not syncing:fs/jbd/transaction.c:980 spin_lock (fs/jbd/journal.c:f7e94f74) already locked by fs/jbd/comintit.c /249
...
Anyone know what this means?

It's a linux kernel bug. Or, less likely IMO, signs of a hardware fault (e.g. RAM).

You do know that you are told this whenever you post on this forum:

 Don't report problems here - Please report bugs and potential bugs in the bug tracker

Do you not consider "kernel panic error" a problem?

[sal1504]

Charlie

Duh!!! I know it's a linux kernal error and i know its a problem or else i wouldn't have posted this. the information i was looking for is where in the logs can i find out more information on if it's a memory error or a hard drive error or a software error. Everything was working fine until the client load new software on the 2008 server. everything has ran fine for several months. is there any possible way the application loaded on the 2008 domain server can affect the smeserver and if so how. it's hard to report bugs when your not sure what is going on and the forum is the only place to post to determine whether the error needs to be reported as a bug or if there is something else going on.

sal

[Stefano]

you say that the problem arise after your client load a new software on w2008 machine..

how the w2008 machine interacts with SME? does it write on SME's shares?

in any case, this is OT in this forum IMO fot 2 reasons:
- if is a kernel problem, it should be reported in bugzilla or directly upstream
- if is something wrong with a w2008 sw, it's not a SME's issue

my 2c

P.S. If Charlie agrees, I will ask the moderatos to move this topic to "general discussions"

[CharlieBrady]

in any case, this is OT in this forum IMO fot 2 reasons:
- if is a kernel problem, it should be reported in bugzilla or directly upstream
- if is something wrong with a w2008 sw, it's not a SME's issue

It doesn't matter what w2008 does wrong, linux kernel should not panic.

P.S. If Charlie agrees, I will ask the moderatos to move this topic to "general discussions"

No, only place to report a linux kernel panic is in the bug tracker.

[CharlieBrady]

the forum is the only place to post to determine whether the error needs to be reported as a bug

You are wrong. Any "problem" is a potential bug, and should be reported in the bug tracker.

[sal1504]

explain this one to me

the kernal panic error i was receiving was apparently caused by a corrupt registry on a Windows XP workstation. We were able to duplicate the error.

1. We shut down all computers including file servers on the network.
2. We then brought up all the file servers without any issues.
3. We brought up the workstations one at a time. On the forth workstations we got the kernal panic error. We pulled the computer off the network and replaced it with a different workstation and started the procedure over. This time every computer came up without the kernal panic error.
4. We placed the workstation that gave the error back on the network and once again we got the kernal panic error.
5. To troubleshoot the workstation we took it off the network and ran it through the usual software tests (malwarebytes, avg, etc.). There were no threats detected. Hooked the workstation backup to the network and got the kernal panic error.
6. Once again took the workstation off the network and reset the registry to a date previous to the date we started having problems.
Set the workstation back on the network and everything worked fine.

Conclusion is that something in the registry of this workstation was causing the SMEServer to throw a kernal panic error. Any thoughts on way this might happen?

Sal

[Stefano]

do you have roaming profiles enabled?

[CharlieBrady]

the kernal panic error i was receiving was apparently caused by a corrupt registry on a Windows XP workstation.

No, what caused it was a linux kernel bug (probably a file system deadlock bug). What provoked it was perhaps some pattern of network and/or hard drive I/O which occurred under the circumstances you mention.

If you post a full bug report in the bug tracker we might be able to match the panic backtrace to a bug which Red Hat will fix.
Stop wasting your time and mine and open a bug report.

[sal1504]

Stefano
No the roaming profiles are turned off

CharlieBrady
I will post this in the bug tracker but since it is up and working there is no rush on this. I do find it interesting that cleaning the registry on the XP machine fix the problem.

Thanks for the help

Sal

[electroman00]

http://bugs.contribs.org/show_bug.cgi?id=139

#139 not fixed in 7.4 or 8.0

Just don't hold your breath.

So easy even a gaveman can do it...

I'm not a gaveman so....

That leaves me out.

[Stefano]

http://bugs.contribs.org/show_bug.cgi?id=139
#139 not fixed in 7.4 or 8.0
Just don't hold your breath.
So easy even a gaveman can do it...
I'm not a gaveman so....
That leaves me out.

electroman00: your post is OT in this topic and doesn't add anything worth to be remembered..

so.. can you please stop with this attitude?

instead of wasting our (and your) time to write such a post, please spend some time to help developers, thank you