Re: still panic

On Sun, 19 Oct 2003, Dikshie wrote: > > cvsup'd 19 Oct 2003 in the morning (jakarta time), > > > uname -a > FreeBSD ipv6.ppk.itb.ac.id 5.1-CURRENT FreeBSD 5.1-CURRENT #3: Sun Oct 19 21:25: > 57 WIT 2003 root@:/usr/obj/usr/src/sys/PPK i386 > > Fatal trap 12: page fault while in kernel mode >

still panic

cvsup'd 19 Oct 2003 in the morning (jakarta time), > uname -a FreeBSD ipv6.ppk.itb.ac.id 5.1-CURRENT FreeBSD 5.1-CURRENT #3: Sun Oct 19 21:25: 57 WIT 2003 root@:/usr/obj/usr/src/sys/PPK i386 Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdeadc0de fault code

Re: dc and PCMCIA still panic

In message: <[EMAIL PROTECTED]> Chan Tur Wei <[EMAIL PROTECTED]> writes: : Testing for the condition avoids the fault but leaves the card unusable : under -newcard. : : == : --- pccard_cis.c Tue Oct 8 13:04:34 2

Re: dc and PCMCIA still panic

c: [EMAIL PROTECTED] > Subject: Re: dc and PCMCIA still panic > > In message: <[EMAIL PROTECTED]> > Mikhail Teterin <[EMAIL PROTECTED]> writes: > : > Even though it doesn't make sense, can you turn on the debugging > : > informatio

Re: dc and PCMCIA still panic

In message: <[EMAIL PROTECTED]> Mikhail Teterin <[EMAIL PROTECTED]> writes: : > Even though it doesn't make sense, can you turn on the debugging : > information and run again? I use : > : > # Let's debug! : > hw.cbb.debug=1 : > hw.pccard.debug=1 : > hw.pccard.cis_debug=1 : > hw.card

Re: dc and PCMCIA still panic

> Even though it doesn't make sense, can you turn on the debugging > information and run again? I use > > # Let's debug! > hw.cbb.debug=1 > hw.pccard.debug=1 > hw.pccard.cis_debug=1 > hw.cardbus.debug=1 > hw.cardbus.cis_debug=1 Actually, I lied... It is a Xircom RealPort Ethernet 10/100 + Mode

Re: dc and PCMCIA still panic

Even though it doesn't make sense, can you turn on the debugging information and run again? I use # Let's debug! hw.cbb.debug=1 hw.pccard.debug=1 hw.pccard.cis_debug=1 hw.cardbus.debug=1 hw.cardbus.cis_debug=1 Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-cur

Re: dc and PCMCIA still panic

In message: <[EMAIL PROTECTED]> Mikhail Teterin <[EMAIL PROTECTED]> writes: : Today's kernel (cvs update-ed 10 minutes ago) keeps panicing when the : dc-card is inserted :-/ : : The panic always happens in : : Fatal trap 12 : [...] : db> trace : pccard_sca

dc and PCMCIA still panic

Today's kernel (cvs update-ed 10 minutes ago) keeps panicing when the dc-card is inserted :-/ The panic always happens in Fatal trap 12 [...] db> trace pccard_scan_cis([data],0,0) at pccard_scan_cis+0x1a5 pccard_read_cis([data]) at pccard_read_cis+0xb5

Re: Still panic() with userland binary on CURRENT

John Baldwin <[EMAIL PROTECTED]> writes: > On 24-Nov-01 Martin Blapp wrote: > > - realitexpire, td); > > + realitexpire, td->td_proc); > > > > Fixes the panic 100%. > Ouch, something this simple definitely caused a warning, it looks > like warnings are being ig

Re: Still panic() with userland binary on CURRENT

On 26-Nov-01 Garrett Wollman wrote: > < > said: > >>> - realitexpire, td); >>> + realitexpire, td->td_proc); > >> Ouch, something this simple definitely caused a warning, it looks like >> warnings >> are being ignored. :( > > Nope. Look at the prototype for

Re: Still panic() with userland binary on CURRENT

< said: >> - realitexpire, td); >> + realitexpire, td->td_proc); > Ouch, something this simple definitely caused a warning, it looks like warnings > are being ignored. :( Nope. Look at the prototype for callout_reset() and then think about why the last two p

Re: Still panic() with userland binary on CURRENT

On 24-Nov-01 Martin Blapp wrote: > > Hi DES, > > - realitexpire, td); > + realitexpire, td->td_proc); > > Fixes the panic 100%. > > Thanks a lot ! > > Martin Ouch, something this simple definitely caused a warning, it looks like warnings are being ignored

Re: Still panic() with userland binary on CURRENT

Hi DES, - realitexpire, td); + realitexpire, td->td_proc); Fixes the panic 100%. Thanks a lot ! Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Still panic() with userland binary on CURRENT

Martin Blapp <[EMAIL PROTECTED]> writes: > kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x123423bd > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc024d74a > stack pointer

Still panic() with userland binary on CURRENT

Hi DES, John, It does not lock the box completly, but it still panics. Sorry. DDB over serial connection: #./unilockd lock order reversal 1st 0xc04a8e80 sched lock @ /usr/src/sys/kern/kern_mutex.c:319 2nd 0xc049d8a0 sio @ /usr/src/sys/dev/sio/sio.c:2958 kernel trap 12 with interrupts disabl