search for: git10

...> BROKEN == The display remains OFF. > More precisely stated it looks like this: - Last kernel with working resume/thaw http://koji.fedoraproject.org/koji/buildinfo?buildID=538208 kernel-3.16.0-0.rc0.git9.1.fc21 2014-06-13 - First kernel with broken resume/thaw kernel-3.16.0-0.rc0.git10.1.fc21 http://koji.fedoraproject.org/koji/buildinfo?buildID=538244 http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-3.15-git10.xz/f98fb42e79c966f8e139e27b61d933e0/patch-3.15-git10.xz 2014-06-13 The only difference in dmesg between working and broken kernel module with drm.debug=14 is [d...

...t looks like this: >> >> - Last kernel with working resume/thaw >> http://koji.fedoraproject.org/koji/buildinfo?buildID=538208 >> kernel-3.16.0-0.rc0.git9.1.fc21 >> 2014-06-13 >> >> - First kernel with broken resume/thaw >> kernel-3.16.0-0.rc0.git10.1.fc21 >> http://koji.fedoraproject.org/koji/buildinfo?buildID=538244 >> http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-3.15-git10.xz/f98fb42e79c966f8e139e27b61d933e0/patch-3.15-git10.xz >> 2014-06-13 >> >> The only difference in dmesg between working and b...

...>>> - Last kernel with working resume/thaw >>> http://koji.fedoraproject.org/koji/buildinfo?buildID=538208 >>> kernel-3.16.0-0.rc0.git9.1.fc21 >>> 2014-06-13 >>> >>> - First kernel with broken resume/thaw >>> kernel-3.16.0-0.rc0.git10.1.fc21 >>> http://koji.fedoraproject.org/koji/buildinfo?buildID=538244 >>> http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-3.15-git10.xz/f98fb42e79c966f8e139e27b61d933e0/patch-3.15-git10.xz >>> 2014-06-13 >>> >>> The only difference in dmesg b...

...(nouveau developers) generally ask for a git bisection is because we don't know or track specific distributions. Although your search has narrowed the problem down (thanks for that!), we don't know how big the difference is between kernel-3.16.0-0.rc0.git9.1.fc21 and kernel-3.16.0-0.rc0.git10.1.fc21. Is the difference literally just that one patch? Or were there more patches to nouveau or drm that might have been the culprit? So far I haven't succeeded in finding the exact differences between the two kernels. Git bisect on the upstream kernel on the other hand will always point...

...gt; > More precisely stated it looks like this: > > - Last kernel with working resume/thaw > http://koji.fedoraproject.org/koji/buildinfo?buildID=538208 > kernel-3.16.0-0.rc0.git9.1.fc21 > 2014-06-13 > > - First kernel with broken resume/thaw > kernel-3.16.0-0.rc0.git10.1.fc21 > http://koji.fedoraproject.org/koji/buildinfo?buildID=538244 > http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-3.15-git10.xz/f98fb42e79c966f8e139e27b61d933e0/patch-3.15-git10.xz > 2014-06-13 > > The only difference in dmesg between working and broken kernel module...

On Thu, 16 Nov 2006 00:16:26 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Paravirt breaks CONFIG_X86_PAE=y compilation: > > <-- snip --> > > ... > CC init/main.o > In file included from include2/asm/pgtable.h:245, > from > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/mm.h:40, > from >

On Thu, 16 Nov 2006 00:16:26 +0100 Adrian Bunk <bunk@stusta.de> wrote: > Paravirt breaks CONFIG_X86_PAE=y compilation: > > <-- snip --> > > ... > CC init/main.o > In file included from include2/asm/pgtable.h:245, > from > /home/bunk/linux/kernel-2.6/linux-2.6.19-rc5-mm2/include/linux/mm.h:40, > from >

...generally ask for a git bisection is because > we don't know or track specific distributions. Although your search has > narrowed the problem down (thanks for that!), we don't know how big the > difference is between kernel-3.16.0-0.rc0.git9.1.fc21 and > kernel-3.16.0-0.rc0.git10.1.fc21. Is the difference literally just that > one patch? Or were there more patches to nouveau or drm that might have > been the culprit? So far I haven't succeeded in finding the exact > differences between the two kernels. Git bisect on the upstream kernel > on the other han...

...sk for a git bisection is because >> we don't know or track specific distributions. Although your search has >> narrowed the problem down (thanks for that!), we don't know how big the >> difference is between kernel-3.16.0-0.rc0.git9.1.fc21 and >> kernel-3.16.0-0.rc0.git10.1.fc21. Is the difference literally just that >> one patch? Or were there more patches to nouveau or drm that might have >> been the culprit? So far I haven't succeeded in finding the exact >> differences between the two kernels. Git bisect on the upstream kernel >> on t...

...ection is because >>> we don't know or track specific distributions. Although your search has >>> narrowed the problem down (thanks for that!), we don't know how big the >>> difference is between kernel-3.16.0-0.rc0.git9.1.fc21 and >>> kernel-3.16.0-0.rc0.git10.1.fc21. Is the difference literally just that >>> one patch? Or were there more patches to nouveau or drm that might have >>> been the culprit? So far I haven't succeeded in finding the exact >>> differences between the two kernels. Git bisect on the upstream kernel &...

Hello, I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting hangs after these messages on the VGA console: pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff] reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff reserve RAM buffer: 00000001

Hello, I tried out kernel 3.1.0-rc2 on my i386 Laptop with Xen 4.1.1. Booting hangs after these messages on the VGA console: pci 0000:02:09.0: address space collision: [mem 0x000da000-0x000dafff] conflicts with reserved [mem 0x0009f800-0x000fffff] reserve RAM buffer: 00000000 0009f000 - 00000000 0009ffff reserve RAM buffer: 00000000 38400000 - 00000000 3bffffff reserve RAM buffer: 00000001