Skip to contentSkip to conversation

New: VIA VT8233 seems to suffer from the via latency quirk

Bugme-new Andrew Morton 3 participants 7 messages Oct 31, 2006 – Nov 1, 2006 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

(switched to email - please retain all cc's)

Quoted 11 lines · On Mon, 30 Oct 2006 16:20:16 -0800 [email protected] wrote:

http://bugzilla.kernel.org/show_bug.cgi?id=7437

Summary: VIA VT8233 seems to suffer from the via latency quirk
Kernel Version: 2.6.19-rc3
Status: NEW
Severity: normal
Owner: [email protected]
Submitter: [email protected]

Most recent kernel where this bug did not occur: 2.6.19-rc3

Nope. We're asking which kernel did _not_ have this bug?

Quoted 6 lines

Distribution: All
Hardware Environment: ASUS A7V266-E motherboad (northbridge VIA KT266A, southbridge VIA 8233), PCI SB LIVE!, onboard promise IDE controller, additional PCI USB2 card.
Software Environment: any

Quoted 9 lines

Problem Description: Fear to load the PCI bus, because it seems to cause a hard crash with hard drive data corruption. Too much similar to quirk_vialatency in drivers/pci/quirks.c (see description line 163) to be innocent.

Steps to reproduce: Load the PCI bus with, for instance, a big file transfer from an usb mass storage media v2 connected on a PCI USB2 card to the main hard drive and at the same time play music. Randomly crashes the computer and corrupts hard drive data (sometimes beyond repair).

argh. Are you able to identify a change to the via quirk-handling code which prevents this from happening?

#2 lore raw

Unfortunately, this has always happened since kernel 2.4 from years back, even with USB1 devices and I had to drop software raid 0. As far as I understand the quirk code, it's not enabled for the VT8233 southbridge.
I can add the PCI ID of this VT8233 for this quirk code, if it's compatible, and do some crash tests. Crashes are usually easy to produce and not hardware destructive since I got plenty of them. But you may want to proceed in another way.

2006/10/31, Andrew Morton <[email protected]>:

Quoted 40 lines

(switched to email - please retain all cc's)

Quoted 11 lines · On Mon, 30 Oct 2006 16:20:16 -0800 [email protected] wrote:

http://bugzilla.kernel.org/show_bug.cgi?id=7437

Summary: VIA VT8233 seems to suffer from the via latency quirk
Kernel Version: 2.6.19-rc3
Status: NEW
Severity: normal
Owner: [email protected]
Submitter: [email protected]

Most recent kernel where this bug did not occur: 2.6.19-rc3

Nope. We're asking which kernel did _not_ have this bug?

Quoted 6 lines

Distribution: All
Hardware Environment: ASUS A7V266-E motherboad (northbridge VIA KT266A, southbridge VIA 8233), PCI SB LIVE!, onboard promise IDE controller, additional PCI USB2 card.
Software Environment: any

Quoted 9 lines

Problem Description: Fear to load the PCI bus, because it seems to cause a hard crash with hard drive data corruption. Too much similar to quirk_vialatency in drivers/pci/quirks.c (see description line 163) to be innocent.

Steps to reproduce: Load the PCI bus with, for instance, a big file transfer from an usb mass storage media v2 connected on a PCI USB2 card to the main hard drive and at the same time play music. Randomly crashes the computer and corrupts hard drive data (sometimes beyond repair).

argh. Are you able to identify a change to the via quirk-handling code which prevents this from happening?

#3 lore raw
Quoted 8 lines · Sylvain Bertrand

Unfortunately, this has always happened since kernel 2.4 from years back, even with USB1 devices and I had to drop software raid 0. As far as I understand the quirk code, it's not enabled for the VT8233 southbridge.
I can add the PCI ID of this VT8233 for this quirk code, if it's compatible, and do some crash tests. Crashes are usually easy to produce and not hardware destructive since I got plenty of them. But you may want to proceed in another way.

That would be the best way to proceed. If you add your device ids to the quirk, does the machine work properly afterward?

thanks,

greg k-h

#4 lore raw

I enabled the via latency quirk code for my chipset and my workstation does crash the same way.
Then, my crash problem seems not related to this quirk even if symptoms are quite similar.

2006/10/31, Greg KH <[email protected]>:

Quoted 6 lines

That would be the best way to proceed. If you add your device ids to the quirk, does the machine work properly afterward?

thanks,

greg k-h

#5 lore raw
Quoted 4 lines · Sylvain Bertrand

I enabled the via latency quirk code for my chipset and my workstation does crash the same way.
Then, my crash problem seems not related to this quirk even if symptoms are quite similar.

Thank you for testing. Can you try contacting VIA to find out what needs to be fixed here?

#6 lore raw

Ok, I will send an email. In the mean time, I may experiment enabling some of the PCI quirks. Do you have some hints on the quirks which could be good candidates?

2006/11/1, Greg KH <[email protected]>:

Quoted 9 lines · Sylvain Bertrand
Quoted 4 lines

I enabled the via latency quirk code for my chipset and my workstation does crash the same way.
Then, my crash problem seems not related to this quirk even if symptoms are quite similar.

Thank you for testing. Can you try contacting VIA to find out what needs to be fixed here?

#7 lore raw
Quoted 1 line · Sylvain Bertrand

Do you have some hints on the quirks which could be good candidates?

I do not, sorry.

Good luck.