On 05/04/2015 03:38 PM, Johannes Berg wrote:
On Mon, 2015-05-04 at 13:05 +0200, Alexander Riesen wrote:
>>
>> Revert the context tracking code
>>
>> So it seems that the code has problems with different contexts. Still, it
seems
>> a bit heavy-handed to rem
Hi,
I tried to instrument my code (a kernel driver) with __must_hold hints
and noticed that they don't really work: a definitely broken code caused
no errors from sparse.
A test in the "sparse" tree confirmed. Here is the test I used:
static int ctx;
static void must_hold(void) __attribute__((
Hi, all
Simply crashed. No oops-screens. And fast rebooted :)
Under middle load. Nothing serious.
Workstation, running XFree86 4.0.2,
simple programs eating megabytes.
Alex Riesen
Traian AG
P.S.:
>From syslog:
Mar 20 15:41:48 ws018 -- MARK --
Mar 20 15:49:00 ws018 kernel: emory.c:83: bad pmd 5
tils 2.0
Modules Loaded 3c59x nls_koi8-r ntfs smbfs vfat fat nls_iso8859-2
nls_iso8859-1 nls_cp866 binfmt_misc autofs nfs lockd sunrpc nbd
Sincerely yours,
Alexander Riesen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
al.
I have tried two NICs (3COM with 3c90x and Kingstone with tulip),
in promiscuous and normal mode - with the same effect.
Any help and/or information about this/such problem
is greatly appreciated.
Does it cause dropping of packets ?
Is there a way to workaround the processor load ?
Cheers,
5 matches
Mail list logo