Oops: 0003 [#1] PREEMPT SMP NOPTI

2008(!) dual-core Atom box. model name : Intel(R) Atom(TM) CPU 330 @ 1.60GHz [1027540.690329] perf: interrupt took too long (12579 > 12560), lowering kernel.perf_event_max_sample_rate to 15000 [1027540.774026] perf: interrupt took too long (15754 > 15723), lowering kernel.perf_event_max_sa

Kernel panic - not syncing: Fatal exception in interrupt (file_free_rcu+0x14)

Not sure if the stack is crap or not, but this looks like an RCU crash? https://i.imgur.com/sBnNe1p.jpg Kyle. FileServer ~ # uname -a Linux FileServer.OpenWRT.local 4.12.5-gentoo #1 SMP PREEMPT Fri Aug 18 17:23:00 PDT 2017 x86_64 Intel(R) Atom(TM) CPU 330 @ 1.60GHz GenuineIntel GNU/Linux FileSer

Re: [PATCH V3 00/11] block-throttle: add .high limit

Not to compound upon this again. However if BFQ isn't suitable to replace CFQ for high I/O workloads (I've yet to see 20k IOPS on any reasonably sized SAN (SC4020 / v5000, etc)), can't we at-least default BFQ to become the default I/O scheduler for people otherwise requesting CFQ? Paolo has had a t

Fwd: [PATCH V3 00/11] block-throttle: add .high limit

Re-sending as plain-text as the Gmail Android App is still historically broken... -- Forwarded message -- From: Kyle Sanderson Date: Wed, Oct 5, 2016 at 7:09 AM Subject: Re: [PATCH V3 00/11] block-throttle: add .high limit To: Tejun Heo Cc: jmo...@redhat.com, Paolo Valente

Re: BUG: unable to handle kernel paging request at ffffe8ff7fc00001

2611.792716] ntfs: (device sda4): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover. [532611.792780] ntfs: (device sda4): ntfs_fill_super(): Not an NTFS volume. Thanks, Kyle. On Mon, Nov 16, 2015 at 5:53 AM, Kyle Sanderson wrote: > I'll re

BUG: unable to handle kernel paging request at ffffe8ff7fc00001

[290371.835867] BUG: unable to handle kernel paging request at e8ff7fc1 [290371.835891] IP: [] kstat_irqs+0x4f/0x90 [290371.835912] PGD 8172f063 PUD 0 [290371.835929] Oops: [#1] PREEMPT SMP [290371.835950] Modules linked in: xt_hashlimit ts_kmp xt_set ts_bm xt_string xt_length

Re: [PATCHv5] [media] saa7164: use an MSI interrupt when available

This has been plaguing users for years (there's a number of threads on the Ubuntu board). I've been using revision 1 of the patch without issue since early February. This is from having to constantly reboot the system to flawless recording. If something has been outstanding from Brendan, please let