Re: My boss want to kill debian, please help !

From: George Alexandru Dragoi (waruiinu_at_gmail.com)
Date: 01/28/05

  • Next message: belahcene: "How to mirror a screem" 
    Date: Fri, 28 Jan 2005 18:26:20 +0200
To: Henrique de Moraes Holschuh <hmh@debian.org>

    Well, i used what you said, the 2.6.10 kernel from sid (i didn't find
    any 2.6.10-4, but i got 2.6.10, patched by debian team, and that is
    what i am using), 1 on board e1000, 2 new e1000 cards, and that crappy
    e100

    On Fri, 28 Jan 2005 13:05:03 -0200, Henrique de Moraes Holschuh
    <hmh@debian.org> wrote:
    > On Fri, 28 Jan 2005, George Alexandru Dragoi wrote:
    > > and everything got back to normal (guess how charming the tech manager
    > > has begun to talk about debian :( .
    > > this is the lspci line about that e100:
    >
    > Heh.
    >
    > Still, to make things clear. The *hardware* issue with e100 that I know off
    > causes the e100 PHY (not the machine. not the PCI bus. not even the entire
    > e100 board) to lock up. Nothing gets sent, nothing is received. The driver
    > resets the PHY after about 30s I think. It tells you that it thinks the
    > hardware bug is present, and displays something to the effect of "foo
    > workaround activated" on startup.
    >
    > Also, there's something else I should point out: the debian *stable* kernel
    > is too old (I won't say "crap", but it is certainly useless for what I need
    > it). Get the Debian kernel in testing or sid, after verifying that it is
    > currently sane (as of this writing, 2.6.10-4 and 2.4.27-8, both are sane).
    > Backporting policy is well and good, but it doesn't work for the kernel if
    > you are using non-ancient, non-stale hardware.
    >
    > The e100/e1000 drivers have had a *ton* of fixes in the latest revisions
    > (mostly due to new features such as NAPI, but...)
    >
    > My experiences with NICs tell me that you get about 1% chance of receiving a
    > bad one. I got a 3COM that would cause PCI busmaster errors during high
    > loads after a while, and a e100 that would hang the entire machine. But
    > they were defective parts, and would have hung FreeBSD just the same...
    >
    > --
    > "One disk to rule them all, One disk to find them. One disk to bring
    > them all and in the darkness grind them. In the Land of Redmond
    > where the shadows lie." -- The Silicon Valley Tarot
    > Henrique Holschuh
    > 

    -- 
Bla bla
-- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: belahcene: "How to mirror a screem"

    Relevant Pages

    • Re: My boss want to kill debian, please help !
      ... That might not change your kernel for all I know :-) I prefer to run sarge ... selected sid packages. ... and rerun a few scripts, which could reset firewalls, arp tables, etc. ... "One disk to rule them all, ...
      (Debian-User)
    • Re: Software RAID-5 attempt to access beyond end of device...
      ... The reiserfs is on top of an lvm2 on top of a raid5 ... >information that has previously been stored on disk. ... Sep 7 20:32:04 cu kernel: Buffer I/O error on device dm-0, ... PCI: PCI BIOS revision 2.10 entry at 0xf1150, ...
      (Linux-Kernel)
    • Re: Spontaneous reboots
      ... yet I keep experiencing spontaneous reboots and crashes. ... > I have postfix handling mail and use cyrus-imap with virtual ... Page fault while in kernel mode ... > Disk errors: ...
      (freebsd-questions)
    • athlon-xp + fakeraid regression
      ... The build completes fine, the kernel boots fine, the machine will seem to be fine as long as it remains quiescent. ... At the beginning, just after hitting enter on the make command, one of the ad4 disk light goes on solid for several seconds. ... There is a well known thing where these cheap pata fakeraid cards will try to do ata133 if the drive says it can, when really, even if he drives are new ata133 drives and the cables are new and short and shielded, you still shouldn't try to do ata133 since the spec is too tight and you'll just get bit errors or other failures. ... The fix is use ata100 somehow, either by disabling dma entirely in loader.conf (since you have no more selective option there, and the raid card bios never has an option for controlling pio/dma mode like motherboard bios's have) and then use atacontrol in rc.early to set udma5, or by using disks that can only do ata100 and only advertise ata100 to the controller. ...
      (freebsd-current)
    • Re: F8 k3b problem or just random glitch?
      ... I must have been thinking of the last dvd I burnt. ... led went out the last time and a what do we do with this new disk requester had ... but to me a file manager is a 2 pane operation ala mc. ... All this BTW with kernel 2.6.26-rc6 doing the chores. ...
      (Fedora)