Usual pressing "eject" causes crash
I have opened a:
"KDE Kontrol Center" => "Peripherials" => "Storage Media" => "A
certain action" => "Propertias"
and have almost simultaneously pressed the button "eject" on a DVD-drive
- that has led to crash of system.
How next time to avoid crash of system at ejection of a DVD-disk?
==[START]==
$ kgdb ./kernel.debug /var/crash/vmcore.0
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[GDB will not be able to debug user-mode threads:
/usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
(cd0:ata1:0:0:0): READ(10). CDB: 28 0 0 0 1 9 0 0 1 0
(cd0:ata1:0:0:0): CAM Status: SCSI Status Error
(cd0:ata1:0:0:0): SCSI Status: Check Condition
(cd0:ata1:0:0:0): NOT READY asc:3a,0
(cd0:ata1:0:0:0): Medium not present
(cd0:ata1:0:0:0): Unretryable error
(cd0:ata1:0:0:0): cddone: got error 0x6 back
g_vfs_done():cd0[READ(offset=542720, length=2048)]error = 6
warning: udf_readlblks returned error 6
panic: brelse: free buffer onto another queue???
Uptime: 1d21h54m32s
Dumping 958 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 958MB (245232 pages) 942 926 910 894 878 862 846 830 814 798
782 766 750 734 718 702 686 670 654 (CTRL-C to abort) 638 622 606 590
574 558 542 526 510 494 478 462 446 430 414 398 382 366 350 334 318 302
286 270 254 238 222 206 190 174 158 142 126 110 94 78 62 46 30 14
#0 doadump () at pcpu.h:165
165 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) bt full
#0 doadump () at pcpu.h:165
No locals.
#1 0xc050a3d4 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
first_buf_printf = 1
#2 0xc050a706 in panic (fmt=0xc070eb27 "brelse: free buffer onto
another queue???") at /usr/src/sys/kern/kern_shutdown.c:565
td = (struct thread *) 0xc6e2b600
bootopt = 260
newpanic = 0
ap = 0xc6e2b600 "\030\002ЦфюцБф"
buf = "brelse: free buffer onto another queue???", '\0' 214 times>
#3 0xc055f3ae in brelse (bp=0xd89ebf68) at /usr/src/sys/kern/vfs_bio.c:1315
No locals.
#4 0xc10778a8 in ?? ()
No symbol table info available.
<...>SKIP<...>
#36 0xe8df6a24 in ?? ()
No symbol table info available.
---Type to continue, or q to quit---
#37 0xc06ed633 in VOP_CACHEDLOOKUP_APV (vop=0x0, a=0x0) at vnode_if.c:150
rc = 0
Previous frame inner to this frame (corrupt stack?)
(kgdb)
==[STOP]===
$ uname -a
FreeBSD inspirra.localdomain 6.2-STABLE FreeBSD 6.2-STABLE #8: Thu Mar
29 19:29:52 MSD 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/INSPIRRA i386
$ pkg_info -E hal-0\* kde-3\* dbus\* policyk*
dbus-1.0.2_1
dbus-glib-0.73
dbus-qt3-0.70
hal-0.5.8.20070324
kde-3.5.6
policykit-0.1.20060514_3
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: freebsd-update weirdness
Joao Barros wrote: > I just finished installing my new silent router with 6.2R and took > freebsd-update for a spin... > > C3# uname -a > FreeBSD C3.bsdtech.org 6.2-RELEASE-p2 FreeBSD 6.2-RELEASE-p2 #0: Tue > Feb 27 22:41:06 UTC 2007 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 > > C3# freebsd-update fetch > [...] > No updates needed to update system to 6.2-RELEASE-p3. This may look odd, but it's actually correct. The version number reported by `uname` is the version number of the kernel, and the change from 6.2-RELEASE-p2 to 6.2-RELEASE-p3 didn't affect the kernel. Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
freebsd-update weirdness
I just finished installing my new silent router with 6.2R and took freebsd-update for a spin, just wanting to try it out as I usually compile a kernel with ALTQ Notice the advertised p3 and the p2 I got in the end: C3# freebsd-update fetch Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching public key from update1.FreeBSD.org... done. Fetching metadata signature from update1.FreeBSD.org... done. Fetching metadata index... done. Fetching 2 metadata files... done. Inspecting system... done. Preparing to download files... done. Fetching 18 patches.10 done. Applying patches... done. The following files will be updated as part of updating to 6.2-RELEASE-p3: /boot/kernel/kernel /etc/rc.d/jail /usr/bin/dig /usr/bin/host /usr/bin/nslookup /usr/bin/nsupdate /usr/sbin/dnssec-signzone /usr/sbin/freebsd-update /usr/sbin/lwresd /usr/sbin/named /usr/sbin/named-checkconf /usr/sbin/named-checkzone /usr/src/contrib/bind9/lib/dns/include/dns/validator.h /usr/src/contrib/bind9/lib/dns/resolver.c /usr/src/contrib/bind9/lib/dns/validator.c /usr/src/etc/rc.d/jail /usr/src/sys/conf/newvers.sh /usr/src/sys/netinet6/nd6.c /usr/src/usr.sbin/freebsd-update/freebsd-update.sh C3# freebsd-update install Installing updates... done. C3# uname -a FreeBSD C3.bsdtech.org 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 After rebooting: C3# uname -a FreeBSD C3.bsdtech.org 6.2-RELEASE-p2 FreeBSD 6.2-RELEASE-p2 #0: Tue Feb 27 22:41:06 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 C3# freebsd-update fetch Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature from update1.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 6.2-RELEASE-p3. -- Joao Barros ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfw add pipe broken?
On Sunday 01 April 2007 15:22, Mike Tancsa wrote: > At 11:55 AM 4/1/2007, JoaoBR wrote: > >by all respect to Julians work but with ipfw broken and sunday fucked up > > ... > > > >kind of scaring when seeing "I have no time to check, I do it on tuesday" > >or "I need to do the userland ipfw too to add some new features, but, not > >today.." > >please do it all or don't do it, ipfw is an mature and essential > >part where we > >do not espect such sudden surprises in releng6 to happen > > I seriously doubt he intentionally meant to break it Accidents man sure not, no one said that > happen. Roll your sources back to Friday and you will be OK until yaya but essential and especially mature code should be tested before comitting changes I guess, I believe that ipfw wasn't tested before beeing hacked and comitted this time, and overall btw, there was an alert and reply to the commit msg on cvs which then was politly ignored "until tuesday" ... luck that it wasn't the bootstrap or something > its sorted out. Remember, its a best effort, not perfect effort project. sure, but when became perfect the honor is welcome as it comes for free when it went wrong ;) > > ---Mike > > João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell SAS5 Performance Issue
Bjoern A. Zeeb wrote: On Sun, 1 Apr 2007, Richard Tector wrote: A perhaps unrealted issue: I've noticed a large number of messages being produced by the mpt driver after boot occuring approximately every 90 seconds. Apr 1 15:51:43 moses kernel: mpt0: mpt_cam_event: 0x14 Apr 1 15:51:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x14 (ACK not required). Apr 1 15:53:19 moses kernel: mpt0: mpt_cam_event: 0x14 Apr 1 15:53:19 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x14 (ACK not required). Any thoughts anyone? Is there any way to find out what the events correspond to? IMHO 0x14 is "resync complete". Dud you have a degraded RAID-1? Can you tell me what Index: mpt_cam.c === RCS file: /shared/mirror/FreeBSD/r/ncvs/src/sys/dev/mpt/mpt_cam.c,v retrieving revision 1.52 diff -u -p -r1.52 mpt_cam.c --- mpt_cam.c 11 Mar 2007 01:54:59 - 1.52 +++ mpt_cam.c 1 Apr 2007 16:54:27 - @@ -2236,6 +2236,10 @@ mpt_cam_event(struct mpt_softc *mpt, req CAMLOCK_2_MPTLOCK(mpt); break; } + case MPI_EVENT_IR_RESYNC_UPDATE: + uint8_t resync = (data0 >> 16) & 0xff; + mpt_prt(mpt, "IR resync update %d completed.", resync); + break; case MPI_EVENT_EVENT_CHANGE: case MPI_EVENT_INTEGRATED_RAID: case MPI_EVENT_SAS_DEVICE_STATUS_CHANGE: gives you; especially how far it counts up? Now you come to mention it, I believe it was indeed the array rebuilding. I'll try your patch and force a resync of the mirror tomorrow morning and report back with the output. Would be a useful feature to have. On a side note the array is now marked as Optimal in the BIOS so I assume the following messages, sent about 2 hours later, were various ways of saying "Complete"? Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x14 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x14 (ACK not required). Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x21 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x21 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x15 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x15 (ACK not required). Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x21 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x21 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). Thank you for your help, Richard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfw add pipe broken?
At 11:55 AM 4/1/2007, JoaoBR wrote: by all respect to Julians work but with ipfw broken and sunday fucked up ... kind of scaring when seeing "I have no time to check, I do it on tuesday" or "I need to do the userland ipfw too to add some new features, but, not today.." please do it all or don't do it, ipfw is an mature and essential part where we do not espect such sudden surprises in releng6 to happen I seriously doubt he intentionally meant to break it Accidents happen. Roll your sources back to Friday and you will be OK until its sorted out. Remember, its a best effort, not perfect effort project. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: scsi/mpt problem with latest source
> > > > (xpt0:mpt0:0:-1:-1): reset bus periph:sim:channel:target:lun target == lun == -1 == wildcard, so the initial bus reset applies to a nexus for all targets and luns on that channel on that sim (mpt0) on that periph (xpt0) would you mind to tell why it happens and this "-1" values ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB devices fail to re-attach on 6.2
On 3/31/07, Maxim Khitrov <[EMAIL PROTECTED]> wrote: Right now I don't even mount it. I boot the system up, insert the drive, give it a few seconds, and then remove it. After I've done this once, attaching the drive a second time doesn't work. - Max Ok, I think I figured it out. Here's basically what I was doing... Besides my flash drive, I had a usb hard drive (Vantec NexStar 2.5" enclosure) connected to the laptop. FreeBSD was installed onto the USB hard drive, because I wanted to download the source and put just the things I needed onto the actual laptop drive. That, and I was also doing full-disk encryption using GELI, so I needed an external OS to do this work. At this point in time, I have the system running from the build-in drive, which means that I can disconnect the usb one. Guess what happens when that drive is removed? Everything works normally again. I can connect and disconnect the flash drive as many times as I want and it works every time. But as soon as I connect the Vantec enclosure, even if I don't use it, I can only connect the flash drive once. After that, we're back to the original problem. Does anyone have a guess as to why the external enclosure would cause this sort of a problem? Could it be consuming too much power (but then why is the flash drive detected the first time)? - Max ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: scsi/mpt problem with latest source
On Sunday 01 April 2007 14:49, Matthew Jacob wrote: > > this reset bus didn't and do not happen with some day older sources: > > > > (xpt0:mpt0:0:-1:-1): reset bus > > Well, don't worry about it. It's always been happening. > > > no, I do not boot verbose > > Thanks. I'll make this message show up under 'bootverbose' only., > good to know, so it was hidden before would you mind to tell why it happens and this "-1" values ? thank's for your attention > > > > ... > > > > da0 at mpt0 bus 0 target 0 lun 0 > > > > da1 at mpt0 bus 0 target 1 lun 0 > > > > > > > > > > > > > > > > -- > > > > > > > > João > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > > > > segura. Service fornecido pelo Datacenter Matik > > > > https://datacenter.matik.com.br > > > > ___ > > > > freebsd-stable@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > To unsubscribe, send any mail to > > > > "[EMAIL PROTECTED]" > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > > > segura. Service fornecido pelo Datacenter Matik > > > https://datacenter.matik.com.br > > > > -- > > > > João > > > > > > > > > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > > segura. Service fornecido pelo Datacenter Matik > > https://datacenter.matik.com.br > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > segura. Service fornecido pelo Datacenter Matik > https://datacenter.matik.com.br -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: scsi/mpt problem with latest source
this reset bus didn't and do not happen with some day older sources: > > (xpt0:mpt0:0:-1:-1): reset bus Well, don't worry about it. It's always been happening. no, I do not boot verbose Thanks. I'll make this message show up under 'bootverbose' only., > > ... > > da0 at mpt0 bus 0 target 0 lun 0 > > da1 at mpt0 bus 0 target 1 lun 0 > > > > > > > > -- > > > > João > > > > > > > > > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > > segura. Service fornecido pelo Datacenter Matik > > https://datacenter.matik.com.br > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > segura. Service fornecido pelo Datacenter Matik > https://datacenter.matik.com.br -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[releng_6 tinderbox] failure on i386/pc98
TB --- 2007-04-01 16:16:03 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-04-01 16:16:03 - starting RELENG_6 tinderbox run for i386/pc98 TB --- 2007-04-01 16:16:03 - cleaning the object tree TB --- 2007-04-01 16:16:21 - checking out the source tree TB --- 2007-04-01 16:16:21 - cd /tinderbox/RELENG_6/i386/pc98 TB --- 2007-04-01 16:16:21 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2007-04-01 16:25:42 - building world (CFLAGS=-O2 -pipe) TB --- 2007-04-01 16:25:42 - cd /src TB --- 2007-04-01 16:25:42 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2007-04-01 17:26:01 - generating LINT kernel config TB --- 2007-04-01 17:26:01 - cd /src/sys/pc98/conf TB --- 2007-04-01 17:26:01 - /usr/bin/make -B LINT TB --- 2007-04-01 17:26:01 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-04-01 17:26:01 - cd /src TB --- 2007-04-01 17:26:01 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Apr 1 17:26:02 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] nexus.o(.text+0x8c0): In function `nexus_remap_msix': : undefined reference to `msix_remap' nexus.o(.text+0x8ed): In function `nexus_release_msix': : undefined reference to `msix_release' nexus.o(.text+0x926): In function `nexus_alloc_msi': : undefined reference to `msi_alloc' nexus.o(.text+0x980): In function `nexus_release_msi': : undefined reference to `msi_release' *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-04-01 17:37:34 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-04-01 17:37:34 - ERROR: failed to build lint kernel TB --- 2007-04-01 17:37:34 - tinderbox aborted TB --- 0.66 user 1.84 system 4891.00 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: scsi/mpt problem with latest source
On Sunday 01 April 2007 14:02, Matthew Jacob wrote: > pleasep pooint out what the error is, and are you booting verbose? > > On 4/1/07, JoaoBR <[EMAIL PROTECTED]> wrote: > > with new sources I get an mpt error which is not present with sources > > from march 28 > > > > mpt0: port 0xdc00-0xdcff mem > > 0xfd7e-0xfd7f,0xfd7c-0xfd7d irq 16 at device 4.0 on pci1 > > mpt0: [GIANT-LOCKED] > > mpt0: MPI Version=1.2.14.0 > > ... this reset bus didn't and do not happen with some day older sources: > > (xpt0:mpt0:0:-1:-1): reset bus no, I do not boot verbose > > ... > > da0 at mpt0 bus 0 target 0 lun 0 > > da1 at mpt0 bus 0 target 1 lun 0 > > > > > > > > -- > > > > João > > > > > > > > > > > > > > > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > > segura. Service fornecido pelo Datacenter Matik > > https://datacenter.matik.com.br > > ___ > > freebsd-stable@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada > segura. Service fornecido pelo Datacenter Matik > https://datacenter.matik.com.br -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: scsi/mpt problem with latest source
pleasep pooint out what the error is, and are you booting verbose? On 4/1/07, JoaoBR <[EMAIL PROTECTED]> wrote: with new sources I get an mpt error which is not present with sources from march 28 mpt0: port 0xdc00-0xdcff mem 0xfd7e-0xfd7f,0xfd7c-0xfd7d irq 16 at device 4.0 on pci1 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.14.0 ... (xpt0:mpt0:0:-1:-1): reset bus ... da0 at mpt0 bus 0 target 0 lun 0 da1 at mpt0 bus 0 target 1 lun 0 -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell SAS5 Performance Issue
On 4/1/07, Richard Tector <[EMAIL PROTECTED]> wrote: Matthew Jacob wrote: > On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote: >> Matthew Jacob wrote: >> > It's been seen before but the fix isn't know yet. >> > >> > On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote: >> >> I'm suffering from very slow write performance on a Dell PowerEdge >> 860 >> >> with the SAS5/IR controller (mpt driver) running either >> 6.2-RELEASE or >> >> 6.2-STABLE with sources from yesterday. The controller hosts 2 >> Western >> >> Digital 320GB SATA disks in a RAID1 configuration. >> >> Reads approach 65MB/s however writes appear extremely slow, in the >> >> region of 6-7MB/s with a dd and a blocksize of 1MB all the way >> down to >> >> about 300KB/s while extracting a ports snapshot. >> >> >> >> It was suggested to me that perhaps write caching has been >> disabled on >> >> the controller however no options exist within the BIOS >> configuration to >> >> view/adjust *any* caching options. >> >> >> >> Has anyone else experienced this issue? If so how did they resolve >> it? >> >> Also, is there any way to toggle the caching settings from FreeBSD? >> A perhaps unrealted issue: I've noticed a large number of messages being produced by the mpt driver after boot occuring approximately every 90 seconds. Apr 1 15:51:43 moses kernel: mpt0: mpt_cam_event: 0x14 Apr 1 15:51:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x14 (ACK not required). Apr 1 15:53:19 moses kernel: mpt0: mpt_cam_event: 0x14 Apr 1 15:53:19 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x14 (ACK not required). Any thoughts anyone? Is there any way to find out what the events correspond to? MPI spec, instantiated in MPILIB MPI_EVENT_IR_RESYNC_UPDATE internal raid resync update? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell SAS5 Performance Issue
On Sun, 1 Apr 2007, Richard Tector wrote: A perhaps unrealted issue: I've noticed a large number of messages being produced by the mpt driver after boot occuring approximately every 90 seconds. Apr 1 15:51:43 moses kernel: mpt0: mpt_cam_event: 0x14 Apr 1 15:51:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x14 (ACK not required). Apr 1 15:53:19 moses kernel: mpt0: mpt_cam_event: 0x14 Apr 1 15:53:19 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x14 (ACK not required). Any thoughts anyone? Is there any way to find out what the events correspond to? IMHO 0x14 is "resync complete". Dud you have a degraded RAID-1? Can you tell me what Index: mpt_cam.c === RCS file: /shared/mirror/FreeBSD/r/ncvs/src/sys/dev/mpt/mpt_cam.c,v retrieving revision 1.52 diff -u -p -r1.52 mpt_cam.c --- mpt_cam.c 11 Mar 2007 01:54:59 - 1.52 +++ mpt_cam.c 1 Apr 2007 16:54:27 - @@ -2236,6 +2236,10 @@ mpt_cam_event(struct mpt_softc *mpt, req CAMLOCK_2_MPTLOCK(mpt); break; } + case MPI_EVENT_IR_RESYNC_UPDATE: + uint8_t resync = (data0 >> 16) & 0xff; + mpt_prt(mpt, "IR resync update %d completed.", resync); + break; case MPI_EVENT_EVENT_CHANGE: case MPI_EVENT_INTEGRATED_RAID: case MPI_EVENT_SAS_DEVICE_STATUS_CHANGE: gives you; especially how far it counts up? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfw add pipe broken?
On Sunday 01 April 2007 12:04, Mike Tancsa wrote: > At 10:07 AM 4/1/2007, JoaoBR wrote: > >it seems I can not add pipes with releng6 sources from the last days > > > >ipfw add pipe 1 ip from any to any > >ipfw: getsockopt(IP_FW_ADD): Invalid argument > > > >or any similar add pipe command does not work > >(sure I have options DUMMYNET in > >kernel) > > > >world and kernel from march 29 works still fine > > > >anything changed? > > There were a bunch of MFCs. When I try from a kernel today, > seems the thing happened on saturday by all respect to Julians work but with ipfw broken and sunday fucked up ... kind of scaring when seeing "I have no time to check, I do it on tuesday" or "I need to do the userland ipfw too to add some new features, but, not today.." please do it all or don't do it, ipfw is an mature and essential part where we do not espect such sudden surprises in releng6 to happen -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dell SAS5 Performance Issue
Matthew Jacob wrote: On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote: Matthew Jacob wrote: > It's been seen before but the fix isn't know yet. > > On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote: >> I'm suffering from very slow write performance on a Dell PowerEdge 860 >> with the SAS5/IR controller (mpt driver) running either 6.2-RELEASE or >> 6.2-STABLE with sources from yesterday. The controller hosts 2 Western >> Digital 320GB SATA disks in a RAID1 configuration. >> Reads approach 65MB/s however writes appear extremely slow, in the >> region of 6-7MB/s with a dd and a blocksize of 1MB all the way down to >> about 300KB/s while extracting a ports snapshot. >> >> It was suggested to me that perhaps write caching has been disabled on >> the controller however no options exist within the BIOS configuration to >> view/adjust *any* caching options. >> >> Has anyone else experienced this issue? If so how did they resolve it? >> Also, is there any way to toggle the caching settings from FreeBSD? A perhaps unrealted issue: I've noticed a large number of messages being produced by the mpt driver after boot occuring approximately every 90 seconds. Apr 1 15:51:43 moses kernel: mpt0: mpt_cam_event: 0x14 Apr 1 15:51:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x14 (ACK not required). Apr 1 15:53:19 moses kernel: mpt0: mpt_cam_event: 0x14 Apr 1 15:53:19 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x14 (ACK not required). Any thoughts anyone? Is there any way to find out what the events correspond to? Regards, Richard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfw add pipe broken?
At 10:07 AM 4/1/2007, JoaoBR wrote: it seems I can not add pipes with releng6 sources from the last days ipfw add pipe 1 ip from any to any ipfw: getsockopt(IP_FW_ADD): Invalid argument or any similar add pipe command does not work (sure I have options DUMMYNET in kernel) world and kernel from march 29 works still fine anything changed? There were a bunch of MFCs. When I try from a kernel today, [smicro1U]# ipfw pipe 3 config bw 512Kb [smicro1U]# ipfw pipe show 3: 512.000 Kbit/s0 ms 50 sl. 0 queues (1 buckets) droptail [smicro1U]# [smicro1U]# ipfw add 1 pipe 3 ip from 10.0.0.0/8 to any ipfw: getsockopt(IP_FW_ADD): Invalid argument [smicro1U]# [smicro1U]# dmesg | tail -1 ipfw: opcode 50 size 2 wrong [smicro1U]# -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
scsi/mpt problem with latest source
with new sources I get an mpt error which is not present with sources from march 28 mpt0: port 0xdc00-0xdcff mem 0xfd7e-0xfd7f,0xfd7c-0xfd7d irq 16 at device 4.0 on pci1 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.14.0 ... (xpt0:mpt0:0:-1:-1): reset bus ... da0 at mpt0 bus 0 target 0 lun 0 da1 at mpt0 bus 0 target 1 lun 0 -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ipfw add pipe broken?
it seems I can not add pipes with releng6 sources from the last days ipfw add pipe 1 ip from any to any ipfw: getsockopt(IP_FW_ADD): Invalid argument or any similar add pipe command does not work (sure I have options DUMMYNET in kernel) world and kernel from march 29 works still fine anything changed? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Kernel Dumps on to gmirror device?
I've got a 6.1 server that's panicing and I'd like to debug it. The problem is that I can't get a kernel dump on to my gmirror device. It looks like since 6.1 this has been supported (it says so in the release notes). In my rc.conf I have: dumpdev="/dev/mirror/gm0s1b"$a Which is my swap partition. On booting it says: kernel dumps on /dev/mirror/gm0s1b But when it panics it says: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor write, page not present instruction pointer = 0x20:0xc057ff9f stack pointer = 0x28:0xe2df3c44 frame pointer = 0x28:0xe2df3c4c 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 = 13 (swi4: clock sio) trap number = 12 panic: page fault Uptime: 1d4h15m55s GEOM_MIRROR: Device gm0: provider mirror/gm0 destroyed. GEOM_MIRROR: Device gm0 destroyed. Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... I'm guessing it's because the GEOM_MIRROR device has been destroyed just before it wants to dump? Any suggestions on a way forward to getting a dump out? Thanks, Tim. Hi Tim Do you really need to run 6.1 ? To be honest I found a lot of issues with 6.1 that were fixed in 6.2 so my advice would be to upgrade to 6.2-STABLE and more than likely this will either be fixed or will probably not happen at all. -Clay ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Kernel Dumps on to gmirror device?
I've got a 6.1 server that's panicing and I'd like to debug it. The problem is that I can't get a kernel dump on to my gmirror device. It looks like since 6.1 this has been supported (it says so in the release notes). In my rc.conf I have: dumpdev="/dev/mirror/gm0s1b"$a Which is my swap partition. On booting it says: kernel dumps on /dev/mirror/gm0s1b But when it panics it says: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor write, page not present instruction pointer = 0x20:0xc057ff9f stack pointer = 0x28:0xe2df3c44 frame pointer = 0x28:0xe2df3c4c 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 = 13 (swi4: clock sio) trap number = 12 panic: page fault Uptime: 1d4h15m55s GEOM_MIRROR: Device gm0: provider mirror/gm0 destroyed. GEOM_MIRROR: Device gm0 destroyed. Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... I'm guessing it's because the GEOM_MIRROR device has been destroyed just before it wants to dump? Any suggestions on a way forward to getting a dump out? Thanks, Tim. -- Tim Bishop http://www.bishnet.net/tim/ PGP Key: 0x5AE7D984 pgp9T1dbCb1cm.pgp Description: PGP signature
