The problem you're describing may be fixed in cvs20080402xx and later. Could you try the latest CVS tarball and see if you're still "scheduling atomic"?
If you are, please compile with debug enabled, and attach a gzipped copy of /var/log/kern.log to a post in this thread, if possible.
Thanks for your response. I downloaded and compiled the cvs tarball. Everything worked fine until my machine started hanging while watching mythtv over the wireless. dmesg and /var/log/kernel/errors.log show "scheduling atomic" errors
Output of dmesg
Output of /var/log/kernel/errors.log
I compiled it with debugging and modprobed it with debug=31. Here are the /var/log/kernel/errors.log
and /var/log/syslog (too big for pastebin or attachment, private link below) files immediately afterwards
and now the cvs driver causes my whole system to hang, even after I recomile without debug
You seem to have found an interesting corner case. Can you try the attached patch? It should (OK, may) help at least one of the "scheduling while atomic" messages you're getting.
(edit) fatah Glad to see you're looking at code. I checked just to be sure, and that particular fix is already in. Thanks.[/quote1qqknv6k]
Thanks for the patch. I gunzipped it in the /usr/src/rt73-<version>/Modules directory and applied
make && make install
and reloaded the module. Unfortunately, my system locked up completely a few minutes later (had to hard reset, same as before) and /var/log/kernel/errors.log showed
May 5 19:03:08 landau kernel: BUG: scheduling while atomic: emerald/0x10000200/8233
May 5 19:03:08 landau kernel: BUG: scheduling while atomic: X/0x10000200/6470
Note that this was patched on yesterday's cvs build.
What's goin' on?
Do you have a syslog for that effort? FWIW you can trim that to a more manageable size by grepping on the timestamp. For example, using the syslog from your previous post,[code233rrwis]egrep 'May 5 01:4' /var/log/syslog|gzip >syslog.gz[/code233rrwis]would capture all the information needed.
Well I loaded the driver again a couple of hours ago and it seems to be working without errors all of a sudden. This would be the 188.8.131.52 CVS 2008050416 version with your patch above.
The syslog output so far is as follows
No messages in /var/log/kernel/errors.log yet... /var/log/kernel/info.log says
Should it cause a system freeze again I'll post the syslog. For now, it seems to be working. Thanks again.
Well I loaded the driver again a couple of hours ago and it seems to be working without errors all of a sudden.[/quote145qfqjt]Not reassuring. Are you watching mythtv over the wireless?
BTW, thanks for the quick turnaround.