- Arch-general - lists.archlinux.org

[arch-general] Need some tips/help with kernel bisection
by Mauro Santos 13 May '14

13 May '14

After the update to kernel 3.14 my laptop stopped suspending/hibernating properly. I have narrowed down the problem somewhat, but before I submit a bug upstream, I'd like to try and bisect the kernel to find exactly what broke things for me (and I suppose I might be asked by upstream to bisect the kernel anyway). I have never done this before, and I suppose there might be a few catches I should be aware of before I start what will be a time consuming process. My plan is to start with the current PKGBUILD for the kernel (or a PKGBUILD from AUR) and modify it a little for my needs. However I don't know if I should start with a kernel configuration file from the 3.13 series or if I can use the one that is used by the current kernel. I was thinking of making use of 'make localmodconfig' to cut down on the compilation time, but I don't know if there are any catches I should be aware of. Should I use 'make config' followed by 'make localmodconfig' or using only the later is ok? Can I compile the kernel on the same dir where I'm using 'git bisect' or is it advisable to clone that to a new dir and build in the new dir? In case compiling in place is ok, should I use 'make clean' before compiling a new kernel? Regarding patches, I suppose I shouldn't need to include any extra patches or are there any known needed patches required to build kernel 3.13? -- Mauro Santos

1 0

[arch-general] archlinux kernel 3.14.2-1 Broadcom BCM4312 firmware-files not found
by Andreas Adelmann 13 May '14

13 May '14

Hello List, my Netbook: Packard Bell DOT M Intel Z520 1.33G 1GB RAM Broadcom BCM4312 802.11b/g LP-PHY (rev 01) arch 32-bit fully updated. I'm using b43-firmware from AUR. uname -a: Linux laptop 3.14.2-1-ARCH #1 SMP PREEMPT Mon 14 April 21:01:08 CEST 2014 i686 GNU/Linux With Kernel 3.13.8-1 and b43-firmware-5.100.130 all works very well. After Upgrade my System with Kernel 3.14.1-1 with same package of Firmware installed and a reboot, i got this message on every boot: Apr 30 15:50:47 laptop kernel: b43-pci-bridge 0000:03:00.0: enabling device (0004 -> 0006) Apr 30 15:50:47 laptop kernel: ssb: Found chip with id 0x4312, rev 0x01 and package 0x00 Apr 30 15:50:47 laptop kernel: ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243) Apr 30 15:50:47 laptop kernel: ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243) Apr 30 15:50:47 laptop kernel: ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243) Apr 30 15:50:47 laptop kernel: ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243) Apr 30 15:50:47 laptop kernel: ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0 Apr 30 15:50:47 laptop kernel: b43-phy0: Broadcom 4312 WLAN found (core revision 15) Apr 30 15:50:47 laptop kernel: b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1 Apr 30 15:50:47 laptop kernel: b43-phy0 ERROR: Firmware file "b43/lp0initvals15.fw" not found Apr 30 15:50:47 laptop kernel: Broadcom 43xx driver loaded [ Features: PMNLS ] Apr 30 15:50:47 laptop kernel: b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found Apr 30 15:50:47 laptop kernel: b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website. The files are propper installed under /usr/lib/firmware/b43/ What have i done: reinstalled firmware b43-firmware-5.100.130 by using Kernel 3.14.1-1 and 3.14.2-1 - no success. Updating to b43-firmware-6.30.163.46 using Kernel 3.14.1-1 and 3.14.2-1 - no success. Downgrading to Kernel 3.13.8-1 both firmware versions works as expected. Sorry for my bad english. Regards

2 2

[arch-general] kernel 3.14.2 hangs - VirtualBox suspected
by Łukasz Michalski 13 May '14

13 May '14

