Re: 2Re: panic: found dirty cache page 0xf046f1c0
As Alfred Perlstein wrote... On Sat, 23 Jan 1999, Matthew Dillon wrote: i have 'ed' driver and mine blows up as well. :Here too... pretty quickly after boot on a SMP machine (current as of Jan :12) that pushes quite a bit of traffic, the following messages appear: : :de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) :de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) :de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) I have seen these messages on both Freebsd/x86 and /axp with single CPU machines. Almost all of them disappeared when I started using decent UTP cabling. Believe it or not. So, I'd say the messages are not linked to SMP at all. : :de0: Digital 21140A Fast Ethernet rev 0x22 int a irq 16 on pci0.12.0 :de0: 21140A [10-100Mb/s] pass 2.2 :de0: address 00:c0:f0:1f:5d:0d :de0: enabling Full Duplex 100baseTX port Three people getting these panics, three people with DEC ethernet cards. Random complaints about card during ifconfig: speaker goes click, console gets junked, etc etc etc. s there anyone having this panic who does NOT have a DEC ethernet card ? Wilko _ __ | / o / / _ Bulteemail: wi...@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl __ Powered by FreeBSD __ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 2Re: panic: found dirty cache page 0xf046f1c0
: :i have 'ed' driver and mine blows up as well. : :panic: found dirty cache page 0xf047ae60 :Debugger(panic) Ok, so much for if_de being the cause. BTW, for anybody who doesn't want to wait for us to find the bug, you can comment out the MADV_FREE code and that should put a stop to it. The MADV_FREE code isn't broken, but it seems to cause the bug to occur which is why *I* haven't commented it out - I'd rather find the bug. Also, update your kernel trees and turn on the INVARIANTS options: options INVARIANTS options INVARIANT_SUPPORT -Matt Matthew Dillon dil...@backplane.com : :btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and :i'm running X and doing a 'make release' : :Is it safe to enable crashdumps on IDE disks yet? : :-Alfred I don't know. I wasn't aware that there was a problem with crash dumps on ide disks. There shouldn't be. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 2Re: panic: found dirty cache page 0xf046f1c0
On Sat, 23 Jan 1999, Matthew Dillon wrote: : :i have 'ed' driver and mine blows up as well. : :panic: found dirty cache page 0xf047ae60 :Debugger(panic) Ok, so much for if_de being the cause. BTW, for anybody who doesn't want to wait for us to find the bug, you can comment out the MADV_FREE code and that should put a stop to it. The MADV_FREE code isn't broken, but it seems to cause the bug to occur which is why *I* haven't commented it out - I'd rather find the bug. Also, update your kernel trees and turn on the INVARIANTS options: options INVARIANTS options INVARIANT_SUPPORT cvsup'd and added, i'm going to run the code for a bit hopefully to get you some output from the INVARIANTS. :Is it safe to enable crashdumps on IDE disks yet? I don't know. I wasn't aware that there was a problem with crash dumps on ide disks. There shouldn't be. Last 3 times i enabled it, it dumped on the wrong partition because it got confused about LBA mode, anyone have a suggestion to test to make sure it won't dump on my /usr instead of swap? (i don't have LBA enabled in my IDE disk flags 0xe0ffe0ff) -Alfred To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 2Re: panic: found dirty cache page 0xf046f1c0
On Sat, 23 Jan 1999, Matthew Dillon wrote: : :i have 'ed' driver and mine blows up as well. : :panic: found dirty cache page 0xf047ae60 :Debugger(panic) Ok, so much for if_de being the cause. BTW, for anybody who doesn't want to wait for us to find the bug, you can comment out the MADV_FREE code and that should put a stop to it. The MADV_FREE code isn't broken, but it seems to cause the bug to occur which is why *I* haven't commented it out - I'd rather find the bug. Also, update your kernel trees and turn on the INVARIANTS options: options INVARIANTS options INVARIANT_SUPPORT -Matt Matthew Dillon dil...@backplane.com : :btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and :i'm running X and doing a 'make release' : :Is it safe to enable crashdumps on IDE disks yet? : :-Alfred I don't know. I wasn't aware that there was a problem with crash dumps on ide disks. There shouldn't be. Crashdumps on IDE disks never stopped working for me. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 2Re: panic: found dirty cache page 0xf046f1c0
On Sat, Jan 23, 1999 at 06:51:54PM -0800, Matthew Dillon wrote: : :btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and :i'm running X and doing a 'make release' : :Is it safe to enable crashdumps on IDE disks yet? : :-Alfred I don't know. I wasn't aware that there was a problem with crash dumps on ide disks. There shouldn't be. FWIW, I've had crash dumps enabled on my IDE-based system for a long time, and never had a problem with them. -- ++ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| |lcrem...@tidalwave.net| http://st-lcremean.tidalwave.net/~lee | To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: 2Re: panic: found dirty cache page 0xf046f1c0
On Sun, 24 Jan 1999, Brian Feldman wrote: :btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and :i'm running X and doing a 'make release' : :Is it safe to enable crashdumps on IDE disks yet? : :-Alfred I don't know. I wasn't aware that there was a problem with crash dumps on ide disks. There shouldn't be. Crashdumps on IDE disks never stopped working for me. gee, that's nice to know. Brian, search the -current lists about this, there was/is some confusion in the driver about LBA. Basically, LBA would work at ALL times for the disk, except during a crash dump where it would use those addresses as CHS or something and cream one of my partitions. This lovely affected 2 seperate machines. -Alfred To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
