wierd error on kern.log (I think it could be a rt61 bug)

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4424

ferrazrafael

09-11-2007 22:26:26

kern.log i receive this error message

/var/log/kern.log

Nov 9 070654 barton2800 kernel ------------[ cut here ]------------
Nov 9 070654 barton2800 kernel kernel BUG at include/linux/timer.h153!
Nov 9 070654 barton2800 kernel invalid opcode 0000 [#1]
Nov 9 070654 barton2800 kernel SMP
Nov 9 070654 barton2800 kernel Modules linked in ipv6 isofs udf ppdev lp button ac battery cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats cpufreq_ondemand freq_table nls_utf8 ntfs dm_snapshot dm_mirror dm_mod snd_pcm_oss snd_mixer_oss w83l785ts asb100 hwmon_vid eeprom loop nvidiafb fb_ddc i2c_algo_bit vgastate rt61 snd_mpu401 snd_mpu401_uart firmware_class parport_pc parport ns558 snd_rawmidi snd_seq_device nvidia(P) gameport rtc_cmos rtc_core rtc_lib snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_timer snd soundcore shpchp pci_hotplug snd_page_alloc i2c_nforce2 i2c_core nvidia_agp agpgart tsdev evdev ext3 jbd mbcache ide_cd cdrom ide_disk ata_generic libata scsi_mod usbhid hid amd74xx floppy generic ide_core forcedeth ehci_hcd ohci_hcd usbcore thermal processor fan
Nov 9 070654 barton2800 kernel CPU 0
Nov 9 070654 barton2800 kernel EIP 0060[<e10f34b9>] Tainted P VLI
Nov 9 070654 barton2800 kernel EFLAGS 00010282 (2.6.22-3-k7 #1)
Nov 9 070654 barton2800 kernel EIP is at LinkDown+0xf7/0x35b [rt61]
Nov 9 070654 barton2800 kernel eax de8c9190 ebx de8c0000 ecx 00000000 edx 00000068
Nov 9 070654 barton2800 kernel esi de8c94a4 edi de8c94c6 ebp 00000000 esp d8403bf8
Nov 9 070654 barton2800 kernel ds 007b es 007b fs 00d8 gs 0033 ss 0068
Nov 9 070654 barton2800 kernel Process NetworkManager (pid 3496, ti=d8402000 task=d9141a90 task.ti=d8402000)
Nov 9 070654 barton2800 kernel Stack def36800 de8c0000 def36800 00000000 e10eb67c def36800 00011042 00001003
Nov 9 070654 barton2800 kernel c024b4be def36800 c024a9a8 cec355b0 ffffffed 00000000 def36800 c0252875
Nov 9 070654 barton2800 kernel 00000000 c02bf3e0 cec355b0 00000000 00000000 00000000 00000000 00000000
Nov 9 070654 barton2800 kernel Call Trace
Nov 9 070654 barton2800 kernel [<e10eb67c>] rt61_close+0x14/0xe9 [rt61]
Nov 9 070654 barton2800 kernel [<c024b4be>] dev_close+0x4b/0x67
Nov 9 070654 barton2800 kernel [<c024a9a8>] dev_change_flags+0x4d/0xfb
Nov 9 070654 barton2800 kernel [<c0252875>] rtnl_setlink+0x298/0x3ad
Nov 9 070654 barton2800 kernel [<c0167758>] cache_alloc_refill+0x62/0x482
Nov 9 070654 barton2800 kernel [<c02525dd>] rtnl_setlink+0x0/0x3ad
Nov 9 070654 barton2800 kernel [<c0252078>] rtnetlink_rcv_msg+0x1a1/0x1bb
Nov 9 070654 barton2800 kernel [<c025eae2>] netlink_run_queue+0x5c/0xd2
Nov 9 070654 barton2800 kernel [<c0251ed7>] rtnetlink_rcv_msg+0x0/0x1bb
Nov 9 070654 barton2800 kernel [<c0251e96>] rtnetlink_rcv+0x25/0x3d
Nov 9 070654 barton2800 kernel [<c025ef48>] netlink_data_ready+0x12/0x4c
Nov 9 070654 barton2800 kernel [<c025defc>] netlink_sendskb+0x19/0x30
Nov 9 070654 barton2800 kernel [<c025ef2a>] netlink_sendmsg+0x267/0x273
Nov 9 070654 barton2800 kernel [<c024184f>] sock_sendmsg+0xd0/0xeb
Nov 9 070654 barton2800 kernel [<c01333b1>] autoremove_wake_function+0x0/0x35
Nov 9 070654 barton2800 kernel [<c01333b1>] autoremove_wake_function+0x0/0x35
Nov 9 070654 barton2800 kernel [<c02419fc>] sys_sendmsg+0x192/0x1f7
Nov 9 070654 barton2800 kernel [<c0242394>] sys_recvmsg+0x1b9/0x1cd
Nov 9 070654 barton2800 kernel [<c025e157>] netlink_insert+0x10f/0x119
Nov 9 070654 barton2800 kernel [<c015b98d>] __handle_mm_fault+0x8c5/0x95d
Nov 9 070654 barton2800 kernel [<c0242663>] sys_getsockname+0x9f/0xb0
Nov 9 070654 barton2800 kernel [<c02a861d>] _spin_lock_bh+0x8/0x18
Nov 9 070654 barton2800 kernel [<c0243360>] release_sock+0x12/0x8d
Nov 9 070654 barton2800 kernel [<c0244a09>] sock_setsockopt+0x4b7/0x4c1
Nov 9 070654 barton2800 kernel [<c018d121>] inotify_d_instantiate+0x41/0x66
Nov 9 070654 barton2800 kernel [<c0179683>] d_alloc+0x155/0x1a4
Nov 9 070654 barton2800 kernel [<c017952a>] d_instantiate+0x63/0x67
Nov 9 070654 barton2800 kernel [<c0242a68>] sys_socketcall+0x223/0x242
Nov 9 070654 barton2800 kernel [<c011ac6a>] do_page_fault+0x0/0x57e
Nov 9 070654 barton2800 kernel [<c0103d06>] sysenter_past_esp+0x6b/0xa1
Nov 9 070654 barton2800 kernel =======================
Nov 9 070654 barton2800 kernel Code 00 75 09 c6 83 cc 39 01 00 00 eb 2b a1 80 51 34 c0 05 c4 09 00 00 83 bb 90 91 00 00 00 89 83 98 91 00 00 8d 83 90 91 00 00 74 04 <0f> 0b eb fe 8b 50 08 e8 be 76 03 df 0f b6 8b 58 94 00 00 8d 93
Nov 9 070654 barton2800 kernel EIP [<e10f34b9>] LinkDown+0xf7/0x35b [rt61] SSESP 0068d8403bf8
Nov 9 071156 barton2800 kernel NVRM Xid (000200) 13, 0000 01013900 00000039 00000328 00000000 00000800
Nov 9 071800 barton2800 kernel Kernel logging (proc) stopped.
Nov 9 071800 barton2800 kernel Kernel log daemon terminating.

im using rt61-cvs-2007110612.

Im having trouble with network-manager (since I update NM im receiving apt-get error every thing i install.. maybe NM is causing this or vice-versa)
im using debian unstable 2.6.22-3

Vern

10-11-2007 20:59:57

Hi ferrazrafael,

Could you compile the driver with debug enabled, then run with debug=15?

If you have /etc/syslog.conf set up to also put debug messages into /var/log/kern.log, then please attach a gzipped copy of kern.log for whatever interval covers modprobe to rmmod to a posting here.

If not, then please attach a gzipped copy of /var/log/debug and your Oops info to a posting here.

The purpose of this exercise is to try to find out how far along in LinkDown() we get.

I'll take a look at what you provide.

Thanks,

ferrazrafael

11-11-2007 23:34:33

how i configure the syslog.conf what i change?

here is the logs

Vern

19-11-2007 02:29:15

Hi ferrazrafael,

I'm afraid I dropped the ball somewhat, here. From the log info you've provided, it looks like your syslog.conf is set up just fine.

Anyway, the attached patch addresses an omission in dma buf allocation exception handling, and also provides a little more debug info.

Could you apply it to a vanilla copy of the latest CVS and attach a copy of thee resulting log file to a posting here?

Thanks,

ferrazrafael

20-11-2007 23:07:24

how I apply this patch? isnt safer you post one driver patched?

Vern

21-11-2007 17:44:08

Hi ferrazrafael,

Its not really that bad
[code21ewaygk]1. Download the patch.
2. After you sign out, or before you sign in, click on the download tab at the top of the page; then download and untar the legacy rt61 driver.
3. 'cd <to Module subdirectory of untarred ball>'
4. 'zcat <downloaded patch file> | patch'
5. Do usual 'make clean debug' &c.[/code21ewaygk]

ferrazrafael

21-11-2007 18:48:07

here is the debug and kern.log

Vern

21-11-2007 20:36:28

Hi ferrazrafael,

Are you running with debug=15 (or debug=31)? If not please read the README and TESTING files & repost your logs.

Thanks,

ferrazrafael

22-11-2007 00:04:36

im runing with debug=15.. in testing file is saying to run with 31 but you said to run with 15 and i run 15.. is to run with 15 or 31?

ferrazrafael

22-11-2007 00:36:46

here is the log runing in debug=31

Vern

22-11-2007 01:54:50

Hi ferrazrafael,

Thanks for the extra effort. Very strange. I'm not seeing anything at all of what I would expect. Could you attach a copy of your /etc/syslog.conf to a post here?

In the meantime, I'll puzzle over the information I do have.

Thanks,

ferrazrafael

22-11-2007 10:59:27

[codev7k4cezw]# /etc/syslog.conf Configuration file for syslogd.
#
# For more information see syslog.conf(5)
# manpage.

#
# First some standard logfiles. Log by facility.
#

auth,authpriv.* /var/log/auth.log
*.*;auth,authpriv.none -/var/log/syslog
#cron.* /var/log/cron.log
daemon.* -/var/log/daemon.log
kern.* -/var/log/kern.log
lpr.* -/var/log/lpr.log
mail.* -/var/log/mail.log
user.* -/var/log/user.log

#
# Logging for the mail system. Split it up so that
# it is easy to write scripts to parse these files.
#
mail.info -/var/log/mail.info
mail.warn -/var/log/mail.warn
mail.err /var/log/mail.err

# Logging for INN news system
#
news.crit /var/log/news/news.crit
news.err /var/log/news/news.err
news.notice -/var/log/news/news.notice

#
# Some `catch-all' logfiles.
#
*.=debug;\
auth,authpriv.none;\
news.none;mail.none -/var/log/debug
*.=info;*.=notice;*.=warn;\
auth,authpriv.none;\
cron,daemon.none;\
mail,news.none -/var/log/messages

#
# Emergencies are sent to everybody logged in.
#
*.emerg *

#
# I like to have messages displayed on the console, but only on a virtual
# console I usually leave idle.
#
#daemon,mail.*;\
# news.=crit;news.=err;news.=notice;\
# *.=debug;*.=info;\
# *.=notice;*.=warn /dev/tty8

# The named pipe /dev/xconsole is for the `xconsole' utility. To use it,
# you must invoke `xconsole' with the `-file' option:
#
# $ xconsole -file /dev/xconsole [...]
#
# NOTE: adjust the list below, or you'll go crazy if you have a reasonably
# busy site..
#
daemon.*;mail.*;\
news.err;\
*.=debug;*.=info;\
*.=notice;*.=warn |/dev/xconsole
[/codev7k4cezw]

Vern

23-11-2007 18:44:11

Hi ferrazrafael,

Well, syslog.conf looks OK to me. I'll just have to puzzle along some more, I guess.

Thanks,

bhebing

02-12-2007 07:25:21

I have the same problem. When I bring the link down, this bug shows up in the syslog.

I'm using the daily-CVS from december 1 on a 2.6.22 ubuntu SMP kernel. Can I help with giving some more info? This bug is very annoying...

leon

02-12-2007 15:28:20

Hello,
Could the patch from Javispedro concerning "workaround the kernel bug by just checking timer_pending before add_timer" be a solution to your problem ?
see rt2x00.serialmonkey.com/phpBB2/viewtopic.php?t=4257

Vern

02-12-2007 19:06:30

Hi bhebing,

Yes. If you could compile with debug enabled and run with debug=31, then attach a gzipped copy of /var/log/kern.log to a posting here, that'd be good.

Thanks,