Hi, I recently updated kernel to 3.14.2 and now I see i/o subsystem hang in few minutes after I start VirtualBox 4.3.10 machines (with Windows7). messages.log below. It looks like every process that tries to access /dev/md3 (even kworker and md3_resync) hangs forever. Anyone has similar problems? May 13 12:35:29 serenity kernel: kworker/u16:9 D 0000000000000000 0 112 2 0x00000000 May 13 12:35:29 serenity kernel: Workqueue: writeback bdi_writeback_workfn (flush-9:3) May 13 12:35:29 serenity kernel: ffff8804175177c0 0000000000000046 ffff88042fc575a0 ffff880417518000 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff880417517fd8 00000000000146c0 ffff880417518000 May 13 12:35:29 serenity kernel: 0000000034ca04fb ffff880417517710 ffff880412a11e10 ffff8804175177b8 May 13 12:35:29 serenity kernel: Call Trace: May 13 12:35:29 serenity kernel: [<ffffffff81292817>] ? check_blkcg_changed+0x57/0x210 May 13 12:35:29 serenity kernel: [<ffffffff81145d35>] ? mempool_alloc_slab+0x15/0x20 May 13 12:35:29 serenity kernel: [<ffffffff8128ce7f>] ? blk_throtl_bio+0x35f/0x940 May 13 12:35:29 serenity kernel: [<ffffffff81145d35>] ? mempool_alloc_slab+0x15/0x20 May 13 12:35:29 serenity kernel: [<ffffffff81145df1>] ? mempool_alloc+0x61/0x170 May 13 12:35:29 serenity kernel: [<ffffffffa04fe523>] ? __ext4_handle_dirty_metadata+0x83/0x1a0 [ext4] May 13 12:35:29 serenity kernel: [<ffffffff8150b609>] schedule+0x29/0x70 May 13 12:35:29 serenity kernel: [<ffffffffa048a666>] wait_barrier+0xc6/0x190 [raid10] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa048eca4>] make_request+0x44/0x130 [raid10] May 13 12:35:29 serenity kernel: [<ffffffffa0458a83>] md_make_request+0x103/0x260 [md_mod] May 13 12:35:29 serenity kernel: [<ffffffff81145d35>] ? mempool_alloc_slab+0x15/0x20 May 13 12:35:29 serenity kernel: [<ffffffff81145df1>] ? mempool_alloc+0x61/0x170 May 13 12:35:29 serenity kernel: [<ffffffff8126f728>] generic_make_request+0xf8/0x150 May 13 12:35:29 serenity kernel: [<ffffffff8126f7f8>] submit_bio+0x78/0x190 May 13 12:35:29 serenity kernel: [<ffffffff811ef800>] _submit_bh+0x140/0x230 May 13 12:35:29 serenity kernel: [<ffffffff811f1379>] __block_write_full_page+0x129/0x370 May 13 12:35:29 serenity kernel: [<ffffffff811f4c70>] ? I_BDEV+0x10/0x10 May 13 12:35:29 serenity kernel: [<ffffffff811f17d2>] block_write_full_page_endio+0xb2/0x150 May 13 12:35:29 serenity kernel: [<ffffffff811f1885>] block_write_full_page+0x15/0x20 May 13 12:35:29 serenity kernel: [<ffffffff811f53f8>] blkdev_writepage+0x18/0x20 May 13 12:35:29 serenity kernel: [<ffffffff8114e0f3>] __writepage+0x13/0x40 May 13 12:35:29 serenity kernel: [<ffffffff8114e680>] write_cache_pages+0x1e0/0x4d0 May 13 12:35:29 serenity kernel: [<ffffffff8114e0e0>] ? mapping_tagged+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffff8114e9bd>] generic_writepages+0x4d/0x80 May 13 12:35:29 serenity kernel: [<ffffffff811504ee>] do_writepages+0x1e/0x30 May 13 12:35:29 serenity kernel: [<ffffffff811e5dc0>] __writeback_single_inode+0x40/0x2b0 May 13 12:35:29 serenity kernel: [<ffffffff811e72ca>] writeback_sb_inodes+0x26a/0x430 May 13 12:35:29 serenity kernel: [<ffffffff811e752f>] __writeback_inodes_wb+0x9f/0xd0 May 13 12:35:29 serenity kernel: [<ffffffff811e778b>] wb_writeback+0x22b/0x360 May 13 12:35:29 serenity kernel: [<ffffffff811d4361>] ? get_nr_inodes+0x51/0x70 May 13 12:35:29 serenity kernel: [<ffffffff811e7d5f>] bdi_writeback_workfn+0x33f/0x4c0 May 13 12:35:29 serenity kernel: [<ffffffff81088068>] process_one_work+0x168/0x450 May 13 12:35:29 serenity kernel: [<ffffffff81088ac2>] worker_thread+0x132/0x3e0 May 13 12:35:29 serenity kernel: [<ffffffff81088990>] ? manage_workers.isra.23+0x2d0/0x2d0 May 13 12:35:29 serenity kernel: [<ffffffff8108f2ea>] kthread+0xea/0x100 May 13 12:35:29 serenity kernel: [<ffffffff8108f200>] ? kthread_create_on_node+0x1a0/0x1a0 May 13 12:35:29 serenity kernel: [<ffffffff8151757c>] ret_from_fork+0x7c/0xb0 May 13 12:35:29 serenity kernel: [<ffffffff8108f200>] ? kthread_create_on_node+0x1a0/0x1a0 May 13 12:35:29 serenity kernel: jbd2/md3-8 D 0000000000000000 0 496 2 0x00000000 May 13 12:35:29 serenity kernel: ffff8804136e5ca0 0000000000000046 0000000000000001 ffff88041963ce80 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff8804136e5fd8 00000000000146c0 ffff88041963ce80 May 13 12:35:29 serenity kernel: ffff8804136e5bf0 ffffffff8119d6e6 0000000000000046 0000000000000000 May 13 12:35:29 serenity kernel: Call Trace: May 13 12:35:29 serenity kernel: [<ffffffff8119d6e6>] ? kmem_cache_free+0x216/0x240 May 13 12:35:29 serenity kernel: [<ffffffff810ba100>] ? cpuacct_charge+0x50/0x60 May 13 12:35:29 serenity kernel: [<ffffffff810a991c>] ? update_curr+0xec/0x1b0 May 13 12:35:29 serenity kernel: [<ffffffff810a9e8f>] ? dequeue_entity+0x13f/0x580 May 13 12:35:29 serenity kernel: [<ffffffff8150b609>] schedule+0x29/0x70 May 13 12:35:29 serenity kernel: [<ffffffffa049a7e5>] jbd2_journal_commit_transaction+0x215/0x19c0 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff8101567f>] ? __switch_to+0x1af/0x540 May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffff8107928e>] ? try_to_del_timer_sync+0x5e/0x90 May 13 12:35:29 serenity kernel: [<ffffffffa04a1c4c>] kjournald2+0xec/0x2a0 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa04a1b60>] ? commit_timeout+0x10/0x10 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff8108f2ea>] kthread+0xea/0x100 May 13 12:35:29 serenity kernel: [<ffffffff8108f200>] ? kthread_create_on_node+0x1a0/0x1a0 May 13 12:35:29 serenity kernel: [<ffffffff8151757c>] ret_from_fork+0x7c/0xb0 May 13 12:35:29 serenity kernel: [<ffffffff8108f200>] ? kthread_create_on_node+0x1a0/0x1a0 May 13 12:35:29 serenity kernel: md3_resync D 0000000000000000 0 1297 2 0x00000000 May 13 12:35:29 serenity kernel: ffff8800c3fb1b48 0000000000000046 ffff88042fff9d80 ffff88040634ebf0 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff8800c3fb1fd8 00000000000146c0 ffff88040634ebf0 May 13 12:35:29 serenity kernel: ffffffff81b0acc0 0000000000011200 0000000000000000 ffff88040634ebf0 May 13 12:35:29 serenity kernel: Call Trace: May 13 12:35:29 serenity kernel: [<ffffffff81190861>] ? alloc_pages_current+0xb1/0x160 May 13 12:35:29 serenity kernel: [<ffffffffa048af79>] ? r10buf_pool_alloc+0x1b9/0x2b0 [raid10] May 13 12:35:29 serenity kernel: [<ffffffff8150b609>] schedule+0x29/0x70 May 13 12:35:29 serenity kernel: [<ffffffffa048a505>] raise_barrier+0x135/0x1a0 [raid10] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa048b2cf>] sync_request+0x25f/0x19b0 [raid10] May 13 12:35:29 serenity kernel: [<ffffffffa045cdb6>] ? is_mddev_idle+0x136/0x170 [md_mod] May 13 12:35:29 serenity kernel: [<ffffffffa0460593>] md_do_sync+0x8c3/0xe40 [md_mod] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa045ca90>] ? md_register_thread+0xe0/0xe0 [md_mod] May 13 12:35:29 serenity kernel: [<ffffffffa045cbe5>] md_thread+0x155/0x160 [md_mod] May 13 12:35:29 serenity kernel: [<ffffffffa045ca90>] ? md_register_thread+0xe0/0xe0 [md_mod] May 13 12:35:29 serenity kernel: [<ffffffff8108f2ea>] kthread+0xea/0x100 May 13 12:35:29 serenity kernel: [<ffffffff8108f200>] ? kthread_create_on_node+0x1a0/0x1a0 May 13 12:35:29 serenity kernel: [<ffffffff8151757c>] ret_from_fork+0x7c/0xb0 May 13 12:35:29 serenity kernel: [<ffffffff8108f200>] ? kthread_create_on_node+0x1a0/0x1a0 May 13 12:35:29 serenity kernel: thunderbird D 0000000000000000 0 1323 1 0x00000004 May 13 12:35:29 serenity kernel: ffff8804044b3b60 0000000000000086 ffff880419674000 ffff88040634ce80 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff8804044b3fd8 00000000000146c0 ffff88040634ce80 May 13 12:35:29 serenity kernel: ffffffff810b3aa4 0000000000000000 ffff8804044ef400 0000000070efd2c9 May 13 12:35:29 serenity kernel: Call Trace: May 13 12:35:29 serenity kernel: [<ffffffff810b3aa4>] ? add_wait_queue+0x44/0x50 May 13 12:35:29 serenity kernel: [<ffffffff810b3b4d>] ? remove_wait_queue+0x4d/0x60 May 13 12:35:29 serenity kernel: [<ffffffff811ce4f3>] ? poll_freewait+0x53/0xb0 May 13 12:35:29 serenity kernel: [<ffffffff811cf6fa>] ? do_sys_poll+0x14a/0x570 May 13 12:35:29 serenity kernel: [<ffffffff8150b609>] schedule+0x29/0x70 May 13 12:35:29 serenity kernel: [<ffffffffa049708d>] wait_transaction_locked+0x8d/0xd0 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa04973c2>] start_this_handle+0x262/0x610 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff8119c95a>] ? kmem_cache_alloc+0x1fa/0x220 May 13 12:35:29 serenity kernel: [<ffffffffa0497b8b>] jbd2__journal_start+0xfb/0x210 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffffa04d233a>] ? ext4_dirty_inode+0x2a/0x60 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04fdead>] __ext4_journal_start_sb+0x6d/0x110 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04d233a>] ext4_dirty_inode+0x2a/0x60 [ext4] May 13 12:35:29 serenity kernel: [<ffffffff811e65d8>] __mark_inode_dirty+0x38/0x2d0 May 13 12:35:29 serenity kernel: [<ffffffff811d55e1>] update_time+0x81/0xd0 May 13 12:35:29 serenity kernel: [<ffffffff811d5729>] touch_atime+0xf9/0x170 May 13 12:35:29 serenity kernel: [<ffffffff81145b1a>] generic_file_aio_read+0x54a/0x720 May 13 12:35:29 serenity kernel: [<ffffffff811ba137>] do_sync_read+0x67/0xa0 May 13 12:35:29 serenity kernel: [<ffffffff811ba797>] vfs_read+0x97/0x160 May 13 12:35:29 serenity kernel: [<ffffffff811bb2e9>] SyS_read+0x59/0xd0 May 13 12:35:29 serenity kernel: [<ffffffff81517629>] system_call_fastpath+0x16/0x1b May 13 12:35:29 serenity kernel: Chrome_FileUser D 0000000000000000 0 1410 1 0x00000000 May 13 12:35:29 serenity kernel: ffff8803f9a79b60 0000000000000082 ffffffff810a98a9 ffff8803fa9b2740 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff8803f9a79fd8 00000000000146c0 ffff8803fa9b2740 May 13 12:35:29 serenity kernel: ffff8803fb2e7000 ffff8803fb2e6e00 ffff88042fcd4738 ffff8803fb2e6e00 May 13 12:35:29 serenity kernel: Call Trace: May 13 12:35:29 serenity kernel: [<ffffffff810a98a9>] ? update_curr+0x79/0x1b0 May 13 12:35:29 serenity kernel: [<ffffffff810a9e8f>] ? dequeue_entity+0x13f/0x580 May 13 12:35:29 serenity kernel: [<ffffffff810a57f8>] ? __enqueue_entity+0x78/0x80 May 13 12:35:29 serenity kernel: [<ffffffff810aa3f0>] ? dequeue_task_fair+0x120/0x530 May 13 12:35:29 serenity kernel: [<ffffffff810a41a5>] ? sched_clock_cpu+0xb5/0xe0 May 13 12:35:29 serenity kernel: [<ffffffff810156c1>] ? __switch_to+0x1f1/0x540 May 13 12:35:29 serenity kernel: [<ffffffff8150b609>] schedule+0x29/0x70 May 13 12:35:29 serenity kernel: [<ffffffffa049708d>] wait_transaction_locked+0x8d/0xd0 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa04973c2>] start_this_handle+0x262/0x610 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff8119c95a>] ? kmem_cache_alloc+0x1fa/0x220 May 13 12:35:29 serenity kernel: [<ffffffffa0497b8b>] jbd2__journal_start+0xfb/0x210 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffffa04d233a>] ? ext4_dirty_inode+0x2a/0x60 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04fdead>] __ext4_journal_start_sb+0x6d/0x110 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04d233a>] ext4_dirty_inode+0x2a/0x60 [ext4] May 13 12:35:29 serenity kernel: [<ffffffff811e65d8>] __mark_inode_dirty+0x38/0x2d0 May 13 12:35:29 serenity kernel: [<ffffffff811d55e1>] update_time+0x81/0xd0 May 13 12:35:29 serenity kernel: [<ffffffff811d5729>] touch_atime+0xf9/0x170 May 13 12:35:29 serenity kernel: [<ffffffff81145b1a>] generic_file_aio_read+0x54a/0x720 May 13 12:35:29 serenity kernel: [<ffffffff811ba137>] do_sync_read+0x67/0xa0 May 13 12:35:29 serenity kernel: [<ffffffff811ba797>] vfs_read+0x97/0x160 May 13 12:35:29 serenity kernel: [<ffffffff811bb2e9>] SyS_read+0x59/0xd0 May 13 12:35:29 serenity kernel: [<ffffffff81517629>] system_call_fastpath+0x16/0x1b May 13 12:35:29 serenity kernel: Chrome_CacheThr D 0000000000000000 0 1412 1 0x00000000 May 13 12:35:29 serenity kernel: ffff8803faf09ab0 0000000000000082 0000000000000001 ffff8803fa9b3ae0 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff8803faf09fd8 00000000000146c0 ffff8803fa9b3ae0 May 13 12:35:29 serenity kernel: ffffffff810acfa3 00000000cb458df0 ffff880419600700 00000000000146c0 May 13 12:35:29 serenity kernel: Call Trace: May 13 12:35:29 serenity kernel: [<ffffffff810acfa3>] ? find_busiest_group+0x143/0x8b0 May 13 12:35:29 serenity kernel: [<ffffffff8150b609>] schedule+0x29/0x70 May 13 12:35:29 serenity kernel: [<ffffffffa049708d>] wait_transaction_locked+0x8d/0xd0 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa04973c2>] start_this_handle+0x262/0x610 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff8119c95a>] ? kmem_cache_alloc+0x1fa/0x220 May 13 12:35:29 serenity kernel: [<ffffffffa0497b8b>] jbd2__journal_start+0xfb/0x210 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffffa04d233a>] ? ext4_dirty_inode+0x2a/0x60 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04fdead>] __ext4_journal_start_sb+0x6d/0x110 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04d233a>] ext4_dirty_inode+0x2a/0x60 [ext4] May 13 12:35:29 serenity kernel: [<ffffffff811e65d8>] __mark_inode_dirty+0x38/0x2d0 May 13 12:35:29 serenity kernel: [<ffffffff811d55e1>] update_time+0x81/0xd0 May 13 12:35:29 serenity kernel: [<ffffffff811d5840>] file_update_time+0xa0/0xf0 May 13 12:35:29 serenity kernel: [<ffffffff81144a2c>] __generic_file_aio_write+0x14c/0x3e0 May 13 12:35:29 serenity kernel: [<ffffffff81144d13>] generic_file_aio_write+0x53/0xe0 May 13 12:35:29 serenity kernel: [<ffffffffa04c6261>] ext4_file_write+0xb1/0x4e0 [ext4] May 13 12:35:29 serenity kernel: [<ffffffff811c3a59>] ? pipe_read+0x509/0x520 May 13 12:35:29 serenity kernel: [<ffffffff811ba1d7>] do_sync_write+0x67/0xa0 May 13 12:35:29 serenity kernel: [<ffffffff811ba91a>] vfs_write+0xba/0x1e0 May 13 12:35:29 serenity kernel: [<ffffffff811bb58a>] SyS_pwrite64+0x9a/0xc0 May 13 12:35:29 serenity kernel: [<ffffffff81517629>] system_call_fastpath+0x16/0x1b May 13 12:35:29 serenity kernel: BrowserBlocking D 0000000000000000 0 1431 1 0x00000000 May 13 12:35:29 serenity kernel: ffff8800c0871ab8 0000000000000082 0000000000000000 ffff8803fc463ae0 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff8800c0871fd8 00000000000146c0 ffff8803fc463ae0 May 13 12:35:29 serenity kernel: ffff8800cb458f40 ffff8800c0871a10 ffffffff8114323f ffff8800cb458d00 May 13 12:35:29 serenity kernel: Call Trace: May 13 12:35:29 serenity kernel: [<ffffffff8114323f>] ? find_get_page+0x5f/0xc0 May 13 12:35:29 serenity kernel: [<ffffffff811ed988>] ? __find_get_block_slow+0xc8/0x170 May 13 12:35:29 serenity kernel: [<ffffffff811ed2b0>] ? generic_block_bmap+0x70/0x70 May 13 12:35:29 serenity kernel: [<ffffffff8150b609>] schedule+0x29/0x70 May 13 12:35:29 serenity kernel: [<ffffffff8150b8f4>] io_schedule+0x94/0xf0 May 13 12:35:29 serenity kernel: [<ffffffff811ed2be>] sleep_on_buffer+0xe/0x20 May 13 12:35:29 serenity kernel: [<ffffffff8150bce3>] __wait_on_bit+0x83/0xa0 May 13 12:35:29 serenity kernel: [<ffffffff811ed2b0>] ? generic_block_bmap+0x70/0x70 May 13 12:35:29 serenity kernel: [<ffffffff8150bd87>] out_of_line_wait_on_bit+0x87/0xb0 May 13 12:35:29 serenity kernel: [<ffffffff810b4060>] ? autoremove_wake_function+0x40/0x40 May 13 12:35:29 serenity kernel: [<ffffffff811ed3aa>] __wait_on_buffer+0x2a/0x30 May 13 12:35:29 serenity kernel: [<ffffffffa04d6b3d>] ext4_find_entry+0x3bd/0x4f0 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04d6cda>] ext4_lookup+0x6a/0x170 [ext4] May 13 12:35:29 serenity kernel: [<ffffffff811c46ed>] lookup_real+0x1d/0x70 May 13 12:35:29 serenity kernel: [<ffffffff811c9229>] do_last.isra.36+0x539/0xe30 May 13 12:35:29 serenity kernel: [<ffffffff811c7785>] ? path_init+0x335/0x410 May 13 12:35:29 serenity kernel: [<ffffffff811c9be7>] path_openat+0xc7/0x6e0 May 13 12:35:29 serenity kernel: [<ffffffff810a0c0f>] ? try_to_wake_up+0x1ff/0x2e0 May 13 12:35:29 serenity kernel: [<ffffffff811cb40d>] do_filp_open+0x4d/0xc0 May 13 12:35:29 serenity kernel: [<ffffffff811d82d7>] ? __alloc_fd+0xa7/0x130 May 13 12:35:29 serenity kernel: [<ffffffff811b9cbe>] do_sys_open+0x14e/0x250 May 13 12:35:29 serenity kernel: [<ffffffff811b9dde>] SyS_open+0x1e/0x20 May 13 12:35:29 serenity kernel: [<ffffffff81517629>] system_call_fastpath+0x16/0x1b May 13 12:35:29 serenity kernel: BrowserBlocking D 0000000000000000 0 1432 1 0x00000000 May 13 12:35:29 serenity kernel: ffff8803fa099b60 0000000000000082 ffff88041f00be00 ffff8800bf7af5c0 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff8803fa099fd8 00000000000146c0 ffff8800bf7af5c0 May 13 12:35:29 serenity kernel: ffff8803fa099aa8 ffffffff8109cb2a ffff880419600700 ffff88041f00be00 May 13 12:35:29 serenity kernel: Call Trace: May 13 12:35:29 serenity kernel: [<ffffffff8109cb2a>] ? update_rq_clock.part.78+0x1a/0x130 May 13 12:35:29 serenity kernel: [<ffffffff8101f575>] ? native_sched_clock+0x35/0xb0 May 13 12:35:29 serenity kernel: [<ffffffff8101f5f9>] ? sched_clock+0x9/0x10 May 13 12:35:29 serenity kernel: [<ffffffff810a41a5>] ? sched_clock_cpu+0xb5/0xe0 May 13 12:35:29 serenity kernel: [<ffffffff810156c1>] ? __switch_to+0x1f1/0x540 May 13 12:35:29 serenity kernel: [<ffffffff8150b609>] schedule+0x29/0x70 May 13 12:35:29 serenity kernel: [<ffffffffa049708d>] wait_transaction_locked+0x8d/0xd0 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa04973c2>] start_this_handle+0x262/0x610 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff8119c95a>] ? kmem_cache_alloc+0x1fa/0x220 May 13 12:35:29 serenity kernel: [<ffffffffa0497b8b>] jbd2__journal_start+0xfb/0x210 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffffa04d233a>] ? ext4_dirty_inode+0x2a/0x60 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04fdead>] __ext4_journal_start_sb+0x6d/0x110 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04d233a>] ext4_dirty_inode+0x2a/0x60 [ext4] May 13 12:35:29 serenity kernel: [<ffffffff811e65d8>] __mark_inode_dirty+0x38/0x2d0 May 13 12:35:29 serenity kernel: [<ffffffff811d55e1>] update_time+0x81/0xd0 May 13 12:35:29 serenity kernel: [<ffffffff811d5729>] touch_atime+0xf9/0x170 May 13 12:35:29 serenity kernel: [<ffffffff81145b1a>] generic_file_aio_read+0x54a/0x720 May 13 12:35:29 serenity kernel: [<ffffffff811ba137>] do_sync_read+0x67/0xa0 May 13 12:35:29 serenity kernel: [<ffffffff811ba797>] vfs_read+0x97/0x160 May 13 12:35:29 serenity kernel: [<ffffffff811bb2e9>] SyS_read+0x59/0xd0 May 13 12:35:29 serenity kernel: [<ffffffff81517629>] system_call_fastpath+0x16/0x1b May 13 12:35:29 serenity kernel: loop0 D 0000000000000000 0 1660 2 0x00000000 May 13 12:35:29 serenity kernel: ffff8803fc1d58a8 0000000000000046 ffff8803fc1d58b8 ffff88041963b110 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff8803fc1d5fd8 00000000000146c0 ffff88041963b110 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff88041963b110 ffff8800cbb93e68 ffff880417806f78 May 13 12:35:29 serenity kernel: Call Trace: May 13 12:35:29 serenity kernel: [<ffffffff810a0d52>] ? default_wake_function+0x12/0x20 May 13 12:35:29 serenity kernel: [<ffffffff810b4032>] ? autoremove_wake_function+0x12/0x40 May 13 12:35:29 serenity kernel: [<ffffffff810b3915>] ? __wake_up_common+0x55/0x90 May 13 12:35:29 serenity kernel: [<ffffffff8150b609>] schedule+0x29/0x70 May 13 12:35:29 serenity kernel: [<ffffffffa048a666>] wait_barrier+0xc6/0x190 [raid10] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa048eca4>] make_request+0x44/0x130 [raid10] May 13 12:35:29 serenity kernel: [<ffffffffa0458a83>] md_make_request+0x103/0x260 [md_mod] May 13 12:35:29 serenity kernel: [<ffffffff81145df1>] ? mempool_alloc+0x61/0x170 May 13 12:35:29 serenity kernel: [<ffffffff8126f728>] generic_make_request+0xf8/0x150 May 13 12:35:29 serenity kernel: [<ffffffff8126f7f8>] submit_bio+0x78/0x190 May 13 12:35:29 serenity kernel: [<ffffffff8114e02f>] ? test_set_page_writeback+0x14f/0x1e0 May 13 12:35:29 serenity kernel: [<ffffffffa04d3125>] ext4_io_submit+0x25/0x50 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04d3393>] ext4_bio_write_page+0x213/0x320 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04cad7a>] mpage_submit_page+0x5a/0x80 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04caeb0>] mpage_process_page_bufs+0x110/0x120 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04cb0a0>] mpage_prepare_extent_to_map+0x1e0/0x300 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa0497b8b>] ? jbd2__journal_start+0xfb/0x210 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffffa04cf400>] ? ext4_writepages+0x3c0/0xd20 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04fdead>] ? __ext4_journal_start_sb+0x6d/0x110 [ext4] May 13 12:35:29 serenity kernel: [<ffffffffa04cf42b>] ext4_writepages+0x3eb/0xd20 [ext4] May 13 12:35:29 serenity kernel: [<ffffffff811504ee>] do_writepages+0x1e/0x30 May 13 12:35:29 serenity kernel: [<ffffffff811445ed>] __filemap_fdatawrite_range+0x5d/0x80 May 13 12:35:29 serenity kernel: [<ffffffff8114470a>] filemap_write_and_wait_range+0x2a/0x70 May 13 12:35:29 serenity kernel: [<ffffffffa04c67a0>] ext4_sync_file+0x110/0x370 [ext4] May 13 12:35:29 serenity kernel: [<ffffffff811eb8a6>] vfs_fsync+0x26/0x40 May 13 12:35:29 serenity kernel: [<ffffffffa0eaefb2>] loop_thread+0x392/0x6a0 [loop] May 13 12:35:29 serenity kernel: [<ffffffffa0eae8e0>] ? __do_lo_send_write+0x120/0x120 [loop] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa0eaec20>] ? lo_receive+0x210/0x210 [loop] May 13 12:35:29 serenity kernel: [<ffffffff8108f2ea>] kthread+0xea/0x100 May 13 12:35:29 serenity kernel: [<ffffffff8108f200>] ? kthread_create_on_node+0x1a0/0x1a0 May 13 12:35:29 serenity kernel: [<ffffffff8151757c>] ret_from_fork+0x7c/0xb0 May 13 12:35:29 serenity kernel: [<ffffffff8108f200>] ? kthread_create_on_node+0x1a0/0x1a0 May 13 12:35:29 serenity kernel: jbd2/dm-0-8 D 0000000000000000 0 1732 2 0x00000000 May 13 12:35:29 serenity kernel: ffff8803fc331bb8 0000000000000046 0000000000000000 ffff8803fa4f6220 May 13 12:35:29 serenity kernel: 00000000000146c0 ffff8803fc331fd8 00000000000146c0 ffff8803fa4f6220 May 13 12:35:29 serenity kernel: ffff8803fc331b18 ffffffff810b3ba4 ffff88041892d200 0000000000000001 May 13 12:35:29 serenity kernel: Call Trace: May 13 12:35:29 serenity kernel: [<ffffffff810b3ba4>] ? __wake_up+0x44/0x50 May 13 12:35:29 serenity kernel: [<ffffffffa0eae70d>] ? loop_make_request+0x11d/0x1d0 [loop] May 13 12:35:29 serenity kernel: [<ffffffff811ed2b0>] ? generic_block_bmap+0x70/0x70 May 13 12:35:29 serenity kernel: [<ffffffff8150b609>] schedule+0x29/0x70 May 13 12:35:29 serenity kernel: [<ffffffff8150b8f4>] io_schedule+0x94/0xf0 May 13 12:35:29 serenity kernel: [<ffffffff811ed2be>] sleep_on_buffer+0xe/0x20 May 13 12:35:29 serenity kernel: [<ffffffff8150bce3>] __wait_on_bit+0x83/0xa0 May 13 12:35:29 serenity kernel: [<ffffffff811ed2b0>] ? generic_block_bmap+0x70/0x70 May 13 12:35:29 serenity kernel: [<ffffffff8150bd87>] out_of_line_wait_on_bit+0x87/0xb0 May 13 12:35:29 serenity kernel: [<ffffffff810b4060>] ? autoremove_wake_function+0x40/0x40 May 13 12:35:29 serenity kernel: [<ffffffff811ed3aa>] __wait_on_buffer+0x2a/0x30 May 13 12:35:29 serenity kernel: [<ffffffffa049bf4a>] jbd2_journal_commit_transaction+0x197a/0x19c0 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffffa04a1c4c>] kjournald2+0xec/0x2a0 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff810b4020>] ? __wake_up_sync+0x20/0x20 May 13 12:35:29 serenity kernel: [<ffffffffa04a1b60>] ? commit_timeout+0x10/0x10 [jbd2] May 13 12:35:29 serenity kernel: [<ffffffff8108f2ea>] kthread+0xea/0x100 May 13 12:35:29 serenity kernel: [<ffffffff8108f200>] ? kthread_create_on_node+0x1a0/0x1a0 May 13 12:35:29 serenity kernel: [<ffffffff8151757c>] ret_from_fork+0x7c/0xb0 May 13 12:35:29 serenity kernel: [<ffffffff8108f200>] ? kthread_create_on_node+0x1a0/0x1a0

