On Wed, Feb 14, 2001 at 02:51:03AM -0500, Shawn Starr wrote:
>
> hmmm this is my chipset:
>
> Which motherboard do you have?
No clue, it's an old p166, and I'm not about to open up the case..
>
> 00:00.0 Host bridge: Intel Corporation 430HX - 82439HX TXC [Triton II] (rev 03)
> 00:07.0 ISA
On Wed, Feb 14, 2001 at 02:51:03AM -0500, Shawn Starr wrote:
hmmm this is my chipset:
Which motherboard do you have?
No clue, it's an old p166, and I'm not about to open up the case..
00:00.0 Host bridge: Intel Corporation 430HX - 82439HX TXC [Triton II] (rev 03)
00:07.0 ISA bridge:
I have a box w/ the following controllers:
00:00.0 Host bridge: Intel Corporation 430HX - 82439HX TXC [Triton II] (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
00:07.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
I
I have a box w/ the following controllers:
00:00.0 Host bridge: Intel Corporation 430HX - 82439HX TXC [Triton II] (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] (rev 01)
00:07.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
I
As the subject states, w/ 2.4.2-pre3, whenever something starts doing
heavy i/o (most notably mozilla during startup, diff, recursive greps,
etc), it drops into 'D' state:
343 ?S 0:00 /bin/sh /usr/local/src/mozilla/dist/bin/run-mozilla.sh
As the subject states, w/ 2.4.2-pre3, whenever something starts doing
heavy i/o (most notably mozilla during startup, diff, recursive greps,
etc), it drops into 'D' state:
343 ?S 0:00 /bin/sh /usr/local/src/mozilla/dist/bin/run-mozilla.sh
I'm running it now, looks good. :)
On Fri, Feb 09, 2001 at 11:51:48AM -0500, Zach Brown wrote:
>
> > The maestro3 driver, included in 2.4.2-pre2 (which I assume is the
> > same as maestro3-2.4-20010204.tar.gz, I haven't bothered to try it;
> > I'm perfectly happy w/ my patch), oopses upon
I'm running it now, looks good. :)
On Fri, Feb 09, 2001 at 11:51:48AM -0500, Zach Brown wrote:
The maestro3 driver, included in 2.4.2-pre2 (which I assume is the
same as maestro3-2.4-20010204.tar.gz, I haven't bothered to try it;
I'm perfectly happy w/ my patch), oopses upon shutdown.
The maestro3 driver, included in 2.4.2-pre2 (which I assume is the
same as maestro3-2.4-20010204.tar.gz, I haven't bothered to try it;
I'm perfectly happy w/ my patch), oopses upon shutdown.
I'm submitting my patch again, both to the maestro3 maintainer,
and to lk this time; please see fit to
The maestro3 driver, included in 2.4.2-pre2 (which I assume is the
same as maestro3-2.4-20010204.tar.gz, I haven't bothered to try it;
I'm perfectly happy w/ my patch), oopses upon shutdown.
I'm submitting my patch again, both to the maestro3 maintainer,
and to lk this time; please see fit to
A few minutes ago, I got the following:
Feb 3 13:09:10 pea kernel: UDP: short packet: 0/58
.. and the driver hung. I had to reinsert the card to get
networking back. This is after 10 hours of uptime, using
the patch i sent previously against 2.4.1's xirc2ps_cs.
So the answer is, yes, it
A few minutes ago, I got the following:
Feb 3 13:09:10 pea kernel: UDP: short packet: 0/58
.. and the driver hung. I had to reinsert the card to get
networking back. This is after 10 hours of uptime, using
the patch i sent previously against 2.4.1's xirc2ps_cs.
So the answer is, yes, it
I downloaded the pcmcia-cs 3.1.24 package and hand-merged the bugfix(es?)
into 2.4.1's xirc2ps_cs.c. A(n attempt at a) patch to bring 2.4.1
up to pcmcia-cs's version is attached to this email. So far, no
problems, but it'll be at least 48 hours before I can say whether
it happens or not.. This
My logs show the following:
xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh)
eth0: Xircom: port 0x300, irq 3, hwaddr 00:80:C7:1E:28:2A
eth0: MII link partner: 0021
eth0: MII selected
eth0: media 10BaseT, silicon revision 4
UDP: short packet: 137/58
NETDEV WATCHDOG: eth0: transmit timed out
My logs show the following:
xirc2ps_cs.c 1.31 1998/12/09 19:32:55 (dd9jn+kvh)
eth0: Xircom: port 0x300, irq 3, hwaddr 00:80:C7:1E:28:2A
eth0: MII link partner: 0021
eth0: MII selected
eth0: media 10BaseT, silicon revision 4
UDP: short packet: 137/58
NETDEV WATCHDOG: eth0: transmit timed out
I downloaded the pcmcia-cs 3.1.24 package and hand-merged the bugfix(es?)
into 2.4.1's xirc2ps_cs.c. A(n attempt at a) patch to bring 2.4.1
up to pcmcia-cs's version is attached to this email. So far, no
problems, but it'll be at least 48 hours before I can say whether
it happens or not.. This
16 matches
Mail list logo
