[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: [parisc-linux] Call for Testing



Hello Kyle,

>
> Hi,
>
> I've backported some more patches to 2.6.8 for possible[1] inclusion in
> sarge (they fix some possibly important bits).
>
> You can find kernels here:
> 	http://www.parisc-linux.org/~kyle/debian-kernel/2005-03-27/
>
Hope you will be also interested by those additional test:
  a. a b180 booting fine its initrd.img :-) (from your pkg kernel-image-2.6.8-2-32_2.6.8-7_hppa.deb)

  b. a b2k trying first the same pkg all seems to works fine until 'cechecking
all fs :-( (here is the full boot log:)
Current command line:
2/vmlinux initrd=2/initrd.img root=/dev/md2 HOME=/ panic=120 profile=2 console=ttyS0
TERM=vt102
 0: 2/vmlinux
 1: initrd=2/initrd.img
 2: root=/dev/md2
 3: HOME=/
 4: panic=120
 5: profile=2
 6: console=ttyS0
 7: TERM=vt102

<#>    edit the numbered field
'b'    boot with this command line
'r'    restore command line
'l'    list dir
? b

Command line for kernel: ' root=/dev/md2 HOME=/ panic=120 profile=2 console=ttyS0
TERM=vt102 palo_kernel=2/vmlinux'
Selected kernel: /vmlinux from partition 2
Selected ramdisk: /initrd.img from partition 2
ELF32 executable
Entry 00100000 first 00100000 n 2
Segment 0 load 00100000 size 2242736 mediaptr 0x1000
Segment 1 load 00324000 size 1056902 mediaptr 0x225000
Loading ramdisk 4714496 bytes @ 0fb6f000...
Branching to kernel entry point 0x00100000.  If this is the last
message you see, you may need to switch your console.  This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org

Linux version 2.6.8-2-32 (kyle@caradhras) (gcc version 3.3.5 (Debian 1:3.3.5-12))
#1 Sun Mar 27 06:04:08 EST 2005
FP[0] enabled: Rev 1 Model 16
The 32-bit Kernel has started...
Determining PDC firmware type: System Map.
model 00005d00 00000481 00000000 00000002 77e93910 100000f0 00000008 000000b2
000000b2
vers  00000301
CPUID vers 17 rev 11 (0x0000022b)
capabilities 0x3
model 9000/785/B2000
Total Memory: 256 Mb
initrd: 1fb6f000-1ffee000
initrd: reserving 0fb6f000-0ffee000 (mem_max 10000000)
LCD display at f05d0008,f05d0000 registered
Built 1 zonelists
Kernel command line:  root=/dev/md2 HOME=/ panic=120 profile=2 console=ttyS0
TERM=vt102 palo_kernel=2/vmlinux
kernel profiling enabled
PID hash table entries: 16 (order 4: 128 bytes)
Console: colour dummy device 160x64
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 262144k available
Calibrating delay loop... 799.53 BogoMIPS
Security Scaffold v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
checking if image is initramfs...it isn't (ungzip failed); looks like an
initrd
NET: Registered protocol family 16
EISA bus registered
Searching for devices...
Found devices:
1. Astro BC Runway Port at 0xfed00000 [10] { 12, 0x0, 0x582, 0x0000b }
2. Elroy PCI Bridge at 0xfed30000 [10/0] { 13, 0x0, 0x782, 0x0000a }
3. Elroy PCI Bridge at 0xfed32000 [10/1] { 13, 0x0, 0x782, 0x0000a }
4. Kazoo W+ at 0xfffa0000 [32] { 0, 0x0, 0x5d0, 0x00004 }
5. Memory at 0xfed10200 [49] { 1, 0x0, 0x09d, 0x00009 }
CPU(s): 1 x PA8600 (PCX-W+) at 400.000000 MHz
SBA found Astro 2.1 at 0xfed00000
lba version TR4.0 (0x5) found at 0xfed30000
PCI: Enabled native mode for NS87415 (pif=0x8f)
lba version TR4.0 (0x5) found at 0xfed32000
SCSI subsystem initialized
TC classifier action (bugs to netdev@oss.sgi.com cc hadi@cyberus.ca)
STI GSC/PCI core graphics driver Version 0.9a
STI PCI graphic ROM found at f4940000 (128 kB), fb at fb000000 (16 MB)
    id 35acda16-9a02587, conforms to spec rev. 8.0c
    graphics card name: HPA4982A
stifb: 'HPA4982A' (id: 0x35acda16) not supported.
unwind_init: start = 0x10325720, end = 0x103468b0, entries = 8473
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
Initializing Cryptographic API
SuperIO: Found NS87560 Legacy I/O device at 0000:00:0e.1 (IRQ 64)
SuperIO: Serial port 1 at 0x3f8
SuperIO: Serial port 2 at 0x2f8
SuperIO: Parallel port at 0x378
SuperIO: Floppy controller at 0x3f0
SuperIO: ACPI at 0x7e0
SuperIO: USB regulator enabled
Soft power switch enabled, polling @ 0xf0400804.
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 25 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 99) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 100) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
sticon: Initializing STI text console.
Console: switching to colour STI console 160x64
mice: PS/2 mouse device common for all mice
HP SDC: No SDC found.
HP SDC MLC: Registering the System Domain Controller's HIL MLC.
HP SDC MLC: Request for raw HIL ISR hook denied
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 4604 blocks [1 disk] into ram disk... done.
VFS: Mounted root (cramfs filesystem) readonly.
Freeing unused kernel memory: 316k freed
initrd-tools: 0.1.77
NET: Registered protocol family 1
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: raid1 personality registered as nr 3
sym0: <895a> rev 0x1 at pci 0000:00:0f.0 irq 65
sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.18k
Using anticipatory io scheduler
  Vendor: QUANTUM   Model: ATLAS5-9LVD       Rev: HP04
  Type:   Direct-Access                      ANSI SCSI revision: 03
