Bug#463606: Test results on Geode
Graham wrote: Thanks for the report, Bill. Based on the CPUID [1] and core speed [2], I am guessing that this is a Geode LX 800; can you confirm this? Correct. The board is an Advantech PCM3353: http://www.advantech.com/applied/products/PCM-3353.pdf Have you tried running the long NOP test app, posted at bug 464962? Nope. I'll try to get to that. b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#463606: Test results on Geode
Guys: Seeing similar problems here too, with 2.6.24-686. 2.6.23-686 worked fine. My details: # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 10 model name : Geode(TM) Integrated Processor by AMD PCS stepping: 2 cpu MHz : 499.904 cache size : 128 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow up bogomips: 1001.54 clflush size: 32 (Yes, I know this machine isn't _technically_ a 686!). linux-image-2.6.24-1-486 seems to run fine. b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337974: i2o controller probe failed err -110
Sven: Sven Luther wrote: On Thu, Jan 05, 2006 at 09:37:44AM -0600, Bill Gatliff wrote: I noticed the BTS for the aforementioned ends with: tags 344739 patch tags 344767 patch Does that mean that the grub in unstable fixes the issue? No, this means someone provided a patch, which the grub maintainers could or not use to fix the problem in an upload to unstable. You could apply those patches to the grub package and rebuild it otoo. Nothing makes my palms sweat faster than tinkering with grub... :( b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337974: i2o controller probe failed err -110
Sven: Sven Luther wrote: On Wed, Jan 04, 2006 at 10:58:43PM -0600, Bill Gatliff wrote: Oh, and BTW, this is : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344767 Thanks for all the great feedback! I noticed the BTS for the aforementioned ends with: tags 344739 patch tags 344767 patch Does that mean that the grub in unstable fixes the issue? b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337974: i2o controller probe failed err -110
Max: maximilian attems wrote: use initramfs-tools this shouldn't fail: apt-get install initramfs-tools add to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd good luck ;) I patched up my /etc/lvm/lvm.config and now the kernel package installs clean. It won't successfully boot, however. It hangs with: ... Waiting for /sys/block/sdb/dev ... /sys/block/sdb/dev seems to be down ... The /dev/sdb device is where my root filesystem is at. Not quite sure why the kernel can't find it... Any ideas? b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337974: i2o controller probe failed err -110
Max: maximilian attems wrote: use initramfs-tools this shouldn't fail: apt-get install initramfs-tools add to /etc/kernel-img.conf ramdisk = /usr/sbin/mkinitramfs /usr/sbin/mkinitrd good luck ;) One other thing. When I try to --purge the package, I get this: # dpkg --purge linux-image-2.6.14-2-k7 (Reading database ... 206960 files and directories currently installed.) Removing linux-image-2.6.14-2-k7 ... Searching for GRUB installation directory ... found: /boot/grub . The link /vmlinuz is a damaged link Removing symbolic link vmlinuz Unless you used the optional flag in lilo, you may need to re-run lilo The link /initrd.img is a damaged link Removing symbolic link initrd.img Unless you used the optional flag in lilo, you may need to re-run lilo Purging configuration files for linux-image-2.6.14-2-k7 ... Searching for GRUB installation directory ... found: /boot/grub . ... and it just hangs there. b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337974: linux-image-2.6.12-1-k7: i2o controller probe failed err -110
Package: linux-image-2.6.12-1-k7 Version: 2.6.12-10 Severity: critical Justification: breaks the whole system Kernel hangs at boot after failing to init iop0: ... iop0: get status timeout iop0: reset rejected trying to clear iop0: unable to clear (status=0xbe) i2o controller probe failed err -110 [hang] The very same system boots fine under 2.6.8, where it uses dpti instead of iop. The dpti driver on 2.6.12 looks like it issues the same messages as it does under 2.6.8 (suggests that it is working properly), but apparently iop steps in shortly thereafter and tries (unsuccessfully) to take over. My dmesg from 2.6.8: ... Loading Adaptec I2O RAID: Version 2.4 Build 5go Detecting Adaptec I2O RAID controllers... ACPI: PCI interrupt :00:0b.1[A] - GSI 19 (level, low) - IRQ 185 Adaptec I2O RAID controller 0 at f887f000 size=10 irq=185 dpti: If you have a lot of devices this could take a few minutes. dpti0: Reading the hardware resource table. TID 008 Vendor: ADAPTEC Device: AIC-7899 Rev: 0001 TID 009 Vendor: ADAPTEC Device: AIC-7899 Rev: 0001 TID 010 Vendor: ADAPTEC Device: AIC-7899 Rev: 0001 TID 011 Vendor: ADAPTEC Device: AIC-7899 Rev: 0001 TID 518 Vendor: IBM Device: DDYS-T18350N Rev: SA2A TID 523 Vendor: ADAPTEC Device: RAID-5 Rev: 370F scsi2 : Vendor: Adaptec Model: 3410SFW:370F Vendor: IBM Model: DDYS-T18350N Rev: SA2A Type: Direct-Access ANSI SCSI revision: 03 Vendor: ADAPTEC Model: RAID-5Rev: 370F Type: Direct-Access ANSI SCSI revision: 02 A grep for iop0 in my 2.6.8 dmesg produces no results. I don't have a dmesg for 2.6.12, since the system won't boot. :) -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages linux-image-2.6.12-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2.1 The GNU core utilities ii initrd-tools 0.1.84 tools to create initrd image for p ii module-init-tools 3.2-pre9-2 tools for managing Linux kernel mo linux-image-2.6.12-1-k7 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338030: yaird error: Could not read output for /sbin/lvdisplay -c (fatal)
Package: yaird Version: 0.0.11-11 Severity: grave Justification: renders package unusable # apt-get install linux-image-2.6.14-1-k7 Reading package lists... Done Building dependency tree... Done linux-image-2.6.14-1-k7 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 296 not upgraded. 1 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Setting up linux-image-2.6.14-1-k7 (2.6.14-2) ... Using /usr/sbin/mkinitrd.yaird to build the ramdisk. Full list of probed ramdisk generating tools : /usr/sbin/mkinitrd /usr/sbin/mkinitrd.yaird /usr/sbin/mkinitramfs. yaird error: Could not read output for /sbin/lvdisplay -c (fatal) Failed to create initrd image. dpkg: error processing linux-image-2.6.14-1-k7 (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: linux-image-2.6.14-1-k7 E: Sub-process /usr/bin/dpkg returned an error code (1) # lvdisplay -c /dev/0/0:0:3:1:-1:1:426778624:52097:-1:0:0:254:0 /dev/sda1: Checksum error Couldn't read volume group metadata. Volume group vg0 not found # lvs /dev/sda1: Checksum error Couldn't read volume group metadata. Volume group vg0 not found LV VG Attr LSize Origin Snap% Move Copy% 00-wi-ao 203.50G # lvscan ACTIVE'/dev/0/0' [203.50 GB] inherit /dev/sda1: Checksum error Couldn't read volume group metadata. Volume group vg0 not found # mount /dev/mapper/0-0 on / type ext3 (rw,errors=remount-ro) /dev/sda1 on /boot type ext3 (rw) /dev/sda5 on /tmp type ext3 (rw) /dev/hda1 on /mnt/backup type ext3 (ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) usbfs on /proc/bus/usb type usbfs (rw) tmpfs on /dev type tmpfs (rw,size=10M,mode=0755) nfsd on /proc/fs/nfsd type nfsd (rw) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages yaird depends on: ii cpio 2.6-9 GNU cpio -- a program to manage ar ii dash 0.5.2-7 The Debian Almquist Shell ii libc62.3.5-6 GNU C Library: Shared libraries an ii libhtml-template-perl2.6-2 HTML::Template : A module for usin ii libparse-recdescent-perl 1.94.free-1 Generates recursive-descent parser ii perl 5.8.7-7 Larry Wall's Practical Extraction yaird recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338030: yaird error: Could not read output for /sbin/lvdisplay -c (fatal)
Jonas Smedegaard wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 07 Nov 2005 15:45:14 -0600 Bill Gatliff [EMAIL PROTECTED] wrote: yaird error: Could not read output for /sbin/lvdisplay -c (fatal) Failed to create initrd image. # lvdisplay -c /dev/0/0:0:3:1:-1:1:426778624:52097:-1:0:0:254:0 /dev/sda1: Checksum error Couldn't read volume group metadata. Volume group vg0 not found lvdisplay belongs to lvm2 I believe. Why do you file this bugreport against yaird? It seems to me that you have problems with your LVM headers or something. Alright. I'll send a report to lvm2. b.g. -- Bill Gatliff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
