VIA chipset discussion

VIA chipset discussion

[David D.W. Downey]

Could those that were involved in the VIA chipset discussion email me
privately at pgpkeys@hislinuxbox.com?

I'm truly interested in solving this issue. I personally think it's more
than just the chipset causing the problems.


I'm looking for members of the list that are using the kernel support for
the following


VIA chipset
Promise controller (PDC2026# with specifics on the PDC20265 (ATA100))
SMP support
IDE + SCSI mix in the system.


I'm trying to track a number of POSSIBLE bugs (can't say they are for
sure) and any input from folks with this mix of drivers would be
exponentially useful, even if for nothing more than discounting some of my
thoughts.


Also, can anyone summurize the already known and specific problems with
combinations of the above requirements? I would truly appreciate that. 

David D.W. Downey

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Pete Toscano]

well, i know there's a problem with the via apollo pro 133a chipset,
smp, apic, and usb.  it looks like the usb driver (usb-uhci) doesn't
receive any interrupts if apic is enabled.  if you disable apic from the
lilo prompt with "noapic", then it'll all work (of course, without
apic).  

according to the linux-usb maintainers, it's a pci irq routing problem.
i've asked jeff garzik and martin mares if they'll look into it, but
they're pretty busy and i haven't heard anything back from them (not
that'd i'd expect to for quite a while, considering their load).  i've
asked on the list too, but i've only heard back from people with the
same problem, not anyone who can fix the problem.

i've pretty much got the same system as you, except for the ultra66
promise card.

pete


On Wed, 17 Jan 2001, David D.W. Downey wrote:

> 
> Could those that were involved in the VIA chipset discussion email me
> privately at pgpkeys@hislinuxbox.com?
> 
> I'm truly interested in solving this issue. I personally think it's more
> than just the chipset causing the problems.
> 
> 
> I'm looking for members of the list that are using the kernel support for
> the following
> 
> 
> VIA chipset
> Promise controller (PDC2026# with specifics on the PDC20265 (ATA100))
> SMP support
> IDE + SCSI mix in the system.
> 
> 
> I'm trying to track a number of POSSIBLE bugs (can't say they are for
> sure) and any input from folks with this mix of drivers would be
> exponentially useful, even if for nothing more than discounting some of my
> thoughts.
> 
> 
> Also, can anyone summurize the already known and specific problems with
> combinations of the above requirements? I would truly appreciate that. 
> 
> David D.W. Downey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Rogerio Brito]

[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]

On Jan 17 2001, David D.W. Downey wrote:
> 
> Could those that were involved in the VIA chipset discussion email me
> privately at pgpkeys@hislinuxbox.com?

	Just to add a datapoint to the discussion, I'm using a VIA
	chipset here (in fact, it's an Asus A7V board with a Duron), a
	2.2.18 kernel with André's patches and I'm only using IDE
	(UDMA/66 and UDMA/33 here) and I'm *not* seeing any problems.

	Perhaps this may be a problem with some revisions of the
	chipset (or, perhaps, I'm not stressing my system enough for
	the bugs to show their heads).

	I'm attaching the output of lspci of my machine to this
	message.

	I also used a 2.4.0 kernel with all support for everything
	here enabled, but the HD where I had that kernel died. :-( So,
	I'm back using a 2.2.0 kernel.

> I'm truly interested in solving this issue. I personally think it's
> more than just the chipset causing the problems.

	This may be a possibility, since I'm using this very same
	chipset and I'm not seeing any problems...

> VIA chipset
> Promise controller (PDC2026# with specifics on the PDC20265 (ATA100))

	I'm using these (but I don't have anything in my Promise
	controller yet, since I couldn't find UDMA/100 drives when I
	bought my machine).

> SMP support
> IDE + SCSI mix in the system.

	But I'm not using SMP nor SCSI here.


	Hope this helps, Roger...

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Rogerio Brito - rbrito@iname.com - http://www.ime.usp.br/~rbrito/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

[-- Attachment #2: lspci.txt --]
[-- Type: text/plain, Size: 917 bytes --]

00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02)
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8305
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 22)
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10)
00:04.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10)
00:04.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10)
00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RT8139 (rev 10)
00:0a.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01)
00:0d.0 Multimedia audio controller: Ensoniq: Unknown device 5880 (rev 02)
00:11.0 Unknown mass storage controller: Promise Technology, Inc.: Unknown device 0d30 (rev 02)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04)

