Don't know about ac11 but I tried the proposed-2.2.11pre4 with the
2.2.10 patches. It had a bunch of failures that I checked manually.
Basically, it looks like some of the chunks in the patches are
integrated into pre4. I didn't find anything except these cases.
Kernel compiled O.K. (gcc 2.7.2.3) and rebooted fine. Then I started
compiling XFree86 3.3.4 with gcc 2.95 and started getting a lot of
Oops. I think it was like:
Aug 6 12:27:01 mammoth kernel: Unable to handle kernel paging request at virtual
address 3a6f2e72
Aug 6 12:27:01 mammoth kernel: current->tss.cr3 = 06f44000, %cr3 = 06f44000
Aug 6 12:27:01 mammoth kernel: *pde = 00000000
Aug 6 12:27:01 mammoth kernel: Oops: 0000
Aug 6 12:27:01 mammoth kernel: CPU: 0
Aug 6 12:27:01 mammoth kernel: EIP: 0010:[d_lookup+101/220]
Aug 6 12:27:01 mammoth kernel: EFLAGS: 00010282
Aug 6 12:27:01 mammoth kernel: eax: 000004f0 ebx: 3a6f2e5a ecx: 4e08309e edx:
4e08347f
Aug 6 12:27:01 mammoth kernel: esi: 8751c7b3 edi: 00000001 ebp: 3a6f2e72 esp:
c68b5f30
Aug 6 12:27:01 mammoth kernel: ds: 0018 es: 0018 ss: 0018
Aug 6 12:27:01 mammoth kernel: Process make (pid: 4147, process nr: 88,
stackpage=c68b5000)
Aug 6 12:27:01 mammoth kernel: Stack: 00000001 c6c9eae0 c0246d8c c6a69035 8751c7b3
0000000d c012f6a1 c6c9eae0
Aug 6 12:27:01 mammoth kernel: c68b5f80 c68b5f80 c6a69042 c012f8e9 c6c9eae0
c68b5f80 00000001 c6a69000
Aug 6 12:27:01 mammoth kernel: c6a69000 00000001 bfffdc78 c6a69000 c6a69035
0000000d 8751c7b3 c012f9c1
Aug 6 12:27:01 mammoth kernel: Call Trace: [cached_lookup+21/84]
[lookup_dentry+253/428] [__namei+41/92] [sys_newstat+46/148] [system_call+52/56]
Aug 6 12:27:01 mammoth kernel: Code: 8b 6d 00 8b 74 24 18 39 73 48 75 eb 8b 74 24 24
39 73 0c 75
Aug 6 12:27:02 mammoth kernel: Unable to handle kernel paging request at virtual
address 3a6f2e72
So it looks like there is either a problem with pre4 or with the RAID
patches on top of that. I didn't have time to mess with it so I
rebooted into 2.2.10 /w RAID patches and everything has been "fine"
(except for a problem with xfs in 3.3.4 that caused me to looks my X
server for a while...).
For reference:
Personalities : [raid0]
read_ahead 1024 sectors
md3 : active raid0 sdb6[1] sda6[0] 755456 blocks 16k chunks
md2 : active raid0 sdb5[1] sda5[0] 2098944 blocks 16k chunks
md1 : active raid0 sdb3[1] sda3[0] 4196224 blocks 16k chunks
md0 : active raid0 sdb1[1] sda1[0] 1574656 blocks 16k chunks
unused devices: <none>
For reference:
Aug 6 08:02:52 mammoth kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
Aug 6 08:02:52 mammoth kernel: translucent personality registered
Aug 6 08:02:52 mammoth kernel: linear personality registered
Aug 6 08:02:52 mammoth kernel: raid0 personality registered
Aug 6 08:02:52 mammoth kernel: raid1 personality registered
Aug 6 08:02:52 mammoth kernel: raid5 personality registered
Aug 6 08:02:52 mammoth kernel: raid5: measuring checksumming speed
Aug 6 08:02:52 mammoth kernel: raid5: MMX detected, trying high-speed MMX checksum
routines
Aug 6 08:02:52 mammoth kernel: pII_mmx : 784.860 MB/sec
Aug 6 08:02:52 mammoth kernel: p5_mmx : 829.056 MB/sec
Aug 6 08:02:52 mammoth kernel: 8regs : 602.742 MB/sec
Aug 6 08:02:52 mammoth kernel: 32regs : 368.808 MB/sec
Aug 6 08:02:52 mammoth kernel: using fastest function: p5_mmx (829.056 MB/sec)
Aug 6 08:02:52 mammoth kernel: (scsi0) <Adaptec AIC-7895 Ultra SCSI host adapter>
found at PCI 14/0
Aug 6 08:02:52 mammoth kernel: (scsi0) Wide Channel A, SCSI ID=7, 32/255 SCBs
Aug 6 08:02:52 mammoth kernel: (scsi0) Warning - detected auto-termination
Aug 6 08:02:52 mammoth kernel: (scsi0) Please verify driver detected settings are
correct.
Aug 6 08:02:52 mammoth kernel: (scsi0) If not, then please properly set the device
termination
Aug 6 08:02:52 mammoth kernel: (scsi0) in the Adaptec SCSI BIOS by hitting CTRL-A
when prompted
Aug 6 08:02:52 mammoth kernel: (scsi0) during machine bootup.
Aug 6 08:02:52 mammoth kernel: (scsi0) Cables present (Int-50 NO, Int-68 NO, Ext-68
NO)
Aug 6 08:02:52 mammoth kernel: (scsi0) Downloading sequencer code... 374 instructions
downloaded
Aug 6 08:02:52 mammoth kernel: (scsi1) <Adaptec AIC-7895 Ultra SCSI host adapter>
found at PCI 14/1
Aug 6 08:02:52 mammoth kernel: (scsi1) Wide Channel B, SCSI ID=7, 32/255 SCBs
Aug 6 08:02:52 mammoth kernel: (scsi1) Warning - detected auto-termination
Aug 6 08:02:52 mammoth kernel: (scsi1) Please verify driver detected settings are
correct.
Aug 6 08:02:52 mammoth kernel: (scsi1) If not, then please properly set the device
termination
Aug 6 08:02:52 mammoth kernel: (scsi1) in the Adaptec SCSI BIOS by hitting CTRL-A
when prompted
Aug 6 08:02:52 mammoth kernel: (scsi1) during machine bootup.
Aug 6 08:02:52 mammoth kernel: (scsi1) Cables present (Int-50 NO, Int-68 NO, Ext-68
NO)
Aug 6 08:02:52 mammoth kernel: (scsi1) Downloading sequencer code... 374 instructions
downloaded
Aug 6 08:02:52 mammoth kernel: scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast
SCSI) 5.1.19/3.2.4
Aug 6 08:02:52 mammoth kernel: <Adaptec AIC-7895 Ultra SCSI host adapter>
Aug 6 08:02:52 mammoth kernel: scsi1 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast
SCSI) 5.1.19/3.2.4
Aug 6 08:02:52 mammoth kernel: <Adaptec AIC-7895 Ultra SCSI host adapter>
Aug 6 08:02:52 mammoth kernel: scsi : 2 hosts.
Aug 6 08:02:52 mammoth kernel: (scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8.
Aug 6 08:02:52 mammoth kernel: Vendor: SEAGATE Model: ST34520W Rev: 1487
Aug 6 08:02:52 mammoth kernel: Type: Direct-Access ANSI SCSI
revision: 02
Aug 6 08:02:52 mammoth kernel: Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Aug 6 08:02:52 mammoth kernel: (scsi0:0:3:0) Synchronous at 10.0 Mbyte/sec, offset 15.
Aug 6 08:02:52 mammoth kernel: Vendor: HP Model: C1533A Rev: A708
Aug 6 08:02:52 mammoth kernel: Type: Sequential-Access ANSI SCSI
revision: 02
Aug 6 08:02:52 mammoth kernel: (scsi0:0:6:0) Synchronous at 10.0 Mbyte/sec, offset 15.
Aug 6 08:02:52 mammoth kernel: Vendor: SONY Model: CD-R CDU948S Rev: 1.0j
Aug 6 08:02:52 mammoth kernel: Type: CD-ROM ANSI SCSI
revision: 02
Aug 6 08:02:52 mammoth kernel: (scsi1:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8.
Aug 6 08:02:52 mammoth kernel: Vendor: SEAGATE Model: ST34520W Rev: 1487
Aug 6 08:02:52 mammoth kernel: Type: Direct-Access ANSI SCSI
revision: 02
Aug 6 08:02:52 mammoth kernel: Detected scsi disk sdb at scsi1, channel 0, id 0, lun 0
Aug 6 08:02:52 mammoth kernel: scsi : detected 2 SCSI disks total.
Aug 6 08:02:52 mammoth kernel: SCSI device sda: hdwr sector= 512 bytes. Sectors=
8888924 [4340 MB] [4.3 GB]
Aug 6 08:02:52 mammoth kernel: SCSI device sdb: hdwr sector= 512 bytes. Sectors=
8888924 [4340 MB] [4.3 GB]
Aug 6 08:02:52 mammoth kernel: Partition check:
Aug 6 08:02:52 mammoth kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
Aug 6 08:02:52 mammoth kernel: sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 >
Aug 6 08:02:52 mammoth kernel: md.c: sizeof(mdp_super_t) = 4096
Aug 6 08:02:52 mammoth kernel: hda: hda1 hda2 hda3
Aug 6 08:02:52 mammoth kernel: autodetecting RAID arrays
Aug 6 08:02:52 mammoth kernel: autorun ...
Aug 6 08:02:52 mammoth kernel: ... autorun DONE.
..
..
..
It goes on an on, I can send the latest if anyone is interested -- I
don't know if this is from the boot that crashed or not.
QUESTION: Why is p5_mmx faster than pII_mmx when I have dual PII-350
CPU's?
For Reference:
raiddev /dev/md0
raid-level 0
nr-raid-disks 2
persistent-superblock 1
nr-spare-disks 0
chunk-size 16
device /dev/sda1
raid-disk 0
device /dev/sdb1
raid-disk 1
raiddev /dev/md1
raid-level 0
nr-raid-disks 2
persistent-superblock 1
nr-spare-disks 0
chunk-size 16
device /dev/sda3
raid-disk 0
device /dev/sdb3
raid-disk 1
raiddev /dev/md2
raid-level 0
nr-raid-disks 2
persistent-superblock 1
nr-spare-disks 0
chunk-size 16
device /dev/sda5
raid-disk 0
device /dev/sdb5
raid-disk 1
raiddev /dev/md3
raid-level 0
nr-raid-disks 2
persistent-superblock 1
nr-spare-disks 0
chunk-size 16
device /dev/sda6
raid-disk 0
device /dev/sdb6
raid-disk 1
On Fri, 06 Aug 1999, Aaron D. Turner wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>
>
> I've got a VA Research PII 450 server (for running MySQL) running a 2.0.36
> kernel with the raid0145-19990108-2.0.36 patch (RAID1) which so far has
> seemed stable.
>
> For peformance reasons, we're looking to upgrade to the 2.2.x series
> kernel. VA is telling me in no uncertain terms that I should stay the
> hell away from 2.2.10, but alas the latest RAID patch is for 2.2.10.
>
> Can anyone provide some solid advice about what kernel/patch to run for a
> production server? Does the 2.2.10-ac11 work with the latest RAID
> patch/solve the corruption issues I've seen reported with eariler 2.2.10
> kernels?
>
> Thanks.
>
> - --
> Aaron Turner | Either which way, one half dozen or another.
> [EMAIL PROTECTED] | http://www.pobox.com/~aturner/
>
> "There is no worse tyranny than to make a man pay for something he does
> not want merely because you think it would be good for him."
> - -Benjamin Franklin
>
> All emails from this account are PGP signed. Lack of a signature is "bad".
> PGP Key fingerprint = FB E1 CE ED 57 E4 AB 80 59 6E 60 BF 45 1B 20 E8
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6.2
>
> iQCVAwUBN6sc4DM3jpXy1kJtAQGz+QP+PZz52f9Btxxu2QysdQk1eMwr7qg8TV5t
> 40ExgM+fY7MgCpd0bmi6BRA3nznYOAUROryJ5ksZrklveWgkrN4uuZsdbusmyyjW
> ps4gjvw+RTcIODZOd4hOOpwvJAbB9WIGwsqSwzqfjn0MiD9RfNW2mCp7ZyZ4Nx+p
> 581Rd5dfM70=
> =ajuU
> -----END PGP SIGNATURE-----
