Displaying 8 results from an estimated 8 matches for "0x844".
Did you mean:
0x44
2005 Sep 06
2
Kernel Panic!
...13f/0x18e
Sep 3 04:03:10 qu015 kernel: [<c016a553>] shrink_dcache_memory
+0x14/0x2b
Sep 3 04:03:10 qu015 kernel: [<c0144e2c>] shrink_slab+0xf8/0x161
Sep 3 04:03:10 qu015 kernel: [<c01460b8>] balance_pgdat+0x1d2/0x2f8
Sep 3 04:03:10 qu015 kernel: [<c02c5604>] schedule+0x844/0x87a
Sep 3 04:03:10 qu015 kernel: [<c01462a8>] kswapd+0xca/0xcc
Sep 3 04:03:10 qu015 kernel: [<c011f6ee>] autoremove_wake_function
+0x0/0x2d
Sep 3 04:03:10 qu015 kernel: [<c02c7296>] ret_from_fork+0x6/0x14
Sep 3 04:03:10 qu015 kernel: [<c011f6ee>] autoremove_wake_fu...
2020 Apr 02
0
[vhost:vhost 22/22] vdpa_sim.c:undefined reference to `vringh_iov_push_iotlb'
..._complete_iotlb'
m68k-linux-ld: drivers/vdpa/vdpa_sim/vdpa_sim.o: in function `vdpasim_set_status':
vdpa_sim.c:(.text+0x764): undefined reference to `vringh_init_iotlb'
m68k-linux-ld: drivers/vdpa/vdpa_sim/vdpa_sim.o: in function `vdpasim_set_vq_ready':
vdpa_sim.c:(.text+0x844): undefined reference to `vringh_init_iotlb'
m68k-linux-ld: drivers/vdpa/vdpa_sim/vdpa_sim.o: in function `vdpasim_dev_init':
vdpa_sim.c:(.init.text+0xe4): undefined reference to `vringh_set_iotlb'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitt...
2004 Apr 26
2
[LLVMdev] x86 cogen quality
...i[0x849e768]
lli[0x849e974]
/lib/tls/libc.so.6[0x420277b8]
/lib/tls/libc.so.6(abort+0x1d5)[0x42028c55]
/lib/tls/libc.so.6[0x42021043]
lli(llvm::MRegisterInfo::isPhysicalRegister(unsigned)+0x25)[0x8314863]
lli((anonymous
namespace)::RA::assignRegOrStackSlotAtInterval(llvm::LiveIntervals::Interval*)+0x844)[0x8307d16]
lli((anonymous namespace)::RA::linearScan()+0x3c1)[0x8306aff]
lli((anonymous
namespace)::RA::runOnMachineFunction(llvm::MachineFunction&)+0x1d7)[0x83066f1]
lli(llvm::MachineFunctionPass::runOnFunction(llvm::Function&)+0x28)[0x83144fe]
lli(llvm::PassManagerTraits<llvm::Functi...
2005 Jul 15
2
Strange problem with SIP and CAPI
...EN=0014
Controller/PLCI/NCCI = 0x101
Info = 0x0
-- CONNECT_CONF ID=003 #0x0844 LEN=0014
Controller/PLCI/NCCI = 0x101
Info = 0x0
== received CONNECT_CONF PLCI = 0x101 INFO = 0
> sent CONNECT_REQ MN =0x844
-- Called 010xxxxxx:b0478xxxxxx
-- INFO_IND ID=003 #0x811c LEN=0015
Controller/PLCI/NCCI = 0x101
InfoNumber = 0x8002
InfoElement = default
-- INFO_IND ID=003 #0x811c LEN=0015
Controller/PLCI/NCCI = 0x101
InfoNumbe...
2004 Apr 21
0
[LLVMdev] x86 cogen quality
On Wed, Apr 21, 2004 at 11:01:48AM +0200, Finn S Andersen wrote:
> For some of the benchmarks the linear scan regalloc
> works. When it does, results are in the x1.0 - 1.5
> range. Unfortunately, the linear scan allocator breaks
> on most of my code.
Is there a chance you can try cvs? I would be interested to
get a simplified test case where the allocator breaks. A lot of
2004 Apr 21
4
[LLVMdev] x86 cogen quality
Hi, I have a question about x86 code quality.
I have run a few benchmarks and compared the
running time of executables created by LLVM to
executables created by gcc.
It appears that code generated by LLVM is x1.5 - x3
times slower than code generated by gcc, for the x86
For some of the benchmarks the linear scan regalloc
works. When it does, results are in the x1.0 - 1.5
range. Unfortunately,
2008 May 21
9
Slow pkginstalls due to long door_calls to nscd
Hi all,
I am installing a zone onto two different V445s running S10U4 and the
zones are taking hours to install (about 1000 packages), that is, the
problem is identical on both systems. A bit of trussing and dtracing has
shown that the pkginstalls being run by the zoneadm install are making
door_call calls to nscd that are taking very long, so far observed to be
5 to 40 seconds, but always in
2007 Nov 14
10
[GE users] Apple Leopard has dtrace -- anyone used the SGE probes/scripts yet?
Hi,
Chris (cc) and I try to get the SGE master monitor work with Apple Leopard
dtrace. Unfortunately we are stuck with the error msg below.
Anyone having an idea what could be the cause? What I can rule out as
cause is function inlining for the reasons explained below.
Background information on SGE master monitor implementation is under
http://wiki.gridengine.info/wiki/index.php/Dtrace