Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Wed, Jul 22, 2009 at 04:45:42AM +0200, Frans Pop wrote: Note that an additional issue was found with 2.6.27 after the change to -fno-strict-overflow. See http://lkml.org/lkml/2009/7/20/80 and follow-ups for details. The cause (compiler bug in gcc-4.2.4) was identified in http://lkml.org/lkml/2009/7/21/423 and it looks like it's going to be fixed with a kernel patch: http://lkml.org/lkml/2009/7/21/499. But it shows that there may definitely be unexpected effects from the change for arches using gcc-4.2 or later in Lenny. From that thread it looks like its only an issue for gcc-4.2 (not 4.3). But, since we did include gcc-4.2 in lenny and the patch is trivial I went ahead and applied it. Thanks! -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
Note that an additional issue was found with 2.6.27 after the change to -fno-strict-overflow. See http://lkml.org/lkml/2009/7/20/80 and follow-ups for details. The cause (compiler bug in gcc-4.2.4) was identified in http://lkml.org/lkml/2009/7/21/423 and it looks like it's going to be fixed with a kernel patch: http://lkml.org/lkml/2009/7/21/499. But it shows that there may definitely be unexpected effects from the change for arches using gcc-4.2 or later in Lenny. Cheers, FJP -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Thu, Jul 16, 2009 at 03:13:56PM +0200, Frans Pop wrote: On Thursday 16 July 2009, Frans Pop wrote: On Wednesday 15 July 2009, dann frazier wrote: On Mon, Jul 13, 2009 at 11:22:12AM +0200, Frans Pop wrote: Linus has committed a different solution: replacing -fwrapv by -fno-strict-overflow. See upstream commit a137802ee839ace40079bebde24cfb416f73208a. I tried applying that fix, but it causes a build failure because the compiler we use for lenny (gcc-4.1) doesn't support it. It seems strange that upstream would drop '-fwrapv' due to problems w/ gcc-4.1.x, but then require an option that's not supported by gcc-4.1 at all. Maybe that option got added in the 4.1.x stream after Debian released it? Maybe I'm missing a kernel change that would prevent this option from being used in 4.1? That's weird. IIUC the 'call cc-option' function is supposed to check whether an option is supported by the gcc version being used and only actually add it if it is. See Documentation/kbuild/makefiles.txt and scripts/Kbuild.include. 2.6.24-17 + Linus' patch builds fine here for s390 with gcc-4.1; the -fno-strict-overflow option is not added. Found the issue. linux-2.6 passes the CC flag in an included makefile snippet (.kernelvariables). Just merging the patch from upstream causes this sequence to happen: CC = gcc Does CC support -fno-strict-overflow? If so, add it to CFLAGS CC = gcc-4.1 Adjusting the order fixes it.. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Wednesday 15 July 2009, dann frazier wrote: On Mon, Jul 13, 2009 at 11:22:12AM +0200, Frans Pop wrote: Linus has committed a different solution: replacing -fwrapv by -fno-strict-overflow. See upstream commit a137802ee839ace40079bebde24cfb416f73208a. I tried applying that fix, but it causes a build failure because the compiler we use for lenny (gcc-4.1) doesn't support it. It seems strange that upstream would drop '-fwrapv' due to problems w/ gcc-4.1.x, but then require an option that's not supported by gcc-4.1 at all. Maybe that option got added in the 4.1.x stream after Debian released it? Maybe I'm missing a kernel change that would prevent this option from being used in 4.1? That's weird. IIUC the 'call cc-option' function is supposed to check whether an option is supported by the gcc version being used and only actually add it if it is. See Documentation/kbuild/makefiles.txt and scripts/Kbuild.include. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Thursday 16 July 2009, Frans Pop wrote: On Wednesday 15 July 2009, dann frazier wrote: On Mon, Jul 13, 2009 at 11:22:12AM +0200, Frans Pop wrote: Linus has committed a different solution: replacing -fwrapv by -fno-strict-overflow. See upstream commit a137802ee839ace40079bebde24cfb416f73208a. I tried applying that fix, but it causes a build failure because the compiler we use for lenny (gcc-4.1) doesn't support it. It seems strange that upstream would drop '-fwrapv' due to problems w/ gcc-4.1.x, but then require an option that's not supported by gcc-4.1 at all. Maybe that option got added in the 4.1.x stream after Debian released it? Maybe I'm missing a kernel change that would prevent this option from being used in 4.1? That's weird. IIUC the 'call cc-option' function is supposed to check whether an option is supported by the gcc version being used and only actually add it if it is. See Documentation/kbuild/makefiles.txt and scripts/Kbuild.include. 2.6.24-17 + Linus' patch builds fine here for s390 with gcc-4.1; the -fno-strict-overflow option is not added. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Mon, Jul 13, 2009 at 11:22:12AM +0200, Frans Pop wrote: Linus has committed a different solution: replacing -fwrapv by -fno-strict-overflow. See upstream commit a137802ee839ace40079bebde24cfb416f73208a. I tried applying that fix, but it causes a build failure because the compiler we use for lenny (gcc-4.1) doesn't support it. It seems strange that upstream would drop '-fwrapv' due to problems w/ gcc-4.1.x, but then require an option that's not supported by gcc-4.1 at all. Maybe that option got added in the 4.1.x stream after Debian released it? Maybe I'm missing a kernel change that would prevent this option from being used in 4.1? For Debian, I guess our options are to either just revert the fwrapv fix, or add the above changset but make it dependent on compiler version. Both should be equivalent for the debian binaries, but the latter would be an improvement for folks who build their own kernels from our source with newer compilers. No idea how significant that # of users is though. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
Linus has committed a different solution: replacing -fwrapv by -fno-strict-overflow. See upstream commit a137802ee839ace40079bebde24cfb416f73208a. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Friday 10 July 2009, dann frazier wrote: Maybe the -fwrapv change? Bingo. Makes a lot of sense too for an issue related to gcc version. Reverting only that patch on top of -17 results in good boot too. Gah! And it's even a known issue: - http://bugzilla.kernel.org/show_bug.cgi?id=13012 - http://lkml.org/lkml/2009/4/9/458 Does not yet look to be fixed upstream though. I only found 740ebe4a54, but that's mips only. P.S. Having the full series history in the kernel source was great for tracking this bug! It allowed me to use my own (cross-)build system I normally use to build upstream kernels (using 'make deb-pkg') in a very straightforward manner. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
Processing commands for cont...@bugs.debian.org: tags 536354 patch Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
tags 536354 patch thanks On Friday 10 July 2009, Frans Pop wrote: On Friday 10 July 2009, dann frazier wrote: Maybe the -fwrapv change? Bingo. Makes a lot of sense too for an issue related to gcc version. I've proposed the attached patch on lkml: http://lkml.org/lkml/2009/7/10/49. From: Frans Pop elen...@planet.nl Subject: Only add '-fwrapv' gcc CFLAGS for gcc 4.3 and later This flag has been shown to cause init to segfault for kernels compiled with gcc-4.1. gcc version 4.2.4 has been shown to be OK, but as there is some uncertainty the flag is only added for 4.3 and later. This fixes http://bugzilla.kernel.org/show_bug.cgi?id=13012. Signed-off-by: Frans Pop elen...@planet.nl diff --git a/Makefile b/Makefile index 0aeec59..2f8756e 100644 --- a/Makefile +++ b/Makefile @@ -565,7 +565,8 @@ KBUILD_CFLAGS += $(call cc-option,-Wdeclaration-after-statement,) KBUILD_CFLAGS += $(call cc-option,-Wno-pointer-sign,) # disable invalid can't wrap optimizations for signed / pointers -KBUILD_CFLAGS += $(call cc-option,-fwrapv) +KBUILD_CFLAGS += $(shell if [ $(call cc-version) -ge 0430 ]; then \ + echo $(call cc-option,-fwrapv); fi ;) # revert to pre-gcc-4.4 behaviour of .eh_frame KBUILD_CFLAGS += $(call cc-option,-fno-dwarf2-cfi-asm)
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Fri, 2009-07-10 at 09:51 +0200, Frans Pop wrote: tags 536354 patch thanks On Friday 10 July 2009, Frans Pop wrote: On Friday 10 July 2009, dann frazier wrote: Maybe the -fwrapv change? Bingo. Makes a lot of sense too for an issue related to gcc version. I've proposed the attached patch on lkml: http://lkml.org/lkml/2009/7/10/49. Perhaps we should be using -fno-strict-overflow instead of simply removing this option? Ben. -- Ben Hutchings No political challenge can be met by shopping. - George Monbiot signature.asc Description: This is a digitally signed message part
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Friday 10 July 2009, Ben Hutchings wrote: On Fri, 2009-07-10 at 09:51 +0200, Frans Pop wrote: On Friday 10 July 2009, Frans Pop wrote: On Friday 10 July 2009, dann frazier wrote: Maybe the -fwrapv change? Bingo. Makes a lot of sense too for an issue related to gcc version. I've proposed the attached patch on lkml: http://lkml.org/lkml/2009/7/10/49. Perhaps we should be using -fno-strict-overflow instead of simply removing this option? It looks like that option was only introduced with gcc 4.2. At least, I can't find it in the manual for gcc 4.1. So it would not make any difference for this bug. It does make the case a bit stronger to change my check to also allow -fwrapv for gcc 4.2 though. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Friday 10 July 2009, Frans Pop wrote: I've proposed the attached patch on lkml: http://lkml.org/lkml/2009/7/10/49. The version check in the patch was incorrect. Here's an improved version that also allows -fwrapv for gcc 4.2. See also the follow ups on lkml. From: Frans Pop elen...@planet.nl Subject: Only add '-fwrapv' to gcc CFLAGS for gcc 4.2 and later This flag has been shown to cause init to segfault for kernels compiled with gcc-4.1. gcc version 4.2.4 has been shown to be OK. This fixes http://bugzilla.kernel.org/show_bug.cgi?id=13012. Reported-by: Barry K. Nathan bar...@pobox.com Signed-off-by: Frans Pop elen...@planet.nl diff --git a/Makefile b/Makefile index 0aeec59..2519fde 100644 --- a/Makefile +++ b/Makefile @@ -565,7 +565,8 @@ KBUILD_CFLAGS += $(call cc-option,-Wdeclaration-after-statement,) KBUILD_CFLAGS += $(call cc-option,-Wno-pointer-sign,) # disable invalid can't wrap optimizations for signed / pointers -KBUILD_CFLAGS += $(call cc-option,-fwrapv) +KBUILD_CFLAGS += $(shell if [ $(call cc-version) -ge 0402 ]; then \ + echo $(call cc-option,-fwrapv); fi ;) # revert to pre-gcc-4.4 behaviour of .eh_frame KBUILD_CFLAGS += $(call cc-option,-fno-dwarf2-cfi-asm)
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
Package: linux-2.6 Version: 2.6.26-17 Severity: important A user reported on d-s390 [1] that a Lenny installation on s390 failed with a kernel panic during boot. I could reproduce the panic on my Hercules system using the installer. I then installed the current Lenny kernel on my installed Hercules system (running sid), and when I rebooted that with .26 I got the same panic, so it looks to be a kernel problem and not an installer problem. We included an s390 specific patch in 2.6.26-16 for #511334, but TBH I would be surprised if that was the cause given that it was very well tested. I'll try to look into this myself but can't give an ETA for results. Cheers, FJP [1] http://lists.debian.org/debian-s390/2009/07/msg2.html (contains boot log from submitter) Here's the boot log from my Hercules system: 0.00! Initializing cgroup subsys cpuset 0.00! Initializing cgroup subsys cpu 0.00! Linux version 2.6.26-2-s390 (Debian 2.6.26-17) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Mon Jun 22 09:19:01 UTC 2009 0.00! We are running native (31 bit mode) 0.00! This machine has an IEEE fpu 0.00! Zone PFN ranges: 0.00! Normal 0 -65536 0.00! Movable zone start PFN for each node 0.00! early_node_map 1! active PFN ranges 0.00! 0:0 -65535 0.00! Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65023 0.00! Kernel command line: ro vmpoff=LOGOFF root=/dev/disk/by-path/ccw-0.0.0120-part1 BOOT_IMAGE=3 0.00! PID hash table entries: 1024 (order: 10, 4096 bytes) 17179569.184434! console ttyS0! enabled 17179569.186173! Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) 17179569.196175! Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) 17179569.323701! Memory: 250240k/262144k available (2273k kernel code, 0k reserved, 843k data, 148k init) 17179569.324046! Write protected kernel read-only data: 0x12000 - 0x2eefff 17179569.327670! Security Framework initialized 17179569.327875! SELinux: Disabled at boot. 17179569.328068! Capability LSM initialized 17179569.329135! Mount-cache hash table entries: 512 17179569.336415! Initializing cgroup subsys ns 17179569.336625! Initializing cgroup subsys cpuacct 17179569.337083! Initializing cgroup subsys devices 17179569.372905! CPUs: 2 configured, 0 standby 17179569.712223! cpu 0 phys_idx=0 vers=00 ident=002623 machine=3090 unused= 17179569.720062! cpu 1 phys_idx=1 vers=00 ident=102623 machine=3090 unused= 17179569.720223! Brought up 2 CPUs 17179569.727662! net_namespace: 660 bytes 17179569.733664! NET: Registered protocol family 16 17179569.734205! debug: Initialization complete 17179569.845231! NET: Registered protocol family 2 17179569.904364! IP route cache hash table entries: 2048 (order: 1, 8192 bytes) 17179569.915461! TCP established hash table entries: 8192 (order: 4, 65536 bytes) 17179569.919237! TCP bind hash table entries: 8192 (order: 4, 65536 bytes) 17179569.923241! TCP: Hash tables configured (established 8192 bind 8192) 17179569.923520! TCP reno registered 17179569.945827! NET: Registered protocol family 1 17179569.951199! checking if image is initramfs... it is 17179595.776001! Freeing initrd memory: 4834k freed 17179595.813741! audit: initializing netlink socket (disabled) 17179595.814102! type=2000 audit(1247133977.122:1): initialized 17179595.826079! VFS: Disk quotas dquot_6.5.1 17179595.827719! Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) 17179595.828598! msgmni has been set to 498 17179595.833376! Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254) 17179595.833664! io scheduler noop registered 17179595.833861! io scheduler anticipatory registered 17179595.834079! io scheduler deadline registered 17179595.835142! io scheduler cfq registered (default) 17179595.923494! brd: module loaded 17179595.925446! cio: Channel measurement facility using basic format (autodetected) 17179595.925743! qdio: loading QDIO base support version 2 17179595.929133! qdio : Not all CHSCs supported. Continuing. 17179595.929513! sclp_config: no configuration management. 17179595.959702! TCP cubic registered 17179595.962630! NET: Registered protocol family 10 17179595.989321! lo: Disabled Privacy Extensions 17179596.003133! Mobile IPv6 17179596.003321! NET: Registered protocol family 17 17179596.009185! registered taskstats version 1 17179596.030724! Freeing unused kernel memory: 148k freed 17179596.042499! Kernel panic - not syncing: Attempted to kill init Here is what should be happening at that point: Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... 17179598.312944! dasd(eckd): 0.0.0120: PSF-SSC on storage subsystem HRC.ZZ0001.0120 returned rc=0
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
A user reported on d-s390 [1] that a Lenny installation on s390 failed with a kernel panic during boot. I could reproduce the panic on my Hercules system using the installer. Hmmm. This is fun. If I cross-compile the kernel myself it boots fine. I used my own cross-build system for this, not the Debian build system. Here's what I did: - apt-get source linux-2.6 (on lenny of course) - apply patches from all series files (1-17; except *-extra) - copy kernel config from 2.6.26-2-s390 - cross-build - install and boot the resulting .deb package Did I miss anything here? Anyway, I wonder if the problem is maybe just a weird error in the build environment used to build the current official package. If that is the case then a simple rebuild could fix that. Dann: could you maybe rebuild the kernel for s390 and send me the resulting image so I could check that? Cheers, FJP -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Thu, Jul 09, 2009 at 03:03:51PM +0200, Frans Pop wrote: A user reported on d-s390 [1] that a Lenny installation on s390 failed with a kernel panic during boot. I could reproduce the panic on my Hercules system using the installer. Hmmm. This is fun. If I cross-compile the kernel myself it boots fine. I used my own cross-build system for this, not the Debian build system. Here's what I did: - apt-get source linux-2.6 (on lenny of course) - apply patches from all series files (1-17; except *-extra) - copy kernel config from 2.6.26-2-s390 - cross-build - install and boot the resulting .deb package Did I miss anything here? Anyway, I wonder if the problem is maybe just a weird error in the build environment used to build the current official package. If that is the case then a simple rebuild could fix that. Dann: could you maybe rebuild the kernel for s390 and send me the resulting image so I could check that? I'll start a build on zelenka once my build-dep install request is fulfilled. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Thursday 09 July 2009, dann frazier wrote: The buildd log shows that 2.6.26-17 was built w/ gcc-4.1_4.1.2-25. Is there a cross-compiler available w/ that version? Unfortunately not that I know of. Packages currently available on emdebian are incomplete. And I've had very mixed results trying to build a cross toolchain myself. It costs loads of effort with a fairly big chance of failure If someone knows a source I'll be happy to try it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Thu, Jul 09, 2009 at 10:05:15AM -0600, dann frazier wrote: On Thu, Jul 09, 2009 at 03:03:51PM +0200, Frans Pop wrote: A user reported on d-s390 [1] that a Lenny installation on s390 failed with a kernel panic during boot. I could reproduce the panic on my Hercules system using the installer. Hmmm. This is fun. If I cross-compile the kernel myself it boots fine. I used my own cross-build system for this, not the Debian build system. Here's what I did: - apt-get source linux-2.6 (on lenny of course) - apply patches from all series files (1-17; except *-extra) - copy kernel config from 2.6.26-2-s390 - cross-build - install and boot the resulting .deb package Did I miss anything here? Anyway, I wonder if the problem is maybe just a weird error in the build environment used to build the current official package. If that is the case then a simple rebuild could fix that. Dann: could you maybe rebuild the kernel for s390 and send me the resulting image so I could check that? I'll start a build on zelenka once my build-dep install request is fulfilled. Here's a simple rebuild from zelenka's lenny chroot: http://people.debian.org/~dannf/bugs/536354/ (will appear once slow rsync finishes) -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Thursday 09 July 2009, dann frazier wrote: On Thu, Jul 09, 2009 at 10:05:15AM -0600, dann frazier wrote: Here's a simple rebuild from zelenka's lenny chroot: http://people.debian.org/~dannf/bugs/536354/ Thanks Dann. That paniced too. After that I've managed after all to build a 4.1 cross toolchain [1]. And the kernel I just built with that also panics. So, progress: I can now start narrowing it down. Should be easy enough as I was smart enough to commit each patch series in git after applying. Here's what I currently know for certain: * 2.6.26-13 built with gcc-4.1 (4.1.2-24) boots [2] * 2.6.26-17 built with gcc-4.1 (4.1.2-25) panics * 2.6.26-17 built with gcc-4.2 (4.2.4-6) boots So, the failure is gcc related. Now we have to find out if it is a specific kernel patch that gcc 4.1 does not like, or a regression in gcc itself. [1] I now have an s390 cross compiler, built on a Lenny i386 Toshiba laptop, installed in an i386 Sid chroot on an amd64 Lenny HP notebook :-P [2] This just happens to be the last .26 kernel I still had installed in Hercules. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Thursday 09 July 2009, Frans Pop wrote: Here's what I currently know for certain: * 2.6.26-13 built with gcc-4.1 (4.1.2-24) boots [2] * 2.6.26-17 built with gcc-4.1 (4.1.2-25) panics * 2.6.26-17 built with gcc-4.2 (4.2.4-6) boots Bisect... - the following all built with gcc-4.1 (4.1.2-25): * 2.6.26-15lenny3 panics * 2.6.26-14 panics * 2.6.26-13 boots * 2.6.26-13lenny1 boots * 2.6.26-13lenny2 boots = the problem is in 2.6.26-14 (I guess this also tells us a lot about how many users run Lenny s390 with a Debian kernel :-/ Unless maybe s390x is not affected.) /me looks at patches in -14 Hmmm, panic is about where modules first get loaded, let's try reverting bugfix/parisc/fix-loading-large-kmods.patch. Nope. Still panics. Do you have any ideas? Bastian maybe? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Thu, Jul 09, 2009 at 11:46:37PM +0200, Frans Pop wrote: On Thursday 09 July 2009, Frans Pop wrote: Here's what I currently know for certain: * 2.6.26-13 built with gcc-4.1 (4.1.2-24) boots [2] * 2.6.26-17 built with gcc-4.1 (4.1.2-25) panics * 2.6.26-17 built with gcc-4.2 (4.2.4-6) boots Bisect... - the following all built with gcc-4.1 (4.1.2-25): * 2.6.26-15lenny3 panics * 2.6.26-14 panics * 2.6.26-13 boots * 2.6.26-13lenny1 boots * 2.6.26-13lenny2 boots = the problem is in 2.6.26-14 (I guess this also tells us a lot about how many users run Lenny s390 with a Debian kernel :-/ Unless maybe s390x is not affected.) /me looks at patches in -14 Hmmm, panic is about where modules first get loaded, let's try reverting bugfix/parisc/fix-loading-large-kmods.patch. Nope. Still panics. Do you have any ideas? Bastian maybe? I'd suggest the CVE-2009-0029 fixes. Lots of arch-specific stuff in there. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Thursday 09 July 2009, dann frazier wrote: I'd suggest the CVE-2009-0029 fixes. Lots of arch-specific stuff in there. Nope. Other suggestions welcome. I'll nail it down tomorrow. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Thu, 2009-07-09 at 23:46 +0200, Frans Pop wrote: On Thursday 09 July 2009, Frans Pop wrote: Here's what I currently know for certain: * 2.6.26-13 built with gcc-4.1 (4.1.2-24) boots [2] * 2.6.26-17 built with gcc-4.1 (4.1.2-25) panics * 2.6.26-17 built with gcc-4.2 (4.2.4-6) boots Bisect... - the following all built with gcc-4.1 (4.1.2-25): * 2.6.26-15lenny3 panics * 2.6.26-14 panics * 2.6.26-13 boots * 2.6.26-13lenny1 boots * 2.6.26-13lenny2 boots = the problem is in 2.6.26-14 (I guess this also tells us a lot about how many users run Lenny s390 with a Debian kernel :-/ Unless maybe s390x is not affected.) /me looks at patches in -14 Hmmm, panic is about where modules first get loaded, let's try reverting bugfix/parisc/fix-loading-large-kmods.patch. Nope. Still panics. Do you have any ideas? Bastian maybe? If this is a compiler bug then it doesn't necessarily relate in any obvious way to any of the code changes. :-( You may have to bisect the patch series. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Bug#536354: linux-2.6: [s390,lenny] kernel panic during boot
On Fri, Jul 10, 2009 at 12:32:45AM +0200, Frans Pop wrote: On Thursday 09 July 2009, dann frazier wrote: I'd suggest the CVE-2009-0029 fixes. Lots of arch-specific stuff in there. Nope. Other suggestions welcome. I'll nail it down tomorrow. Maybe the -fwrapv change? -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