2 2

[arch-general] linux-3.14.3-1 and FAT32 /boot partition mount fail
by Andrey Mivrenik 12 May '14

12 May '14

Hello, After Linux kernel update my system can't boot properly because of this error: > [FAILED] Failed to mount /boot Although it gives me opportunity to login as root. When I try to mount it manually: > mount: unknown filesystem type 'vfat' Kernel downgrade to 3.14.2-1 resolved this. So, did I miss something or it's a bug? I have to use FAT32 for /boot because I have that UEFI thing. Regards, -- *GPG Key ID:* D782DAB8

3 3

[arch-general] NTP: Possible permissions bug
by Kyle Terrien 12 May '14

12 May '14

Hi fellow Archers, I seem to be having trouble with ntpd.service since the 4.2.7 upgrade. I can't get ntpd to run as the ntp user. I'm using the /etc/ntp.conf provided by the package ntp. When starting ntpd.service (systemctl start ntp.service), ntpd spikes the CPU for a moment, and then spikes the CPU about every 5 minutes afterward. What's more is ntpq -p returns "No association ID's returned". I ran "ntpd -g -u ntp:ntp -p /run/ntpd.pid -d" (from the Systemd unit file). The results: <http://sprunge.us/QbYL> The part I found of interest were the lines that read: intres: EAI_SYSTEM errno 11 (Resource temporarily unavailable) means try again, right? select() returned -1: Interrupted system call select() returned -1: Interrupted system call I took out the "-u ntp:ntp" parameter (so ntp runs as root), and these errors disappeared. Also, ntpq -p returns the NTP servers I'm synchronized with. So, I'm pretty sure the issue is permissions related, but I have no idea what it's running into. Any insight? I currently modified /usr/lib/systemd/system/ntpd.service so that ntpd runs as root instead of the user ntp. (Is there a cleaner way to tweak a systemd unit file?) Everything seems to run fine for now. On a side note, the Wiki says that timedatectl (part of systemd) can use ntp for synchronization [1]. However, the man page for timedatectl shows an example where chrony (another NTP server) is running. Does ntpd.service need to be running for timedatectl to set time via NTP? Is there a way to force timedatectl to query NTP (for testing)? --Kyle [1] https://wiki.archlinux.org/index.php/Ntp#systemd_services