Re: VIA chipset discussion

[Matthew Fredrickson]

On Thu, Jan 18, 2001 at 02:04:08AM -0200, Rogerio Brito wrote:
> On Jan 17 2001, David D.W. Downey wrote:
> > 
> > Could those that were involved in the VIA chipset discussion email me
> > privately at pgpkeys@hislinuxbox.com?
> 
> 	Just to add a datapoint to the discussion, I'm using a VIA
> 	chipset here (in fact, it's an Asus A7V board with a Duron), a
> 	2.2.18 kernel with André's patches and I'm only using IDE
> 	(UDMA/66 and UDMA/33 here) and I'm *not* seeing any problems.

BTW, are you having any trouble with your ps/2 mouse port in X?  On my new
ASUS board, ps/2 mouse devices (just in X, gpm works fine) act a little
crazy (random mouse movement, random clicking, etc., except I'm not the
one doing all the random movement).  I'm not sure what it is, though I do
know it's not as bad once I upgraded from 2.2.18pre21 to 2.4.0.  I think
I'm going to try using the mouse as a usb device and see if I still have
trouble.  Anyway, just wondering if you're seeing the same problem.

Matthew Fredrickson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[John O'Donnell]

Matthew Fredrickson wrote:

> On Thu, Jan 18, 2001 at 02:04:08AM -0200, Rogerio Brito wrote:
> 
>> On Jan 17 2001, David D.W. Downey wrote:
>> 
>>> Could those that were involved in the VIA chipset discussion email me
>>> privately at pgpkeys@hislinuxbox.com?
>> 
>> 	Just to add a datapoint to the discussion, I'm using a VIA
>> 	chipset here (in fact, it's an Asus A7V board with a Duron), a
>> 	2.2.18 kernel with André's patches and I'm only using IDE
>> 	(UDMA/66 and UDMA/33 here) and I'm *not* seeing any problems.
> 
> 
> BTW, are you having any trouble with your ps/2 mouse port in X?  On my new
> ASUS board, ps/2 mouse devices (just in X, gpm works fine) act a little
> crazy (random mouse movement, random clicking, etc., except I'm not the
> one doing all the random movement).  I'm not sure what it is, though I do
> know it's not as bad once I upgraded from 2.2.18pre21 to 2.4.0.  I think
> I'm going to try using the mouse as a usb device and see if I still have
> trouble.  Anyway, just wondering if you're seeing the same problem.

I have the ASUS CUV4X.
VIA vt82c686a (cf/cg) IDE UDMA66 controller on pci0:4.1
I also run DMA66 with no problems here.

I never have seen any issues with the PS/2 mouse and X.
I use the Logitech cordless wheel mouse.  I use the "MouseManPlusPS/2"
driver in XFree.  When I was first setting this up (about a year ago)
I had the problems you mention.  I read an article on setting up your
scroll wheel in X and it said to use the IMPS/2 setting.  This was
nothing but trouble, till I RTFM on XFree and mice and found my solution.
Can you tell us what kind of mouse this is and how you have it set up in
XFree.

Let's take this mouse discussion off list as it has nuttin to do with
the kernel....
Johnny O

-- 
<SomeLamer> what's the difference between chattr and chmod?
<SomeGuru> SomeLamer: man chattr > 1; man chmod > 2; diff -u 1 2 | less
	-- Seen on #linux on irc
=== Never ask a geek why, just nod your head and slowly back away.===
+==============================+====================================+
| John O'Donnell (Sr. Systems Engineer, Net Admin, Webmaster, etc.) |
| Voice FX Corporation (a subsidiary of Student Advantage)          |
| One Plymouth Meeting         |     E-Mail: johnod@voicefx.com     |
| Suite 610                    |           www.voicefx.com          |
| Plymouth Meeting, PA 19462   |         www.campusdirect.com       |
+==============================+====================================+

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Howard Johnson]

On Thu, Jan 18, 2001 at 06:32:39PM -0500, John O'Donnell wrote:
> Matthew Fredrickson wrote:
> 
> I have the ASUS CUV4X.
> VIA vt82c686a (cf/cg) IDE UDMA66 controller on pci0:4.1
> I also run DMA66 with no problems here.
> 
> I never have seen any issues with the PS/2 mouse and X.
> I use the Logitech cordless wheel mouse.  I use the "MouseManPlusPS/2"
> driver in XFree.  When I was first setting this up (about a year ago)
> I had the problems you mention.  I read an article on setting up your
> scroll wheel in X and it said to use the IMPS/2 setting.  This was
> nothing but trouble, till I RTFM on XFree and mice and found my solution.
> Can you tell us what kind of mouse this is and how you have it set up in
> XFree.
> 
> Let's take this mouse discussion off list as it has nuttin to do with
> the kernel....
> Johnny O

I'm seeing the same mouse problems... fine under 2.2.x, but jumps around under
a couple of 2.4.x releases (2.4.0-test6, IIRC, and 2.4.1-pre7). I find it odd
that if it isn't a kernel-related problem, that it's only manifesting itself
under 2.4.

I'm running a slot A athlon on an abit KA7-100.

--
Howard Johnson
merlin@mwob.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Vojtech Pavlik]

On Thu, Jan 18, 2001 at 11:42:25PM +0000, Howard Johnson wrote:
> On Thu, Jan 18, 2001 at 06:32:39PM -0500, John O'Donnell wrote:
> > Matthew Fredrickson wrote:
> > 
> > I have the ASUS CUV4X.
> > VIA vt82c686a (cf/cg) IDE UDMA66 controller on pci0:4.1
> > I also run DMA66 with no problems here.
> > 
> > I never have seen any issues with the PS/2 mouse and X.
> > I use the Logitech cordless wheel mouse.  I use the "MouseManPlusPS/2"
> > driver in XFree.  When I was first setting this up (about a year ago)
> > I had the problems you mention.  I read an article on setting up your
> > scroll wheel in X and it said to use the IMPS/2 setting.  This was
> > nothing but trouble, till I RTFM on XFree and mice and found my solution.
> > Can you tell us what kind of mouse this is and how you have it set up in
> > XFree.
> > 
> > Let's take this mouse discussion off list as it has nuttin to do with
> > the kernel....
> > Johnny O
> 
> I'm seeing the same mouse problems... fine under 2.2.x, but jumps around under
> a couple of 2.4.x releases (2.4.0-test6, IIRC, and 2.4.1-pre7). I find it odd
> that if it isn't a kernel-related problem, that it's only manifesting itself
> under 2.4.
> 
> I'm running a slot A athlon on an abit KA7-100.

My bet is ACPI/powermanagement messing with it ...

-- 
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[John O'Donnell]

Vojtech Pavlik wrote:
> 
> On Thu, Jan 18, 2001 at 11:42:25PM +0000, Howard Johnson wrote:
> > On Thu, Jan 18, 2001 at 06:32:39PM -0500, John O'Donnell wrote:
> > > Matthew Fredrickson wrote:
> > >
> > > I have the ASUS CUV4X.
> > > VIA vt82c686a (cf/cg) IDE UDMA66 controller on pci0:4.1
> > > I also run DMA66 with no problems here.
> > >
> > > I never have seen any issues with the PS/2 mouse and X.
> > > I use the Logitech cordless wheel mouse.  I use the "MouseManPlusPS/2"
> > > driver in XFree.  When I was first setting this up (about a year ago)
> > > I had the problems you mention.  I read an article on setting up your
> > > scroll wheel in X and it said to use the IMPS/2 setting.  This was
> > > nothing but trouble, till I RTFM on XFree and mice and found my solution.
> > > Can you tell us what kind of mouse this is and how you have it set up in
> > > XFree.
> >
> > I'm seeing the same mouse problems... fine under 2.2.x, but jumps around under
> > a couple of 2.4.x releases (2.4.0-test6, IIRC, and 2.4.1-pre7). I find it odd
> > that if it isn't a kernel-related problem, that it's only manifesting itself
> > under 2.4.
> >
> > I'm running a slot A athlon on an abit KA7-100.
> 
> My bet is ACPI/powermanagement messing with it ...

Forgive me.  I know _nothing_ about Power Management resources.
What kind of resouces would PM use to interfere with the mouse.
FYI I have power management turned off in my BIOS and in the kernel
I have CONFIG_APM and ONLY  CONFIG_APM_REAL_MODE_POWER_OFF.
How does that compare with the rest of you?
Johnny O

-- 
=== Never ask a geek why, just nod your head and slowly back away.===
+==============================+====================================+
| John O'Donnell (Sr. Systems Engineer, Net Admin, Webmaster, etc.) |
| Voice FX Corporation (a subsidiary of Student Advantage)          |
| One Plymouth Meeting         |     E-Mail: johnod@voicefx.com     |
| Suite 610                    |           www.voicefx.com          |
| Plymouth Meeting, PA 19462   |         www.campusdirect.com       |
+==============================+====================================+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Matthew Fredrickson]

On Fri, Jan 19, 2001 at 11:42:01AM -0500, John O'Donnell wrote:
> Vojtech Pavlik wrote:
> > 
> > On Thu, Jan 18, 2001 at 11:42:25PM +0000, Howard Johnson wrote:
> > > On Thu, Jan 18, 2001 at 06:32:39PM -0500, John O'Donnell wrote:
> > > > Matthew Fredrickson wrote:
> > > >
> > > > I have the ASUS CUV4X.
> > > > VIA vt82c686a (cf/cg) IDE UDMA66 controller on pci0:4.1
> > > > I also run DMA66 with no problems here.
> > > >
> > > > I never have seen any issues with the PS/2 mouse and X.
> > > > I use the Logitech cordless wheel mouse.  I use the "MouseManPlusPS/2"
> > > > driver in XFree.  When I was first setting this up (about a year ago)
> > > > I had the problems you mention.  I read an article on setting up your
> > > > scroll wheel in X and it said to use the IMPS/2 setting.  This was
> > > > nothing but trouble, till I RTFM on XFree and mice and found my solution.
> > > > Can you tell us what kind of mouse this is and how you have it set up in
> > > > XFree.
> > >
> > > I'm seeing the same mouse problems... fine under 2.2.x, but jumps around under
> > > a couple of 2.4.x releases (2.4.0-test6, IIRC, and 2.4.1-pre7). I find it odd
> > > that if it isn't a kernel-related problem, that it's only manifesting itself
> > > under 2.4.
> > >
> > > I'm running a slot A athlon on an abit KA7-100.
> > 
> > My bet is ACPI/powermanagement messing with it ...
> 
> Forgive me.  I know _nothing_ about Power Management resources.
> What kind of resouces would PM use to interfere with the mouse.
> FYI I have power management turned off in my BIOS and in the kernel
> I have CONFIG_APM and ONLY  CONFIG_APM_REAL_MODE_POWER_OFF.
> How does that compare with the rest of you?

The same for me if I remember correctly (I've been dinking around on the
linux side of my box sparingly with X not working correctly), though I
might have compiled in some other ACPI stuff if I thought it looked cool
(heh).  My trouble is that I figure that the kernel must have _something_
to do with it since my problem got slightly better since upgrading from
2.2.18 to 2.4.0.  just my .02

Matthew Fredrickson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[David D.W. Downey]

On Fri, 19 Jan 2001, John O'Donnell wrote:

I also have APM disabled. (I don't think APM support is useful on a server
so I default disable it.)



> 
> Forgive me.  I know _nothing_ about Power Management resources.
> What kind of resouces would PM use to interfere with the mouse.
> FYI I have power management turned off in my BIOS and in the kernel
> I have CONFIG_APM and ONLY  CONFIG_APM_REAL_MODE_POWER_OFF.
> How does that compare with the rest of you?
> Johnny O
> 
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Howard Johnson]

