Re: Unresolved symbol in 2.4.4p1, ia32
> From:Jonathan Hudson <[EMAIL PROTECTED]> > X-Newsreader: knews 1.0b.1 > x-no-productlinks: yes > X-Newsgroups: fa.linux.kernel > Content-Type: text/plain; charset=iso-8859-1 > Date:Sat, 07 Apr 2001 21:01:56 GMT > Bytes: 235 > Sender: [EMAIL PROTECTED] > Precedence: bulk > X-Mailing-List: [EMAIL PROTECTED] > > depmod: *** Unresolved symbols in > /lib/modules/2.4.4-pre1/kernel/drivers/ide/ide-cd.o > depmod: strstr > > depmod: *** Unresolved symbols in > /lib/modules/2.4.4-pre1/kernel/drivers/parport/parport.o > depmod: strstr > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > > I think strstr (apparently a new function) got left out of i386_ksyms.c: The following appears to have fixed it for me: --- arch/i386/kernel/i386_ksyms.c.~1~ Mon Apr 9 10:54:58 2001 +++ arch/i386/kernel/i386_ksyms.c Mon Apr 9 12:46:45 2001 @@ -97,6 +97,7 @@ EXPORT_SYMBOL_NOVERS(__put_user_2); EXPORT_SYMBOL_NOVERS(__put_user_4); +EXPORT_SYMBOL(strstr); EXPORT_SYMBOL(strtok); EXPORT_SYMBOL(strpbrk); EXPORT_SYMBOL(simple_strtol); -- todd -- ** This footnote confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
compile error with 2.4.4-pre2
I get this when I try to compile 2.4.4-pre2
(I'm assuming the list is working this morning, since I've received no
messages).
Thanks.
-- todd --
$ make bzImage
gcc -D__KERNEL__ -I/var/src/linux-2.4.3/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2
-march=i686 -c -o init/main.o init/main.c
In file included from /var/src/linux-2.4.3/include/asm/rwsem.h:20,
from /var/src/linux-2.4.3/include/asm/semaphore.h:42,
from /var/src/linux-2.4.3/include/linux/fs.h:199,
from /var/src/linux-2.4.3/include/linux/capability.h:17,
from /var/src/linux-2.4.3/include/linux/binfmts.h:5,
from /var/src/linux-2.4.3/include/linux/sched.h:9,
from /var/src/linux-2.4.3/include/linux/mm.h:4,
from /var/src/linux-2.4.3/include/linux/slab.h:14,
from /var/src/linux-2.4.3/include/linux/proc_fs.h:5,
from init/main.c:15:
/var/src/linux-2.4.3/include/asm/spinlock.h:36: warning: `SPIN_LOCK_UNLOCKED' redefined
/var/src/linux-2.4.3/include/linux/spinlock.h:55: warning: this is the location of the
previous definition
/var/src/linux-2.4.3/include/asm/spinlock.h:38: warning: `spin_lock_init' redefined
/var/src/linux-2.4.3/include/linux/spinlock.h:58: warning: this is the location of the
previous definition
/var/src/linux-2.4.3/include/asm/spinlock.h:47: warning: `spin_is_locked' redefined
/var/src/linux-2.4.3/include/linux/spinlock.h:60: warning: this is the location of the
previous definition
/var/src/linux-2.4.3/include/asm/spinlock.h:48: warning: `spin_unlock_wait' redefined
/var/src/linux-2.4.3/include/linux/spinlock.h:62: warning: this is the location of the
previous definition
/var/src/linux-2.4.3/include/asm/spinlock.h:131: warning: `RW_LOCK_UNLOCKED' redefined
/var/src/linux-2.4.3/include/linux/spinlock.h:118: warning: this is the location of
the previous definition
/var/src/linux-2.4.3/include/asm/spinlock.h:133: warning: `rwlock_init' redefined
/var/src/linux-2.4.3/include/linux/spinlock.h:121: warning: this is the location of
the previous definition
/var/src/linux-2.4.3/include/asm/spinlock.h:164: warning: `read_unlock' redefined
/var/src/linux-2.4.3/include/linux/spinlock.h:123: warning: this is the location of
the previous definition
/var/src/linux-2.4.3/include/asm/spinlock.h:165: warning: `write_unlock' redefined
/var/src/linux-2.4.3/include/linux/spinlock.h:125: warning: this is the location of
the previous definition
In file included from /var/src/linux-2.4.3/include/asm/rwsem.h:20,
from /var/src/linux-2.4.3/include/asm/semaphore.h:42,
from /var/src/linux-2.4.3/include/linux/fs.h:199,
from /var/src/linux-2.4.3/include/linux/capability.h:17,
from /var/src/linux-2.4.3/include/linux/binfmts.h:5,
from /var/src/linux-2.4.3/include/linux/sched.h:9,
from /var/src/linux-2.4.3/include/linux/mm.h:4,
from /var/src/linux-2.4.3/include/linux/slab.h:14,
from /var/src/linux-2.4.3/include/linux/proc_fs.h:5,
from init/main.c:15:
/var/src/linux-2.4.3/include/asm/spinlock.h:26: conflicting types for `spinlock_t'
/var/src/linux-2.4.3/include/linux/spinlock.h:54: previous declaration of `spinlock_t'
/var/src/linux-2.4.3/include/asm/spinlock.h:68: parse error before `{'
/var/src/linux-2.4.3/include/asm/spinlock.h:78: parse error before `void'
/var/src/linux-2.4.3/include/asm/spinlock.h:93: parse error before `do'
/var/src/linux-2.4.3/include/asm/spinlock.h:121: conflicting types for `rwlock_t'
/var/src/linux-2.4.3/include/linux/spinlock.h:117: previous declaration of `rwlock_t'
/var/src/linux-2.4.3/include/asm/spinlock.h:146: parse error before `void'
/var/src/linux-2.4.3/include/asm/spinlock.h:155: parse error before `void'
make: *** [init/main.o] Error 1
root [pcx4168] /usr/src/linux
$
**
This footnote confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
**
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: lvm 0.8 to 0.9 conversion?
I've been on vacation Nope, no snapshots. Well, I couldn't get my orginal volume group visible under both lvm 0.8 and 0.9. I don't know why. So I grabbed a big empty hard disk, created a new volume group that was visible under both, dded all the logical volumes over to it, updated fstab and removed the offending vg. I've yet to recreate the original vg, copy stuff back and remove the new drive. I should point out that the offending vg was relatively ancient, I think I created it when 0.7 was king under some something like 2.2.14. Now I'm running 2.4.0-ac4 and all works well. > Date: Wed, 27 Dec 2000 20:53:36 +0100 > From: Andrea Arcangeli <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > X-GnuPG-Key-URL: http://e-mind.com/~andrea/aa.gnupg.asc > X-PGP-Key-URL: http://e-mind.com/~andrea/aa.asc > > On Sat, Dec 23, 2000 at 04:29:19PM -0500, Todd M. Roy wrote: > > group is visible, and you just told meit should be, then I can just > > copy volumes over under test13-pre3 and destroy and recreate the > > first volume group. > > Is it possible you had a snapshot in the volume group when you started > lvm 0.9 the first time? snapshots are not persistent on pre3 so it doesn't make > sense to left them before rebooting the kernel, and maybe lvmtools 0.9 doesn't > cope correctly with non persistent snapshot created by 0.8 driver (trivial to > temporarly workaround, just delete any snapshot volume before using 0.9 lvm :). > > Andrea > > ** This footnote confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: lvm 0.8 to 0.9 conversion?
I've been on vacation Nope, no snapshots. Well, I couldn't get my orginal volume group visible under both lvm 0.8 and 0.9. I don't know why. So I grabbed a big empty hard disk, created a new volume group that was visible under both, dded all the logical volumes over to it, updated fstab and removed the offending vg. I've yet to recreate the original vg, copy stuff back and remove the new drive. I should point out that the offending vg was relatively ancient, I think I created it when 0.7 was king under some something like 2.2.14. Now I'm running 2.4.0-ac4 and all works well. > Date: Wed, 27 Dec 2000 20:53:36 +0100 > From: Andrea Arcangeli <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > X-GnuPG-Key-URL: http://e-mind.com/~andrea/aa.gnupg.asc > X-PGP-Key-URL: http://e-mind.com/~andrea/aa.asc > > On Sat, Dec 23, 2000 at 04:29:19PM -0500, Todd M. Roy wrote: > > group is visible, and you just told meit should be, then I can just > > copy volumes over under test13-pre3 and destroy and recreate the > > first volume group. > > Is it possible you had a snapshot in the volume group when you started > lvm 0.9 the first time? snapshots are not persistent on pre3 so it doesn't make > sense to left them before rebooting the kernel, and maybe lvmtools 0.9 doesn't > cope correctly with non persistent snapshot created by 0.8 driver (trivial to > temporarly workaround, just delete any snapshot volume before using 0.9 lvm :). > > Andrea > > ** This footnote confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
scsi/zip mounting problem with 2.4.0-ac4/6 (at least)
Alan and All, I've detected a bug somewhere in 2.4.0-acX, at least in ac4, the first ac kernel I built. It seems that I can't mount a scsi zip disk in, unless the following has occurred: 1. There is a disk in the zip drive when I boot. 2. I fdisk the scsi block device and re-write the partition table. (I accidently discovered this). in other words I get this: mount: /dev/sda4 is not a valid block device. If I try to insert a zipdisk and mount it after I boot up. This problem does NOT occur as late as 2.4.0-final. Specifics of my system: The SCSI board is a real cheap SYM810A based Fast SCSI-2 PCI board. I use the sym53c8xx driver built in, as is scsi disk support. The only thing I use the scsi board for is the external zip 100 drive. It still occurs in ac6. (I've only build ac4 and 6). Here is the specifics from a dmesg of 2.4.0 booting: (2.4.0-ac4 and 6) is the same. SCSI subsystem driver Revision: 1.00 sym53c8xx: at PCI bus 0, device 13, function 0 sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up) sym53c8xx: 53c810a detected sym53c810a-0: rev 0x12 on pci bus 0 device 13 function 0 irq 10 sym53c810a-0: ID 7, Fast-10, Parity Checking sym53c810a-0: restart (scsi reset). scsi0 : sym53c8xx - version 1.6b Vendor: IOMEGAModel: ZIP 100 Rev: C.22 Type: Direct-Access ANSI SCSI revision: 02 Detected scsi removable disk sda at scsi0, channel 0, id 5, lun 0 sym53c810a-0-<5,*>: target did not report SYNC. sym53c810a-0-<5,*>: target did not report SYNC. sym53c810a-0-<5,*>: target did not report SYNC. sym53c810a-0-<5,*>: target did not report SYNC. sym53c810a-0-<5,*>: target did not report SYNC. sda : READ CAPACITY failed. sda : status = 1, message = 00, host = 0, driver = 28 sda : extended sense code = 2 sda : block size assumed to be 512 bytes, disk size 1GB. sda: I/O error: dev 08:00, sector 0 unable to read partition table Thanks, Todd ** This footnote confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
lvm 0.9.1-beta1 still segfaults vgexport
Andrea,
Sorry to say but lvm 0.9.1-beta1 still segfaults
at the same place, line 140 of pv_read_all_pv_of_vg.c
pv_this is still null.
This with a straight 2.4.0 kernel with an onstream tape
patch and the generated lvm patch. Lvm is a module (on
my home machine).
-- todd --
gdb /sbin/vgexport core:
...
#0 0x400427f3 in pv_read_all_pv_of_vg (vg_name=0xb794 "vg01PV_EXP",
pv=0xb710, reread=0) at pv_read_all_pv_of_vg.c:140
140 for ( p = 0; pv_this[p] != NULL; p++) {
(gdb) print pv_this
$1 = (pv_v2_t **) 0x0
(gdb) bt
#0 0x400427f3 in pv_read_all_pv_of_vg (vg_name=0xb794 "vg01PV_EXP",
pv=0xb710, reread=0) at pv_read_all_pv_of_vg.c:140
#1 0x400487af in vg_read (vg_name=0xb794 "vg01PV_EXP",
vg=0xb750)
at vg_read.c:61
#2 0x4004733d in vg_check_exist (vg_name=0xb794 "vg01PV_EXP")
at vg_check_exist.c:54
#3 0x80491ee in main (argc=2, argv=0xb8cc) at vgexport.c:182
#4 0x4007b213 in __libc_start_main (main=0x8048d00 , argc=2,
ubp_av=0xb8cc, init=0x80489c4 <_init>, fini=0x80495b4 <_fini>,
rtld_fini=0x4000d660 <_dl_fini>, stack_end=0xb8c4)
at ../sysdeps/generic/libc-start.c:129
...
**
This footnote confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
**
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: [lvm-devel] Re: lvm 0.9.1-beta1 still segfaults vgexport
Andrea,
This worked for me on my home machine!!
Thank you!
-- todd --
Andrea Arcangeli wrote:
>
> On Sun, Jan 14, 2001 at 05:32:34PM +0100, Andrea Arcangeli wrote:
> > BTW, I can easily reproduce. I was near to go into it yesterday but got
> > interrupted by other issues (like the merging of the 0.9.1-beta1 kernel driver
> > and extraction of the strictly necessary fixes from the 0.9.1-beta1 userspace
> > against 0.9).
>
> This looks the right fix for the vgexport segfault trivially reproducible
> on 0.9 and 0.9.1_beta1 lvmtools. Now that I see the details of the bug
> it was possible to reproduce it also with `vgdisplay -D xxx' where
> xxx is just a random name of a not existent VG.
>
> --- ./tools/lib/pv_read_all_pv_of_vg.c.~1~ Mon Jan 15 03:35:51 2001
> +++ ./tools/lib/pv_read_all_pv_of_vg.c Mon Jan 15 04:57:00 2001
> @@ -137,6 +137,11 @@
> while ( pv_this[np] != NULL) np++;
>}
>
> + if ( np == 0) {
> + ret = -LVM_EPV_READ_ALL_PV_OF_VG_NP;
> + goto pv_read_all_pv_of_vg_end;
> + }
> +
>/* avoid multiple access pathes */
>for ( p = 0; pv_this[p] != NULL; p++) {
> /* avoid multiple access pathes for now (2.4.0-test8)
>
> I also got a reminder from Marco d'Itri to integrate this hack for
> some more non-x86 platform:
>
> --- ./tools/lib/pv_get_size.c.~1~ Mon Jan 15 03:35:51 2001
> +++ ./tools/lib/pv_get_size.c Mon Jan 15 04:04:03 2001
> @@ -58,7 +58,7 @@
> #define read_le(x) (x)
> #endif
>
> -#if !defined(__alpha__) && !defined(__s390__)
> +#ifdef __i386__
> int pv_get_size ( char *dev_name, struct partition *part_ptr) {
> int i = 0;
> int dir_cache_count = 0;
>
> Andrea
**
This footnote confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
**
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
oops with dd with test10-pre4
I got this oops dding partitions. test10-pre3 works fine. below is a representative sample. Thanks -- todd -- root@pcx4168:~# fdisk -l /dev/hda Disk /dev/hda: 255 heads, 63 sectors, 1216 cylinders Units = cylinders of 16065 * 512 bytes Device BootStart EndBlocks Id System /dev/hda1 164514048+ 83 Linux native /dev/hda265 121457852+ 6 FAT16 /dev/hda4 1200 1216136552+ 82 Linux swap root@pcx4168:~# fdisk -l /dev/hdc Disk /dev/hdc: 255 heads, 63 sectors, 3739 cylinders Units = cylinders of 16065 * 512 bytes Device BootStart EndBlocks Id System /dev/hdc1 1 128 1028128+ 83 Linux native /dev/hdc2 * 129 1844498206 FAT16 /dev/hdc3 185 3720 28402920 8e Linux LVM /dev/hdc4 3721 3739152617+ 83 Linux native root@pcx4168:~# dd if=/dev/hdc2 of=/dev/hda2 bs=32k invalid operand: CPU:0 EIP:0010:[] EFLAGS: 00010282 eax: 001c ebx: 0200 ecx: c12ea000 edx: esi: c11f6448 edi: 0001 ebp: 0762e045 esp: c12ebecc ds: 0018 es: 0018 ss: 0018 Process kswapd (pid: 2, stackpage=c12eb000) Stack: c020eb65 c020ed24 0066 400fa000 40102000 c75bc3e4 400f7000 c01262c3 c13e3620 c75cf4a0 400f9000 c75bc3e4 0004 400f7000 c75cf4a0 c13e3620 0004 404f7000 c75be400 40102000 40102000 c75be400 c012637d Call Trace: [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 90 f7 c5 02 00 00 00 74 18 6a 68 68 24 ed 20 kernel BUG at vmscan.c:102! invalid operand: CPU:0 EIP:0010:[] EFLAGS: 00010286 eax: 001c ebx: 0700 ecx: c025c004 edx: 0021 esi: c11f65e0 edi: 0001 ebp: 07634045 esp: c57abb4c ds: 0018 es: 0018 ss: 0018 Process dd (pid: 2372, stackpage=c57ab000) Stack: c020eb65 c020ed24 0066 b000 c000 c75bbff8 bfff9000 0401 c01262c3 c13e3620 c75cf560 bfffe000 c75bbff8 0003 bfff9000 c75cf560 c13e3620 0003 c03f9000 c75bebfc c000 c000 c75bebfc c012637d Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 90 f7 c5 02 00 00 00 74 18 6a 68 68 24 ed 20 Segmentation fault root@pcx4168:~# cpuinfo:root [pcx4168] /proc $ cat cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 5 model name : Pentium II (Deschutes) stepping: 2 cpu MHz : 448.000878 cache size : 512 KB fdiv_bug: no hlt_bug : no sep_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr bogomips: 894.57 .~. Todd Roy, Senior Database Administrator .~. /V\ Holstein Association, U.S.A. Inc. /V\ // \\ [EMAIL PROTECTED] // \\ /( )\ 1-802-254-4551x4230 /( )\ ^^-^^ ^^-^^ ** This footnote confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
lvm 0.8 to 0.9 conversion?
Now that in 2.4.0-test12-pre4, lvm 0.9 has replaced 0.8, is it possible to do a conversion of lvm created physical volumes, volume groups and logical volumes from 0.8 to 0.9? Sorry if this is already a FAQ that I just haven't found yet. -- todd -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: lvm 0.8 to 0.9 conversion?
Andre, One of my two volume groups, unfortunately the one with /usr, /var, /opt, and /home, isn't recognized by 0.9's vgscan when I reboot under 2.4.0-test13-pre4.But since the second volume group is visible, and you just told meit should be, then I can just copy volumes over under test13-pre3 and destroy and recreate the first volume group. Thanks, -- todd -- On Sat, Dec 23, 2000 at 02:24:39PM -0500, Todd M. Roy wrote: > >> Now that in 2.4.0-test12-pre4, lvm 0.9 has replaced 0.8, is it possible >> to do a conversion of lvm created physical volumes, volume groups >> and logical volumes from 0.8 to 0.9? >on-disk format isn't changed so no conversion is needed. You only >need to upgrade the lvm tools to use the new kernel driver, grab the tools from www.sistina.com. Andre - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
new aic7xxx needs berkeley db?
Hi All, I notice that the new aic7xxx driver needs some version of the berkekey db. (the make file has -ldb1 in it). It blew up on my because I apparently don't have it installed. -- .~. Todd Roy, Senior Database Administrator .~. /V\ Holstein Association, U.S.A. Inc. /V\ // \\ [EMAIL PROTECTED] // \\ /( )\ 1-802-254-4551x4230 /( )\ ^^-^^ ^^-^^ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
new aic7xxx driver needs berkeley db?
Hi All, I notice that the new aic7xxx driver in 2.4.3-pre7 needs some version of the berkeley db. (the make file has -ldb1 in it). It blew up on my because I apparently don't have it installed. .~. Todd Roy, Senior Database Administrator .~. /V\ Holstein Association, U.S.A. Inc. /V\ // \\ [EMAIL PROTECTED] // \\ /( )\ 1-802-254-4551x4230 /( )\ ^^-^^ ^^-^^ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
re: 2.4.3-p8 pci_fixup_vt8363 + ASUS A7V "Optimal" = IDE disk corruption
Wayne,
I have also been seeing disk corruption with my ASUS A7V with both
2.4.3-pre7 and pre8.
-- todd --
Hi,
I'm running kernel 2.4.3-pre8 on an ASUS A7V (BIOS 1007) motherboard and
recently noticed that it sometimes corrupts my hard disk, an IBM 75GXP
on
the onboard PDC20265 IDE controller. The corruption is detectable with
a
simple 'dd if=/dev/urandom of=test bs=16384 count=32768; cp test test2 ;
diff test test2'.
I traced the problem to a combination of choosing "Optimal" for the
System
Permorfance Setting in the BIOS and the the new pci_fixup_vt8363 added
to
arch/i386/kernel/pci-pc.c in kernel 2.4.3-pre3. So I did a bunch of
tests
using no pci_fixup function, the pci_fixup_vt8363 function, and the
following subset of pci_fixup_vt8363:
pci_read_config_byte(d, 0x54, &tmp);
if(tmp & (1<<2)) {
printk("PCI: Bus master Pipeline request disabled\n");
pci_write_config_byte(d, 0x54, tmp & ~(1<<2));
}
pci_read_config_byte(d, 0x70, &tmp);
if(tmp & (1<<2)) {
printk("PCI: Disabled Master Read Caching\n");
pci_write_config_byte(d, 0x70, tmp & ~(1<<2));
}
The results for me:
Normal Optimal
-- ---
no pci_fixupno corruption no corruption
pci_fixup_vt8363 subset corruption corruption
pci_fixup_vt8363no corruption corruption
At this point my skills and perseverance gave out, but if someone would
like me to do a few more specific tests, I could.
Below is the output of 'lspci -xxx -s 0:0' on this hardware, with no
pci_fixup, for both the Normal and Optimal BIOS settings, in the form of
a
unified diff. Hopefully this will shed some light on what the BIOS is
doing, as we don't see to have pci_fixup_vt8363 quite right yet.
Cheers,
Wayne
--
.~. Todd Roy, Senior Database Administrator .~.
/V\ Holstein Association, U.S.A. Inc. /V\
// \\ [EMAIL PROTECTED] // \\
/( )\ 1-802-254-4551x4230 /( )\
^^-^^ ^^-^^
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
patch for ide.2.4.5-ac8
Andre,
Minor typo fix:
--- ide-dma.c.~1~ Tue Jun 5 14:39:06 2001
+++ ide-dma.c Tue Jun 5 15:04:54 2001
@@ -708,15 +708,15 @@
if ((!dma_base) && (!second_chance)) {
unsigned long set_bmiba = 0;
second_chance++;
- switch(dev->vender) {
- PCI_VENDOR_ID_AL:
- set_bmiba = DEFAULT_BMALIBA; break;
- PCI_VENDOR_ID_VIA:
- set_bmiba = DEFAULT_BMCRBA; break;
- PCI_VENDOR_ID_INTEL:
- set_bmiba = DEFAULT_BMIBA; break;
- default:
- return dma_base;
+ switch (dev->vendor) {
+case PCI_VENDOR_ID_AL:
+ set_bmiba = DEFAULT_BMALIBA; break;
+case PCI_VENDOR_ID_VIA:
+ set_bmiba = DEFAULT_BMCRBA; break;
+case PCI_VENDOR_ID_INTEL:
+ set_bmiba = DEFAULT_BMIBA; break;
+default:
+ return dma_base;
}
pci_write_config_dword(dev, 0x20, set_bmiba|1);
goto second_chance_to_dma;
Cheers,
Todd
**
This footnote confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
**
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda
Matthias, I tried pretty much the same thing, and I also tried your patch. Unhappily when I access my zip drive using the aic7xxx driver my system becomes pretty much unresposive, just short of locking up completely. ie at least the emergency alt-sysrq keys still work. I guess we'll just have to wait for Justin to come out with the real patch... -- todd -- > X-Apparently-To: [EMAIL PROTECTED] via web13607.mail.yahoo.com > X-Track: 1: 40 > Date:Mon, 30 Apr 2001 01:39:56 +0200 > From:Matthias Andree <[EMAIL PROTECTED]> > Mail-Followup-To: Linux-Kernel mailing list <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > User-Agent: Mutt/1.2.5i > Sender: [EMAIL PROTECTED] > Precedence: bulk > X-Mailing-List: [EMAIL PROTECTED] > > On Sun, 29 Apr 2001, J . A . Magallon wrote: > > > > Command found on device queue > > > aic7xxx_abort returns 8194 > > > > I have seen blaming for this error to aic7xxx new driver prior to version > > 6.1.11. It was included in the 2.4.3-ac series, but its has not got into > > main 2.4.4 (there is still 6.1.5). Everything needs its time. > > Since the official aic7xxx site doesn't carry a patch against 2.4.4 yet > (just 2.4.3) which has cosmetic issues when being patched, I made a > patch against 2.4.4: I took the 2.4.3-aic7xxx-6.1.12 patch, applied to > 2.4.4, bumped the version to read -ma1 in EXTRAVERSION, and made a new > patch against vanilla 2.4.4, to be found at: > > *** WARNING BELOW *** > > http://mandree.home.pages.de/kernelpatches/v2.4/v2.4.4/ > 72k linux-2.4.4-aic7xxx-to-6.1.12.patch.gz > > Apply with patch -p1. > > NOTE: Do not expect this patch to last until after either Justin has a > patch against 2.4.4 available or 2.4.5 has been released. > > *** WARNING *** I did not yet try to boot it, that will have to wait > until later. > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > ** This footnote confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.3 2.4.4pre8: aic7xxx showstopper bug fails to detect sda
Matthias, I tried 2.4.4 with the old aic7 driver and it worked fine. I have no control over that stupid, stupid mime-sweeper message. Thats our anal-retentive network administrators work -- todd -- -- .~. Todd Roy, Senior Database Administrator .~. /V\ Holstein Association, U.S.A. Inc. /V\ // \\ [EMAIL PROTECTED] // \\ /( )\ 1-802-254-4551x4230 /( )\ ^^-^^ ^^-^^ ** This footnote confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