5 10

[arch-general] error: haskell-core: signature
by Ralf Mardorf 12 May '14

12 May '14

Hi, I don't know what to do, to get rid of the haskell-core errors [1] Regards, Ralf [1] https://github.com/archhaskell/habs/blob/master/README.md # cat /etc/pacman.conf [snip] [haskell-core] Server = http://xsounds.org/~haskell/core/$arch # pacman -Syu error: haskell-core: signature from "ArchHaskell (Magnus Therning) <magnus(a)therning.org>" is unknown trust :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date archaudio-production is up to date haskell-core is up to date error: database 'haskell-core' is not valid (invalid or corrupted database (PGP signature)) # pacman-key -l [snip] pub 2048D/4209170B 2012-12-26 uid ArchHaskell (Magnus Therning) <magnus(a)therning.org> sub 2048D/A418C0FE 2012-12-26 # gpg --list-keys [snip] pub 2048D/4209170B 2012-12-26 uid ArchHaskell (Magnus Therning) <magnus(a)therning.org> sub 2048D/A418C0FE 2012-12-26

3 2

[arch-general] Selective upgrade: pacman -Syu, "yes" but not the kernel
by Mihamina Rakotomandimby 12 May '14

12 May '14

Hi all, I would like to make my system up to date except for the kernel. "pacman -Syu" propose to upgrade a bunch of softwares that includes the kernel There's nothing wrong on upgrading the kernel, but I would like to delay it to the week-end. It's not a definitive refusal, it's just temporary. How to tell pacman "OK for the upgrades, but dont upgrade the kernel for now"? It currently wants to proceed with Packages (43): firefox-29.0.1-1 gawk-4.1.1-1 gcc-4.9.0-2 gcc-libs-4.9.0-2 grub-1:2.02.beta2-3 gtkspell3-3.0.6-1 gvfs-1.20.2-1 gvfs-gphoto2-1.20.2-1 gvfs-mtp-1.20.2-1 gvfs-smb-1.20.2-1 imagemagick-6.8.9.1-1 intel-dri-10.1.3-1 libcacard-2.0.0-2 libcdr-0.0.16-2 libmspub-0.0.6-2 libreoffice-base-4.2.4-1 libreoffice-calc-4.2.4-1 libreoffice-common-4.2.4-1 libreoffice-draw-4.2.4-1 libreoffice-en-US-4.2.4-1 libreoffice-fr-4.2.4-1 libreoffice-gnome-4.2.4-1 libreoffice-impress-4.2.4-1 libreoffice-writer-4.2.4-1 libva-1.3.1-1 libxcb-1.10-2 linux-3.14.3-1 linux-headers-3.14.3-1 man-pages-3.66-1 mesa-10.1.3-1 mesa-libgl-10.1.3-1 nouveau-dri-10.1.3-1 nspr-4.10.5-1 nss-3.16.1-1 pacman-4.1.2-6 poppler-0.26.0-1 poppler-glib-0.26.0-1 python2-paramiko-1.14.0-1 sdl-1.2.15-6 unrar-1:5.1.5-1 xarchiver-0.5.3-4 xf86-input-evdev-2.8.4-1 xfce4-mount-plugin-0.6.7-1