On Fri, Jan 19, 2001 at 03:53:33PM +0100, Vojtech Pavlik wrote:
> On Thu, Jan 18, 2001 at 11:42:25PM +0000, Howard Johnson wrote:
> > On Thu, Jan 18, 2001 at 06:32:39PM -0500, John O'Donnell wrote:
> > > Matthew Fredrickson wrote:
> 
> My bet is ACPI/powermanagement messing with it ...

Ah, APM. So often blamed. So often the cause. ;-)

Yep, pulling APM support out of my kernel seems to have fixed the problem. I'll
start playing with APM settings, then.

Cheers.

-- 
Howard Johnson
merlin@mwob.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Rogerio Brito]

On Jan 18 2001, Matthew Fredrickson wrote:
> BTW, are you having any trouble with your ps/2 mouse port in X?

	Like I said in the previous e-mail, I'm using right now an
	Asus A7V mobo with Linus' stock kernel 2.2.18 with André's
	patches.

	I'm using basically a Debian potato here with XFree86 3.3.6
	and a Microsoft Intellimouse (with IMPS/2 protocol) and
	everything seems to be working fine. Before my brand new 40GB
	Samsung HD died, I was using a more modified potato, including
	XFree86 4.0.1e (or 4.0.1f, I don't remember). Everything was
	also working fine with this older setup.

> On my new ASUS board, ps/2 mouse devices (just in X, gpm works fine)
> act a little crazy (random mouse movement, random clicking, etc.,
> except I'm not the one doing all the random movement).  I'm not sure
> what it is, though I do know it's not as bad once I upgraded from
> 2.2.18pre21 to 2.4.0.

	I usually only follow Alan's pre series when things are broken
	with the final releases, so I don't know about 2.2.18preX. I'm
	sorry that I can't help.

> I think I'm going to try using the mouse as a usb device and see if
> I still have trouble.

	Unfortunately, I have never ever seen a USB device, so I have
	no experience here to help you.

> Anyway, just wondering if you're seeing the same problem.

	No, but have you tried changing the mouse? I've had problems
	with a Matrox G400 AGP 16MB monohead that I purchased when I
	got my system. It did crash when X was running in Linux and
	FreeBSD (and many versions of X, for that matter), but under
	Windows it worked flawlessly.

	When I used Matrox's drivers with XFree86 4.x, it worked
	perfectly.  I changed my Matrox and now I'm using a new one
	under X 3.3.6 under potato (a stable platform that I use) and
	everything is fine).

	So, perhaps you could try changing your mouse?


	[]s, Roger...

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Rogerio Brito - rbrito@iname.com - http://www.ime.usp.br/~rbrito/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Andy Galasso]

I'm not sure how relevant it is, but FWIW here's what I've got:

MSI 694D Pro Motherboard 2xPIII-800 100MHz FSB
Linux-2.4.0-prerelease SMP
Promise FastTrak100 controller card
4 IBM DTLA-307030 drives attached to Promise card
boot params: ide2=0xac00 ide3=0xb400

Here's an excerpt of what I get when trying to boot:

VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:7.1
    ide0: BM-DMA at 0x9000-0x9007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0x9008-0x900f, BIOS settings: hdc:DMA, hdd:pio
PDC20267: IDE controller on PCI bus 00 dev 70
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER Mode.
PDC20267: neither IDE port enabled (BIOS)
hde: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hde: IBM-DTLA-307030, ATA DISK drive
hdf: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hdf: IBM-DTLA-307030, ATA DISK drive
hdg: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hdg: IBM-DTLA-307030, ATA DISK drive
hdh: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
hdh: IBM-DTLA-307030, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0xac00-0xac07,0xae06 on irq 16
ide3 at 0xb400-0xb407,0xb606 on irq 16 (shared with ide2)
hde: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63
hdf: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63
hdg: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63
hdh: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63
Partition check:
 hde:hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
ide2: reset: master: error (0x00?)
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x50 { DriveReady SeekComplete }
hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
ide2(?): unexpected interrupt, status=0x58, count=1
ide2: reset: master: error (0x00?)
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
end_request: I/O error, dev 21:00 (hde), sector 0
hde: drive not ready for command
 unable to read partition table
 hdf:hdf: irq timeout: status=0x50 { DriveReady SeekComplete }
hdf: irq timeout: status=0x50 { DriveReady SeekComplete }
hdf: irq timeout: status=0x50 { DriveReady SeekComplete }
hdf: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
ide2(?): unexpected interrupt, status=0x58, count=2
ide2: reset: master: error (0x00?)
hdf: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdf: drive not ready for command
hdf: irq timeout: status=0x50 { DriveReady SeekComplete }
hdf: irq timeout: status=0x50 { DriveReady SeekComplete }
hdf: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
ide2(?): unexpected interrupt, status=0x58, count=3
ide2: reset: master: error (0x00?)
hdf: status error: status=0x58 { DriveReady SeekComplete DataRequest }
end_request: I/O error, dev 21:40 (hdf), sector 0
hdf: drive not ready for command
 unable to read partition table
...
(similar for hdg ... hdh ...)
...
  
-Andy Galasso


On Wed, Jan 17, 2001 at 02:02:17PM -0800, David D.W. Downey wrote:
> 
> Could those that were involved in the VIA chipset discussion email me
> privately at pgpkeys@hislinuxbox.com?
> 
> I'm truly interested in solving this issue. I personally think it's more
> than just the chipset causing the problems.
> 
> 
> I'm looking for members of the list that are using the kernel support for
> the following
> 
> 
> VIA chipset
> Promise controller (PDC2026# with specifics on the PDC20265 (ATA100))
> SMP support
> IDE + SCSI mix in the system.
> 
> 
> I'm trying to track a number of POSSIBLE bugs (can't say they are for
> sure) and any input from folks with this mix of drivers would be
> exponentially useful, even if for nothing more than discounting some of my
> thoughts.
> 
> 
> Also, can anyone summurize the already known and specific problems with
> combinations of the above requirements? I would truly appreciate that. 
> 
> David D.W. Downey
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[David D.W. Downey]

I get something similar. *I* get it when I mix drives on the various
controllers, aka ATA33/66 and ATA100 drives. I also get this error from
the CDROM when using the ATA100 controller for my ATA100 30GB drive and
the ATA33/66 controller for the CDROM. (Cyber 48X generic IDE CDROM).
 

On Sat, 20 Jan 2001, Andy Galasso wrote:

> I'm not sure how relevant it is, but FWIW here's what I've got:
> 
> MSI 694D Pro Motherboard 2xPIII-800 100MHz FSB
> Linux-2.4.0-prerelease SMP
> Promise FastTrak100 controller card
> 4 IBM DTLA-307030 drives attached to Promise card
> boot params: ide2=0xac00 ide3=0xb400
> 
> Here's an excerpt of what I get when trying to boot:
> 
> VP_IDE: IDE controller on PCI bus 00 dev 39
> VP_IDE: chipset revision 16
> VP_IDE: not 100% native mode: will probe irqs later
> VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:7.1
>     ide0: BM-DMA at 0x9000-0x9007, BIOS settings: hda:pio, hdb:pio
>     ide1: BM-DMA at 0x9008-0x900f, BIOS settings: hdc:DMA, hdd:pio
> PDC20267: IDE controller on PCI bus 00 dev 70
> PDC20267: chipset revision 2
> PDC20267: not 100% native mode: will probe irqs later
> PDC20267: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER Mode.
> PDC20267: neither IDE port enabled (BIOS)
> hde: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
> hde: IBM-DTLA-307030, ATA DISK drive
> hdf: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
> hdf: IBM-DTLA-307030, ATA DISK drive
> hdg: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
> hdg: IBM-DTLA-307030, ATA DISK drive
> hdh: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
> hdh: IBM-DTLA-307030, ATA DISK drive
> ide1 at 0x170-0x177,0x376 on irq 15
> ide2 at 0xac00-0xac07,0xae06 on irq 16
> ide3 at 0xb400-0xb407,0xb606 on irq 16 (shared with ide2)
> hde: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63
> hdf: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63
> hdg: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63
> hdh: 60036480 sectors (30739 MB) w/1916KiB Cache, CHS=59560/16/63
> Partition check:
>  hde:hde: irq timeout: status=0x50 { DriveReady SeekComplete }
> hde: irq timeout: status=0x50 { DriveReady SeekComplete }
> hde: irq timeout: status=0x50 { DriveReady SeekComplete }
> hde: irq timeout: status=0x50 { DriveReady SeekComplete }
> ide2: reset: master: error (0x00?)
> hde: irq timeout: status=0x50 { DriveReady SeekComplete }
> hde: irq timeout: status=0x50 { DriveReady SeekComplete }
> hde: irq timeout: status=0x50 { DriveReady SeekComplete }
> hde: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> ide2(?): unexpected interrupt, status=0x58, count=1
> ide2: reset: master: error (0x00?)
> hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> end_request: I/O error, dev 21:00 (hde), sector 0
> hde: drive not ready for command
>  unable to read partition table
>  hdf:hdf: irq timeout: status=0x50 { DriveReady SeekComplete }
> hdf: irq timeout: status=0x50 { DriveReady SeekComplete }
> hdf: irq timeout: status=0x50 { DriveReady SeekComplete }
> hdf: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> ide2(?): unexpected interrupt, status=0x58, count=2
> ide2: reset: master: error (0x00?)
> hdf: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> hdf: drive not ready for command
> hdf: irq timeout: status=0x50 { DriveReady SeekComplete }
> hdf: irq timeout: status=0x50 { DriveReady SeekComplete }
> hdf: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> ide2(?): unexpected interrupt, status=0x58, count=3
> ide2: reset: master: error (0x00?)
> hdf: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> end_request: I/O error, dev 21:40 (hdf), sector 0
> hdf: drive not ready for command
>  unable to read partition table
> ...
> (similar for hdg ... hdh ...)
> ...
>   
> -Andy Galasso
> 
> 
> On Wed, Jan 17, 2001 at 02:02:17PM -0800, David D.W. Downey wrote:
> > 
> > Could those that were involved in the VIA chipset discussion email me
> > privately at pgpkeys@hislinuxbox.com?
> > 
> > I'm truly interested in solving this issue. I personally think it's more
> > than just the chipset causing the problems.
> > 
> > 
> > I'm looking for members of the list that are using the kernel support for
> > the following
> > 
> > 
> > VIA chipset
> > Promise controller (PDC2026# with specifics on the PDC20265 (ATA100))
> > SMP support
> > IDE + SCSI mix in the system.
> > 
> > 
> > I'm trying to track a number of POSSIBLE bugs (can't say they are for
> > sure) and any input from folks with this mix of drivers would be
> > exponentially useful, even if for nothing more than discounting some of my
> > thoughts.
> > 
> > 
> > Also, can anyone summurize the already known and specific problems with
> > combinations of the above requirements? I would truly appreciate that. 
> > 
> > David D.W. Downey
> > 
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > Please read the FAQ at http://www.tux.org/lkml/
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Andre Hedrick]

