=== Signoff report for [testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 6 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 11 fully signed off packages
* 195 packages missing signoffs
* 0 packages older than 14 days
(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)
== New packages in [testing] in last 24 hours (6 total) ==
On 05/21/2012 03:21 PM, Tobias Powalowski wrote:
> Please report any issues that arise.
I've run into an issue with my usb keyboard (it's an Apple wired one).
Frequently, the first keys to be pressed after not using the keyboard
for a few seconds are not registered. Sometimes, the keyboard then
freezes entirely (not even caps lock leds will work), which can be
fixed be un- and re-plugging it in.
A similar issue is described here [1] and here [2].
I haven't had time for further investigation. There are no problems
with linux 3.3.7-1.
[1] http://lkml.indiana.edu/hypermail/linux/kernel/1205.0/00882.html
[2] http://permalink.gmane.org/gmane.linux.usb.general/64408
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Here are my additional impressions after trying to read a bit more
from make_request.
* Single char variable names suck. It's difficult to tell what type
they are, what they're used for and makes it difficult to track
where the variable is used in the function - try to highlight the
variable name in the editor.
While not a strict rule, there are reasons why people tend to use
single char variable names mostly for specific things - e.g. loop
variables, transient integral variables or in numerical context.
They're either localized to small scope of code so keeping track of
them is easy and/or people are familiar with such usages.
So, I would *much* prefer if I don't have to keep trying to track
what the hell c, d, k, j, l mean and where they're used.
* Due to the various style issues, lack of documentation and other
abundant idiosyncrasies in the code, at least I find the code almost
aggravating. It's complicated, difficult to read and full of
unnecessary differences and smart tricks (smart is not a positive
word here). I don't think we want code like this in the kernel.
Hell, I would get pretty upset if I encounter this type of code
while trying to update some block API.
* Maybe I haven't seen enough of it but my feeling about closure
hasn't gone up. It likely has gone further down. It doesn't
actually seem to solve the pain points of async programming while
adding ample headaches. The usages that I followed could be easily
served by either domain-specific async sequencer or the existing ref
/ async / whatever mechanism / convention. If you have good example
usage in bcache, please feel free to explain it.
So, I don't know. If this is a driver for some super obscure device
that would fall out of use in some years and doesn't interact with /
affect the rest of the kernel, maybe we can put it in with big giant
blinking red warnings about the dragons inside, but as it currently
stands I don't think I can ack the code base and am afraid that it
would need non-trivial updates to be upstreamable.
I'm gonna stop reading and, for now
NACKED-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
05-30-2012, 08:54 AM
Zhi Yong Wu
On Thu, May 10, 2012 at 11:07 AM, Kent Overstreet
<koverstreet@google.com> wrote:
> bcache: a cache for arbitrary block devices using an SSD.
>
> Short overview:
> Bcache does both writethrough and writeback caching. It presents itself as a
> new block device, a bit like say md. You can cache an arbitrary number of
> block devices with a single cache device, and attach and detach things at
> runtime - it's quite flexible.
>
> It's very fast. It uses a b+ tree for the index, along with a journal to
> coalesce index updates, and a bunch of other cool tricks like auxiliary binary
> search trees with software floating point keys for searching within btree
> nodes.
>
> Bcache is solid, production ready code. There are still bugs being found that
> affect specific configurations, but there haven't been any major issues found
> in awhile - it's well past time I started working on getting it into mainline.
>
> It's a lot of code - I tried to split it out so that it'd make some sort of
> sense for reviewing. Let me know if there's anything else I can do to make
This feature is so interesting; Do you have one clean public git tree
about this patchset? So that i can pull it to play with it.
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
05-30-2012, 09:16 AM
"Guillermo Leira"
> -----Mensaje original-----
> De: arch-general-bounces@archlinux.org [mailto:arch-general-
> bounces@archlinux.org] En nombre de Sergey Manucharian
> Enviado el: martes, 29 de mayo de 2012 23:47
> Para: General Discussion about Arch Linux
> Asunto: Re: [arch-general] linux-3.4.0-1 enters [testing]
>
> Excerpts from Tobias Powalowski's message from Mon 21-May-12 15:21:
> > Hi guys,
> >
> > Upstream changes:
> > http://kernelnewbies.org/LinuxChanges
> >
> > The x86_32 switch is not yet enabled.
> >
> > Please report any issues that arise.
> > Thanks.
>
> The problem with ath5k still persists:
>
> ath5k phy0: gain calibration timeout
>
> https://bbs.archlinux.org/viewtopic.php?id=139270
Mine came back to life with 3.4, after some weeks of nightmare...
05-30-2012, 11:20 AM
Martti Kühne
On Mon, May 21, 2012 at 03:21:07PM +0200, Tobias Powalowski wrote:
> Please report any issues that arise.
As mentioned on irc already I have had trouble with linux 3.4-1 and the
network driver (RTL8111/8168B, using r8169 module) with uswsusp 0.8-6 and
virtualbox 4.1.16-1 guests, connected through the host's bridge setup. I
haven't read up on how to script pausing all running virtual machines before
suspending, however trying to suspend with vboxes running leaves me with a
badly screwed-up, unkillable brctl process and [1] on trying to shut
down/reboot.
Update: Hmm, not sure, but it looks like it is taking a while for the virtual
maichines to recover from the host's suspend / pause and unpause.
However I added a script [2] to pause everything in /etc/pm/sleep.d, which
seems to solve the foreground issue with the unkillable process and shutdown
issues.
Update 2: As it looks, the problem of not being able to shutdown/reboot
persists despite pausing the machines, although the usage count ends up on -1
with it.
> Could I make a request to all list subscribers, please?
>
> Please start with a new blank message when you start a new thread.
>
> Please DO NOT simply reply to an old message changing its Subject.
>
> Several reasons for it:
>
> 1. It's not a reply to the old thread. 2. It's not related to the old
> thread in any way. 3. Messes up threading in email clients.
All of these good suggestions are resumed and printed for further
reference in these two links:
Sadly, some modern MUA (mostly webmails or those from smartphone devices)
simply overwrite the good mailing lists guidance and delete the required
e-mail headers so messages are left unthreaded.
Solution? Not quite easy, you have to remove the users... err, I mean, to
use a standard-compliant MUA O:-)
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: jq5ac2$l92$6@dough.gmane.org">http://lists.debian.org/jq5ac2$l92$6@dough.gmane.org
05-30-2012, 06:20 PM
Myra Nelson
On Wed, May 30, 2012 at 2:38 AM, Myra Nelson <myra.nelson@hughes.net> wrote:
> On Mon, May 21, 2012 at 8:21 AM, Tobias Powalowski
> <tobias.powalowski@googlemail.com> wrote:
>> Hi guys,
>>
>> Upstream changes:
>> http://kernelnewbies.org/LinuxChanges
>>
>> The x86_32 switch is not yet enabled.
>>
>> Please report any issues that arise.
>> Thanks.
>>
>> greetings
>> tpowa
>> --
>> Tobias Powalowski
>> Archlinux Developer & Package Maintainer (tpowa)
>> http://www.archlinux.org
>> tpowa@archlinux.org
>>
>>
> Tobias et. al.
>
> I've been running this kernel since it hit testing. I haven't had any
> problems?. I did experience the same shut down error message as Mauro
> Santos this evening.
>
> May 29 23:51:46 gandalf shutdown[30259]: shutting down for system reboot
> May 29 23:51:47 gandalf init: Switching to runlevel: 6
> May 29 23:51:47 gandalf kernel: [88452.180146] BUG: Bad rss-counter
> state mm:ffff88022319f480 idx:1 val:-1
> May 29 23:51:47 gandalf kernel: [88452.180154] BUG: Bad rss-counter
> state mm:ffff88022319f480 idx:2 val:1
> May 29 23:51:47 gandalf kernel: [88452.182941] BUG: Bad rss-counter
> state mm:ffff880221cb6d80 idx:1 val:-1
> May 29 23:51:47 gandalf kernel: [88452.182949] BUG: Bad rss-counter
> state mm:ffff880221cb6d80 idx:2 val:1
> May 29 23:51:47 gandalf kernel: [88452.505462] BUG: Bad rss-counter
> state mm:ffff88022345ed80 idx:1 val:-1
> May 29 23:51:47 gandalf kernel: [88452.505480] BUG: Bad rss-counter
> state mm:ffff88022345ed80 idx:2 val:1
> May 29 23:51:47 gandalf kernel: [88452.519868] BUG: Bad rss-counter
> state mm:ffff880221cb7800 idx:1 val:-1
> May 29 23:51:47 gandalf kernel: [88452.519877] BUG: Bad rss-counter
> state mm:ffff880221cb7800 idx:2 val:1
> May 29 23:51:47 gandalf kernel: [88452.542455] BUG: Bad rss-counter
> state mm:ffff880221cb5f80 idx:1 val:-1
> May 29 23:51:47 gandalf kernel: [88452.542462] BUG: Bad rss-counter
> state mm:ffff880221cb5f80 idx:2 val:1
> May 29 23:51:47 gandalf kernel: [88452.757413] BUG: Bad rss-counter
> state mm:ffff88022319ce00 idx:1 val:-1
> May 29 23:51:47 gandalf kernel: [88452.757423] BUG: Bad rss-counter
> state mm:ffff88022319ce00 idx:2 val:1
> May 29 23:51:50 gandalf pdnsd[633]: Caught signal 15. Exiting.
> May 29 23:51:50 gandalf kernel: [88455.849136] BUG: Bad rss-counter
> state mm:ffff88022345ce00 idx:1 val:-3
> May 29 23:51:50 gandalf kernel: [88455.854393] BUG: Bad rss-counter
> state mm:ffff88022345ce00 idx:2 val:3
> May 29 23:51:50 gandalf kernel: [88456.054883] BUG: Bad rss-counter
> state mm:ffff88022345fb80 idx:1 val:-58
> May 29 23:51:50 gandalf kernel: [88456.059783] BUG: Bad rss-counter
> state mm:ffff88022345fb80 idx:2 val:58
> May 29 23:51:51 gandalf kernel: [88456.109544] BUG: Bad rss-counter
> state mm:ffff880222b62a00 idx:1 val:-1
> May 29 23:51:51 gandalf kernel: [88456.114260] BUG: Bad rss-counter
> state mm:ffff880222b62a00 idx:2 val:1
> May 29 23:51:51 gandalf kernel: [88456.119631] BUG: Bad rss-counter
> state mm:ffff88022345ea00 idx:1 val:-1
> May 29 23:51:51 gandalf kernel: [88456.124267] BUG: Bad rss-counter
> state mm:ffff88022345ea00 idx:2 val:1
>
> I was installing a local lib with cpan that blew up in my face, my bad
> PBKAC, and my memory usage went to 98%. The only was to cure it was to
> reboot. I didn't think any thing of it till I read the message from
> Mauro. My google powers seem to be broken and kernel bugs are a little
> bit above my pay grade. Other wise everything seems to be fine. I'm
> running an AMD Phenom tricore on a Gigabyte board with 8 GB ram.
>
> Myra
>
>
> --
> Life's fun when your sick and psychotic!
Update:
After looking at my everything.log this morning, I'm not sure this is
kernel related - at least directly. When I brought my box out of
standby this morning, I was unable to run anything and received an
error message about "program doesn't exist". Rebooting cured that so I
started looking at logs and found this.
May 30 03:01:01 gandalf anacron[1122]: Jobs will be executed sequentially
May 30 03:18:48 gandalf kernel: [ 2223.677424] ata3: exception Emask
0x10 SAct 0x0 SErr 0x90202 action 0xe frozen
May 30 03:18:48 gandalf kernel: [ 2223.677433] ata3: irq_stat
0x00400000, PHY RDY changed
May 30 03:18:48 gandalf kernel: [ 2223.677441] ata3: SError: {
RecovComm Persist PHYRdyChg 10B8B }
which persisted until I rebooted. Google power revealed this may be
one of the following problems.
Bad power supply, bad sata cable, too many drives plugged into one
molex, or bad hardware. I've replaced my sata cables, made sure there
is only one drive plugged into each molex, and time will tell. I've
also had the keyboard problems mentioned by others on this thread, but
it occurred when I brought my box up from suspend to ram. It was a
minor glitch so I wasn't really concerned with it. It may be related
to the following warnings showing up in my logs.
ay 30 13:03:08 gandalf kernel: [ 0.304887] pci0000:00: ACPI _OSC
request failed (AE_NOT_FOUND), returned control mask: 0x1d
May 30 13:03:08 gandalf kernel: [ 7.318395] ACPI Warning:
0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region
SOR1 1 (20120320/utaddress-251
More research time.
Myra
--
Life's fun when your sick and psychotic!
05-31-2012, 08:07 AM
Arch Website Notification
=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 1 new package in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 143 packages missing signoffs
* 0 packages older than 14 days
(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)
== New packages in [community-testing] in last 24 hours (1 total) ==
* systemd-arch-units-20120528-3 (any)
== Incomplete signoffs for [community] (141 total) ==
1. eric - 16 signoffs
2. tomegun - 10 signoffs
3. dan - 3 signoffs
4. stephane - 2 signoffs
5. pierre - 1 signoffs
05-31-2012, 08:07 AM
Arch Website Notification
=== Signoff report for [testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 8 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 14 fully signed off packages
* 191 packages missing signoffs
* 0 packages older than 14 days
(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)
== New packages in [testing] in last 24 hours (8 total) ==