sym0:5:0: tagged command queuing enabled, command queue depth 16.
scsi(0:0:5:0): Beginning Domain Validation
sym0:5: wide asynchronous.
sym0:5: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
scsi(0:0:5:0): Ending Domain Validation
  Vendor: SEAGATE   Model: ST336704LC        Rev: HP03
  Type:   Direct-Access                      ANSI SCSI revision: 03
sym0:6:0: tagged command queuing enabled, command queue depth 16.
scsi(0:0:6:0): Beginning Domain Validation
sym0:6: wide asynchronous.
sym0:6: FAST-40 WIDE SCSI 80.0 MB/s ST (25.0 ns, offset 31)
scsi(0:0:6:0): Ending Domain Validation
sym1: <875> rev 0x26 at pci 0000:01:03.0 irq 131
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: SCSI BUS has been reset.
scsi1 : sym-2.1.18k
Attached scsi generic sg0 at scsi0, channel 0, id 5, lun 0,  type 0
Attached scsi generic sg1 at scsi0, channel 0, id 6, lun 0,  type 0
SCSI device sda: 17773524 512-byte hdwr sectors (9100 MB)
SCSI device sda: drive cache: write back
 /dev/scsi/host0/bus0/target5/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11
>
Attached scsi disk sda at scsi0, channel 0, id 5, lun 0
SCSI device sdb: 71132960 512-byte hdwr sectors (36420 MB)
SCSI device sdb: drive cache: write through
 /dev/scsi/host0/bus0/target6/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11
p12 p13 >
Attached scsi disk sdb at scsi0, channel 0, id 6, lun 0
md: md1 stopped.
md: bind<sdb3>
md: bind<sda3>
raid1: raid set md1 active with 2 out of 2 mirrors
mdadm: /devfs/mdmd: md2 stopped.
/1 has been started with 2 drivemd: bind<sdb5>
s.
md: bind<sda5>
raid1: raid set md2 active with 2 out of 2 mirrors
mdadm: /devfs/md/2 has been started with 2 drives.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
INIT: version 2.86 booting
Usage: vt-is-UTF8 [option]
valid options are:
        -q  --quiet    don't print result
        -h --help      display this help text and exit
        -V --version   display version information and exit
