Re: How's the nforce4 support in Linux?
On Apr 6, 2005 6:02 PM, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
>
> There still can be a bug in setting up DMA timings etc.
>
> It is hard to even guess as you haven't given any details about your
> system: dmesg/hdparm/lspci/config... (or I overlooked it somehow).
I sent the related dmesg lines, and my .config.
for dmesg and .config :
http://marc.theaimsgroup.com/?l=linux-kernel=79215521092=2
what part of lspci would you need ?
hdparm :
[EMAIL PROTECTED]:~$ sudo hdparm -i /dev/hda
/dev/hda:
Model=Maxtor 6Y160P0, FwRev=YAR41BW0, SerialNo=Y47J8CRE
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: (null):
* signifies the current active mode
(it shows no mode... it's strange, because this drive should be nearly
the same as the following)
[EMAIL PROTECTED]:~$ sudo hdparm -i /dev/hdc
/dev/hdc:
Model=Maxtor 6Y120L0, FwRev=YAR41BW0, SerialNo=Y31LWCXE
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: (null):
* signifies the current active mode
[EMAIL PROTECTED]:~$ sudo hdparm -d /dev/hdc
/dev/hdc:
using_dma= 0 (off)
(Note : hdparm -i says 'udma6', and hdparm -d says 'no dma'...
Strange, isn't it ?)
> > > In my case, the driver stopped for hdb, that is my dvd-burner/player.
> > > It did nothing for hda or hdc, I had to disable DMA myself.
> > >
> > > Will I have to install Windows XP to prove ultra DMA works correctly
> > > on this setup ? I really don't hope...
>
> That would be very helpful.
I'll try that...
> Another useful thing would be to try non-nVidia motherboard
> (if you have one handy) without changing anything else.
I succesfully used these drives with another motherboard (PIIX4)
before, in udma2 mode, for years...
But first thing : I have to check if the cables are correctly plugged
in (I mean in the correct order)... I didn't have the time to do that
yet.
Thanks for your answer.
--
Julien
-
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: How's the nforce4 support in Linux?
On Apr 6, 2005 1:41 PM, Richard B. Johnson <[EMAIL PROTECTED]> wrote: > > How would you know? Windows will just run it as PIOW and be done > with it. Yes, but there's a way to know which mode you're using (maybe not precisely, but at least PIO vs DMA). > Did you ever try to copy a large file in XP? Try it. > Try the same thing in linux on the same hardware. You don't need > a stop-watch. On Win-XP, a 10 megabyte file (hardly large) takes > about 10 seconds. That's 1 megabyte/second. Linux tries to be > a bit faster. Usually, I only have Linux on any hardware I have ;) And there is no point comparing these things here... -- Julien PS: Sorry Richard, I forgot my "reply to all" button... - 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: How's the nforce4 support in Linux?
On Apr 6, 2005 1:41 PM, Richard B. Johnson [EMAIL PROTECTED] wrote: How would you know? Windows will just run it as PIOW and be done with it. Yes, but there's a way to know which mode you're using (maybe not precisely, but at least PIO vs DMA). Did you ever try to copy a large file in XP? Try it. Try the same thing in linux on the same hardware. You don't need a stop-watch. On Win-XP, a 10 megabyte file (hardly large) takes about 10 seconds. That's 1 megabyte/second. Linux tries to be a bit faster. Usually, I only have Linux on any hardware I have ;) And there is no point comparing these things here... -- Julien PS: Sorry Richard, I forgot my reply to all button... - 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: How's the nforce4 support in Linux?
On Apr 6, 2005 6:02 PM, Bartlomiej Zolnierkiewicz [EMAIL PROTECTED] wrote:
There still can be a bug in setting up DMA timings etc.
It is hard to even guess as you haven't given any details about your
system: dmesg/hdparm/lspci/config... (or I overlooked it somehow).
I sent the related dmesg lines, and my .config.
for dmesg and .config :
http://marc.theaimsgroup.com/?l=linux-kernelm=79215521092w=2
what part of lspci would you need ?
hdparm :
[EMAIL PROTECTED]:~$ sudo hdparm -i /dev/hda
/dev/hda:
Model=Maxtor 6Y160P0, FwRev=YAR41BW0, SerialNo=Y47J8CRE
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=268435455
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: (null):
* signifies the current active mode
(it shows no mode... it's strange, because this drive should be nearly
the same as the following)
[EMAIL PROTECTED]:~$ sudo hdparm -i /dev/hdc
/dev/hdc:
Model=Maxtor 6Y120L0, FwRev=YAR41BW0, SerialNo=Y31LWCXE
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive conforms to: (null):
* signifies the current active mode
[EMAIL PROTECTED]:~$ sudo hdparm -d /dev/hdc
/dev/hdc:
using_dma= 0 (off)
(Note : hdparm -i says 'udma6', and hdparm -d says 'no dma'...
Strange, isn't it ?)
In my case, the driver stopped for hdb, that is my dvd-burner/player.
It did nothing for hda or hdc, I had to disable DMA myself.
Will I have to install Windows XP to prove ultra DMA works correctly
on this setup ? I really don't hope...
That would be very helpful.
I'll try that...
Another useful thing would be to try non-nVidia motherboard
(if you have one handy) without changing anything else.
I succesfully used these drives with another motherboard (PIIX4)
before, in udma2 mode, for years...
But first thing : I have to check if the cables are correctly plugged
in (I mean in the correct order)... I didn't have the time to do that
yet.
Thanks for your answer.
--
Julien
-
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: How's the nforce4 support in Linux?
On Apr 5, 2005 4:10 PM, Richard B. Johnson <[EMAIL PROTECTED]> wrote:
> On Tue, 5 Apr 2005, Julien Wajsberg wrote:
>
> > On Mar 26, 2005 12:59 AM, Julien Wajsberg <[EMAIL PROTECTED]> wrote:
> >> I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
> >> experiment the following problem :
> >>
> >> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> >> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> >> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> >> Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
> >> DriveReady SeekComplete DataRequest }
> >> Mar 25 22:42:55 evenflow kernel:
> >> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> >> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> >> Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
> >> Mar 25 22:42:55 evenflow kernel:
> >> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> >> Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
> ^
> >> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> >>
> >> Of course, if I disable DMA with hdparm, this problem disappear.. but
> >> it isn't a long-term solution ;-)
> >>
>
> The long-term solution is to replace either the drive, cable, or the
> motherboard that can't do DMA.
It's a recent drive that did ultra DMA on another motherboard, and a
recent motherboard with a cable that did ultra DMA before.It was ultra
DMA2 on this old motherboard, but it still was ultra DMA.
> A bad DMA operation can write data
> anywhere (right into the middle of the kernel). There isn't
> anything software can do about it. Software sets up the
> controller for a DMA operation, then waits for an interrupt
> that tells it has completed or failed. Software can retry failed
> operations until software gets destroyed by the hardware, but
> there isn't anything else that can be done.
>
> The fact that disabling DMA makes the problem(s) go away is
> proof that it isn't a software problem. There are flash-RAM
> devices that emulate IDE drives. Most of these can't do DMA
> and the IDE driver doesn't accept that fact. That is a known
> bug. One needs to use hdparm to tell it to stop trying to
> use DMA. In your case, the driver stopped using DMA when
> it found out that it didn't work. There is no bug.
In my case, the driver stopped for hdb, that is my dvd-burner/player.
It did nothing for hda or hdc, I had to disable DMA myself.
Will I have to install Windows XP to prove ultra DMA works correctly
on this setup ? I really don't hope...
--
Julien
-
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: How's the nforce4 support in Linux?
On Mar 26, 2005 12:59 AM, Julien Wajsberg <[EMAIL PROTECTED]> wrote:
> I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
> experiment the following problem :
>
> Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
> DriveReady SeekComplete DataRequest }
> Mar 25 22:42:55 evenflow kernel:
> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
> Mar 25 22:42:55 evenflow kernel:
> Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
> Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
>
> Of course, if I disable DMA with hdparm, this problem disappear.. but
> it isn't a long-term solution ;-)
>
> Using vanilla 2.6.11.5 kernel. I attached the config file.
I tried the multidma mode (as opposed to ultradma), and the system
hanged immediately. (Thanks to the patched-for-netpoll forcedeth
driver), I got the following message:
Unknown interrupt or fault at EIP 0206 0060 c0247a3a
There's definitely something wrong here...
I'm still using the same setup as in my first mail.
--
Julien
-
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: How's the nforce4 support in Linux?
On Apr 5, 2005 4:10 PM, Richard B. Johnson [EMAIL PROTECTED] wrote:
On Tue, 5 Apr 2005, Julien Wajsberg wrote:
On Mar 26, 2005 12:59 AM, Julien Wajsberg [EMAIL PROTECTED] wrote:
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
^
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Of course, if I disable DMA with hdparm, this problem disappear.. but
it isn't a long-term solution ;-)
The long-term solution is to replace either the drive, cable, or the
motherboard that can't do DMA.
It's a recent drive that did ultra DMA on another motherboard, and a
recent motherboard with a cable that did ultra DMA before.It was ultra
DMA2 on this old motherboard, but it still was ultra DMA.
A bad DMA operation can write data
anywhere (right into the middle of the kernel). There isn't
anything software can do about it. Software sets up the
controller for a DMA operation, then waits for an interrupt
that tells it has completed or failed. Software can retry failed
operations until software gets destroyed by the hardware, but
there isn't anything else that can be done.
The fact that disabling DMA makes the problem(s) go away is
proof that it isn't a software problem. There are flash-RAM
devices that emulate IDE drives. Most of these can't do DMA
and the IDE driver doesn't accept that fact. That is a known
bug. One needs to use hdparm to tell it to stop trying to
use DMA. In your case, the driver stopped using DMA when
it found out that it didn't work. There is no bug.
In my case, the driver stopped for hdb, that is my dvd-burner/player.
It did nothing for hda or hdc, I had to disable DMA myself.
Will I have to install Windows XP to prove ultra DMA works correctly
on this setup ? I really don't hope...
--
Julien
-
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: How's the nforce4 support in Linux?
On Mar 26, 2005 12:59 AM, Julien Wajsberg [EMAIL PROTECTED] wrote:
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Of course, if I disable DMA with hdparm, this problem disappear.. but
it isn't a long-term solution ;-)
Using vanilla 2.6.11.5 kernel. I attached the config file.
I tried the multidma mode (as opposed to ultradma), and the system
hanged immediately. (Thanks to the patched-for-netpoll forcedeth
driver), I got the following message:
Unknown interrupt or fault at EIP 0206 0060 c0247a3a
There's definitely something wrong here...
I'm still using the same setup as in my first mail.
--
Julien
-
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: How's the nforce4 support in Linux?
On Mar 26, 2005 7:32 PM, Marcin Dalecki <[EMAIL PROTECTED]> wrote:
>
> On 2005-03-26, at 16:19, Arjan van de Ven wrote:
>
> > `
> >> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >> hda: dma_intr: error=0x84 { DriveStatusError BadCRC
> >
> > BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
> > cable used at too high a speed for the cable.
>
> No. It is more likely that the timing programming between the disk and
> host controller
> are in a miss-match state. UDMA mode detection can come in to mind too.
> It makes sense to experiment with hdparm to see if the problem goes
> away in non
> Ultra DMA modes.
Do you mean "multiword dma modes" or "pio modes" ?
--
Julien
-
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: How's the nforce4 support in Linux?
On Mar 26, 2005 7:32 PM, Marcin Dalecki [EMAIL PROTECTED] wrote:
On 2005-03-26, at 16:19, Arjan van de Ven wrote:
`
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC
BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
cable used at too high a speed for the cable.
No. It is more likely that the timing programming between the disk and
host controller
are in a miss-match state. UDMA mode detection can come in to mind too.
It makes sense to experiment with hdparm to see if the problem goes
away in non
Ultra DMA modes.
Do you mean multiword dma modes or pio modes ?
--
Julien
-
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: How's the nforce4 support in Linux?
On Sat, 26 Mar 2005 15:13:47 +0100, Michal Schmidt
<[EMAIL PROTECTED]> wrote:
> Julien Wajsberg wrote:
> > Good point... I just tried, but forcedeth doesn't support netpoll. If
> > you have a pointer, I could try to implement it ;-)
>
> Can you try the attached patch for forcedeth?
> It compiles for me, but I don't have nForce hardware to test it.
Okay, it works :)
maybe I'll have something for you to debug at the next crash...
--
Julien
> --- linux-2.6.12-rc1/drivers/net/forcedeth.c.orig 2005-03-26
> 15:00:12.0 +0100
> +++ linux-2.6.12-rc1/drivers/net/forcedeth.c2005-03-26 15:08:56.0
> +0100
> @@ -1480,6 +1480,13 @@ static void nv_do_nic_poll(unsigned long
> enable_irq(dev->irq);
> }
>
> +#ifdef CONFIG_NET_POLL_CONTROLLER
> +static void nv_poll_controller(struct net_device *dev)
> +{
> + nv_do_nic_poll((long) dev);
> +}
> +#endif
> +
> static void nv_get_drvinfo(struct net_device *dev, struct ethtool_drvinfo
> *info)
> {
> struct fe_priv *np = get_nvpriv(dev);
> @@ -1962,6 +1969,9 @@ static int __devinit nv_probe(struct pci
> dev->get_stats = nv_get_stats;
> dev->change_mtu = nv_change_mtu;
> dev->set_multicast_list = nv_set_multicast;
> +#ifdef CONFIG_NET_POLL_CONTROLLER
> + dev->poll_controller = nv_poll_controller;
> +#endif
> SET_ETHTOOL_OPS(dev, );
> dev->tx_timeout = nv_tx_timeout;
> dev->watchdog_timeo = NV_WATCHDOG_TIMEO;
>
>
>
-
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: How's the nforce4 support in Linux?
On Sat, 26 Mar 2005 15:13:47 +0100, Michal Schmidt
[EMAIL PROTECTED] wrote:
Julien Wajsberg wrote:
Good point... I just tried, but forcedeth doesn't support netpoll. If
you have a pointer, I could try to implement it ;-)
Can you try the attached patch for forcedeth?
It compiles for me, but I don't have nForce hardware to test it.
Okay, it works :)
maybe I'll have something for you to debug at the next crash...
--
Julien
--- linux-2.6.12-rc1/drivers/net/forcedeth.c.orig 2005-03-26
15:00:12.0 +0100
+++ linux-2.6.12-rc1/drivers/net/forcedeth.c2005-03-26 15:08:56.0
+0100
@@ -1480,6 +1480,13 @@ static void nv_do_nic_poll(unsigned long
enable_irq(dev-irq);
}
+#ifdef CONFIG_NET_POLL_CONTROLLER
+static void nv_poll_controller(struct net_device *dev)
+{
+ nv_do_nic_poll((long) dev);
+}
+#endif
+
static void nv_get_drvinfo(struct net_device *dev, struct ethtool_drvinfo
*info)
{
struct fe_priv *np = get_nvpriv(dev);
@@ -1962,6 +1969,9 @@ static int __devinit nv_probe(struct pci
dev-get_stats = nv_get_stats;
dev-change_mtu = nv_change_mtu;
dev-set_multicast_list = nv_set_multicast;
+#ifdef CONFIG_NET_POLL_CONTROLLER
+ dev-poll_controller = nv_poll_controller;
+#endif
SET_ETHTOOL_OPS(dev, ops);
dev-tx_timeout = nv_tx_timeout;
dev-watchdog_timeo = NV_WATCHDOG_TIMEO;
-
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: How's the nforce4 support in Linux?
On Fri, 25 Mar 2005 18:14:22 -0500, Lee Revell <[EMAIL PROTECTED]> wrote: > On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote: > > - audio works too. The only problem is that two applications can't > > open /dev/dsp in the same time. > > Not a problem. ALSA does software mixing for chipsets that can't do it > in hardware. Google for dmix. > > However this doesn't (and can't be made to) work with the in-kernel OSS > emulation (it works fine with the alsa-lib/libaoss emulation). So you > are technically correct in that two OSS apps can't open /dev/dsp at the > same time, but there is no problem with multiple apps sharing the sound > device, as long as they use the ALSA API (which they should be using > anyway). Okay, good to know. Then I'll have to find out why beep-media-player doesn't work with alsa :-) -- Julien - 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: How's the nforce4 support in Linux?
On Fri, 25 Mar 2005 18:20:54 -0500, Lee Revell <[EMAIL PROTECTED]> wrote: > On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote: > > I also experiment sometimes a complete hang of the system. But I > > didn't find how to reproduce the bug yet, especially because it seems > > to happen when I do nothing (when I'm sleeping or am at work ;), and I > > can't get a Oops because I don't have any serial console... > > You could try netconsole... Good point... I just tried, but forcedeth doesn't support netpoll. If you have a pointer, I could try to implement it ;-) -- Julien - 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: How's the nforce4 support in Linux?
On Fri, 25 Mar 2005 18:21:42 -0500, Lee Revell <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
> > Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
> > Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
> > Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
> > Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
> > DriveReady SeekComplete DataRequest }
> > Mar 25 22:42:55 evenflow kernel:
> > Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> > Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
> > Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
> > Mar 25 22:42:55 evenflow kernel:
> > Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
> > Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
> > Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
>
> Are you sure the drive is OK? Those messages are the classic signs of a
> failing drive...
It's nearly new, and it was ok in my last computer (an old P3-500 with
PIIX4, IIRC).
BTW I did a complete badblocks check on it, and it found nothing.
--
Julien
-
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: How's the nforce4 support in Linux?
Hi
Just to answer some questions :
- USB works ok since 2.6.11
- audio works too. The only problem is that two applications can't
open /dev/dsp in the same time.
- network works
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Of course, if I disable DMA with hdparm, this problem disappear.. but
it isn't a long-term solution ;-)
Using vanilla 2.6.11.5 kernel. I attached the config file.
I also experiment sometimes a complete hang of the system. But I
didn't find how to reproduce the bug yet, especially because it seems
to happen when I do nothing (when I'm sleeping or am at work ;), and I
can't get a Oops because I don't have any serial console...
Kind regards,
--
Julien Wajsberg
config-2.6.11.5
Description: Binary data
Re: How's the nforce4 support in Linux?
Hi
Just to answer some questions :
- USB works ok since 2.6.11
- audio works too. The only problem is that two applications can't
open /dev/dsp in the same time.
- network works
I own an Asus A8N-Sli motherboard with the Nforce4-Sli chipset, and I
experiment the following problem :
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Of course, if I disable DMA with hdparm, this problem disappear.. but
it isn't a long-term solution ;-)
Using vanilla 2.6.11.5 kernel. I attached the config file.
I also experiment sometimes a complete hang of the system. But I
didn't find how to reproduce the bug yet, especially because it seems
to happen when I do nothing (when I'm sleeping or am at work ;), and I
can't get a Oops because I don't have any serial console...
Kind regards,
--
Julien Wajsberg
config-2.6.11.5
Description: Binary data
Re: How's the nforce4 support in Linux?
On Fri, 25 Mar 2005 18:21:42 -0500, Lee Revell [EMAIL PROTECTED] wrote:
On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote:
Mar 25 22:42:55 evenflow kernel: hda: dma_timer_expiry: dma status == 0x60
Mar 25 22:42:55 evenflow kernel: hda: DMA timeout retry
Mar 25 22:42:55 evenflow kernel: hda: timeout waiting for DMA
Mar 25 22:42:55 evenflow kernel: hda: status error: status=0x58 {
DriveReady SeekComplete DataRequest }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Mar 25 22:42:55 evenflow kernel: hda: status timeout: status=0xd0 { Busy }
Mar 25 22:42:55 evenflow kernel:
Mar 25 22:42:55 evenflow kernel: ide: failed opcode was: unknown
Mar 25 22:42:55 evenflow kernel: hdb: DMA disabled
Mar 25 22:42:55 evenflow kernel: hda: drive not ready for command
Are you sure the drive is OK? Those messages are the classic signs of a
failing drive...
It's nearly new, and it was ok in my last computer (an old P3-500 with
PIIX4, IIRC).
BTW I did a complete badblocks check on it, and it found nothing.
--
Julien
-
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: How's the nforce4 support in Linux?
On Fri, 25 Mar 2005 18:20:54 -0500, Lee Revell [EMAIL PROTECTED] wrote: On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote: I also experiment sometimes a complete hang of the system. But I didn't find how to reproduce the bug yet, especially because it seems to happen when I do nothing (when I'm sleeping or am at work ;), and I can't get a Oops because I don't have any serial console... You could try netconsole... Good point... I just tried, but forcedeth doesn't support netpoll. If you have a pointer, I could try to implement it ;-) -- Julien - 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: How's the nforce4 support in Linux?
On Fri, 25 Mar 2005 18:14:22 -0500, Lee Revell [EMAIL PROTECTED] wrote: On Fri, 2005-03-25 at 23:59 +0100, Julien Wajsberg wrote: - audio works too. The only problem is that two applications can't open /dev/dsp in the same time. Not a problem. ALSA does software mixing for chipsets that can't do it in hardware. Google for dmix. However this doesn't (and can't be made to) work with the in-kernel OSS emulation (it works fine with the alsa-lib/libaoss emulation). So you are technically correct in that two OSS apps can't open /dev/dsp at the same time, but there is no problem with multiple apps sharing the sound device, as long as they use the ALSA API (which they should be using anyway). Okay, good to know. Then I'll have to find out why beep-media-player doesn't work with alsa :-) -- Julien - 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/
