mldonkey-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: spiralvoice
Subject: [Mldonkey-bugs] [bugs #5100] mlnet causes kernel panic
Date: Tue, 02 Dec 2003 14:20:15 -0500
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.5) Gecko/20031007

This mail is an automated notification from the bugs tracker
 of the project: mldonkey, a free e-Donkey client.

/**************************************************************************/
[bugs #5100] Latest Modifications:

Changes by: 
                spiralvoice <address@hidden>
'Date: 
                Tue 12/02/2003 at 20:20 (Europe/Berlin)

            What     | Removed                   | Added
---------------------------------------------------------------------------
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
This patch report is old. If the bug still exists in current

versions please post a new bug report - spiralvoice






/**************************************************************************/
[bugs #5100] Full Item Snapshot:

URL: <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=5100>
Project: mldonkey, a free e-Donkey client
Submitted by: None
On: Sat 09/06/2003 at 14:53

Category:  Core
Severity:  5 - Average
Item Group:  None
Resolution:  None
Assigned to:  None
Status:  Closed
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: Tue 12/02/2003 at 20:20       By: spiralvoice
This patch report is old. If the bug still exists in current

versions please post a new bug report - spiralvoice

-------------------------------------------------------
Date: Mon 10/20/2003 at 17:18       By: pilot1
I've upgraded to the 2.6.0-test8 kernel and mlnet now runs fine. 

It may have been a problem with the RedHat kernel, as the stock kernel had some 
strange configuration options.

-------------------------------------------------------
Date: Mon 10/20/2003 at 10:17       By: None
* check your hardware

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





-------------------------------------------------------
Date: Sun 09/14/2003 at 00: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: Sat 09/13/2003 at 21: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: Sat 09/13/2003 at 19: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.






File Attachments
-------------------

-------------------------------------------------------
Date: Sat 09/06/2003 at 14:53  Name: messages.  Size: 109KB   By: pilot1
var-log-messages
http://savannah.nongnu.org/bugs/download.php?item_id=5100&amp;item_file_id=637






For detailed info, follow this link:
<http://savannah.nongnu.org/bugs/?func=detailitem&item_id=5100>

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





reply via email to

[Prev in Thread] Current Thread [Next in Thread]