Tiny Core v4.0

[Rich]

Hi miskor
From dmesg:

Kernel command line: initrd=/ubninit quiet BOOT_IMAGE=/ubnkern

These are not the standard names for the kernel and initrd. Did you make any modifications such
as re-mastering or recompiling?

zram: module is from the staging directory, the quality is unknown, you have been warned.
zram: num_devices not specified. Using default: 1
zram: Creating 1 devices ...
zram: disk size not provided. You can use disksize_kb module param to specify size.
Using default: (25% of RAM).
zcache: module is from the staging directory, the quality is unknown, you have been warned.
zcache: module license 'unspecified' taints kernel.
Disabling lock debugging due to kernel taint
r6040: RDC R6040 NAPI net driver,version 0.27 (23Feb2011)
------------[ cut here ]------------
WARNING: at fs/sysfs/dir.c:455 0xc01d4830()
sysfs: cannot create duplicate filename '/class/mdio_bus/0'
Modules linked in: r6040(+) zcache(PC) zram(C) loop
Pid: 83, comm: modprobe Tainted: P         C  3.0.3-tinycore #90210

Those  zram  and  zcache  warnings are not normal, are they? I'm not running 4.0 so I can't tell.

[miskor]

Nope, no remastering or recompiling.

This may be because I used unetbootin for creating bootable SD card from ISO image.

But this should not affect drivers...

MiskoR

[curaga]

Yes, those z* messages are normal. As for the driver bug, it's not much that we can do. Google does not say much.

[miskor]

But in 3.8 driver is working OK!

Something is changed in 4.0 and that affects R6040 driver.

Help me to debug and troubleshoot this issue, I am willing to spend some time on this but I need guidance!

I bet that more users will report this problem...

BR,
MiskoR

[curaga]

Well, it's a regression in the r6040 driver between 2.6.33 and 3.0, and you should report it as such to the kernel bugzilla. However, it still seems to be down from the breach.

You could use git bisect to find out exactly what change broke it; there only appear to be some dozen changes between these two kernel versions, so it'd only be a handful kernel builds. Teaching how to do that is rather out of scope for here.

One easy thing you could try is to build the latest RC kernel, to see if the bug is fixed already.