3 2

[arch-general] Resume from suspend in RAM fails
by nmset＠netcourrier.com 12 May '14

12 May '14

Hello, Resume from suspend in RAM fails even though I have followed the Arch Wiki recommendations, with latest 3.12.7 kernel (and before). The 'resume' hook has been added for mkinitcpio and the machine goes to suspend from the command line (pm-suspend) with no GUI enabled. All keyboard and mouse lights are off and the screen is just black with no backlight. I can't even login through SSH and can't get any PM debug info. It happens on one particular machine only and I'm quite stuck with it. Any suggestions to solve this ? I can provide other relevent information if required. Thanks.

4 7

[arch-general] out of memory while allocating z_stream
by Stephen E. Baker 10 May '14

10 May '14

Hello, As of yesterday I cannot boot, regardless of whether I choose the regular or failback kernel from the boot loader. I haven't been able to find anything on google, so I was hoping someone here might know what's going on. Last time my system was up I installed updates including the latest kernel, and I ran e4defrag over the disk. The computer is a ThinkPad T60, with a Core 2 Duo and 2GB of Ram. I am running the i686 version of Arch Linux. My boot loader is syslinux. In the mean time I'm downloading a new copy of the Arch Install ISO (all my existing recovery disks are too old to chroot from), and I will try reinstalling the kernel. Output: Loading ../vmlinuz-linux... ok Loading ../initramfs-linux.img...ok Probing EDD (edd=off to disable)... ok early console in decompress_kernel Decompressing Linux... Out of memory while allocating z_stream -- System halted

1 2

[arch-general] How to disable systemd-tmpfiles-clean.timer
by Olivier Langlois 10 May '14

10 May '14

Since a recent update (I have first noticed a couple of weeks ago this new systemd enhancement), systemd started to automatically clean /tmp directory daily. This is not something that I like as I prefer to decide when to clean up and to manually perform the clean up. I have tried systemctl stop systemd-tmpfiles-clean.timer systemctl disable systemd-tmpfiles-clean.timer The disabling apparently did not survived a reboot and the undesired systemd service came back. I guess that I could mess with tmpfiles-clean config file but I am just not interested in the service at all. What is the sure way method to disable it for good? thank you,

12 24