Bug#349857: linux-image-2.6-sparc64-2.6.15-1-sparc64: panics on boot on v210
maximilian attems [EMAIL PROTECTED] writes: That gets it further, but then it fails as follows (where sda1 is /boot). If I then get in single-user, I see /dev/sda1 mounted on /, but there is no /dev/sd*, i.e. no sd devices, which looks odd. please try latest klibc-utils and libklibc from incoming.debian.org or later this evening in unstable, calling update-initramfs -u will get those on your initramfs. Does that mean I should file a bug against yaird, which was what failed as above? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349857: linux-image-2.6-sparc64-2.6.15-1-sparc64: panics on boot on v210
Frans Pop [EMAIL PROTECTED] writes: I've seen the same error on my Sparc Ultra 10. The problem is in klibc which is used by initramfs-tools; merging the bug reports. Try installing yaird and using that to generate your initrd. That gets it further, but then it fails as follows (where sda1 is /boot). If I then get in single-user, I see /dev/sda1 mounted on /, but there is no /dev/sd*, i.e. no sd devices, which looks odd. ... Waiting for /dev to be fully populated...done. Activating swap. Checking root file system... fsck 1.37 (21-Mar-2005) /: clean,EXT3 FS on sda2, 55400/641280 fiinternal journal les, 485138/1280188 blocks System time was Thu Jan 26 10:08:17 UTC 2006. Setting the System Clock using the Hardware Clock as reference... System Clock set. System local time is now Thu Jan 26 10:08:19 UTC 2006. Cleaning up ifupdown...done. Calculating module dependencies...done. Loading modules... sd_mod All modules loaded. Checking all file systems... fsck 1.37 (21-Mar-2005) fsck.ext3: No such file or directory while trying to open /dev/sda1 /dev/sda1: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device fsck failed. Please repair manually. By the way, the trouble with reassigning bugs like this is that anyone who checks for existing reports against the kernel (like I did) doesn't see them. It guess it would be helpful if there was some way to leave a pointer in the original place (assuming it's a likely package against which to report the bug). Is it possible to operate the tracker so that it does that? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349857: linux-image-2.6-sparc64-2.6.15-1-sparc64: panics on boot on v210
On Tue, Jan 31, 2006 at 04:54:19PM +, Dave Love wrote: Frans Pop [EMAIL PROTECTED] writes: Try installing yaird and using that to generate your initrd. That gets it further, but then it fails as follows (where sda1 is /boot). If I then get in single-user, I see /dev/sda1 mounted on /, but there is no /dev/sd*, i.e. no sd devices, which looks odd. please try latest klibc-utils and libklibc from incoming.debian.org or later this evening in unstable, calling update-initramfs -u will get those on your initramfs. By the way, the trouble with reassigning bugs like this is that anyone who checks for existing reports against the kernel (like I did) doesn't see them. It guess it would be helpful if there was some way to leave a pointer in the original place (assuming it's a likely package against which to report the bug). Is it possible to operate the tracker so that it does that? nice thought, but the kernel has so many bug reports, we are happy when they are so nicely isolated and easy to fix like that one. early boot troubles are most probably not kernel bugs. regards + good luck -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349857: linux-image-2.6-sparc64-2.6.15-1-sparc64: panics on boot on v210
Package: linux-image-2.6-sparc64-2.6.15-1-sparc64 Severity: important I get the following trying to boot on a v210: ... scsi1 : sym-2.2.1 SCSI device sda: 71132959 512-byte hdwr sectors (36420 MB) SCSI device sda: drive cache: write through SCSI device sda: 71132959 512-byte hdwr sectors (36420 MB) SCSI device sda: drive cache: write through sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sd 0:0:0:0: Attached scsi disk sda hda: ATAPI 24X DVD-ROM drive, 256kB Cache Uniform CD-ROM driver Revision: 3.20 Done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Done. Begin: Running /scripts/local-premount ... Done. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Begin: Running /scripts/log-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... Done. run-init: statfsKernel panic - not syncing: Attempted to kill init! /: error 22 0Press Stop-A (L1-A) to return to the boot prom -- System Information: Debian Release: 3.1 APT prefers stable APT policy: (900, 'stable') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-2-sparc64 Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349857: linux-image-2.6-sparc64-2.6.15-1-sparc64: panics on boot on v210
reassign 349857 klibc merge 349857 347902 thanks On Wednesday 25 January 2006 18:51, Dave Love wrote: I get the following trying to boot on a v210: run-init: statfsKernel panic - not syncing: Attempted to kill init! /: error 22 I've seen the same error on my Sparc Ultra 10. The problem is in klibc which is used by initramfs-tools; merging the bug reports. Try installing yaird and using that to generate your initrd. pgp3CFklOKLkT.pgp Description: PGP signature