On Sat, 20 Jan 2001, Andy Galasso wrote:

> I'm not sure how relevant it is, but FWIW here's what I've got:
> 
> MSI 694D Pro Motherboard 2xPIII-800 100MHz FSB
> Linux-2.4.0-prerelease SMP
> Promise FastTrak100 controller card
> 4 IBM DTLA-307030 drives attached to Promise card
> boot params: ide2=0xac00 ide3=0xb400

DON'T the above silly "ide2=0xac00 ide3=0xb400"!

> hde: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
> hdf: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
> hdg: probing with STATUS(0x50) instead of ALTSTATUS(0xff)
> hdh: probing with STATUS(0x50) instead of ALTSTATUS(0xff)

You have no altstatus register because of using 2.2 crippled access on 2.4
fully enabled.

> ide1 at 0x170-0x177,0x376 on irq 15
> ide2 at 0xac00-0xac07,0xae06 on irq 16
> ide3 at 0xb400-0xb407,0xb606 on irq 16 (shared with ide2)

You have now lost your interrupt parser in the driver :-(

>  hde:hde: irq timeout: status=0x50 { DriveReady SeekComplete }

No one is to every override the driver on setting up the IO base.

Cheers,


Andre Hedrick
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Petr Vandrovec]

On 17 Jan 01 at 17:40, Pete Toscano wrote:
> according to the linux-usb maintainers, it's a pci irq routing problem.
> i've asked jeff garzik and martin mares if they'll look into it, but
> they're pretty busy and i haven't heard anything back from them (not
> that'd i'd expect to for quite a while, considering their load).  i've
> asked on the list too, but i've only heard back from people with the
> same problem, not anyone who can fix the problem.

