results but one
concern. Notably, when running in conjuction with BitDefender Anti-Virus I
have noticed issues when cloning large git projects (seems to be a good stress
test on open()). I believe the problems go away when BD is stopped. At this
point I'm not sure if the issue lies more with
On 12/29/18 3:34 PM, Orion Poplawski wrote:
On 12/29/18 3:04 PM, Orion Poplawski wrote:
On Thu 22-02-18 15:14:54, Kunal Shubham wrote:
>> On Fri 16-02-18 15:14:40, t.vi...@samsung.com wrote:
>> From: Vivek Trivedi
>> >> If fanotify userspace response server thread is
On 12/29/18 3:04 PM, Orion Poplawski wrote:
On Thu 22-02-18 15:14:54, Kunal Shubham wrote:
>> On Fri 16-02-18 15:14:40, t.vi...@samsung.com wrote:
>> From: Vivek Trivedi
>> >> If fanotify userspace response server thread is frozen first,
>> it may fail to send res
vent->response) {
+ ret =
wait_event_freezable(group->fanotify_data.access_waitq,
+ event->response);
+ if (ret < 0)
+ return ret;
+ }
/* userspace responded, convert to something usable */
From: Orion Poplawski
While trying look at just "warning" or stronger messages with "journalctl
--priority 0..4" I keep
seeing:
Sep 29 07:10:29 barry kernel: Zone ranges:
Sep 29 07:10:29 barry kernel: DMA [mem 0x1000-0x00ff]
Sep 29 07:10:29 barry ker
Peter Hurley hurleysoftware.com> writes:
> Based on the other reports from Mikael and David, I suspect this problem
> may have to do with my commit 699390354da6c258b65bf8fa79cfd5feaede50b6:
>
>pty: Ignore slave pty close() if never successfully opened
>
> This commit poisons the pty under ce
41:e3ccc1e2:ace1579a rd_LVM_LV=vg_root/root
rd_LVM_LV=vg_root/swap rd_NO_LUKS rd_NO_DM LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us
crashkernel=512M-2G:64M,2G-:128M console=tty0 console=ttyS0,115200
Any ideas? I'm at a loss.
--
Orion Poplawski
Technical Manage
:53:01 saga kernel: sd 7:0:0:0: Attached scsi generic sg5 type 0
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA DivisionFAX: 303-415-9702
3380 Mitchell Lane [EMAIL PROTECTED]
Boulder, CO 80301 http://www.cora.nw
Robert Hancock wrote:
Orion Poplawski wrote:
Can someone please explain to me what these mean?
EDAC k8 MC1: general bus error: participating processor(local node
origin), time-out(no timeout) memory transaction type(generic read),
mem or i/o(mem access), cache level(generic)
EDAC MC1: CE
0xc8f4, row
1, channel 0, label "": k8_edac
EDAC MC1: CE - no information available: k8_edac Error Overflow set
EDAC k8 MC1: extended error code: ECC chipkill x4 error
Thanks!
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division
Ingo Molnar wrote:
* Lee Revell <[EMAIL PROTECTED]> wrote:
This fixes all the NFS related latency problems I was seeing. Now the
longest latency from an NFS kernel compile with "make -j64" is 391
usecs in get_swap_page.
great! The latest patches (-42-08 and later) have the reworked
nfs_scan_li
11 matches
Mail list logo
