panic: kern/52718
Is anyone going to look at this before the next release? Of course, if more info is needed, I'll send it along. No dump is available - it panics during boot. http://www.freebsd.org/cgi/query-pr.cgi?pr=52718 Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: kern/52718
Just out of curosity... I had this same error a while back on one of my boxes. I ended up booting to a recovery cd and running an fsck_ffs on it and it fixed the problem. Mine would get to a login and *WHAM* it's dead. Worth a shot to see if that fixes your problem or not Regards, Nick H. Network Operations Center Hosting Support Intl. [EMAIL PROTECTED] Please rate my performance! http://www.supportteam.net/rate.php3 Please submit all new support requests to http://ticketmonster.hostingsupport.com/ --- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it. - Original Message - From: Bryan Liesner [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 29, 2003 3:49 PM Subject: panic: kern/52718 : : Is anyone going to look at this before the next release? : Of course, if more info is needed, I'll send it along. No dump is : available - it panics during boot. : : http://www.freebsd.org/cgi/query-pr.cgi?pr=52718 : : Thanks : ___ : [EMAIL PROTECTED] mailing list : http://lists.freebsd.org/mailman/listinfo/freebsd-current : To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: kern/52718
without the correct keywords in your mail, it's unlikely either the CAM or Mutex people would see it before then On Thu, 29 May 2003, Bryan Liesner wrote: Is anyone going to look at this before the next release? Of course, if more info is needed, I'll send it along. No dump is available - it panics during boot. http://www.freebsd.org/cgi/query-pr.cgi?pr=52718 Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: kern/52718
On Thu, 29 May 2003, Julian Elischer wrote:
without the correct keywords in your mail, it's unlikely either
the CAM or Mutex people would see it before then
Here's a copy of my original mail, which was pretty much ignored, with
the exception of Terry Lambert. I feel that the subject was pretty
clear. If it wasn't clear enough, then I stand corrected.
Date: Mon, 26 May 2003 12:11:35 -0400 (EDT)
From: Bryan Liesner [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: panic since changes to kern_umtx.c
The change from kern_umtx.c rev 1.2 to 1.3 brought out the following
panic on my system. The panic does not occur if I revert back to 1.2
or if I turn off my USB hard drive (uses EHCI) and run with rev 1.3
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc0135b0a7
stack pointer = 0x10:0xd68f2c48
frame pointer = 0x10:0xd68f2c64
code segment = base 0x0 limit 0x, type 0x1b
processor eflags= interrupt enabled, resume, IOPL=0
current process = 12 (swi7: tty:sio clock)
trap number = 12
panic page fault
DDB says it was in heap_up+0x27
...
(kgdb) l *heap_up+0x27
0xc0136be7 is in heap_up (../../../cam/cam_queue.c:345).
340 * equal too, or greater than j respectively.
341 */
342 static __inline int
343 queue_cmp(cam_pinfo **queue_array, int i, int j)
344 {
345 if (queue_array[i]-priority == queue_array[j]-priority)
346 return ( queue_array[i]-generation
347 - queue_array[j]-generation );
348 else
349 return ( queue_array[i]-priority
(kgdb)
350 - queue_array[j]-priority );
351 }
352
353 /*
354 * swap: Given an array of cam_pinfo* elements and indexes i and j,
355 * exchange elements i and j.
356 */
357 static __inline void
358 swap(cam_pinfo **queue_array, int i, int j)
359 {
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: kern/52718
On Thu, 29 May 2003, Nick H. wrote: Just out of curosity... I had this same error a while back on one of my boxes. I ended up booting to a recovery cd and running an fsck_ffs on it and it fixed the problem. Mine would get to a login and *WHAM* it's dead. Worth a shot to see if that fixes your problem or not Tried that, and it still panics. Way before we get to a login, at the point where it starts to set up the disks... Thanks! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: kern/52718
Bryan Liesner wrote: Is anyone going to look at this before the next release? Of course, if more info is needed, I'll send it along. No dump is available - it panics during boot. http://www.freebsd.org/cgi/query-pr.cgi?pr=52718 This was caused by rev. 1.3 of a commit by Jeff Robertson to kern_utmx.c. The problem is that the proc struct is not locked for: FOREACH_THREAD_IN_PROC(td-td_proc, td0) in the lock and unlock. Either lock the proc before and unlock it after this, in both _utmx_lock() and _utmx_unlock(), or revert the code to 1.2. It's pretty simple. No one needs t look at it, all they need to do is act on information already present. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: kern/52718
- Original Message - From: Terry Lambert [EMAIL PROTECTED] To: Bryan Liesner [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, May 30, 2003 5:02 PM Subject: Re: panic: kern/52718 Bryan Liesner wrote: Is anyone going to look at this before the next release? Of course, if more info is needed, I'll send it along. No dump is available - it panics during boot. http://www.freebsd.org/cgi/query-pr.cgi?pr=52718 This was caused by rev. 1.3 of a commit by Jeff Robertson to kern_utmx.c. The problem is that the proc struct is not locked for: FOREACH_THREAD_IN_PROC(td-td_proc, td0) in the lock and unlock. Either lock the proc before and unlock it after this, in both _utmx_lock() and _utmx_unlock(), or revert the code to 1.2. It's pretty simple. No one needs t look at it, all they need to do is act on information already present. kern_sig.c has same issue in several places. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] David Xu ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: kern/52718
David Xu wrote: This was caused by rev. 1.3 of a commit by Jeff Robertson to kern_utmx.c. The problem is that the proc struct is not locked for: FOREACH_THREAD_IN_PROC(td-td_proc, td0) in the lock and unlock. Either lock the proc before and unlock it after this, in both _utmx_lock() and _utmx_unlock(), or revert the code to 1.2. kern_sig.c has same issue in several places. Just looked... YUCK! The Process group code and the code in the filt_sigdetach() have got to be what you are talking about, right? I'm constantly surprised at some of the race windows I find in production code (not just FreeBSD), that are just waiting there to chew someone's leg off the first chance they get... 8-(. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: kern/52718
- Original Message - From: Terry Lambert [EMAIL PROTECTED] To: David Xu [EMAIL PROTECTED] Cc: Bryan Liesner [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, May 30, 2003 5:27 PM Subject: Re: panic: kern/52718 David Xu wrote: This was caused by rev. 1.3 of a commit by Jeff Robertson to kern_utmx.c. The problem is that the proc struct is not locked for: FOREACH_THREAD_IN_PROC(td-td_proc, td0) in the lock and unlock. Either lock the proc before and unlock it after this, in both _utmx_lock() and _utmx_unlock(), or revert the code to 1.2. kern_sig.c has same issue in several places. Just looked... YUCK! The Process group code and the code in the filt_sigdetach() have got to be what you are talking about, right? Yes. :( I'm constantly surprised at some of the race windows I find in production code (not just FreeBSD), that are just waiting there to chew someone's leg off the first chance they get... 8-(. Welcome to fix it. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
