| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AC311A8E81420D4EBC1F26E6479848FE065B7D5B@SDCEXCHANGE01.ad.amcc.com> Date: Tue, 16 Mar 2010 09:19:21 -0700 From: "Rupjyoti Sarmah" <rsarmah@...c.com> To: "Jiri Kosina" <jkosina@...e.cz> Cc: <linux-kernel@...r.kernel.org> Subject: RE: Failure with the 2.6.34-rc1 kernel It has been failing from this commit. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commi t;h=ef1a8de8ea004a689b2aa9f5cefcba2b1a0262f2 . Also, the u-boot restarts the board very quickly. It does not go to the kernel prompt at all. Regards, Rup -----Original Message----- From: Jiri Kosina [mailto:jkosina@...e.cz] Sent: Tuesday, March 16, 2010 9:18 PM To: Rupjyoti Sarmah Cc: linux-kernel@...r.kernel.org Subject: Re: Failure with the 2.6.34-rc1 kernel On Tue, 16 Mar 2010, Rupjyoti Sarmah wrote: > We are seeing issues in booting some of our boards with this new kernel. > Kernel version upto 2.6.33 works fine on the boards like Canyonlands, > Katmai, Glacier etc. > These boards are not booting with kernel later than 2.6.33. Please let > me know how about fixing these issues ? You'd need to provide at least dmesg from the working and non-working cases. Also git-bisect between 2.6.33 and 2.6.34-rc1 might help you identify the commit that broke your hardware. -- Jiri Kosina SUSE Labs, Novell Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists