[Mldonkey-bugs] [bug #5100] mlnet causes kernel panic

[nobody]

=================== BUG #5100: LATEST MODIFICATIONS ==================
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=5100&group_id=1409

Changes by: Anonymous user        Date: lun 20.10.2003 à 04:17

------------------ Additional Follow-up Comments ----------------------------
* check your hardware

* check the integrity of your filesystem(s) with fsck







=================== BUG #5100: FULL BUG SNAPSHOT ===================


Signalé par: pilot1                   Projet: mldonkey, a free e-Donkey client
Signalé le: sam 06.09.2003 à 08:53
Category:  Core                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         
Release:  2.00                        Release:  2.5-3                       
Platform Version:  Linux i386-i686    Binaries Origin:  Downloaded from Savannah

Summary:  mlnet causes kernel panic

Original Submission:  mlnet seems to periodically cause a kernel panic (not 
when booting, just at seemingly random times when the computer is already on), 
the computer is a XP1800/512mb RAM, and is running RedHat 9, kernel 2.4.20-8.

My /var/log/messages file is attached, you can find the text of the kernel 
panic inside it. Notice that it happens right after an SSH session to the 
computer is closed, could that be related? (In the log, it shows up as a "su", 
but I was logged in over SSH and I used "su" to gain root permissions.)

I rebooted the computer with the on/off switch  once I noticed the kernel 
panic, I left everything after the kernel panic in the log (the reboot is all 
there is, I think), in case that helps you with anythig.

Please fix this, MLdonkey is useless to me while this problem remains unfixed :)

Follow-up Comments
*******************

-------------------------------------------------------
Date: lun 20.10.2003 à 04:17        By: None
* check your hardware

* check the integrity of your filesystem(s) with fsck





-------------------------------------------------------
Date: sam 13.09.2003 à 18:08        By: Saubloed
Interesting. Maybe you should report it as a Kernel bug.

I have never done this - maybe its complicated. :)



http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html

-------------------------------------------------------
Date: sam 13.09.2003 à 15:44        By: pilot1
Well, I'm not running mlnet as root, and I'm getting a kernel panic within 6 
hours after starting it.



It may be a conflict with my hardware, but I have no idea what it would be 
conflicting with. I've tried compiling a new kernel, but it always fails during 
'make modules'

-------------------------------------------------------
Date: sam 13.09.2003 à 13:19        By: Saubloed
I think a program can only cause a kernel panic if you run it as root.

If you run mldonkey as root its your fault. Never run a program as root if you 
dont need it.



If you can make a Linux kernel panic with a program its a security hole.

Normally a damaged hardware causes a kernel panic and not the software.


La liste CC est vide


Fichiers attachés
****************

-------------------------------------------------------
Date: sam 06.09.2003 à 08:53  Name: messages.  Size: 109KB   By: pilot1
var-log-messages
http://savannah.nongnu.org/bugs/download.php?group_id=1409&bug_id=5100&bug_file_id=637


For detailed info, follow this link:
http://savannah.nongnu.org/bugs/?func=detailbug&bug_id=5100&group_id=1409

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/