Kernel Panic (2.6.22-14-generic) with Deluge Torrent (0.5.4-1ubuntu3)

[Chow Loong Jin]

On Ubuntu Gutsy (now Beta, installation was done using Tribe 5), Deluge Torrent seems to be able to bring my system to a complete halt. Sound stops, Daemons stop, and all input is refused. I usually hit the reboot button immediately.

So, one fine day (today) I went and checked my syslog. Here's what I found:

Oct 12 15:51:30 Hyperair-PC kernel: [ 1906.640351] KERNEL: assertion (!atomic_read(&sk->sk_wmem_alloc)) failed at /build/buildd/linux-source-2.6.22-2.6.22/net/ipv4/af_inet.c (149)
Oct 12 15:55:33 Hyperair-PC syslogd 1.4.1#21ubuntu3: restart.

That's what it looks like every time this happens. First the assertion, then 4-5 minute later, the lockup. On a side note, my keyboard LEDs don't flash.

Now, I had my doubts that this is Deluge's fault. So, I went a few weeks without running Deluge (or any other torrent client). No problems. No lockups. Nothing. Just yesterday I let Deluge run overnight, and this morning, found my system with all the hard disks powered down, and completely hung.

EDIT: Same error with the version from the repository, but without the entry in syslog.

[Marco Rodrigues (gothicx)]

You're using a not supported version of deluge torrent. Current gutsy version is 0.5.4.1-1ubuntu3.

[Chow Loong Jin (hyperair)]

Ah yes, I know that. But the point here is.. How can a userspace application cause the kernel to grind to a halt? Surely that's an issue?

[Chow Loong Jin (hyperair)]

Ok, so I've tried using the version in the repository. The same thing happens, only a lot faster, and without the strange entry in syslog.

[Chow Loong Jin (hyperair)]

Tried the version in the Gutsy repository and it had problems as well.

[Adam Niedling (krychek)]

Any update on this bug?