bugmldonkey, a multi-networks file-sharing client - Bugs: bug #5100, mlnet causes kernel panic

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #5100: mlnet causes kernel panic

Submitter:  Invalid User ID <#22815>
Submitted:  Sat 06 Sep 2003 12:53:28 PM UTC
   
 
Category:  Core Severity:  3 - Normal
Item Group:  None Status:  None
Assigned to:  None Open/Closed:  Closed
Release:  2.00 Release:  2.5-3
Operating System:  Linux Binaries Origin:  Binary from Savannah
CPU type:  None

Jump to the original submission

Tue 02 Dec 2003 07:20:13 PM UTC, comment #6: 

This patch report is old. If the bug still exists in current
versions please post a new bug report - spiralvoice

spiralvoice <spiralvoice>
Group administrator
Mon 20 Oct 2003 03:18:45 PM UTC, comment #5: 

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.

Invalid User ID <#22815>
Mon 20 Oct 2003 08:17:25 AM UTC, comment #4: 
  • check your hardware
  • check the integrity of your filesystem(s) with fsck



Anonymous
Sat 13 Sep 2003 10:08:50 PM UTC, comment #3: 

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

Invalid User ID <#23091>
Sat 13 Sep 2003 07:44:43 PM UTC, comment #2: 

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'

Invalid User ID <#22815>
Sat 13 Sep 2003 05:19:36 PM UTC, comment #1: 

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.

Invalid User ID <#23091>
Sat 06 Sep 2003 12:53:28 PM UTC, 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 :)

Invalid User ID <#22815>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

 

Follows 1 latest change.

Date Changed by Updated Field Previous Value => Replaced by
2003-12-02 spiralvoice Open/ClosedOpen Closed

Back to the top

Powered by Savane 3.13-4b48.
Corresponding source code