Opened 10 years ago

Closed 10 years ago

#3845 closed Bug (worksforme)

Kernel problem with Transmission

Reported by: lonk Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.13
Severity: Normal Keywords:
Cc:

Description (last modified by charles)

I've build the last transmission on Debian Lenny and I get this error just after the launch of transmission. It come on my console.

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376] Oops: 0000 [#2] SMP 

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376] Process transmission-da (pid: 1811, ti=f1c70000 task=f78aa660 task.ti=f1c70000)

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376] Stack: 00000004 c015d9ad c18e1900 c0164cab 00c71f54 ffffffff 00000000 0000000e 

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376]        00000000 c18e1900 c1800f80 c181ea00 c171a600 c1eaf760 c1748da0 c1c2f080 

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376]        c1cec340 c1e21bc0 c1bac8a0 c1ac3740 c1789380 c1ee4c60 c18218c0 00000004 

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376] Call Trace:

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376]  [<c015d9ad>] unlock_page+0x19/0x23

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376]  [<c0164cab>] __invalidate_mapping_pages+0x8c/0xdf

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376]  [<c0164d05>] invalidate_mapping_pages+0x7/0x9

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376]  [<c01607e7>] sys_fadvise64_64+0x17f/0x19b

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376]  [<c0108857>] sysenter_past_esp+0x78/0xb1

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376]  =======================

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376] Code: c1 eb 1e 69 db c0 0a 00 00 81 c3 40 88 36 c0 2b 8b a8 0a 00 00 d3 e8 6b c0 0c 03 83 a0 0a 00 00 5b c3 53 89 c3 83 ec 08 8d 40 04 <39> 43 04 89 14 24 89 4c 24 04 74 15 89 e0 b9 01 00 00 00 50 ba 

Message from syslogd@my at Dec 22 12:14:51 ...
 kernel:[912334.494376] EIP: [<c0138815>] __wake_up_bit+0x9/0x2e SS:ESP 0068:f1c71f24

More info from /var/log/syslog:

Dec 22 12:14:51 my kernel: [912334.494376] Pid: 1811, comm: transmission-da Tainted: G      D   (2.6.26-2-686-bigmem #1)
Dec 22 12:14:51 my kernel: [912334.494376] EIP: 0060:[<c0138815>] EFLAGS: 00210286 CPU: 0
Dec 22 12:14:51 my kernel: [912334.494376] EIP is at __wake_up_bit+0x9/0x2e
Dec 22 12:14:51 my kernel: [912334.494376] EAX: 86a92c04 EBX: 86a92c00 ECX: 00000000 EDX: c18e1900
Dec 22 12:14:51 my kernel: [912334.494376] ESI: 00000000 EDI: 00008ed4 EBP: f05c036c ESP: f1c71f24
Dec 22 12:14:51 my kernel: [912334.494376]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Dec 22 12:14:51 my kernel: [912334.494376] Process transmission-da (pid: 1811, ti=f1c70000 task=f78aa660 task.ti=f1c70000)
Dec 22 12:14:51 my kernel: [912334.494376] Stack: 00000004 c015d9ad c18e1900 c0164cab 00c71f54 ffffffff 00000000 0000000e 
Dec 22 12:14:51 my kernel: [912334.494376]        00000000 c18e1900 c1800f80 c181ea00 c171a600 c1eaf760 c1748da0 c1c2f080 
Dec 22 12:14:51 my kernel: [912334.494376]        c1cec340 c1e21bc0 c1bac8a0 c1ac3740 c1789380 c1ee4c60 c18218c0 00000004 
Dec 22 12:14:51 my kernel: [912334.494376] Call Trace:
Dec 22 12:14:51 my kernel: [912334.494376]  [<c015d9ad>] unlock_page+0x19/0x23
Dec 22 12:14:51 my kernel: [912334.494376]  [<c0164cab>] __invalidate_mapping_pages+0x8c/0xdf
Dec 22 12:14:51 my kernel: [912334.494376]  [<c0164d05>] invalidate_mapping_pages+0x7/0x9
Dec 22 12:14:51 my kernel: [912334.494376]  [<c01607e7>] sys_fadvise64_64+0x17f/0x19b
Dec 22 12:14:51 my kernel: [912334.494376]  [<c0108857>] sysenter_past_esp+0x78/0xb1
Dec 22 12:14:51 my kernel: [912334.494376]  =======================
Dec 22 12:14:51 my kernel: [912334.494376] Code: c1 eb 1e 69 db c0 0a 00 00 81 c3 40 88 36 c0 2b 8b a8 0a 00 00 d3 e8 6b c0 0c 03 83 a0 0a 00 00 5b c3 53 89 c3 83 ec 08 8d 40 04 <39> 43 04 89 14 24 89 4c 24 04 74 15 89 e0 b9 01 00 00 00 50 ba 
Dec 22 12:14:51 my kernel: [912334.494376] EIP: [<c0138815>] __wake_up_bit+0x9/0x2e SS:ESP 0068:f1c71f24
Dec 22 12:14:51 my kernel: [912334.494376] ---[ end trace 35c98775191f6640 ]---

By the way, it's boring to have to register just to post a bug... Now I have to find how to unregister this shit.

Change History (7)

comment:1 Changed 10 years ago by charles

  • Description modified (diff)

comment:2 Changed 10 years ago by charles

do you have a gdb backtrace to show this too? It would be helpful to see what's going on in Transmission when this happens.

comment:3 Changed 10 years ago by lonk

% gdb --args /opt/transmission/bin/transmission-daemon --config-dir /opt/transmission/conf -e /home/dl/transmission.log --log-error --log-info --log-debug
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(gdb) r
Starting program: /opt/transmission/bin/transmission-daemon --config-dir /opt/transmission/conf -e /home/dl/transmission.log --log-error --log-info --log-debug
[Thread debugging using libthread_db enabled]

Program exited normally.
(gdb)

comment:4 Changed 10 years ago by lonk

I don't want to receive any mail from trac. Since it's seems not possible to configure it in this way, I'll delete my account. Good luck. PS: Please stop releasing your configure script with -g and -ggdb3 since it's useless.

EDIT: lol I also receive mails from trac when I post a comment! Thanks!

Last edited 10 years ago by lonk (previous) (diff)

comment:5 Changed 10 years ago by charles

I'm not sure how I'm supposed to connect what part of Transmission's code is being called, and under what circumstances, when this kernel warning happens. gdb isn't reporting anything at all, and syslog's call trace doesn't walk backwards into the userspace transmission code, and 2.6.26 is pretty old. Do you have any information that would connect these syslog messages back to a transmission backtrace?

(Also, -g and -ggdb3 are thrown into the test builds for debugging purposes, but not in the supported releases. I'm not sure why against this, or what it has to do with this ticket...?)

comment:6 Changed 10 years ago by charles

I'd like to figure out what's causing this, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

comment:7 Changed 10 years ago by livings124

  • Resolution set to worksforme
  • Status changed from new to closed

This ticket needs more info, and lonk has deleted his account. Please reopen with more information.

Note: See TracTickets for help on using tickets.