I'm using kernel module below. Find which device your USB is. If it is
0:07.2 and 0:07.3, take 7*8 + 2 = 58 (resp. 59). Then try

for irq in 16 17 18 19; do
  insmod setpci devfn=58 irq=$irq
  insmod setpci devfn=59 irq=$irq
  modprobe <your usb ohci/uhci/alt-uhci>
  does it work -> stop
done

After you'll find correct IRQ, you are done ;-) Put this into your
initscript before usb loading (you must compile USB as module), or
you can insert your devfn/irq pair somewhere into pirq_get_info()...

My BIOS (Apollo Pro 133x) returns incorrect routing table when LPT is
not in ECP mode. When it is in ECP, reported routing table is correct
(and my USB is on IRQ19, if that matters).

/*
# Based on Makefile for the Linux video drivers.
# 5 Aug 1999, James Simmons, <mailto:jsimmons@edgeglobal.com>
# Rewritten to use lists instead of if-statements.

default:
    (cd /usr/src/linux; make SUBDIRS=/usr/src/linus/pci modules)

O_TARGET := setp.o

# All of the (potential) objects that export symbols.
# This list comes from 'grep -l EXPORT_SYMBOL *.[hc]'.

# Each configuration option enables a list of files.

obj-m += setpci.o

ifdef TOPDIR
include $(TOPDIR)/Rules.make
endif

clean:
    rm -f core *.o *.a *.s
*/

