site  contact  subhomenews

2.6.34 kernel progress

October 20, 2010 — BarryK
I tested the kernel, patched with the last version of Aufs2. I reported recently about the kernel with Aufs2.1 patch, and md5sum and tar do not work properly.

Well, I tested md5sum and still got the wrong sums. But, testing on two other computers, the md5sum is correct. Hmmm.

A couple of items of good news:

1. video=640x480 works (doesn't in kernel)
2. OpenOffice works (doesn't in kernel).

Tonight I will compile the kernel.

Comments success
Username: BarryK
I compiled that kernel, and success, md5sum works. However, the md5sum bug only occurs on certain hardware, a PC with SiS chips (I tested on two others, with Intel chips and they were ok). lspci reports: [code]00:00.0 Host bridge: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host (rev 11) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25) 00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0) 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) 00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91) 01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600 GT] (rev a2) [/code] I am testing booting off a USB Flash stick. But there is bad news. The kernel has only one patch, it reverts an earlier patch that is reported to break some USB interfaces. But in my case the reversion has broken things. So, it is a no-win situation, and I will have to contact the kernel developers pronto. patched
Username: BarryK
"I am conducting an experiment. I have been in contact with one of the kernel developers and he is puzzled that I have trouble with as it only reverts one very small patch. He has requested that I get in contact with some other developers, but I have been looking at it... Here is the changelog for [code] Revert "USB delay init quirk for logitech Harmony 700-series devices" This reverts commit 631b2d37894bb2a891d8897e1861362a23dde4d9. It was found to cause a number of USB devices to not work properly because we call usb_disable_autosuspend too soon. This is not an issue with any other kernel version.[/code] Here is the patch in question:;a=commitdiff;h=93362a875fc69881ae69299efaf19a55a1f57db0 ...well, I am far from an expert here, but it seems to me that moving the call to function usb_detect_quirks() to a different place in the code is what has broken other USB interfaces. That patch was applied back in the kernel, and it also seems to me that just reverting a patch like that could break things. Other patches applied since are maybe depending on usb_detect_quirks() being in the new location. This could be a very subtle problem. ..Am I too naive? It just seems to me, from the point of view of someone unfamiliar with managing a project with thousands of patches being submitted, that just taking out an old one is asking for trouble. Anyway, I thought that I would take a punt. I don't know, I haven't studied the code in depth, maybe this will break something... I have restored the original call to usb_detect_quirks(), in the code, so it is now called in two places. I'm compiling it now, let's see what happens.

Special seems ok
Username: BarryK
"My "special" hacked seems ok. Reckon I will go for this one for the next Wary. special patch
Username: BarryK
"As I say, I am blundering in here, knowing nothing about this code, just a superficial assessment, but this is my "special" patch: [code]The official patch breaks some hardware. It only reverts a patch that was in, but I have my own replacement for the patch: do this manually, to file /usr/src/linux- # diff -u hub.cORIG hub.c --- hub.cORIG 2010-10-20 20:18:19.000000000 +0800 +++ hub.c 2010-10-22 07:46:03.000000000 +0800 @@ -1791,6 +1791,7 @@ pm_runtime_set_active(&udev->dev); pm_runtime_enable(&udev->dev); + usb_detect_quirks(udev); /*BK*/ err = usb_enumerate_device(udev); /* Read descriptors */ if (err < 0) goto fail; [/code]

Tags: wary