Re: Help with panic: vm_fault
"N.J. Thomas" <[EMAIL PROTECTED]> writes: > * Brad Marsh <[EMAIL PROTECTED]> [2006-01-12 11:09:29 -0800]: > > or singly, not in pairs... > > This should never be the case. If your memory is acceptable one module > at a time, why wouldn't the system accept two? Capacitive loading, for one reason. Not common, but I've certainly seen it (particularly with lower-end machines a couple or so years back). And since different brands of memory modules will have different capacitances (and there may be some variation even among "identical" units), it may not be easy to reproduce. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help with panic: vm_fault
Thanks for the help...I booted the GENERIC kernel, and it allowed me to log in as root, but as soon as I started to to anything (I think I did "cd") it panicked. I'm going to run the memtest86 and see if it says anything. If you think it would be useful, I could do more debugging on the new vmcore file. Thanks again! --- Brad Marsh <[EMAIL PROTECTED]> wrote: > Date: Thu, 12 Jan 2006 14:58:23 -0800 (PST) > From: Brad Marsh <[EMAIL PROTECTED]> > Subject: Re: Help with panic: vm_fault > To: Mark Tinguely <[EMAIL PROTECTED]> > > > Does the Mainboard say that it can handle this amount > > of RAM? > > The manual for the motherboard says I can use up to two 1GB modules. > > (And I used to have two 256MB modules, so I know it can handle two at > a > time. Also, right now I'm using one 512 and one 256.) > > > Do you have 2 video cards, for example a built into the > > mainboard but disabled? > > Just the built-in video adapter. > > > Is this a GENERIC kernel or has it been modified? I see > > the compile directory is DEBUG, so I am guessing it > > could be a custom kernel. > > Yeah, I customized it first thing. Then after all this trouble I > built > a debug kernel and put the two modules in again so I'd have the debug > info. > > > > #17 0xc062b6bf in Xint0x80_syscall () at > > > ../../../i386/i386/exception.s:200 > > > #18 0x0033 in ?? () > > > Previous frame inner to this frame (corrupt stack?) > > > (kgdb) q > > > > Level 17 is wrong, because that is not a caller of > > pmap_change_wiring(). > > Maybe the stack frame got corrupted and the strange VA > > is another side effect of the corruption. > > > ...if this is not a GENERIC kernel, could you try > > boo[t]ing say the install CD to eliminate > > options in the kernel? > > Great idea. I kept the original GENERIC kernel around just for this > purpose. Back in a while... > > Thanks! > > P.S. I've been working toward testing with memtest86, but this > machine > doesn't have a floppy, the USB floppy isn't working (strangely enough > - > it used to), and I don't have any CDs at this office that the burner > can use! I'm having a lovely day. :^) __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help with panic: vm_fault
* Brad Marsh <[EMAIL PROTECTED]> [2006-01-12 11:09:29 -0800]: > OK...in agreement, I've read that memory modules will sometimes work > in pairs, not individually Older memory/systems used to only take memory that worked in pairs, newer ones shouldn't have that problem. In the worst case, it may accept a single module, but maybe not run as fast as it would with a pair. But my memory-fu isn't up to date, and perhaps someone could correct me. > or singly, not in pairs... This should never be the case. If your memory is acceptable one module at a time, why wouldn't the system accept two? Thomas -- N.J. Thomas [EMAIL PROTECTED] Etiamsi occiderit me, in ipso sperabo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help with panic: vm_fault
OK...in agreement, I've read that memory modules will sometimes work in pairs, not individually, or singly, not in pairs... Thanks! P.S. "Juraj", you're right. I'm sure FreeBSD can handle more than 1GB RAM - it's just my system. I was hoping someone could look at the debug info and say something helpful like "it's for sure your memory module hardware!". :^) --- "N.J. Thomas" <[EMAIL PROTECTED]> wrote: > > So my comclusion is that FreeBSD is having trouble booting with 2 > > 512MB RAM sticks. The BIOS recognizes the RAM ok > > Before you do anything else, I strongly recommend you put in both of > the new memory modules in and run memtest86+. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help with panic: vm_fault
* Brad Marsh <[EMAIL PROTECTED]> [2006-01-12 09:33:37 -0800]: > I removed both of those and put in two 512MB sticks of Kingston PC2700 > RAM - and that's when I got the panic. [...] > So my comclusion is that FreeBSD is having trouble booting with 2 > 512MB RAM sticks. The BIOS recognizes the RAM ok Before you do anything else, I strongly recommend you put in both of the new memory modules in and run memtest86+. Thomas -- N.J. Thomas [EMAIL PROTECTED] Etiamsi occiderit me, in ipso sperabo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help with panic: vm_fault
c on
isa0
sc0: at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on
isa0
uhub0: device problem (SET_ADDR_FAILED), disabling port 1
Timecounter "TSC" frequency 2806380287 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 57259MB at ata0-master UDMA133
ad1: 76319MB at ata0-slave UDMA100
acd0: CDROM at ata1-master UDMA33
Trying to mount root from ufs:/dev/ad0s1a
<118>Loading configuration files.
<118>kernel dumps on /dev/ad0s1b
<118>Entropy harvesting:
<118> interrupts
<118> ethernet
<118> point_to_point
<118> kickstart
<118>.
<118>swapon: adding /dev/ad0s1b as swap device
panic: vm_fault: fault on nofault entry, addr: e0c19000
KDB: enter: panic
panic: from debugger
Uptime: 1s
Dumping 991 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 991MB (253680 pages) 975 959 943 927 911 895 879 863 847 831
815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543
527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255
239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) where
#0 doadump () at pcpu.h:165
#1 0xc0503f22 in boot (howto=260) at ../../../kern/kern_shutdown.c:399
#2 0xc05041e8 in panic (fmt=0xc065ef0a "from debugger")
at ../../../kern/kern_shutdown.c:555
#3 0xc044c4cd in db_panic (addr=-1068383073, have_addr=0, count=-1,
modif=0xeab419c0 "") at ../../../ddb/db_command.c:438
#4 0xc044c464 in db_command (last_cmdp=0xc06bc1e4, cmd_table=0x0,
aux_cmd_tablep=0xc0685d50, aux_cmd_tablep_end=0xc0685d54)
at ../../../ddb/db_command.c:350
#5 0xc044c52c in db_command_loop () at ../../../ddb/db_command.c:458
#6 0xc044e139 in db_trap (type=3, code=0) at
../../../ddb/db_main.c:221
#7 0xc051c71b in kdb_trap (type=3, code=0, tf=0xeab41b00)
at ../../../kern/subr_kdb.c:473
#8 0xc063c2dc in trap (frame=
{tf_fs = -357302264, tf_es = -1068433368, tf_ds = -1067057112,
tf_edi = 1, tf_esi = -1066949029, tf_ebp = -357295296, tf_isp =
-357295316, tf_ebx = -357295252, tf_edx = 0, tf_ecx = -1061072896,
tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1068383073, tf_cs =
32, tf_eflags = 658, tf_esp = -357295264, tf_ss = -1068482185}) at
../../../i386/i386/trap.c:591
#9 0xc062b66a in calltrap () at ../../../i386/i386/exception.s:139
#10 0xc051c49f in kdb_enter (msg=0x12 )
at cpufunc.h:60
#11 0xc0504177 in panic (
fmt=0xc067a65b "vm_fault: fault on nofault entry, addr: %lx")
---Type to continue, or q to quit---
at ../../../kern/kern_shutdown.c:539
#12 0xc05f132c in vm_fault (map=0xc0c43000, vaddr=3770781696,
fault_type=2 '\002', fault_flags=0) at ../../../vm/vm_fault.c:277
#13 0xc063c51e in trap_pfault (frame=0xeab41ca4, usermode=0,
eva=3770782502)
at ../../../i386/i386/trap.c:731
#14 0xc063c169 in trap (frame=
{tf_fs = -1068367864, tf_es = -1039269848, tf_ds = 40, tf_edi =
-1039246336, tf_esi = 0, tf_ebp = -357294800, tf_isp = -357294896,
tf_ebx = -1039251408, tf_edx = -1039246336, tf_ecx = -1039428312,
tf_eax = -357294916, tf_trapno = 12, tf_err = 2, tf_eip = -1067218097,
tf_cs = 32, tf_eflags = 66182, tf_esp = -1039246336, tf_ss =
-357294844}) at ../../../i386/i386/trap.c:432
#15 0xc062b66a in calltrap () at ../../../i386/i386/exception.s:139
#16 0xc0638b4f in pmap_change_wiring (pmap=0xc20e4830, va=59, wired=0)
at ../../../i386/i386/pmap.c:2255
#17 0xc062b6bf in Xint0x80_syscall () at
../../../i386/i386/exception.s:200
#18 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) q
%^Dexit
Script done on Thu Jan 12 08:25:40 2006
Device 1K-blocks UsedAvail Capacity
/dev/ad0s1b 15974400 1597440 0%
/dev/md0 15974400 1597440 0%
Total 31948800 3194880 0%
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Juraj Pisar - Yuri
icq: 268103467
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Help with panic: vm_fault
3c0-0x3df iomem 0xa-0xb on
isa0
uhub0: device problem (SET_ADDR_FAILED), disabling port 1
Timecounter "TSC" frequency 2806380287 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 57259MB at ata0-master UDMA133
ad1: 76319MB at ata0-slave UDMA100
acd0: CDROM at ata1-master UDMA33
Trying to mount root from ufs:/dev/ad0s1a
<118>Loading configuration files.
<118>kernel dumps on /dev/ad0s1b
<118>Entropy harvesting:
<118> interrupts
<118> ethernet
<118> point_to_point
<118> kickstart
<118>.
<118>swapon: adding /dev/ad0s1b as swap device
panic: vm_fault: fault on nofault entry, addr: e0c19000
KDB: enter: panic
panic: from debugger
Uptime: 1s
Dumping 991 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 991MB (253680 pages) 975 959 943 927 911 895 879 863 847 831
815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543
527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255
239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) where
#0 doadump () at pcpu.h:165
#1 0xc0503f22 in boot (howto=260) at ../../../kern/kern_shutdown.c:399
#2 0xc05041e8 in panic (fmt=0xc065ef0a "from debugger")
at ../../../kern/kern_shutdown.c:555
#3 0xc044c4cd in db_panic (addr=-1068383073, have_addr=0, count=-1,
modif=0xeab419c0 "") at ../../../ddb/db_command.c:438
#4 0xc044c464 in db_command (last_cmdp=0xc06bc1e4, cmd_table=0x0,
aux_cmd_tablep=0xc0685d50, aux_cmd_tablep_end=0xc0685d54)
at ../../../ddb/db_command.c:350
#5 0xc044c52c in db_command_loop () at ../../../ddb/db_command.c:458
#6 0xc044e139 in db_trap (type=3, code=0) at
../../../ddb/db_main.c:221
#7 0xc051c71b in kdb_trap (type=3, code=0, tf=0xeab41b00)
at ../../../kern/subr_kdb.c:473
#8 0xc063c2dc in trap (frame=
{tf_fs = -357302264, tf_es = -1068433368, tf_ds = -1067057112,
tf_edi = 1, tf_esi = -1066949029, tf_ebp = -357295296, tf_isp =
-357295316, tf_ebx = -357295252, tf_edx = 0, tf_ecx = -1061072896,
tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -1068383073, tf_cs =
32, tf_eflags = 658, tf_esp = -357295264, tf_ss = -1068482185}) at
../../../i386/i386/trap.c:591
#9 0xc062b66a in calltrap () at ../../../i386/i386/exception.s:139
#10 0xc051c49f in kdb_enter (msg=0x12 )
at cpufunc.h:60
#11 0xc0504177 in panic (
fmt=0xc067a65b "vm_fault: fault on nofault entry, addr: %lx")
---Type to continue, or q to quit---
at ../../../kern/kern_shutdown.c:539
#12 0xc05f132c in vm_fault (map=0xc0c43000, vaddr=3770781696,
fault_type=2 '\002', fault_flags=0) at ../../../vm/vm_fault.c:277
#13 0xc063c51e in trap_pfault (frame=0xeab41ca4, usermode=0,
eva=3770782502)
at ../../../i386/i386/trap.c:731
#14 0xc063c169 in trap (frame=
{tf_fs = -1068367864, tf_es = -1039269848, tf_ds = 40, tf_edi =
-1039246336, tf_esi = 0, tf_ebp = -357294800, tf_isp = -357294896,
tf_ebx = -1039251408, tf_edx = -1039246336, tf_ecx = -1039428312,
tf_eax = -357294916, tf_trapno = 12, tf_err = 2, tf_eip = -1067218097,
tf_cs = 32, tf_eflags = 66182, tf_esp = -1039246336, tf_ss =
-357294844}) at ../../../i386/i386/trap.c:432
#15 0xc062b66a in calltrap () at ../../../i386/i386/exception.s:139
#16 0xc0638b4f in pmap_change_wiring (pmap=0xc20e4830, va=59, wired=0)
at ../../../i386/i386/pmap.c:2255
#17 0xc062b6bf in Xint0x80_syscall () at
../../../i386/i386/exception.s:200
#18 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) q
%^Dexit
Script done on Thu Jan 12 08:25:40 2006
Device 1K-blocks UsedAvail Capacity
/dev/ad0s1b 15974400 1597440 0%
/dev/md0 15974400 1597440 0%
Total 31948800 3194880 0%
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: copying from DVD drive causes crash: vm_fault: pager readerror, pid 13421 (cp) on FreeBSD 5.3-STABLE
Hello I observe a similiar behaviour here on an ASUS Laptop with a MATSHITAUJ-831D/1.00 DVD-RW Drive. Altough only with DVD's, but not with CD's. Installed is FreeBSD 5.3-RELEASE-p2. The only difference to the GENERIC kernel is that I added the device atapicam to the kernel. The failure occures with both way accessing the drive (acd0 and cd0). If you need more output, pls. tell me. Chris On Thu, 6 Jan 2005, O. Hartmann wrote: Daniel O'Connor schrieb: On Thu, 6 Jan 2005 23:16, O. Hartmann wrote: Doing dd from the DVD drive (NEC ND 3500AG/2.18) fails in a corrupt image afterwards, copying with 'cp' from a inserted CD triggers the shown error and box dies immediately: Jan 6 12:17:20 edda kernel: cd9660: RockRidge Extension Jan 6 12:17:50 edda kernel: acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 Jan 6 12:18:07 edda last message repeated 3 times Jan 6 12:29:44 edda kernel: cd9660: RockRidge Extension Jan 6 12:30:54 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:30:54 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:30:58 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:30:58 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:01 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:31:01 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:08 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:31:08 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:19 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Same happens when trying to to a 'tar ztf file.foo' (tar archive located on DVD) -> FreeBSD dies and freezes immediately. Does it panic or hang? The DVD has errors on it which is why you can't read it.. Obviously the OS crashing when presented with bad media is not a good thing :) The box hang. The media is all right, I tried it on a FreeBSD 4.10 box and a Windows box (equipted with the same DVD-RW drive, running on a different hardware platform). Writing 'clear' images to the drive results in corrupted media, either DVD and/or CD-R/W. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: copying from DVD drive causes crash: vm_fault: pager readerror, pid 13421 (cp) on FreeBSD 5.3-STABLE
Daniel O'Connor schrieb: On Thu, 6 Jan 2005 23:16, O. Hartmann wrote: Doing dd from the DVD drive (NEC ND 3500AG/2.18) fails in a corrupt image afterwards, copying with 'cp' from a inserted CD triggers the shown error and box dies immediately: Jan 6 12:17:20 edda kernel: cd9660: RockRidge Extension Jan 6 12:17:50 edda kernel: acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 Jan 6 12:18:07 edda last message repeated 3 times Jan 6 12:29:44 edda kernel: cd9660: RockRidge Extension Jan 6 12:30:54 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:30:54 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:30:58 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:30:58 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:01 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:31:01 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:08 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:31:08 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:19 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Same happens when trying to to a 'tar ztf file.foo' (tar archive located on DVD) -> FreeBSD dies and freezes immediately. Does it panic or hang? The DVD has errors on it which is why you can't read it.. Obviously the OS crashing when presented with bad media is not a good thing :) The box hang. The media is all right, I tried it on a FreeBSD 4.10 box and a Windows box (equipted with the same DVD-RW drive, running on a different hardware platform). Writing 'clear' images to the drive results in corrupted media, either DVD and/or CD-R/W. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: copying from DVD drive causes crash: vm_fault: pager read error, pid 13421 (cp) on FreeBSD 5.3-STABLE
On Thu, 6 Jan 2005 23:16, O. Hartmann wrote: > Doing dd from the DVD drive (NEC ND 3500AG/2.18) fails in a corrupt > image afterwards, copying with 'cp' from a inserted CD triggers the > shown error and box dies immediately: > > > Jan 6 12:17:20 edda kernel: cd9660: RockRidge Extension > Jan 6 12:17:50 edda kernel: acd0: FAILURE - READ_BIG ILLEGAL REQUEST > asc=0x64 ascq=0x00 error=4 > Jan 6 12:18:07 edda last message repeated 3 times > Jan 6 12:29:44 edda kernel: cd9660: RockRidge Extension > Jan 6 12:30:54 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR > asc=0x11 ascq=0x00 error=4 > Jan 6 12:30:54 edda kernel: vm_fault: pager read error, pid 13421 (cp) > Jan 6 12:30:58 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR > asc=0x11 ascq=0x00 error=4 > Jan 6 12:30:58 edda kernel: vm_fault: pager read error, pid 13421 (cp) > Jan 6 12:31:01 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR > asc=0x11 ascq=0x00 error=4 > Jan 6 12:31:01 edda kernel: vm_fault: pager read error, pid 13421 (cp) > Jan 6 12:31:08 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR > asc=0x11 ascq=0x00 error=4 > Jan 6 12:31:08 edda kernel: vm_fault: pager read error, pid 13421 (cp) > Jan 6 12:31:19 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR > asc=0x11 ascq=0x00 error=4 > Same happens when trying to to a 'tar ztf file.foo' (tar archive located > on DVD) -> FreeBSD dies and freezes immediately. Does it panic or hang? The DVD has errors on it which is why you can't read it.. Obviously the OS crashing when presented with bad media is not a good thing :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpzrfmq7GHO6.pgp Description: PGP signature
copying from DVD drive causes crash: vm_fault: pager read error, pid 13421 (cp) on FreeBSD 5.3-STABLE
Doing dd from the DVD drive (NEC ND 3500AG/2.18) fails in a corrupt image afterwards, copying with 'cp' from a inserted CD triggers the shown error and box dies immediately: Jan 6 12:17:20 edda kernel: cd9660: RockRidge Extension Jan 6 12:17:50 edda kernel: acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 Jan 6 12:18:07 edda last message repeated 3 times Jan 6 12:29:44 edda kernel: cd9660: RockRidge Extension Jan 6 12:30:54 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:30:54 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:30:58 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:30:58 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:01 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:31:01 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:08 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Jan 6 12:31:08 edda kernel: vm_fault: pager read error, pid 13421 (cp) Jan 6 12:31:19 edda kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x00 error=4 Same happens when trying to to a 'tar ztf file.foo' (tar archive located on DVD) -> FreeBSD dies and freezes immediately. Box is a FreeBSD 5.3-STABLE box (cvsupdated and builtworld today). Hardware is a ASUS CUR-DLS based mainboard, SMP disabled, dmesg shown here: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #23: Thu Jan 6 09:45:18 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/EDDA ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (1000.04-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x387fbff real memory = 1073721344 (1023 MB) avail memory = 1041166336 (992 MB) ioapic0 irqs 0-15 on motherboard ioapic1 irqs 16-31 on motherboard netsmb_dev: loaded npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 7.0 (no driver attached) isab0: port 0xe800-0xe80f at device 15.0 on pci0 isa0: on isab0 atapci0: port 0xd400-0xd40f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ohci0: mem 0xfc00-0xfc000fff irq 9 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ugen0: OmniVision OV511+ Camera, rev 1.00/1.00, addr 2 pcib1: on acpi0 pci1: on pcib1 em0: port 0xd000-0xd03f mem 0xfb80-0xfb81 irq 2 1 at device 2.0 on pci1 em0: Ethernet address: 00:07:e9:14:8f:7b em0: Speed:N/A Duplex:N/A sym0: <1010-33> port 0xb800-0xb8ff mem 0xfa80-0xfa801fff,0xfb00-0xfb0003ff irq 24 at device 5.0 on pci1 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym0: [GIANT-LOCKED] sym1: <1010-33> port 0xb400-0xb4ff mem 0xf980-0xf9801fff,0xfa00-0xfa0003ff irq 25 at device 5.1 on pci1 sym1: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. sym1: [GIANT-LOCKED] atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77a,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xc8000-0xcbfff,0xc-0xc7fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <8 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 fb0 at vga0 Timecounter "TSC" frequency 140141 Hz quality 800 Timecounters tick every 1.250 msec Fast IPsec: Initialized Secur
vm_fault
Hi, ssh began stop logging me into the
server ("Connection closed by [server ip]" after i tried to relogin. I
configured host.allow to allow me logging from this IP. Before this
problem I noticed that my webserver is down and i restarted apache after
through ssh connection. that time i checked for processes and noticed
strange thing i haven't see before:
root 196 0.0 0.0 664 280 ?? Is 12:10AM 0:00.01 sh /etc/rc
autoboot
then i checked some log files in /var/log/ and logged out. so now i fail
to login. I'm a newbie running FreeBSD 4.7.
thanks!
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
vm_fault
Hi, Per the recommendation, I had the system administrators have removed the
cover and cleanse the dust. They also noted an error with the server, it is
as follows: The following error was printed on the screen, it appears the
server utilized all the console buffer space making keyboard interaction
impossible.
vm_fault: pager read error, pid 1 (init)
Does this mean anything to anyone? any suggestions?
-Antonio
===
Sounds like hardware problems caused by overheating.
Open the PC cover and blow out all the dust.
Leave cover off and see if problem reoccurs.
---Original Message-
[EMAIL PROTECTED]
I'm a newbie running FreeBSD (I believe it's 4.4... am at the moment
unable to check, as the computer is down) to host some of my websites. I
sent a query to this mailing list before about receiving some errors when
trying to access my website, after which, ssh would stop logging me into the
server ("Connection closed by [server ip]"), and all web pages would bring
up a "Forbidden" error. After this, the server would go down
completely... or at least I was unable to ping it, access it through http,
or anything
else that I tried...
This has been happening regularly, about every 3-7 hours after the
computer is rebooted. However, while the computer is running, I can
distinguish nothing out of the ordinary.
However, tonight, it "crashed" while i was logged in through ssh.
Suddenly, almost every command that I issued or program I tried to run came
back as "Device not configured."
e.g.:
# reboot
/sbin/reboot : Device not configured
Some things work... (lynx, ping, ps -- all seem to work fine) but
many other commands just return the "Device not configured" or "Segmentation
fault" errors. Also very odd: ls, cd, pwd, etc. seem to work fine, but
when I ls any directory, no files come up. It is completely blank
Anyway, I'm very scared and at my wit's end. The system will appear
normal once it's rebooted, but the same thing will happen within a few
hours... Any suggestions on what to look for? Are there certain log files
that
may contain information on this? I think the most recent thing I did to
the server was several weeks ago, when I installed "wusage" to analyze
web logs... i had since deleted it. Maybe something went wrong there?
I have also noticed two processes running that I hadn't seen
before:
6 con Is+ 0:00.11 sh /etc/rc autoboot
447 con I+ 0:00.00 sh /etc/rc autoboot
Errors when trying to access a php/mysql driven website
Warning: open(/tmp/sess_4a23ba911863d07812e9cdf99656586f,
O_RDWR)
failed: Device not configured (6) in
Warning: open(/tmp/sess_4a23ba911863d07812e9cdf99656586f,
O_RDWR)
failed: Device not configured (6) in Unknown on line 0
Warning: Failed to write session data (files). Please verify
that the
current setting of session.save_path is correct (/tmp) in Unknown
on line
0
===
I then try to login via ssh... but I get "Connection closed by
[my ip]".
_
Share holiday photos without swamping your Inbox. Get MSN Extra Storage
now! http://join.msn.com/?PAGE=features/es
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