#include <linux/config.h>
#include <linux/module.h>
#include <linux/errno.h>
#include <linux/init.h>
#include <linux/pci.h>

static unsigned int devfn = -1;
static unsigned int irq   = -1;
MODULE_PARM(devfn, "i");
MODULE_PARM(irq, "i");

static int loadme(void) {
    struct pci_dev* dev;
    
    pci_for_each_dev(dev) {
        printk(KERN_DEBUG "%p: %04X: %04X:%04X -> %d\n",
            dev, dev->devfn, dev->vendor, dev->device, dev->irq);
        if (dev->devfn == devfn)
            dev->irq = irq;
    }
    return -EBUSY;
}

module_init(loadme);
 

                                            Best regards,
                                                Petr Vandrovec
                                                vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: VIA chipset discussion

[Vojtech Pavlik]

On Sun, Jan 21, 2001 at 03:04:37AM -0800, David D.W. Downey wrote:
> 
> OK, currently at work so I don't have the affected system in front of
> me. I'm doing this from memory..
> 
> My apologies to those that responded to me. I've been unable to work on
> this issue for the last few days due to work.
> 
> My particular board is the MSI 694D Pro Dual processor board. It uses the
> VT82C686A chipset and the PDC20265 Promise ATA100.
> 
> I'm running dual PIII-733s with 1GB of Corsair RAM. The board, CPUs, and
> memory all run at 133MHz. The drives are 
> 
>     ide0: BM-DMA at 0xb000-0xb007, BIOS settings: hda:DMA, hdb:DMA
> hda: WDC WD153AA, ATA DISK drive
> hda: 30064608 sectors (15393 MB) w/2048KiB Cache, CHS=1871/255/63, UDMA(66)
>     ide0: BM-DMA at 0xb000-0xb007, BIOS settings: hda:DMA, hdb:DMA
> hdb: WDC WD300BB-00AUA1, ATA DISK drive
> hdb: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=3649/255/63, UDMA(66)
> Now to recap...
> Kernel command line: BOOT_IMAGE=new ro root=304 idebus=66 hdc=ignore
> ide_setup: hdc=ignore -- BAD OPTION

