Re: 2.2.20pre1: Problems with SMP
On Wed, May 16, 2001 at 12:56:55PM -0700, Johannes Erdfelt wrote: > > Could you try this patch? It applies on top of 2.2.20pre1 > > It also cleans up a couple of comments That fixes it alright. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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.2.20pre1: Problems with SMP
On Wed, May 16, 2001 at 12:56:55PM -0700, Johannes Erdfelt wrote: Could you try this patch? It applies on top of 2.2.20pre1 It also cleans up a couple of comments That fixes it alright. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: ENOIOCTLCMD?
n -ENOIOCTLCMD;
+ return -ENOTTY;
case WDIOC_GETSUPPORT:
return copy_to_user((struct watchdog_info *)arg, ,
sizeof(ident))?-EFAULT:0;
case WDIOC_KEEPALIVE:
diff -ur linux-2.4.4-ac8/drivers/char/softdog.c linux/drivers/char/softdog.c
--- linux-2.4.4-ac8/drivers/char/softdog.c Tue Feb 13 14:13:43 2001
+++ linux/drivers/char/softdog.cSat May 12 15:00:53 2001
@@ -132,7 +132,7 @@
};
switch (cmd) {
default:
- return -ENOIOCTLCMD;
+ return -ENOTTY;
case WDIOC_GETSUPPORT:
if(copy_to_user((struct watchdog_info *)arg, ,
sizeof(ident)))
return -EFAULT;
diff -ur linux-2.4.4-ac8/drivers/char/wdt.c linux/drivers/char/wdt.c
--- linux-2.4.4-ac8/drivers/char/wdt.c Fri Feb 9 11:30:22 2001
+++ linux/drivers/char/wdt.cSat May 12 15:06:40 2001
@@ -311,7 +311,7 @@
switch(cmd)
{
default:
- return -ENOIOCTLCMD;
+ return -ENOTTY;
case WDIOC_GETSUPPORT:
return copy_to_user((struct watchdog_info *)arg, ,
sizeof(ident))?-EFAULT:0;
diff -ur linux-2.4.4-ac8/drivers/char/wdt285.c linux/drivers/char/wdt285.c
--- linux-2.4.4-ac8/drivers/char/wdt285.c Mon Oct 16 12:58:51 2000
+++ linux/drivers/char/wdt285.c Sat May 12 15:00:53 2001
@@ -136,7 +136,7 @@
switch(cmd)
{
default:
- return -ENOIOCTLCMD;
+ return -ENOTTY;
case WDIOC_GETSUPPORT:
i = verify_area(VERIFY_WRITE, (void*) arg, sizeof(struct
watchdog_info));
if (i)
diff -ur linux-2.4.4-ac8/drivers/char/wdt_pci.c linux/drivers/char/wdt_pci.c
--- linux-2.4.4-ac8/drivers/char/wdt_pci.c Fri Feb 9 11:30:22 2001
+++ linux/drivers/char/wdt_pci.cSat May 12 15:00:53 2001
@@ -327,7 +327,7 @@
switch(cmd)
{
default:
- return -ENOIOCTLCMD;
+ return -ENOTTY;
case WDIOC_GETSUPPORT:
return copy_to_user((struct watchdog_info *)arg, ,
sizeof(ident))?-EFAULT:0;
--
Shane Wegner: [EMAIL PROTECTED]
http://www.cm.nu/~shane/
PGP: 1024D/FFE3035D
A0ED DAC4 77EC D674 5487
5B5C 4F89 9A4E FFE3 035D
-
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: ENOIOCTLCMD?
;
case WDIOC_GETSUPPORT:
return copy_to_user((struct watchdog_info *)arg, ident,
sizeof(ident))?-EFAULT:0;
case WDIOC_KEEPALIVE:
diff -ur linux-2.4.4-ac8/drivers/char/softdog.c linux/drivers/char/softdog.c
--- linux-2.4.4-ac8/drivers/char/softdog.c Tue Feb 13 14:13:43 2001
+++ linux/drivers/char/softdog.cSat May 12 15:00:53 2001
@@ -132,7 +132,7 @@
};
switch (cmd) {
default:
- return -ENOIOCTLCMD;
+ return -ENOTTY;
case WDIOC_GETSUPPORT:
if(copy_to_user((struct watchdog_info *)arg, ident,
sizeof(ident)))
return -EFAULT;
diff -ur linux-2.4.4-ac8/drivers/char/wdt.c linux/drivers/char/wdt.c
--- linux-2.4.4-ac8/drivers/char/wdt.c Fri Feb 9 11:30:22 2001
+++ linux/drivers/char/wdt.cSat May 12 15:06:40 2001
@@ -311,7 +311,7 @@
switch(cmd)
{
default:
- return -ENOIOCTLCMD;
+ return -ENOTTY;
case WDIOC_GETSUPPORT:
return copy_to_user((struct watchdog_info *)arg, ident,
sizeof(ident))?-EFAULT:0;
diff -ur linux-2.4.4-ac8/drivers/char/wdt285.c linux/drivers/char/wdt285.c
--- linux-2.4.4-ac8/drivers/char/wdt285.c Mon Oct 16 12:58:51 2000
+++ linux/drivers/char/wdt285.c Sat May 12 15:00:53 2001
@@ -136,7 +136,7 @@
switch(cmd)
{
default:
- return -ENOIOCTLCMD;
+ return -ENOTTY;
case WDIOC_GETSUPPORT:
i = verify_area(VERIFY_WRITE, (void*) arg, sizeof(struct
watchdog_info));
if (i)
diff -ur linux-2.4.4-ac8/drivers/char/wdt_pci.c linux/drivers/char/wdt_pci.c
--- linux-2.4.4-ac8/drivers/char/wdt_pci.c Fri Feb 9 11:30:22 2001
+++ linux/drivers/char/wdt_pci.cSat May 12 15:00:53 2001
@@ -327,7 +327,7 @@
switch(cmd)
{
default:
- return -ENOIOCTLCMD;
+ return -ENOTTY;
case WDIOC_GETSUPPORT:
return copy_to_user((struct watchdog_info *)arg, ident,
sizeof(ident))?-EFAULT:0;
--
Shane Wegner: [EMAIL PROTECTED]
http://www.cm.nu/~shane/
PGP: 1024D/FFE3035D
A0ED DAC4 77EC D674 5487
5B5C 4F89 9A4E FFE3 035D
-
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.2.20pre1: Problems with SMP
On Mon, May 07, 2001 at 11:02:50AM -0700, Johannes Erdfelt wrote: > On Mon, May 07, 2001, Shane Wegner <[EMAIL PROTECTED]> wrote: > > > > That does indeed correct the problem. 2.2.20pre1 now works > > as expected. > > Hmm, that uses a VIA based chipset. I didn't know they did SMP yet. Does > 2.4 work on this system? The last 2.4 kernel I tried was 2.4.3 I believe and it worked fine more or less. I haven't tried any later 2.4 kernels yet. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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.2.20pre1: Problems with SMP
On Mon, May 07, 2001 at 11:36:49AM +0100, Alan Cox wrote: > > Just booted up 2.2.20pre1 and am getting some funny > > results. The system boots but is very slow. Every few > > seconds I get: > > Stuck on TLB IPI wait (CPU#0) > > > > Booting vanilla 2.2.19 works fine. The machine is an > > Intel Pentium III 850MHZ on an Abit VP6 board. If any > > further information is needed, let me know. > > Can you back out the change to io_apic.c and tell me if that fixes it. If so > let Johannes Erdfelt and I know. That does indeed correct the problem. 2.2.20pre1 now works as expected. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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.2.20pre1: Problems with SMP
On Mon, May 07, 2001 at 11:36:49AM +0100, Alan Cox wrote: Just booted up 2.2.20pre1 and am getting some funny results. The system boots but is very slow. Every few seconds I get: Stuck on TLB IPI wait (CPU#0) Booting vanilla 2.2.19 works fine. The machine is an Intel Pentium III 850MHZ on an Abit VP6 board. If any further information is needed, let me know. Can you back out the change to io_apic.c and tell me if that fixes it. If so let Johannes Erdfelt and I know. That does indeed correct the problem. 2.2.20pre1 now works as expected. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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.2.20pre1: Problems with SMP
On Mon, May 07, 2001 at 11:02:50AM -0700, Johannes Erdfelt wrote: On Mon, May 07, 2001, Shane Wegner [EMAIL PROTECTED] wrote: That does indeed correct the problem. 2.2.20pre1 now works as expected. Hmm, that uses a VIA based chipset. I didn't know they did SMP yet. Does 2.4 work on this system? The last 2.4 kernel I tried was 2.4.3 I believe and it worked fine more or less. I haven't tried any later 2.4 kernels yet. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
2.2.20pre1: Problems with SMP
Hi, Just booted up 2.2.20pre1 and am getting some funny results. The system boots but is very slow. Every few seconds I get: Stuck on TLB IPI wait (CPU#0) Booting vanilla 2.2.19 works fine. The machine is an Intel Pentium III 850MHZ on an Abit VP6 board. If any further information is needed, let me know. Regards, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
2.2.20pre1: Problems with SMP
Hi, Just booted up 2.2.20pre1 and am getting some funny results. The system boots but is very slow. Every few seconds I get: Stuck on TLB IPI wait (CPU#0) Booting vanilla 2.2.19 works fine. The machine is an Intel Pentium III 850MHZ on an Abit VP6 board. If any further information is needed, let me know. Regards, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: softdog and WDIOS_DISABLECARD
Hi,
I have found a potential problem with the current
implementation of the software watchdog. I have
CONFIG_WATCHDOG_NOWAYOUT set for a reliable watchdog.
However, there are instances where I want to explicitly
shut it down. The problem with disabling
CONFIG_WATCHDOG_NOWAYOUT is that events other than an
explicit shutdown can disable the timer. A SIGSEGV
perhaps or the daemon being killed by the OOM handler. In
cases like this, the system should reboot IMO.
This small patch adds the appropriate options to enable and
disable the timer explicitly.
--- softdog.c.orig Wed May 2 00:15:56 2001
+++ softdog.c Wed May 2 00:15:19 2001
@@ -130,6 +130,7 @@
static struct watchdog_info ident = {
identity: "Software Watchdog",
};
+ int rv;
switch (cmd) {
default:
return -ENOIOCTLCMD;
@@ -140,6 +141,25 @@
case WDIOC_GETSTATUS:
case WDIOC_GETBOOTSTATUS:
return put_user(0,(int *)arg);
+ case WDIOC_SETOPTIONS:
+ if(copy_from_user(, (int*) arg, sizeof(int)))
+ return -EFAULT;
+
+ if (rv & WDIOS_DISABLECARD) {
+ lock_kernel();
+ del_timer(_ticktock);
+ unlock_kernel();
+ return 0;
+ }
+
+ if (rv & WDIOS_ENABLECARD) {
+ lock_kernel();
+ mod_timer(_ticktock, jiffies +
+ (soft_margin * HZ));
+ unlock_kernel();
+ return 0;
+ }
+
case WDIOC_KEEPALIVE:
mod_timer(_ticktock, jiffies+(soft_margin*HZ));
return 0;
--
Shane Wegner: [EMAIL PROTECTED]
http://www.cm.nu/~shane/
PGP: 1024D/FFE3035D
A0ED DAC4 77EC D674 5487
5B5C 4F89 9A4E FFE3 035D
-
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: softdog and WDIOS_DISABLECARD
Hi,
I have found a potential problem with the current
implementation of the software watchdog. I have
CONFIG_WATCHDOG_NOWAYOUT set for a reliable watchdog.
However, there are instances where I want to explicitly
shut it down. The problem with disabling
CONFIG_WATCHDOG_NOWAYOUT is that events other than an
explicit shutdown can disable the timer. A SIGSEGV
perhaps or the daemon being killed by the OOM handler. In
cases like this, the system should reboot IMO.
This small patch adds the appropriate options to enable and
disable the timer explicitly.
--- softdog.c.orig Wed May 2 00:15:56 2001
+++ softdog.c Wed May 2 00:15:19 2001
@@ -130,6 +130,7 @@
static struct watchdog_info ident = {
identity: Software Watchdog,
};
+ int rv;
switch (cmd) {
default:
return -ENOIOCTLCMD;
@@ -140,6 +141,25 @@
case WDIOC_GETSTATUS:
case WDIOC_GETBOOTSTATUS:
return put_user(0,(int *)arg);
+ case WDIOC_SETOPTIONS:
+ if(copy_from_user(rv, (int*) arg, sizeof(int)))
+ return -EFAULT;
+
+ if (rv WDIOS_DISABLECARD) {
+ lock_kernel();
+ del_timer(watchdog_ticktock);
+ unlock_kernel();
+ return 0;
+ }
+
+ if (rv WDIOS_ENABLECARD) {
+ lock_kernel();
+ mod_timer(watchdog_ticktock, jiffies +
+ (soft_margin * HZ));
+ unlock_kernel();
+ return 0;
+ }
+
case WDIOC_KEEPALIVE:
mod_timer(watchdog_ticktock, jiffies+(soft_margin*HZ));
return 0;
--
Shane Wegner: [EMAIL PROTECTED]
http://www.cm.nu/~shane/
PGP: 1024D/FFE3035D
A0ED DAC4 77EC D674 5487
5B5C 4F89 9A4E FFE3 035D
-
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: [PATCH] SMP race in ext2 - metadata corruption.
On Fri, Apr 27, 2001 at 09:52:19AM -0700, Linus Torvalds wrote: > > On Fri, 27 Apr 2001, Vojtech Pavlik wrote: > > > > Actually this is done quite often, even on mounted fs's: > > > > hdparm -t /dev/hda > > Note that this one happens to be ok. > > The buffer cache is "virtual" in the sense that /dev/hda is a completely > separate name-space from /dev/hda1, even if there is some physical > overlap. Wouldn't something like "hdparm -t /dev/md0" trigger it though. It is the same device as gets mounted as md devices aren't partitioned. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: [PATCH] SMP race in ext2 - metadata corruption.
On Fri, Apr 27, 2001 at 09:52:19AM -0700, Linus Torvalds wrote: On Fri, 27 Apr 2001, Vojtech Pavlik wrote: Actually this is done quite often, even on mounted fs's: hdparm -t /dev/hda Note that this one happens to be ok. The buffer cache is virtual in the sense that /dev/hda is a completely separate name-space from /dev/hda1, even if there is some physical overlap. Wouldn't something like hdparm -t /dev/md0 trigger it though. It is the same device as gets mounted as md devices aren't partitioned. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: ide.2.2.19.04092001.patch
On Thu, Apr 12, 2001 at 03:05:53PM -0700, Andre Hedrick wrote: > > So you want a VIA-old and VIA-new ?? Hi, Is the version of the driver in the latest IDE patch v4.x? That's odd as that driver does work fine on Linux 2.4.3. It's just the one in 2.2.19+ide.2.2.19.0405 which seems to be locking up. Best regards, Shane > > On Tue, 10 Apr 2001, Shane Wegner wrote: > > > On Mon, Apr 09, 2001 at 05:33:13PM -0700, Andre Hedrick wrote: > > > > > > This is up with some updates > > Hi, > > > > This isn't working here on my Abit VP6 board. The > > ide.2.2.18.1221 works fine but this latest patch as well as > > ide.2.2.19.0325 fails. > > > > Uniform Multi-Platform E-IDE driver Revision: 6.30 > > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > > VP_IDE: IDE controller on PCI bus 00 dev 39 > > VP_IDE: chipset revision 6 > > VP_IDE: not 100% native mode: will probe irqs later > > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > > VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 > > ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio > > ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio > > HPT370: IDE controller on PCI bus 00 dev 70 > > HPT370: chipset revision 3 > > HPT370: not 100% native mode: will probe irqs later > > ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio > > ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio > > hda: Maxtor 92720U8, ATA DISK drive > > hdg: Maxtor 96147U8, ATA DISK drive > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > > ide3 at 0xe400-0xe407,0xe802 on irq 10 > > > > That's where it stops. Locks solid, not even sysrq-b > > works. > > > > Shane > > > > -- > > Shane Wegner: [EMAIL PROTECTED] > > http://www.cm.nu/~shane/ > > PGP: 1024D/FFE3035D > > A0ED DAC4 77EC D674 5487 > > 5B5C 4F89 9A4E FFE3 035D > > > > Andre Hedrick > Linux ATA Development > ASL Kernel Development > ----- > ASL, Inc. Toll free: 1-877-ASL-3535 > 1757 Houret Court Fax: 1-408-941-2071 > Milpitas, CA 95035Web: www.aslab.com -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: ide.2.2.19.04092001.patch
On Thu, Apr 12, 2001 at 03:05:53PM -0700, Andre Hedrick wrote: So you want a VIA-old and VIA-new ?? Hi, Is the version of the driver in the latest IDE patch v4.x? That's odd as that driver does work fine on Linux 2.4.3. It's just the one in 2.2.19+ide.2.2.19.0405 which seems to be locking up. Best regards, Shane On Tue, 10 Apr 2001, Shane Wegner wrote: On Mon, Apr 09, 2001 at 05:33:13PM -0700, Andre Hedrick wrote: This is up with some updates Hi, This isn't working here on my Abit VP6 board. The ide.2.2.18.1221 works fine but this latest patch as well as ide.2.2.19.0325 fails. Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio HPT370: IDE controller on PCI bus 00 dev 70 HPT370: chipset revision 3 HPT370: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio hda: Maxtor 92720U8, ATA DISK drive hdg: Maxtor 96147U8, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide3 at 0xe400-0xe407,0xe802 on irq 10 That's where it stops. Locks solid, not even sysrq-b works. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: ide.2.2.19.04092001.patch
On Mon, Apr 09, 2001 at 05:33:13PM -0700, Andre Hedrick wrote: > > This is up with some updates Hi, This isn't working here on my Abit VP6 board. The ide.2.2.18.1221 works fine but this latest patch as well as ide.2.2.19.0325 fails. Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio HPT370: IDE controller on PCI bus 00 dev 70 HPT370: chipset revision 3 HPT370: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio hda: Maxtor 92720U8, ATA DISK drive hdg: Maxtor 96147U8, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide3 at 0xe400-0xe407,0xe802 on irq 10 That's where it stops. Locks solid, not even sysrq-b works. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: ide.2.2.19.04092001.patch
On Mon, Apr 09, 2001 at 05:33:13PM -0700, Andre Hedrick wrote: This is up with some updates Hi, This isn't working here on my Abit VP6 board. The ide.2.2.18.1221 works fine but this latest patch as well as ide.2.2.19.0325 fails. Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio HPT370: IDE controller on PCI bus 00 dev 70 HPT370: chipset revision 3 HPT370: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio hda: Maxtor 92720U8, ATA DISK drive hdg: Maxtor 96147U8, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide3 at 0xe400-0xe407,0xe802 on irq 10 That's where it stops. Locks solid, not even sysrq-b works. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
Lost timer configuration
Hi, As this doesn't seem to do anything, I'm not too concerned. However, I'm getting messages like these in my kernlog quite regularly. Apr 7 15:20:31 continuum kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a. Apr 7 15:20:31 continuum kernel: probable hardware bug: restoring chip configuration. Apr 7 15:24:20 continuum kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a. Apr 7 15:24:20 continuum kernel: probable hardware bug: restoring chip configuration. Apr 7 15:31:18 continuum kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a. Apr 7 15:31:18 continuum kernel: probable hardware bug: restoring chip configuration. Apr 7 15:40:15 continuum kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a. Apr 7 15:40:15 continuum kernel: probable hardware bug: restoring chip configuration. Actually it's a via 686B I believe. It's an Abit vp6 dual PIII board flashed to the latest bios revision from Abit. The odd thing is that it only occurs when copying files from my cd-rom drive to harddisk. The destination harddisk is SCSI and the cd-rom is on its own IDE channel. It does not occur otherwise. Just out of curiosity, if this was a hardware bug, wouldn't they have fixed it with the 686B chipset? Regards, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
Lost timer configuration
Hi, As this doesn't seem to do anything, I'm not too concerned. However, I'm getting messages like these in my kernlog quite regularly. Apr 7 15:20:31 continuum kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a. Apr 7 15:20:31 continuum kernel: probable hardware bug: restoring chip configuration. Apr 7 15:24:20 continuum kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a. Apr 7 15:24:20 continuum kernel: probable hardware bug: restoring chip configuration. Apr 7 15:31:18 continuum kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a. Apr 7 15:31:18 continuum kernel: probable hardware bug: restoring chip configuration. Apr 7 15:40:15 continuum kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a. Apr 7 15:40:15 continuum kernel: probable hardware bug: restoring chip configuration. Actually it's a via 686B I believe. It's an Abit vp6 dual PIII board flashed to the latest bios revision from Abit. The odd thing is that it only occurs when copying files from my cd-rom drive to harddisk. The destination harddisk is SCSI and the cd-rom is on its own IDE channel. It does not occur otherwise. Just out of curiosity, if this was a hardware bug, wouldn't they have fixed it with the 686B chipset? Regards, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
IDE trouble under 2.2.19pre16 with Hedrick's IDE patch
Hi,
Whenever I write a substantial amount of data (200mb) to
disk, I get these messages. The disks lock for about 10
seconds and then come back for about 10 seconds again.
This continues until the data is successfully written.
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hde: DMA disabled
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
Does anyone happen to know what I can do to fix this? It
happens on Linux 2.4.2 as well. It's an HPT370 controler
on-board. Here is the relevant information.
HPT370: IDE controller on PCI bus 00 dev 70
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:DMA,
hdf:pio
ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA,
hdh:pio
hde: Maxtor 92720U8, ATA DISK drive
hdg: Maxtor 96147U8, ATA DISK drive
ide2 at 0xdc00-0xdc07,0xe002 on irq 10
ide3 at 0xe400-0xe407,0xe802 on irq 10
hde: Maxtor 92720U8, 25965MB w/2048kB Cache,
CHS=52755/16/63, UDMA(66)
hdg: Maxtor 96147U8, 58623MB w/2048kB Cache,
CHS=119108/16/63, UDMA(66)
continuum:~# cat /proc/ide/hpt366
HPT370 Chipset.
--- Primary Channel Secondary
Channel -
enabled enabled
--- drive0 - drive1 drive0
-- drive1 --
DMA enabled:yes no yes
no
UDMA
DMA
PIO
continuum:~# cat /proc/ide/hde/settings
namevalue min max
mode
- --- ---
bios_cyl52755 0
65535 rw
bios_head 16 0 255
rw
bios_sect 63 0 63
rw
breada_readahead4 0 127
rw
bswap 0 0 1
r
current_speed 68 0 69
rw
file_readahead 124 0
2097151 rw
ide_scsi0 0 1
rw
init_speed 68 0 69
rw
io_32bit1 0 3
rw
keepsettings1 0 1
rw
lun 0 0 7
rw
max_kb_per_request 64 1 127
rw
multcount 8 0 8
rw
nice1 1 0 1
rw
nowerr 0 0 1
rw
number 0 0 3
rw
pio_modewrite-only 0 255
w
slow0 0 1
rw
unmaskirq 1 0 1
rw
using_dma 1 0 1
rw
--
Shane Wegner: [EMAIL PROTECTED]
http://www.cm.nu/~shane/
PGP: 1024D/FFE3035D
A0ED DAC4 77EC D674 5487
5B5C 4F89 9A4E FFE3 035D
-
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/
IDE trouble under 2.2.19pre16 with Hedrick's IDE patch
Hi,
Whenever I write a substantial amount of data (200mb) to
disk, I get these messages. The disks lock for about 10
seconds and then come back for about 10 seconds again.
This continues until the data is successfully written.
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hde: DMA disabled
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hde: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
Does anyone happen to know what I can do to fix this? It
happens on Linux 2.4.2 as well. It's an HPT370 controler
on-board. Here is the relevant information.
HPT370: IDE controller on PCI bus 00 dev 70
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:DMA,
hdf:pio
ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA,
hdh:pio
hde: Maxtor 92720U8, ATA DISK drive
hdg: Maxtor 96147U8, ATA DISK drive
ide2 at 0xdc00-0xdc07,0xe002 on irq 10
ide3 at 0xe400-0xe407,0xe802 on irq 10
hde: Maxtor 92720U8, 25965MB w/2048kB Cache,
CHS=52755/16/63, UDMA(66)
hdg: Maxtor 96147U8, 58623MB w/2048kB Cache,
CHS=119108/16/63, UDMA(66)
continuum:~# cat /proc/ide/hpt366
HPT370 Chipset.
--- Primary Channel Secondary
Channel -
enabled enabled
--- drive0 - drive1 drive0
-- drive1 --
DMA enabled:yes no yes
no
UDMA
DMA
PIO
continuum:~# cat /proc/ide/hde/settings
namevalue min max
mode
- --- ---
bios_cyl52755 0
65535 rw
bios_head 16 0 255
rw
bios_sect 63 0 63
rw
breada_readahead4 0 127
rw
bswap 0 0 1
r
current_speed 68 0 69
rw
file_readahead 124 0
2097151 rw
ide_scsi0 0 1
rw
init_speed 68 0 69
rw
io_32bit1 0 3
rw
keepsettings1 0 1
rw
lun 0 0 7
rw
max_kb_per_request 64 1 127
rw
multcount 8 0 8
rw
nice1 1 0 1
rw
nowerr 0 0 1
rw
number 0 0 3
rw
pio_modewrite-only 0 255
w
slow0 0 1
rw
unmaskirq 1 0 1
rw
using_dma 1 0 1
rw
--
Shane Wegner: [EMAIL PROTECTED]
http://www.cm.nu/~shane/
PGP: 1024D/FFE3035D
A0ED DAC4 77EC D674 5487
5B5C 4F89 9A4E FFE3 035D
-
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/
ext2 errors under 2.4.2
Hi, I received the following errors while trying out 2.4.2. After going back to 2.2.19prexx and doing an fsck, it works fine. They came up after about six hours or so of running time. EXT2-fs warning (device md(9,5)): ext2_unlink: Deleting nonexistent file (7635227), 0 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks not in datazone - block = 982921785, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks not in datazone - block = 982921785, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks in system zones - Block = 65536, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks in system zones - Block = 8, count = 1 EXT2-fs warning (device md(9,5)): ext2_unlink: Deleting nonexistent file (7635226), 0 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks not in datazone - block = 982921785, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks not in datazone - block = 982921785, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks in system zones - Block = 65536, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: bit already cleared for block 65536 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks in system zones - Block = 8, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: bit already cleared for block 8 init_special_inode: bogus imode (1011) init_special_inode: bogus imode (1012) init_special_inode: bogus imode (1013) init_special_inode: bogus imode (1026) I'm not sure if those init_special_inode errors are related. /dev/md5 is an md linear array composed of two IDE hard disks on an HPT370 IDE controler. Both Maxtor disks. DMA was enabled on both disks when the errors occurred. Regards, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
ext2 errors under 2.4.2
Hi, I received the following errors while trying out 2.4.2. After going back to 2.2.19prexx and doing an fsck, it works fine. They came up after about six hours or so of running time. EXT2-fs warning (device md(9,5)): ext2_unlink: Deleting nonexistent file (7635227), 0 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks not in datazone - block = 982921785, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks not in datazone - block = 982921785, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks in system zones - Block = 65536, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks in system zones - Block = 8, count = 1 EXT2-fs warning (device md(9,5)): ext2_unlink: Deleting nonexistent file (7635226), 0 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks not in datazone - block = 982921785, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks not in datazone - block = 982921785, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks in system zones - Block = 65536, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: bit already cleared for block 65536 EXT2-fs error (device md(9,5)): ext2_free_blocks: Freeing blocks in system zones - Block = 8, count = 1 EXT2-fs error (device md(9,5)): ext2_free_blocks: bit already cleared for block 8 init_special_inode: bogus imode (1011) init_special_inode: bogus imode (1012) init_special_inode: bogus imode (1013) init_special_inode: bogus imode (1026) I'm not sure if those init_special_inode errors are related. /dev/md5 is an md linear array composed of two IDE hard disks on an HPT370 IDE controler. Both Maxtor disks. DMA was enabled on both disks when the errors occurred. Regards, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: [patch] VIA 4.2x driver for 2.2 kernels
On Wed, Feb 21, 2001 at 08:23:48AM +0100, Vojtech Pavlik wrote: > On Tue, Feb 20, 2001 at 11:15:02PM -0800, Shane Wegner wrote: > > On Wed, Feb 21, 2001 at 08:09:19AM +0100, Vojtech Pavlik wrote: > > > > > > > > You wanted my VIA driver for 2.2. Here is a patch that brings the very > > > > > latest 4.2 driver to the 2.2 kernel. The patch is against the > > > > > 2.2.19-pre13 kernel plus yours 1221 ide patch. > > > > > > > > This drivers breaks with my HP 8110 CD-R drive. It's > > > > sitting on primary slave of a Via 686B controler. When I > > > > try to do a hdparm -d1 -u1 -k1 /dev/hdb, the kernel locks > > > > up hard. Not even an oops. Reverting to the old driver > > > > works fine. > > > > > > Don't do that. Use the kernel option to enable DMA instead. Hi, I have investigated this problem further. The hdparm triggers the error but is not the cause. hdparm accesses /dev/hdb which is my cd-r drive. This triggers the loading of the cdrom and ide-cd modules. Manually loading cdrom succeeds, after which, manually loading ide-cd crashes the system. No need to even open() the device. This works fine with the VIA driver from 2.2.19pre14+ide-2.2.18-1221. Regards, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: [patch] VIA 4.2x driver for 2.2 kernels
On Wed, Feb 21, 2001 at 08:23:48AM +0100, Vojtech Pavlik wrote: On Tue, Feb 20, 2001 at 11:15:02PM -0800, Shane Wegner wrote: On Wed, Feb 21, 2001 at 08:09:19AM +0100, Vojtech Pavlik wrote: You wanted my VIA driver for 2.2. Here is a patch that brings the very latest 4.2 driver to the 2.2 kernel. The patch is against the 2.2.19-pre13 kernel plus yours 1221 ide patch. This drivers breaks with my HP 8110 CD-R drive. It's sitting on primary slave of a Via 686B controler. When I try to do a hdparm -d1 -u1 -k1 /dev/hdb, the kernel locks up hard. Not even an oops. Reverting to the old driver works fine. Don't do that. Use the kernel option to enable DMA instead. Hi, I have investigated this problem further. The hdparm triggers the error but is not the cause. hdparm accesses /dev/hdb which is my cd-r drive. This triggers the loading of the cdrom and ide-cd modules. Manually loading cdrom succeeds, after which, manually loading ide-cd crashes the system. No need to even open() the device. This works fine with the VIA driver from 2.2.19pre14+ide-2.2.18-1221. Regards, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: [patch] VIA 4.2x driver for 2.2 kernels
On Wed, Feb 21, 2001 at 08:09:19AM +0100, Vojtech Pavlik wrote: > On Tue, Feb 20, 2001 at 03:59:27PM -0800, Shane Wegner wrote: > > > > You wanted my VIA driver for 2.2. Here is a patch that brings the very > > > latest 4.2 driver to the 2.2 kernel. The patch is against the > > > 2.2.19-pre13 kernel plus yours 1221 ide patch. > > > > This drivers breaks with my HP 8110 CD-R drive. It's > > sitting on primary slave of a Via 686B controler. When I > > try to do a hdparm -d1 -u1 -k1 /dev/hdb, the kernel locks > > up hard. Not even an oops. Reverting to the old driver > > works fine. > > Don't do that. Use the kernel option to enable DMA instead. > > Hmm, I'll have to look into this anyway - many users seem to do that and > it isn't as harmless as it looks (it worked by pure luck with the > previous version). Ok, can I still use -u1 -k1 -c1 on the drives or is it even necessary anymore. Is the deprecation of -d1 VIA IDE specific or does it apply to the entire subsystem. -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: [patch] VIA 4.2x driver for 2.2 kernels
On Tue, Feb 20, 2001 at 01:40:28PM +0100, Vojtech Pavlik wrote: > Hi Andre! > > You wanted my VIA driver for 2.2. Here is a patch that brings the very > latest 4.2 driver to the 2.2 kernel. The patch is against the > 2.2.19-pre13 kernel plus yours 1221 ide patch. Hi, This drivers breaks with my HP 8110 CD-R drive. It's sitting on primary slave of a Via 686B controler. When I try to do a hdparm -d1 -u1 -k1 /dev/hdb, the kernel locks up hard. Not even an oops. Reverting to the old driver works fine. Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 6 VP_IDE: not 100%% native mode: will probe irqs later VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio HPT370: IDE controller on PCI bus 00 dev 70 HPT370: chipset revision 3 HPT370: not 100%% native mode: will probe irqs later ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:DMA, hdf:pio ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio hdb: Hewlett-Packard CD-Writer Plus 8100, ATAPI CDROM drive VP_IDE: Calibrating PCI clock ... 34.91 MHz hde: Maxtor 92720U8, ATA DISK drive hdg: Maxtor 96147U8, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide2 at 0xdc00-0xdc07,0xe002 on irq 10 ide3 at 0xe400-0xe407,0xe802 on irq 10 hde: Maxtor 92720U8, 25965MB w/2048kB Cache, CHS=52755/16/63, UDMA(66) hdg: Maxtor 96147U8, 58623MB w/2048kB Cache, CHS=119108/16/63, UDMA(66) The one thing I see here which looks odd is the PCI clock timing at 34.91 MHZ. The CPU is not overclocked so the PCI clock should be 33MHZ but that's probably not related. Regards, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: [patch] VIA 4.2x driver for 2.2 kernels
On Tue, Feb 20, 2001 at 01:40:28PM +0100, Vojtech Pavlik wrote: Hi Andre! You wanted my VIA driver for 2.2. Here is a patch that brings the very latest 4.2 driver to the 2.2 kernel. The patch is against the 2.2.19-pre13 kernel plus yours 1221 ide patch. Hi, This drivers breaks with my HP 8110 CD-R drive. It's sitting on primary slave of a Via 686B controler. When I try to do a hdparm -d1 -u1 -k1 /dev/hdb, the kernel locks up hard. Not even an oops. Reverting to the old driver works fine. Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 6 VP_IDE: not 100%% native mode: will probe irqs later VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio HPT370: IDE controller on PCI bus 00 dev 70 HPT370: chipset revision 3 HPT370: not 100%% native mode: will probe irqs later ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:DMA, hdf:pio ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio hdb: Hewlett-Packard CD-Writer Plus 8100, ATAPI CDROM drive VP_IDE: Calibrating PCI clock ... 34.91 MHz hde: Maxtor 92720U8, ATA DISK drive hdg: Maxtor 96147U8, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide2 at 0xdc00-0xdc07,0xe002 on irq 10 ide3 at 0xe400-0xe407,0xe802 on irq 10 hde: Maxtor 92720U8, 25965MB w/2048kB Cache, CHS=52755/16/63, UDMA(66) hdg: Maxtor 96147U8, 58623MB w/2048kB Cache, CHS=119108/16/63, UDMA(66) The one thing I see here which looks odd is the PCI clock timing at 34.91 MHZ. The CPU is not overclocked so the PCI clock should be 33MHZ but that's probably not related. Regards, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: [patch] VIA 4.2x driver for 2.2 kernels
On Wed, Feb 21, 2001 at 08:09:19AM +0100, Vojtech Pavlik wrote: On Tue, Feb 20, 2001 at 03:59:27PM -0800, Shane Wegner wrote: You wanted my VIA driver for 2.2. Here is a patch that brings the very latest 4.2 driver to the 2.2 kernel. The patch is against the 2.2.19-pre13 kernel plus yours 1221 ide patch. This drivers breaks with my HP 8110 CD-R drive. It's sitting on primary slave of a Via 686B controler. When I try to do a hdparm -d1 -u1 -k1 /dev/hdb, the kernel locks up hard. Not even an oops. Reverting to the old driver works fine. Don't do that. Use the kernel option to enable DMA instead. Hmm, I'll have to look into this anyway - many users seem to do that and it isn't as harmless as it looks (it worked by pure luck with the previous version). Ok, can I still use -u1 -k1 -c1 on the drives or is it even necessary anymore. Is the deprecation of -d1 VIA IDE specific or does it apply to the entire subsystem. -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
One liner: compile failure with 2.2.19pre9 aic7xxx
Hi, Seems aic7xxx.h got lost. --- drivers/scsi/hosts.c.orig Thu Feb 8 16:32:00 2001 +++ drivers/scsi/hosts.cThu Feb 8 16:29:48 2001 @@ -136,7 +136,7 @@ #endif #ifdef CONFIG_SCSI_AIC7XXX -#include "aic7xxx.h" +#include "aic7xxx/aic7xxx.h" #endif #ifdef CONFIG_SCSI_IPS -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
One liner: compile failure with 2.2.19pre9 aic7xxx
Hi, Seems aic7xxx.h got lost. --- drivers/scsi/hosts.c.orig Thu Feb 8 16:32:00 2001 +++ drivers/scsi/hosts.cThu Feb 8 16:29:48 2001 @@ -136,7 +136,7 @@ #endif #ifdef CONFIG_SCSI_AIC7XXX -#include "aic7xxx.h" +#include "aic7xxx/aic7xxx.h" #endif #ifdef CONFIG_SCSI_IPS -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: SMP problem with 2.2.19pre8
On Sat, Feb 03, 2001 at 02:07:27PM -0800, Shane Wegner wrote: > Hi, > > I just built this SMP system and am getting some weird > errors from kern.log. The system will run smoothly but > after about a half hour running the distributed.net RC5 > client, the following errors show up. > > Feb 3 04:40:18 continuum kernel: stuck on TLB IPI wait > (CPU#0) > Feb 3 04:40:23 continuum last message repeated 4 times > Feb 3 04:40:45 continuum last message repeated 4 times > Feb 3 04:40:56 continuum kernel: stuck on TLB IPI wait > (CPU#1) > Feb 3 04:41:02 continuum last message repeated 2 times I should also mention that the kernel has the following patches applied. 00-piii-8 01-ide-2.2.18.1221.patch 02-raid-2.2.18b3 -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
SMP problem with 2.2.19pre8
Hi, I just built this SMP system and am getting some weird errors from kern.log. The system will run smoothly but after about a half hour running the distributed.net RC5 client, the following errors show up. Feb 3 04:40:18 continuum kernel: stuck on TLB IPI wait (CPU#0) Feb 3 04:40:23 continuum last message repeated 4 times Feb 3 04:40:45 continuum last message repeated 4 times Feb 3 04:40:56 continuum kernel: stuck on TLB IPI wait (CPU#1) Feb 3 04:41:02 continuum last message repeated 2 times The system doesn't actually crash but it does slow to a crawl such that you can't really do anything with it. It is an Abit VP6 motherboard running 2 P-III 850 CPUs at 100MHZ bus speed. 256MB of PC133 micron ram. If anyone knows whether this is a kernel issue or a hardware one, I would appreciate hearing from you. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
SMP problem with 2.2.19pre8
Hi, I just built this SMP system and am getting some weird errors from kern.log. The system will run smoothly but after about a half hour running the distributed.net RC5 client, the following errors show up. Feb 3 04:40:18 continuum kernel: stuck on TLB IPI wait (CPU#0) Feb 3 04:40:23 continuum last message repeated 4 times Feb 3 04:40:45 continuum last message repeated 4 times Feb 3 04:40:56 continuum kernel: stuck on TLB IPI wait (CPU#1) Feb 3 04:41:02 continuum last message repeated 2 times The system doesn't actually crash but it does slow to a crawl such that you can't really do anything with it. It is an Abit VP6 motherboard running 2 P-III 850 CPUs at 100MHZ bus speed. 256MB of PC133 micron ram. If anyone knows whether this is a kernel issue or a hardware one, I would appreciate hearing from you. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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: SMP problem with 2.2.19pre8
On Sat, Feb 03, 2001 at 02:07:27PM -0800, Shane Wegner wrote: Hi, I just built this SMP system and am getting some weird errors from kern.log. The system will run smoothly but after about a half hour running the distributed.net RC5 client, the following errors show up. Feb 3 04:40:18 continuum kernel: stuck on TLB IPI wait (CPU#0) Feb 3 04:40:23 continuum last message repeated 4 times Feb 3 04:40:45 continuum last message repeated 4 times Feb 3 04:40:56 continuum kernel: stuck on TLB IPI wait (CPU#1) Feb 3 04:41:02 continuum last message repeated 2 times I should also mention that the kernel has the following patches applied. 00-piii-8 01-ide-2.2.18.1221.patch 02-raid-2.2.18b3 -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
Problem with kernel 2.2.18+vm-global-7
Hi, I am using Linux 2.2.18 with vm-global-7 and raid-0.90 applied. The system became virtually unresponsive earlier and after a reboot, I found the following in my logs. By unresponsive I mean ping would work but telnet for example would connect and just sit there. Jan 2 04:36:27 continuum kernel: VM: killing process apache Jan 2 04:40:15 continuum kernel: VM: killing process cmdnsqueue Jan 2 04:41:04 continuum kernel: VM: killing process cron What conditions would trigger this situation? Why would the kernel decide to kill cron and Apache? Cheers, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
Problem with kernel 2.2.18+vm-global-7
Hi, I am using Linux 2.2.18 with vm-global-7 and raid-0.90 applied. The system became virtually unresponsive earlier and after a reboot, I found the following in my logs. By unresponsive I mean ping would work but telnet for example would connect and just sit there. Jan 2 04:36:27 continuum kernel: VM: killing process apache Jan 2 04:40:15 continuum kernel: VM: killing process cmdnsqueue Jan 2 04:41:04 continuum kernel: VM: killing process cron What conditions would trigger this situation? Why would the kernel decide to kill cron and Apache? Cheers, Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D - 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/
