similar to: No xen kernel image for k7 anymore!

Displaying 20 results from an estimated 2000 matches similar to: "No xen kernel image for k7 anymore!"

2004 Sep 10
1
Segfaults on K7
--- Asheesh Laroia <PaulProteus@technologist.com> wrote: > I'm running your debian packages on a K7 currently. They seem to be > working fine, including the xmms-flac package. I seem to be > experiencing > the same flac decoding problems > (state=6:FLAC__FILE_DECODER_STREAM_ERROR) > as Pritpaul Mahal, however. I'll see if I can reproduce these. It > could
2004 Sep 10
0
Segfaults on K7
I'm running your debian packages on a K7 currently. They seem to be working fine, including the xmms-flac package. I seem to be experiencing the same flac decoding problems (state=6:FLAC__FILE_DECODER_STREAM_ERROR) as Pritpaul Mahal, however. I'll see if I can reproduce these. It could just be a problem with my old FLAC files (from 0.9 and before). This K7 doesn't segfault on flac
2020 Oct 05
2
[PATCH] device: return error for unknown chipsets
Previously the code relied on device->pri to be NULL and to fail probing later. We really should just return an error inside nvkm_device_ctor for unsupported GPUs. Fixes: 24d5ff40a732 ("drm/nouveau/device: rework mmio mapping code to get rid of second map") Signed-off-by: Karol Herbst <kherbst at redhat.com> Cc: dann frazier <dann.frazier at canonical.com> ---
2020 Oct 06
1
[PATCH] device: return error for unknown chipsets
On Mon, Oct 05, 2020 at 03:52:30PM +0200, Karol Herbst wrote: > Previously the code relied on device->pri to be NULL and to fail probing > later. We really should just return an error inside nvkm_device_ctor for > unsupported GPUs. > > Fixes: 24d5ff40a732 ("drm/nouveau/device: rework mmio mapping code to get rid of second map") > Signed-off-by: Karol Herbst
2020 Oct 06
1
[PATCH] device: return error for unknown chipsets
On Tue, Oct 06, 2020 at 06:46:35PM +0200, Karol Herbst wrote: > On Tue, Oct 6, 2020 at 6:43 PM dann frazier <dann.frazier at canonical.com> wrote: > > > > On Mon, Oct 05, 2020 at 03:52:30PM +0200, Karol Herbst wrote: > > > Previously the code relied on device->pri to be NULL and to fail probing > > > later. We really should just return an error inside
2006 Feb 16
1
r3 - trunk
Author: acid Date: 2006-02-16 10:45:13 +0000 (Thu, 16 Feb 2006) New Revision: 3 Modified: trunk/changelog trunk/control Log: - Change maintainer and add uploaders field - Prepare changelog for new upload Modified: trunk/changelog =================================================================== --- trunk/changelog 2006-02-15 23:05:09 UTC (rev 2) +++ trunk/changelog 2006-02-16 10:45:13
2007 Mar 12
3
Bug#414471: xen-hypervisor-3.0.3-1-i386-pae: small bug in package description
Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: minor The package description reads: This version of the hypervisor is built with PAE enabled, in order to support systems with more than 4GB of memory. If you have less than that you should probably choose the non -pae version. That's not entirely true. I tried installing the non-pae version on my ProLiant
2006 Feb 18
1
r24 - trunk/debian/patches
Author: tha-guest Date: 2006-02-18 22:55:21 +0000 (Sat, 18 Feb 2006) New Revision: 24 Removed: trunk/debian/patches/30rename-pae-hypervisor.dpatch Log: Guido found a better way to have the pae hypervisor installed with another name without patching upstream and it seems to work as good as the patched upstream version, so I removed my patch from svn again. There seems to be no need to just
2004 Sep 10
2
Segfaults on K7
I got a new Athlon recently, and to my surprise, FLAC started segfaulting, even when recompiled. The problem goes away if I build with --disable-asm-optimizations. Has anyone else had problems of this sort? Here are the specs on the processor: processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 4 model name : AMD Athlon(tm) Processor stepping :
2006 Feb 19
1
r26 - in trunk/debian: . patches
Author: ultrotter Date: 2006-02-19 18:38:10 +0000 (Sun, 19 Feb 2006) New Revision: 26 Added: trunk/debian/patches/30xenchangeset.dpatch Modified: trunk/debian/patches/00list trunk/debian/patches/10sysconfig.dpatch trunk/debian/rules Log: Add 10sysconfig.dpatch description Add 30xenchangeset.dpatch to make the xen changeset configurable Force the xen changeset to be the correct one
2006 Mar 11
1
Non-linear Regression : Error in eval(expr, envir, enclos)
Hi.. i have an expression of the form: model1<-nls(y~beta1*(x1+(k1*x2)+(k1*k1*x3)+(k2*x4)+(k2*k1*x5)+(k2*k2*x6)+(k3*x7)+(k3*k4*x8)+(k3*k2*x9)+(k3*k3*x10)+ (k4*x11)+(k4*k1*x12)+(k4*k2*x13)+(k4*k3*x14)+(k4*k4*x15)+(k5*x16)+(k5*k1*x17)+(k5*k2*x18)+(k5*k3*x19)+
2018 May 21
0
DSE: Remove useless stores between malloc & memset
"memory accesses between the malloc and the memset without an expensive linear scan of the block/function" (1) do you mean just use "memoryIsNotModifiedBetween" function in DSE to check it? x = maloc(..); memset(x, ...) (2) GetUnderlyingObject would give me Value * (from malloc) ? Also another case: memset(s, 0, len); // len > 1 return strlen(s); // optimize to 0 (3)
2006 Jul 02
1
mess
I forgot to present the problem of wine failure to launch also to the wine list. While my amd64 debian etch is in order, 32 bit debian etch has suffered much and is now in a state of semi-mess. Kernel booted is linux-image-2.6-15-1-k7: but #aptitude shows also a collection of kernels, partly broken: BA linux-image-2.6-486 BA linux-image-2.6-686 BA linux-image-2.6-686-smp iA linux-image-2.6-k7
2018 May 21
2
DSE: Remove useless stores between malloc & memset
memoryIsNotModifiedBetween is precisely the sort of expensive walk we shouldn't be doing... I'm surprised it hasn't caused any serious issues yet.  Ideally, what we should be doing is using MemorySSA to find a dependency from the memset: if the closest dependency is the malloc, there aren't any stores between the memset and the malloc.  (But we aren't using MemorySSA in
2003 Mar 22
0
ext3 oops with 2.4.20
Bug report follows. Please CC me if you want me to read the reply, as I'm not subscribed to ext3-users. [1.] One line summary of the problem: Ext3 has just causing filesystem corruption which required fsck to fix. [2.] Full description of the problem/report: I just had my machine lock up with an ext3 oops, preceeded by a bunch of error messages in the logs. On rebooting, after replaying the
2006 Sep 19
1
new issue
hallo, I've chanced packages and now I don't get the strange behaviour I noticed yesterday but a more common problem: kernel panic my grub stanza is: title Xen 3.0.2-1-i386 / Debian GNU/Linux, kernel 2.6.16-2-xen-k7 root (hd0,0) kernel /xen-3.0.2-1-i386.gz module /vmlinuz-2.6.16-2-xen-k7 root=/dev/hda2 ro console=tty0 savedefault and I consider it
2006 Mar 02
1
upgrade report (2.0.6 -> 3.0-testing+pkgxen)
Hi, so here is finally my upgrade report for my testsystem. I tried to upgrade to xen3 while xen2 (hypervisor, dom0 kernel + 1 domU) was running: 1) if xen2 (adams latest packages in this case) were installed and we would release our package as it is, we would generate the following enviorment: # apt-get upgrade -u Reading package lists... Done Building dependency tree... Done The following
1997 Apr 30
2
R-alpha: New Incomplete Beta Function
Here is a drop-in replacement for the R incomplete beta function. src/math/pbeta.c It is a slightly modified version of the cephes library one from Netlib. In the few cases I tried it seems to give at least 14 digit agreement with the one in S-PLUS (its hard to get more). I'm not sure what performance is like. I'd like to know if it helps with some of the problems which have been
2006 Feb 17
1
r9 - trunk/debian
Author: ultrotter Date: 2006-02-17 06:56:29 +0000 (Fri, 17 Feb 2006) New Revision: 9 Modified: trunk/debian/changelog trunk/debian/control Log: Change the version and debian revision, as agreed on the ML Start tracking the bugs that need to be closed on upload Modified: trunk/debian/changelog =================================================================== --- trunk/debian/changelog
2018 May 22
0
DSE: Remove useless stores between malloc & memset
Can you help a bit? I try to work with DSE but I got the following assert: opt: /home/xbolva00/LLVM/llvm/include/llvm/ADT/Optional.h:176: T* llvm::Optional<T>::getPointer() [with T = llvm::MemoryLocation]: Assertion `Storage.hasVal' failed. static bool eliminateStrlen(CallInst *CI, BasicBlock::iterator &BBI, AliasAnalysis *AA, MemoryDependenceResults