Don't use "idebus=66". It's wrong. If you want to force UDMA66/UDMA100,
the correct option is ide0=ata66. If you want to use idebus=, you should
use idebus=33, because that's what your PCI bus most likely operates at.

Also "hdc=ignore" doesn't work either.

>     ide1: BM-DMA at 0xb008-0xb00f, BIOS settings: hdc:DMA, hdd:pio
> hdc: SAMSUNG CD-ROM SC-148F, ATAPI CDROM drive
> hdc: ATAPI 48X CD-ROM drive, 128kB Cache, DMA
> 
> I'm experiencing consistant kernel deaths when doing any type of heavy IO
> as I stated earlier. I'm using the following as my test.
> 
> dd if=/dev/hda4 of=/tmp/testdd.img bs=1024M count=2k
> 
> It gets about 300MB into the file and pukes the kernel.

What does the 'puking' exactly do?

> I get lots of errors about disabling DMA within my logs.

Just this?

> No perosnally, I believe it's a problem with the VIA chipset
> specifically. I've seen a couple of emails regarding the same type of
> problem with various setups and the commonality is the VIA chipset. How is
> this affecting it? I'm not quite sure. (This may already have been covered
> but for the purpose of making sure that I'm not chasing numerous
> possibilities I've ignored some of them.) I **THINK** it's a problem
> specifically with the DMA support. 

The VIA chipsets are not easy to set up and the margins for error are
too thin.

> However, I do still get the kernel deaths even when using ATA33. I've
> specifically noticed that if you install mixed drives (ATA33 + ATA66 +
> ATA100) then the system will consistantly puke as well. Take out the ATA66
> drives and things stabilize for a bit then puke. I'm not sure if dropping
> an ATA33 drive on there by itself is the solution even if it does
> completely stabilize the machine. There is no reason for the ATA66 support
> not to work since it's a combined controller that I'm sure the VIA driver
> maintainer has looked at. (He emailed me but I forgot his name. Please
> accept my apologies for not remembering, no disrespect is intended.)

Me, most likely.

> Is anyone out there with as close a match to my setup as possible wish to
> help me with this? (I'm not discounting the mismatched setups, I just want
> a baseline to go from. If someone with my setup is NOT ahving trouble then
> I may need to look at something different).

-- 
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/