Wondering as their were a lot of XFS related issues early on in
development..? The 2.6.22-rc3 kernel has the core 2 duo coretemp patch by
ruik which I want be running as long as 2.6.22-rc3 does not have any
severe XFS issues?
Justin.
On Sat, 2 Jun 2007, Justin Piszcz wrote:
> Wondering as their were a lot of XFS related issues early on in
> development..? The 2.6.22-rc3 kernel has the core 2 duo coretemp patch by
> ruik which I want be running as long as 2.6.22-rc3 does not have any severe
> XFS issues?
Tracking -rc and running 2.6.22-rc3 for a couple of days now, no
problems with xfs since this infamous 2.6.17 thingy[0]. But that's
pretty useless information I guess, since your setup will be different
from mine. Did you have anything "special" in mind when asking this?
C.
[0] http://oss.sgi.com/projects/xfs/faq.html#dir2
--
BOFH excuse #339:
manager in the cable duct
On Sat, 2 Jun 2007, Christian Kujau wrote:
> On Sat, 2 Jun 2007, Justin Piszcz wrote:
>> Wondering as their were a lot of XFS related issues early on in
>> development..? The 2.6.22-rc3 kernel has the core 2 duo coretemp patch by
>> ruik which I want be running as long as 2.6.22-rc3 does not have any severe
>> XFS issues?
>
> Tracking -rc and running 2.6.22-rc3 for a couple of days now, no problems
> with xfs since this infamous 2.6.17 thingy[0]. But that's pretty useless
> information I guess, since your setup will be different from mine. Did you
> have anything "special" in mind when asking this?
>
> C.
>
> [0] http://oss.sgi.com/projects/xfs/faq.html#dir2
> --
> BOFH excuse #339:
>
> manager in the cable duct
>
Thanks, I'll give it a go then--!
Jun 2 18:23:23 p34 upsd[2225]: Can't connect to UPS [belkin]
(newhidups-auto): No such file or directory
Jun 2 18:24:23 p34 upsmon[2228]: Poll UPS [belkin@localhost] failed -
Driver not connected
Hmm, something changes with USB in 2.6.22-rc3 form 2.6.21..
On Sat, 2 Jun 2007, Christian Kujau wrote:
> On Sat, 2 Jun 2007, Justin Piszcz wrote:
>> Wondering as their were a lot of XFS related issues early on in
>> development..? The 2.6.22-rc3 kernel has the core 2 duo coretemp patch by
>> ruik which I want be running as long as 2.6.22-rc3 does not have any severe
>> XFS issues?
>
> Tracking -rc and running 2.6.22-rc3 for a couple of days now, no problems
> with xfs since this infamous 2.6.17 thingy[0]. But that's pretty useless
> information I guess, since your setup will be different from mine. Did you
> have anything "special" in mind when asking this?
>
> C.
>
> [0] http://oss.sgi.com/projects/xfs/faq.html#dir2
> --
> BOFH excuse #339:
>
> manager in the cable duct
>
>
Justin Piszcz wrote:
> Wondering as their were a lot of XFS related issues early on in
> development..? The 2.6.22-rc3 kernel has the core 2 duo coretemp patch
> by ruik which I want be running as long as 2.6.22-rc3 does not have
> any severe XFS issues?
XFS currently has a data-corrupting bug, where files which were appended
by small amounts may lose their updates on umount - I see this
corrupting hg repos. There's a patch which works for me, and is in
2.6.22-rc3-mm1, but it hasn't been merged upstream yet.
J
On Sat, 2 Jun 2007, Jeremy Fitzhardinge wrote:
> Justin Piszcz wrote:
>> Wondering as their were a lot of XFS related issues early on in
>> development..? The 2.6.22-rc3 kernel has the core 2 duo coretemp patch
>> by ruik which I want be running as long as 2.6.22-rc3 does not have
>> any severe XFS issues?
>
> XFS currently has a data-corrupting bug, where files which were appended
> by small amounts may lose their updates on umount - I see this
> corrupting hg repos. There's a patch which works for me, and is in
> 2.6.22-rc3-mm1, but it hasn't been merged upstream yet.
>
> J
>
>
Ah that's it- and USB appears to be broken as well, I'll stick with
2.6.21.3 for now.
Thanks!
Justin.
On Sat, 2 Jun 2007, Justin Piszcz wrote:
> On Sat, 2 Jun 2007, Jeremy Fitzhardinge wrote:
>> XFS currently has a data-corrupting bug, where files which were appended
>> by small amounts may lose their updates on umount - I see this
>> corrupting hg repos. There's a patch which works for me, and is in
>> 2.6.22-rc3-mm1, but it hasn't been merged upstream yet.
Just for the record, you mean this one:
http://lkml.org/lkml/2007/5/12/93 ..right? (haven't been bitten by
this one...yet)
> Ah that's it- and USB appears to be broken as well, I'll stick with 2.6.21.3
> for now.
Got any pointers? I'm using USB right now, one is i386 with 2.6.22-rc3,
another one is powerpc, tracking -git and USB seems to work.
C.
--
BOFH excuse #15:
temporary routing anomaly
On Sun, 3 Jun 2007, Christian Kujau wrote:
> On Sat, 2 Jun 2007, Justin Piszcz wrote:
>> On Sat, 2 Jun 2007, Jeremy Fitzhardinge wrote:
>>> XFS currently has a data-corrupting bug, where files which were appended
>>> by small amounts may lose their updates on umount - I see this
>>> corrupting hg repos. There's a patch which works for me, and is in
>>> 2.6.22-rc3-mm1, but it hasn't been merged upstream yet.
>
> Just for the record, you mean this one:
> http://lkml.org/lkml/2007/5/12/93 ..right? (haven't been bitten by this
> one...yet)
>
>> Ah that's it- and USB appears to be broken as well, I'll stick with
>> 2.6.21.3 for now.
>
> Got any pointers? I'm using USB right now, one is i386 with 2.6.22-rc3,
> another one is powerpc, tracking -git and USB seems to work.
>
> C.
> --
> BOFH excuse #15:
>
> temporary routing anomaly
>
Sent this in another e-mail to LKML, it breaks support for my UPS:
>From [email protected] Sat Jun 2 18:43:52 2007
Date: Sat, 2 Jun 2007 18:43:52 -0400 (EDT)
From: Justin Piszcz <[email protected]>
To: [email protected]
Subject: Kernel 2.6.22-rc3 breaks USB: Unable to get HID descriptor (error sending control message: Operation not permitted)
I use nut-2.0.4-4 with a UPS attached via USB and from 2.6.21.3 -> 2.6.22-rc3 it
stops working, see below. My .config is attached.
2.6.21.3:
p34:~# /lib/nut/newhidups -u nut -DDDDDD auto
Checking device (050D/0912) (005/002)
- VendorID: 050d
- ProductID: 0912
- Manufacturer:
- Product: UPS
- Serial Number: unknown
- Bus: 005
Trying to match device
Device matches
HID descriptor retrieved (Reportlen = 820)
Size read for the report descriptor: 820
Report descriptor retrieved (Reportlen = 820)
Found HID device
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4)
Report Descriptor size = 820
Report Descriptor: (200 bytes) => 05 84 09 04 A1 01 05 86 09 26 A1 02 85 01 75
08
Detected a UPS: /UPS
Using subdriver: Belkin HID 0.1
Looking up 00840004
Looking up 00860026
Looking up 00860040
entering string_to_path()
parsing UPS
Looking up UPS
hid_lookup_usage: found 840004
parsing BELKINConfig
Looking up BELKINConfig
hid_lookup_usage: found 860026
parsing BELKINConfigVoltage
Looking up BELKINConfigVoltage
hid_lookup_usage: found 860040
Path depth = 3
0: UPage(84), Usage(4)
1: UPage(86), Usage(26)
2: UPage(86), Usage(40)
Entering libusb_get_report
=>> Before exponent: 120, 0/0)
=>> After conversion: 120.000000 (120), 0/0)
Report : (8 bytes) => 01 78 80 00 00 00 00 00
Path: UPS.BELKINConfig.BELKINConfigVoltage, Type: Feature, Value: 120.000000
Looking up 00840004
Looking up 00860026
Looking up 00860042
(works fine)
2.6.22-rc3:
p34:~# /lib/nut/newhidups -u nut -DDDDDD auto
Checking device (050D/0912) (005/002)
- VendorID: 050d
- ProductID: 0912
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 005
Trying to match device
Device matches
failed to claim USB device, trying 2 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
failed to claim USB device, trying 1 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
failed to claim USB device, trying 0 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
Unable to get HID descriptor (error sending control message: Operation not
permitted)
[ Part 2, "" Application/OCTET-STREAM (Name: "config-2.6.22-rc3.bz2") ]
[ 10KB. ]
[ Unable to print this part. ]
Justin Piszcz wrote:
> Sent this in another e-mail to LKML, it breaks support for my UPS:
>
> From [email protected] Sat Jun 2 18:43:52 2007
> Date: Sat, 2 Jun 2007 18:43:52 -0400 (EDT)
> From: Justin Piszcz <[email protected]>
> To: [email protected]
> Subject: Kernel 2.6.22-rc3 breaks USB: Unable to get HID descriptor
> (error sending control message: Operation not permitted)
>
> I use nut-2.0.4-4 with a UPS attached via USB and from 2.6.21.3 ->
> 2.6.22-rc3 it
> stops working, see below. My .config is attached.
>
I also have seen this on -rc2-mm1, my APC UPS status was not showing up.
I haven't investigated in any more detail.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
Christian Kujau wrote:
> Just for the record, you mean this one:
> http://lkml.org/lkml/2007/5/12/93 ..right? (haven't been bitten by
> this one...yet)
That's the one. It's fairly subtle; there's no metadata/filesystem
corruption, and the file just reverts back to a previous length, so if
it were append-only, it would just return to a previous state.
J
Michal Piotrowski wrote:
> It's already merged into mainline
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=df3c7244264f1d12562413aa32d56be802486516
>
Oh, good. I hadn't read through the last couple of days of commits.
J
On Sun, 3 Jun 2007, Jeremy Fitzhardinge wrote:
> Michal Piotrowski wrote:
>> It's already merged into mainline
>>
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=df3c7244264f1d12562413aa32d56be802486516
>>
>
> Oh, good. I hadn't read through the last couple of days of commits.
>
> J
>
>
Nice, any word on the USB bug?