Activating swap.
Adding 255928k swap on /dev/md1.  Priority:-1 extents:1
Checking root file system...
fsck 1.37 (21-Mar-2005)
/dev/md2: clean, 75757/200096 files, 344879/3998EXT3 FS on md2, 40 blocks
internal journal
System time was Tue Mar 29 10:09:33 UTC 2005.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Tue Mar 29 10:09:35 UTC 2005.
Cleaning up ifupdown...done.
Calculating module dependencies... done.
Loading modules...
All modules loaded.
Checking all file systems...
fsck 1.37 (21-Mar-2005)
fsck.ext3: Invalid argument while trying to open /dev/md0
/dev/md0:
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.ext3: Invalid argument while trying to open /dev/md3
/dev/md3:
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.ext3: Invalid argument while trying to open /dev/md4
/dev/md4:
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.ext3: Invalid argument while trying to open /dev/md5
/dev/md5:
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.ext3: Invalid argument while trying to open /dev/md6
/dev/md6:
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.ext3: Invalid argument while trying to open /dev/md7
/dev/md7:
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.ext3: Invalid argument while trying to open /dev/md8
/dev/md8:
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.

CONTROL-D will exit from this shell and continue system startup.

Give root password for maintenance
(or type Control-D to continue):

(just reboot with my custom kernel no pb)
My /etc/fstab being:
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>                       <dump>
 <pass>
/dev/md1        none            swap    sw                              0
      0
/dev/md2        /               ext3    defaults,errors=remount-ro      0
      1
/dev/md0        /boot           ext3    defaults                        0
      1
proc            /proc           proc    defaults                        0
      0
/dev/md3        /var            ext3    defaults                        0
      1
/dev/md4        /tmp            ext3    defaults                        0
      1

#tmpfs          /var/tmp        tmpfs   defaults                        0
      0
/dev/md5        /home           ext3    defaults                        0
      1

/dev/fd0        /floppy         auto    defaults,user,noauto            0
      0
/dev/cdrom      /cdrom          iso9660 defaults,ro,user,noauto         0
      0

# My fs
/dev/md6        /usr/src        ext3    defaults                        0
      1
/dev/md7        /Sources        ext3    defaults                        0
      1
/dev/md8        /Develop        ext3    defaults                        0
      1
# old test
#/dev/sda9      /usr/src        ext2    defaults,errors=continue        0
      0
#/dev/sda10     /Sources        ext2    defaults,errors=continue        0
      0
#/dev/sda11     /Develop        ext2    defaults,errors=continue        0
      0

# OpenCascade
#/dev/sdb1      /CAD            ext3    defaults,noauto                 0
      0
/dev/sdb12      /CAD            ext3    defaults,errors=continue        0
      0

Do you see something wrong?

my md config being:
# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [multipath]
md1 : active raid1 sdb3[1] sda3[0]
      255936 blocks [2/2] [UU]

md2 : active raid1 sdb5[1] sda5[0]
      1599360 blocks [2/2] [UU]

md3 : active raid1 sdb6[1] sda6[0]
      255872 blocks [2/2] [UU]

md4 : active raid1 sdb7[1] sda7[0]
      127872 blocks [2/2] [UU]

md5 : active raid1 sdb8[1] sda8[0]
      127872 blocks [2/2] [UU]

md6 : active raid1 sdb9[1] sda9[0]
      2047872 blocks [2/2] [UU]

md7 : active raid1 sdb10[1] sda10[0]
      2047872 blocks [2/2] [UU]

md8 : active raid1 sdb11[1] sda11[0]
      2047872 blocks [2/2] [UU]

md0 : active raid1 sdb2[1] sda2[0]
      127936 blocks [2/2] [UU]

unused devices: <none>

Strange thing: kernel just seems to bind well md1 and md2 but nor more?

Any idae?

Cheers,
    Joel




Reply to: