5.0-20000917 Snapshot and Gericom Notebook - bad crash
Hello freebsd-current! The loader or the kernel crashed badly on my Gericom Overdose II notebook. I was trying to boot from the bootdisk-set. The mfsroot image is successfuly loaded and the "bootcountdown" ist displayed. After that it looks like there are some cpu-registers dumped. unfortunalty everything scrolls too fast, i cannot really read anything. It any aditional information is needed, please contact me. Regards, Oliver -- And remember: "To Infinity And Far Beyond ... Somehow?!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvsup on recent -CURRENT
Eines schoenen Tages schrieb Ted Sikora: Christian Weisgerber wrote: On this machine which runs -CURRENT from two days ago or so, I'm seeing frequent cvsup client failures of this type: TreeList failed: Network write failure: Connection closed I don't recall ever running into this before. Same here. Last night was okay. It started about 5 days ago. If you just start over it usually finishes okay. Same thing here, but much earlier. It seemed that TCP/IP ist (was?) broken on my machine. Downgraded to -STABLE, machine worked fine, up to -STABLE of last monday. I have the feeling, something in the delayed checksum calculations broke TCP/IP. unfortunalty i crashed the machine last night and still have recovery work to do, so i have no idea, if the bugs have been gone since the last commit of the vx driver. Btw ... not just cvsup showed strange behavior. Everthing dealing with TCP/IP seemed broken. 60% packet loss on ethernet is more than strange. But it seemed nobody else ws having this problem ... regards, oliver -- And remember: "To Infinity And Far Beyond ... Somehow?!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ed driver broken in today's -CURRENT?
Eines schoenen Tages schrieb Andrey A. Chernov: On Sun, May 07, 2000 at 06:44:39PM +0930, Greg Lehey wrote: I've just built a new kernel, based on a cvsup at 2030 UTC on 6 May, and since then *some* Ethernet transactions don't work. I've checked that it's not just a dead card: the previous kernel works fine. I have the funny situation that I can send fine, and I can traceroute to the box, but I can't ping. NFS also objects strenuously: It is not dead card, it is broken TCP, see my similar report in -current, I notice it several hours ago right after TCP changes was commited. Same thing here, but the problems have gone to -stabe too. due to a probable tcp breakage i downgraded my machine to 4.0-stable which worked pretty good. with sources as from may 5th kernel boots fine, but tcp seems broken too. I experience a 50% package loss on out home lan. udp seems broken badly. rpc calls and nfs stopped working. i am using the vx driver on a 3com 3c597 EISA board. network card is ok, packet filtering rules have not been altered since the last kernel version. is nobody else seeing this? any clues? regards, oliver -- And remember: "To Infinity And Far Beyond ... Somehow?!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ed driver broken in today's -CURRENT?
Eines schoenen Tages schrieb Oliver Schonefeld: [snip] It is not dead card, it is broken TCP, see my similar report in -current, I notice it several hours ago right after TCP changes was commited. Same thing here, but the problems have gone to -stabe too. due to a probable tcp breakage i downgraded my machine to 4.0-stable which worked pretty good. with sources as from may 5th kernel boots fine, but tcp seems broken too. I experience a 50% package loss on out home lan. udp seems broken badly. rpc calls and nfs stopped working. i am using the vx driver on a 3com 3c597 EISA board. network card is ok, packet filtering rules have not been altered since the last kernel version. is nobody else seeing this? any clues? kind of looks like a problem in the delayed checksum calculation. while having a cvsup running and doing some nfs testing with a linux box pinging killed the -stable machine. (no flood pinging, just a normal ping) also nfs to the linux box was just beyond beeing awefully slow ... not even creeping is the reight term. kernel output from crash: delayed m_pullup, m-len: 84 off: 61420 p: 1 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0197f14 stack pointer = 0x10:0xc8934e34 frame pointer = 0x10:0xc8934e60 code segemnt= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current procress= 213 (dnetc) interrupt mask = kernel: type 12, code=0 db trace ip_output(c0661e00,c8934ef4,c0661e00,c0661e4a,7) at ip_output+0xba0 ip_output(c0661e00,0,c8934ef4,14,0,0) at ip_output+0x5fb icmp_input(c0661e00,0) at icmp_input+0x716 icmp_input(c0661e00,c0661e00,fbdd809a,,40) at icmp_input+0x697 icmp_input(c0661e00,14,1,c0661e00,fbdd809a) at icmp_input+0x357 ip_input(c0661e00) at ip_input+0x780 ip_input(c01d7beb,0,2f,2f,2f) at ip_input+0x7df crashdump availabale on request. regards, oliver -- And remember: "To Infinity And Far Beyond ... Somehow?!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Serious Network Troubles (with vx driver?)
i recently updated my -current system from -current as of about mid-march to lest sundays's -current (jep, from 4.0 to 5.0) due to the work done to the ida driver. well, the ida driver seems to work, but the network hast complety stopped working. with sunday's -current, after about 2-5 minutes uptime i want not able to even ping machines on my local network. i cvsu'ed to tuesday's -current and pinging of machines some how worked. but resolving of hostname does not work properly. i added "options debug" to my /etc/resolv.conf and i get a lot of "server timeout" messages. after 3-6 failures i get an anwser. i know for sure, that the name servers are ok and i can also ping them, so it must have to do with my system. well, also all tcp/ip connections fail. cvsup failes with a connection timeout and connecting with ssh fails also with the same message. netstat -i shows nothing unusual (no tx/rx errors) and netstat -a shows just an "ESTABLISHED" and the rx/tq queues are empty. i have the bad feeling something is broke with the vx driver, since no one else is having such problems. any suggestions? any ideas? the machine is a compaq prosignia 486 _eisa only_, the boards are 3com 3c597 eisa. the machine worked very well and stable under 4.0 -current. northing unusual is shown, when booting the 5.0 -current kernel and all hardware is detected normally. unfortunalty i am not having a dmesg output here, since i am not home. i am currently building world cvsup'ed as of 7:20 GMT+1 and will see, what happens but i have the bad feeling my network will still be broken ... regards, oliver -- And remember: "To Infinity And Far Beyond ... Somehow?!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Network Trouble II - kernel panic
well, after cvsup'ing and building of the world, the network seems to work a litte better. but under faily heavy load (flood pinging _form_ the host and floodpint _to_ the host) results in a trap 12. seem that actually the heavy output kills the machine. Fatal trap 12: page fault while in kernel mode faul virtual address= 0x8 fault code = supervisor read, page not present instruction pointer = 0x8:0xc019d05c stack pointer = 0x10:0xc8967ce4 frame pointer = 0x10:0xc8967d10 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 266 (ping) interrupt mask = kernel: type 12 trap, code=0 Stopped at in_delayed_cksum+0x64: mov 0x8(%ebx),%eax db trace in_delayed_cksum(c0662800,c8967da4,c0662800,c066284a,c016bb24) at in_delayed_cksum+0x64 ip_output(c0662800,0) at icmp_send+0x62 icmp_refelct(c0662800,c0662800,40,,40) at icmp_refelct+0x203 icmp_input(c0662800,14,1,c0662800,40) at icmp_input+0x357 ip_input(c0662800) at ip_input+0x780 ipintr(c01da3ff,0,10,10,10) at ipintr+0x4b swi_net_next(c895cac0,6,c8967f10,0,807c2a0) at swi_new_next sendto(c895cac0,c8967f80,40,807c2a,32a) at sendto+0x4d syscall2(2f,2f,2f,32a,807c2a0) at syscall2+0x1f1 Xint0x80_syscall() at Xint0x80_syscall+0x26 regards, oliver -- And remember: "To Infinity And Far Beyond ... Somehow?!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/dev/ida ida_eisa.c
hello! all right ... things take longer then we expect them to take. the kernel (everything cvsup'd on saturday) boot fine and the array controller is detected just perfect. also fdisk'ing, disklabel'ing and newfs'ing the drive was no problem. i copied almost the whole current source tree on the drive ... no problem. even a simulated diskfail was no problem. but it looks like the driver is taking much system time. while coping the files a hat a system load of almost 40%, irq and user was much less. i then i ran into bog trouble. it seems that the something the the network drivers is broken ... but that has propably not much to do with the ida driver ... Eines schoenen Tages schrieb Viren R.Shah: mainboard0: CPQ1519 (System Board) on eisa0 slot 0 eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 ida0: Compaq SMART array controller at 0x6000-0x60ff, 0x6c88-0x6c9e ida0: irq 15 (level) on eisa0 slot 6 ida0: drives=1 firm_rev=1.66 i am running 2.26 on that board. maybe you should upgrade regards, oliver -- And remember: "To Infinity And Far Beyond ... Somehow?!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/dev/ida ida_eisa.c
hello! [snipped-a-lot] i am currently building world and will be testing the driver. in about 4 - 5 hours (it's not the fastet machine ;-) i will be able to send feedback ... cheers, oliver -- "Mein Gott, es ist voller Sterne!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Compaq SMART EISA and ida driver - kernel panic
Eines schoenen Tages schrieb Matthew N. Dodd:
[snip]
Could you add
printf("0x%lx\n0x%lx0x%lx\n", qcb, completed, qcb_done);
to ida.c:ida_wait() after this line:
454:qcb_done = idahwqcbptov(ida, completed ~3);
And show us the output.
there we go:
qcb = 0xc0ca7000
completed = 0x (so propably not initalized?!)
qcb_done = 0x0
cheers,
oliver
--
And remember: "To Infinity And Far Beyond ... Somehow?!"
email: [EMAIL PROTECTED]
[EMAIL PROTECTED]
Hi! I'm a .signature virus! Copy me in your ~/.signature
to help me spread! - Save this lifeform ;-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Compaq SMART EISA and ida driver - kernel panic
Eines schoenen Tages schrieb Matthew N. Dodd: [snip] Doh! Looks like Jonathan didn't merge the latest ida_eisa.c that I'd worked on when he fixed the driver to support multiple access methods and added EISA support. Try this patch: [snip] hmm ... the controller shows up with another io-adress, but now the driver panics because of a time out :-( kernel msgs: ida0: Compaq SMART array controller at 0x4000-0x40ff, 0x4c88-0x4c9e ida0: irq 15 (level) on eisa0 slot 4 panic: ida_wait: timeout waiting for completion kernel debugger: ida_wait(c0ca5d00,c0ca7000,1f4,c0ca5d00,0) at ida_wait+0x43 ida_command(c0ca5d00,11,c029eeb4,9,0,1,c0ca5d00,0) at ida_command+0xf8 ida_attach(c0ca5d00,c0ca4c80,c0ca4f00,0,c0ca5d00) at ida_attach+0x28 ida_eisa_attach(c0ca4c80,c029ef08,c0156223,c0ca4c80,c0ca4c80) at ida_eisa_attach+0x187 DEVICE_ATTACH(c0ca4c80,c0ca4c80,c0ca2000,0,c029ef18) at DEVICE_ATTACH+0x2e regards, oliver -- And remember: "To Infinity And Far Beyond ... Somehow?!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Compaq SMART EISA and ida driver - kernel panic
Eines schoenen Tages schrieb Matthew N. Dodd: On Tue, 14 Mar 2000, Oliver Schonefeld wrote: hmm ... the controller shows up with another io-adress, but now the driver panics because of a time out :-( Try this patch: [snip] again, no success. the driver counts down the timeout with the same result as before. stragne thing, after i applied you first patch (setting the other io-adress) the machine would not reboot after the panic. a "call boot()" would also hang the machine. i had to hard-reset that thing. that's all i can observe right now. if you need more informations, please let me know. regards, oliver -- And remember: "To Infinity And Far Beyond ... Somehow?!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Compaq SMART EISA and ida driver - kernel panic
hello *!
i was very happy to se, that the eisa bus attachment stuff had been reviewed
and comitted to the source tree. the kernel compiles w/o problems but
panics, when booting :-(
has anybody with an eisa board have had success (maybe my setup is somehow
wrong?!)
relevent kernel messages:
ahb0: Adaptec 174x SCSI host adapter at 0x3c00-0x3cff, irq 12 (edge)
ahb0: on eisa0 slot 3
ahb0: AHA1740A Single Ended SCSI Adapter, FW Rev. E, ID=7, 64 ECBs
ida0: Compaq SMART array controller at 0x4c88-0x4c9e, irq 15 (level)
ida0: on eisa0 slot 4
panic: ida_wait: incorrect qcb returned
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.372
"trace" in the kernel debugger returnes following output:
panic(c01f7520,c0ca7000,c0ca5d00,,c029ee84) at panic+0xf8
ida_wait(c0ca5d00,c0ca7000,1f4,c0ca5d00,0) at ida_wait+0x75
ida_command(c0ca5d00,11,c029eeb4,9,0,1,c0ca5d00,0) at ida_command+0xf8
ida_attach(c0ca5d00,c0ca4c80,c0ca4f00,0,c0ca5d00) at ida_attach+0x28
ida_eisa_attach(c0ca4c80,c029ef08,c01561fb,c0ca4c80,c0ca4c80) at
ida_eisa_attach+0x187
DEVICE_ATTACH(c0ca4c80,c0ca4c80,c0ca2000,0,c029ef18) at DEVICE_ATTACH+0x2e
[some more, but i think, that was the importtant part, since the adaptec
board ist probed and initialized correclty]
unfortunaly no core dump available.
information on machine:
compaq prosignia 486 w/pentium overdrive (bios version as from 09/25/97)
os set to "UNIX/XENIX"
1x compaq smart array controller (firmware revision 2.26)
os set to "UNIX/XENIX"
one logical volume:
2x quantum fireball 1.08GB (drive mirroring)
setup via compaq system configuration utility (did i miss something?)
1x adaptec 1740
1x adaptec 2742 (floppy controller disabled)
2x 3com 3c597 NICs
without the driver the machine runs just rock solid (lacking a raid, of
course). so something must be wrong, when probing for the controller.
any ideas?
if more information is needed, i will try to provide them,
cheers,
oliver
--
email: [EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ifq_maxlen in vx-driver
hello *! i am using the vx driver in for my two 3c397 boards. when booting i get the following message: vx0 XXX: driver didn't set ifq_maxlen obviosly the ifq_maxlen is not set in the eisa nor in the pci version in the driver. actually, to set this, would be one line in the driver, but unfrotunatly i am not that familiar with the hardware, and do not know, which value this parameter shoul have. maybe, someone knows ... cheers, oliver -- And remember: "Life sucks and then you die!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ida driver in -current and eisa bus attachment
Eines schoenen Tages schrieb Warner Losh: : Someone thought that tm_year was the last two digits of the year : rather than year - 1900. : : Is ELM [version 2.4 PL25 PGP6] that much broken? Looks that way... just compiled elm 2.5.2 ... looks to me, that is fixes my "problem" ... but elm is not really a problem on my bsd box, since this mail is written from an account in my university .. they are running sunos ... -- And remember: "Life sucks and then you die!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ida driver in -current and eisa bus attachment
Eines schoenen Tages schrieb Andre Oppermann: Warner Losh wrote: In message [EMAIL PROTECTED] Andre Oppermann writes: : Sat, 1 Jan 100 17:16:30 +0100 (MET) : Oliver, how old is your PC? it's not a pc ... it's a sun ultra 1 ... and unfortunatly it's not mine. it belongs to my university :-(( Is ELM [version 2.4 PL25 PGP6] that much broken? yes ... my elm is propably broken :-) maybe i should consider using mutt or something else ... nut that does not really solve the problem with the compaq array controller ... -- And remember: "Life sucks and then you die!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ida driver in -current and eisa bus attachment
i wonder what is happening to the ida driver for comapq's smart array controller series. Work on this driver is stalled owing to the fact that nobody that can and wants to work on it has access to the Compaq hardware required. You can't use these controllers except in Compaq systems, which makes things very difficult. that's true :-( If someone has a complete system featuring one or more of these controllers (a mixed PCI/EISA system would be best), there are several people that could put it to good use. well, as you meight have guesses, i own one of these nice little compaq servers. unfortunatly it is an eisa-only version. the good thing is i own two compaq smart array controllers (right now, one is in the machine) and the computer is accessible via internet. for people willing to develop the drivers, i offer access to this machine since i doubt there are any developters living in my town and sending the server to the states is no option. -- And remember: "Life sucks and then you die!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ida driver in -current and eisa bus attachment
i wonder what is happening to the ida driver for comapq's smart array controller series. people say the pci version works but the eisa version is not. in the ida.c file is says: * Specific probe routines are in: * pci/ida_pci.c * i386/eisa/ida_eisa.c but unfortunatly the ida_eisa.c file seems to be missing in the source tree (i just cvsuped the whole thing). i did some research at deja and found out, that matthew dodd wrote the eisa bus attachment and it is downloadabe on his ftp site. unfortunatly (again) the eisa_add_intr() routine has changed and needs an additional argument (which happend to be the irq-trigger). i added EISA_TRIGGER_LEVEL to that call (level is what the controller uses according to the compaq bios). the kernel compiles but crashes with a trap 12 when probing ida0. it crashed in the ida_wait() routine in ida.c while initially trying to attach the board. i wonder if anybody else hat such problems and (that would be even better) has solved them. i am willing to help in developting this driver but my knowlegde of c is bad and my kernel programming excperiences are even worse ... :-( anyways, i hope somebody out there is still working on that thing, regards, oliver -- And remember: "Life sucks and then you die!" email: [EMAIL PROTECTED] [EMAIL PROTECTED] Hi! I'm a .signature virus! Copy me in your ~/.signature to help me spread! - Save this lifeform ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
