search for: lume

Displaying 8 results from an estimated 8 matches for "lume".

Did you mean: lme
2018 Sep 07
1
[PATCH] PCI: Reprogram bridge prefetch registers on resume
[+cc LKML, Dave, Luming] On Fri, Sep 07, 2018 at 05:05:15PM +0200, Peter Wu wrote: > On Fri, Sep 07, 2018 at 01:36:14PM +0800, Daniel Drake wrote: > <..> > > Thomas Martitz reports that this workaround also solves an issue where > > the AMD Radeon Polaris 10 GPU on the HP Zbook 14u G5 is unresponsive > > after S3 suspend/resume. > > Where was this claimed? It
2006 Dec 13
0
Problem in Converting Zoo Objects to Dataframes
...t;,periodici ty="daily") intra<-blpGetData(conn, c("NOK1V FH Equity","AUA AV Equity"), "LAST_PRICE", start=as.chron(as.Date("10/11/2006", "%m/%d/%Y")),end=as.chron(as.Date("12/5/2006","%m/%d/%Y")),barfields="VO LUME", barsize=10) bb=as.data.frame(intra) blpDisconnect(conn) " But there is some problem in converting "intra" zoo object to "intra" a data frame. I get the below error. > bb=as.data.frame(intra) Error in substr(x, as.integer(start), as.integer(stop)) :...
2018 Apr 09
2
Gluster cluster on two networks
...imes on server (systemd -> glusterd): [2018-04-09 11:46:46.254071] C [mem-pool.c:613:mem_pools_init_early] 0-mem-pool: incorrect order of mem-pool initialization (init_done=3) Client logs: Client on 192-net: [2018-04-09 11:35:31.402979] I [MSGID: 114046] [client-handshake.c:1231:client_setvolume_cbk] 5-urd-gds-volume-client-1: Connected to urd-gds-volume-client-1, attached to remote volume '/urd-gds/gluster'. [2018-04-09 11:35:31.403019] I [MSGID: 114047] [client-handshake.c:1242:client_setvolume_cbk] 5-urd-gds-volume-client-1: Server and Client lk-version numbers are not same, reo...
2018 Apr 10
0
Gluster cluster on two networks
...> [2018-04-09 11:46:46.254071] C [mem-pool.c:613:mem_pools_init_early] > 0-mem-pool: incorrect order of mem-pool initialization (init_done=3) > > > Client logs: > > Client on 192-net: > > [2018-04-09 11:35:31.402979] I [MSGID: 114046] [client-handshake.c:1231:client_setvolume_cbk] > 5-urd-gds-volume-client-1: Connected to urd-gds-volume-client-1, attached > to remote volume '/urd-gds/gluster'. > [2018-04-09 11:35:31.403019] I [MSGID: 114047] [client-handshake.c:1242:client_setvolume_cbk] > 5-urd-gds-volume-client-1: Server and Client lk-version numbe...
2018 Apr 10
1
Gluster cluster on two networks
...800f04bf99f urd-gds-003 Connected ad893466-ad09-47f4-8bb4-4cea84085e5b urd-gds-004 Connected bfe05382-7e22-4b93-8816-b239b733b610 urd-gds-000 Connected 912bebfd-1a7f-44dc-b0b7-f001a20d58cd localhost Connected Client mount command (same on both sides): mount -t glusterfs urd-gds-001:/urd-gds-volume /mnt Regards Marcus On Tue, Apr 10, 2018 at 06:24:05PM +0530, Milind Changire wrote: > Marcus, > Can you share server-side gluster peer probe and client-side mount > command-lines. > > > > On Tue, Apr 10, 2018 at 12:36 AM, Marcus Peders?n <marcus.pedersen at slu.se>...
2005 Oct 07
2
Assign references
Folks, I've run into trouble while writing functions that I hope will create and modify a dataframe or two. To that end I've written a toy function that simply sets a couple of variables (well, tries but fails). Searching the archives, Thomas Lumley recently explained the <<- operator, showing that it was necessary for x and y to exist prior to the function call, but I haven't
2018 Apr 10
0
Gluster cluster on two networks
...times on server (systemd -> glusterd): [2018-04-09 11:46:46.254071] C [mem-pool.c:613:mem_pools_init_early] 0-mem-pool: incorrect order of mem-pool initialization (init_done=3) Client logs: Client on 192-net: [2018-04-09 11:35:31.402979] I [MSGID: 114046] [client-handshake.c:1231:client_setvolume_cbk] 5-urd-gds-volume-client-1: Connected to urd-gds-volume-client-1, attached to remote volume '/urd-gds/gluster'. [2018-04-09 11:35:31.403019] I [MSGID: 114047] [client-handshake.c:1242:client_setvolume_cbk] 5-urd-gds-volume-client-1: Server and Client lk-version numbers are not same, reo...
2018 Sep 07
9
[PATCH] PCI: Reprogram bridge prefetch registers on resume
On 38+ Intel-based Asus products, the nvidia GPU becomes unusable after S3 suspend/resume. The affected products include multiple generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs many errors such as: fifo: fault 00 [READ] at 0000005555555000 engine 00 [GR] client 04 [HUB/FE] reason 4a [] on channel -1 [007fa91000 unknown] DRM: failed to idle channel 0 [DRM]