freebsd-current Digest, Vol 65, Issue 5
昆虫博士
Send freebsd-current mailing list submissions to
freebsd...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-current
or, via email, send a message with subject or body 'help' to
freebsd-cur...@freebsd.org
You can reach the person managing the list at
freebsd-cu...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-current digest..."
Today's Topics:
1. Re: Upgrading perl (Randy Bush)
2. [backtrace] kernel dump when shutting down (Xin LI)
3. Re: Possible Threading problem with -CURRENT / MySQL?
(Martin Blapp)
4. ATAPICAM hangs with cdparanoia (Brian Feldman)
5. Re: Serial console - how to reboot? (Eirik Oeverby)
6. Intel S875WP1-E mothterboard and -CURRENT (ast...@ukrtelecom.net)
7. HA: [backtrace] kernel dump when shutting down
(ast...@ukrtelecom.net)
8. USB woes. (Ian FREISLICH)
9. Re: USB woes. (Thorsten Greiner)
10. Re: Possible Threading problem with -CURRENT / MySQL?
(Lasse Laursen)
----------------------------------------------------------------------
Message: 1
Date: Mon, 14 Jun 2004 21:15:52 -0700
From: Randy Bush <ra...@psg.com>
Subject: Re: Upgrading perl
To: noa...@alumni.rice.edu
Cc: cur...@freebsd.org
Message-ID: <16590.30712....@ran.psg.com>
Content-Type: text/plain; charset=us-ascii
> After rebuilding everything, you may want to finalize the upgrade by
> cleaning out /usr/local/lib/perl5/ and /usr/local/lib/perl5/site_perl.
> Due to incorrect plists, there may be some files left there from 5.6.x.
> It might be a good idea to check that each file is present in the
> 5.8.x directory before deleting (as a sanity check for the upgrade), but
> after the complete rebuild it should be safe to remove everything. The
> goal is to completely get rid of the 5.6.x directories:
fwiw, i am now in the habit of putting .pls which are not installed
by portupdate (i.e. gotten from here and there) directly in
/usr/local/lib/perl5/site_perl
so they go across releases and i don't have to dig them out.
randy
------------------------------
Message: 2
Date: Tue, 15 Jun 2004 13:22:29 +0800
From: Xin LI <del...@frontfree.net>
Subject: [backtrace] kernel dump when shutting down
To: ac...@FreeBSD.org, cur...@FreeBSD.org
Message-ID: <2004061505...@frontfree.net>
Content-Type: text/plain; charset="us-ascii"
Hello folks,
I got a strange problem when having HTT enabled on a P4 2.8E processor.
When rebooting the system, after the disk sync and the system is going
to restart, it crashes and generates a crashdump. Strangely, the panic
message seems to be corrupted.
The kernel was built on fresh cvsup'ed code. I have did some local
modifications, however, the crash persists no matter whether I have
applied my modifications.
Here is the backtrace:
(kgdb) beastie# gdb -k kernel.debug /var/crash/vmcore.4
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 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-undermydesk-freebsd"...
panic: blockable sleep lock (sleep mutex) process lock @ /usr/src/sys/kern/ker
n_sig.c:1510
panic messages:
---
panic: blockable sleep lock (sleep mutex) process lock @ /usr/src/sys/kern/ker
n_sig.c:1510
cpuid = 1;
boot() called on cpu#1
Uptime: 14m26s
Dumping 1007 MB
ad2: timeout waiting for write DRQad2: timeout waiting for write DRQad2: timeo
ut waiting for write DRQad2: timeout waiting for write DRQad2: timeout waiting
for write DRQ 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 2
88 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592
608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 9
12spin lock witness lock held by 0xc1e2b420 for > 5 seconds
928 944 960 976 992
---
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:236
236 dumping++;
(kgdb) bt full
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:236
No locals.
#1 0xc0500256 in runq_choose (rq=0x0) at /usr/src/sys/kern/kern_switch.c:583
ke = (struct kse *) 0x0
#2 0xc050b25a in kseq_choose (kseq=0xc1e29800) at /usr/src/sys/kern/sched_ule
c:783
ke = (struct kse *) 0xc1e2b420
swap = (struct runq *) 0xc1e2980c
#3 0xc050c364 in sched_choose () at /usr/src/sys/kern/sched_ule.c:347
kseq = (struct kseq *) 0xc06c4970
ke = (struct kse *) 0xc1e2f780
The system works just fine when HTT is disabled.
Kernel configuration is:
#
# BEASTIE -- Customized kernel configuration file for FreeBSD/i386
#
# $Phantasm$
machine i386
cpu I686_CPU
ident BEASTIE
# To statically compile in device wiring instead of /boot/device.hints
#hints "GENERIC.hints" # Default places to look for devices.
makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols
options SCHED_ULE # ULE scheduler
options INET # InterNETworking
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_DIRHASH # Improve performance on big directories
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS # Pseudo-filesystem framework
options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=0 # Delay (in ms) before probing SCSI
options KTRACE # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions
options KBD_INSTALL_CDEV # install a CDEV entry in /dev
options PFIL_HOOKS # pfil(9) framework
# Debugging for use in -current
options DDB # Enable the kernel debugger
options INVARIANTS # Enable calls of extra sanity checking
options INVARIANT_SUPPORT # Extra sanity checks of internal structures, requi
red by INVARIANTS
options WITNESS # Enable checks to detect deadlocks and cycles
options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed
# To make an SMP kernel, the next two are needed
options SMP # Symmetric MultiProcessor Kernel
device apic # I/O APIC
device isa
device eisa
device pci
# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
options ATA_STATIC_ID # Static device numbering
# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc # AT keyboard controller
device atkbd # AT keyboard
device vga # VGA video card driver
device splash # Splash screen and screen saver support
# syscons is the default console driver, resembling an SCO console
device sc
device agp # support several AGP chipsets
# Floating point support - do not disable.
device npx
# Add suspend/resume support for the i8254.
device pmtimer
# PCI Ethernet NICs that use the common MII bus controller code.
# NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
device miibus # MII bus support
device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'')
# Pseudo devices - the number indicates how many units to allocate.
device random # Entropy device
device loop # Network loopback
device ether # Ethernet support
device ppp # Kernel PPP
device tun # Packet tunnel.
device pty # Pseudo-ttys (telnet etc)
device md # Memory "disks"
# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
device bpf # Berkeley packet filter
#makeoptions CONF_CFLAGS=-fno-builtin
#options MAXDSIZ=(1024UL*1024*1024)
#options MAXSSIZ=(128UL*1024*1024)
#options DFLDSIZ=(1024UL*1024*1024)
options INCLUDE_CONFIG_FILE
#options ADAPTIVE_MUTEXES
#options MUTEX_NOINLINE
options IPSEC
options IPSEC_ESP
device pf
device pflog
device pfsync
options MROUTING
options PIM
options IPDIVERT
options IPSTEALTH
options RANDOM_IP_ID
options ACCEPT_FILTER_DATA
options ACCEPT_FILTER_HTTP
options ZERO_COPY_SOCKETS
#options HZ=100
#options PPS_SYNC
device green_saver
device crypto
device cryptodev
device rndtest
device hifn
device ubsec
options PANIC_REBOOT_WAIT_TIME=0
#options PERFMON
#options DEVICE_POLLING
options AUTO_EOI_1
device acpi
options DDB_UNATTENDED
#options DDB_TRACE
options NULLFS
options FDESCFS
The system used to crash before sync'ing disks. It seems that Nate's
recent commit has removed that crash. More information available
upon request.
Cheers,
--
Xin LI <delphij frontfree net> http://www.delphij.net/
See complete headers for GPG key and other information.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040615/
0dedae80/attachment-0001.bin
------------------------------
Message: 3
Date: Tue, 15 Jun 2004 07:28:08 +0200 (CEST)
From: Martin Blapp <m...@imp.ch>
Subject: Re: Possible Threading problem with -CURRENT / MySQL?
To: Lasse Laursen <lau...@netgroup.dk>
Cc: mike <mi...@mike2k.com>
Message-ID: <2004061507...@cvs.imp.ch>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi,
> Feel free to comment the settings. The machine is an IBM-x-something, dual
> Xeon with HTT enabled. 4 GByte of memory and a ServeRAID controller w. raid
> 10.
We have the same config as you have. IBM X-series 345, FreeBSD Current and
have no locking problems with mysql on a very busy SMP server. With HTT
enabled, we encountered the same problems you had, and some severe crashes
additionally from time to time.
Please turn off HTT and try again.. It has been told to us that the chipset
(serverworks) has buggy HTT support.
Martin
------------------------------
Message: 4
Date: Tue, 15 Jun 2004 01:59:40 -0400
From: Brian Feldman <gr...@FreeBSD.org>
Subject: ATAPICAM hangs with cdparanoia
To: cur...@FreeBSD.org
Message-ID: <2004061505...@green.homeunix.org>
Content-Type: text/plain; charset=us-ascii
Trying to rip a brand new CD with cdparanoia today, I've run into hangs
during the rip (read/seek within a track) process. Sometimes it's a
"cbwait" hang, but it seems I can also get it to lock hard at the console.
Does anyone have experience debugging ATAPICAM/ATA/CAM that will come in
handy trying to figure out why this happens?
The most information I have right now is that it was a generic IO (read)
CCB, and when I looked at the union ccb inside the process doing the
xpt read request, "entries" was 0. Doing a camcontrol reset all locked
things up at that point.
Thanks for any help,
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> gr...@FreeBSD.org \ The Power to Serve! \
Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
------------------------------
Message: 5
Date: Tue, 15 Jun 2004 08:18:19 +0200
From: Eirik Oeverby <ltn...@anduin.net>
Subject: Re: Serial console - how to reboot?
Cc: cur...@freebsd.org
Message-ID: <40CE94AB...@anduin.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Doug White wrote:
> On Sat, 12 Jun 2004, Eirik Oeverby wrote:
>
>
>>I have recently been getting the following messages on my console:
>>swap_pager: indefinite wait buffer: device: #amrd/0x20001, blkno: 1072,
>>size: 4096
>>swap_pager: indefinite wait buffer: device: #amrd/0x20001, blkno: 832,
>>size: 4096
>>swap_pager: indefinite wait buffer: device: #amrd/0x20001, blkno: 512,
>>size: 4096
>>swap_pager: indefinite wait buffer: device: #amrd/0x20001, blkno: 576,
>>size: 4096
>>swap_pager: indefinite wait buffer: device: #amrd/0x20001, blkno: 584,
>>size: 4096
>>
>>I am aware that this usually indicates a bad drive or something, but
>>given that it's a RAID volume hanging on an AMI MegaRAID controller
>>(SCSI), and none of the drives in the array are degraded, that can't
>>really be the case. I'm suspecting a bug in the driver (though freebsd
>>4.10 should be stable, right?) or a faulty cable or such.
>
>
> Yes, usually it means the device is not responding to requests. What kind
> of container is your swap in? Mirror? Stripe?
Mirror. Two 10k SCSI drives, 36gb.
Tried with each of the drives connected in single, no difference. A
reboot solves the problem for another couple of days. What would be
interesting to know is if anything actually triggers this (somehting
that can be easily reproduced) or if it's truly 'random' in terms of
weak HW (cables etc.).
Any ideas?
>
>>What would mitigate the problem for now though would be to have a way to
>>reboot the system. I'm about 1000 miles away from the box, so I can't go
>>there, but I do have access via serial console (which is where I'm
>>getting these messages).
>
>
> [...]
>
>
>>Entering the kernel debugger might help, though I'm actually not sure if
>>it's compiled into the running kernel. But if it is, how can I get to it
>>via serial?
>
>
> If you built the kernel with 'options BREAK_TO_DEBUGGER', then a serial
> break will drop to ddb. From there you could do 'call boot(0)' to attempt
> and orderly shutdown, or 'reset' to, well, reset :) There's also an
> 'ALT_BREAK_TO_DEBUGGER' option that emulates the sun alt-break -- [cr] ~
> ^B.
Okay cool. Is this going to work on -STABLE (4.10) aswell? That would
make my life somewhat easier..
>
> Without either of those, though, maybe you should call someone nearby and
> entice them to press some buttons for you :)
Done, and done. Kudos to that person ;)
Thanks again,
/Eirik
------------------------------
Message: 6
Date: Tue, 15 Jun 2004 09:31:08 +0300
From: ast...@ukrtelecom.net
Subject: Intel S875WP1-E mothterboard and -CURRENT
To: freebs...@FreeBSD.org, freebsd...@FreeBSD.org
Message-ID:
<1152675CA9EDD7118713...@hoexc010.ukrtelecom.net>
Content-Type: text/plain; charset="koi8-r"
Hello all,
w/CURRENT as of 20040614 at a box built around Intel S875WP1-E motherboard
(the one equipped with Promise SATA RAID0+1) and the new (Prescott kernel)
P-IV 3.0 strange things do happen.
Installed just yesterday on the brand-new box and when I say `reboot' it
syncs discs Ok, than from time to time (not every time) after shutting down
ACPI it not even panics (sometimes panics, sometimes - not) and freeses with
very strange appearance on the console screen - like bytes in text mode
video memory are randomly swapped making screen unreadable.
Tried to catch this into debugger but with no luck.
Any clues? What to to to diagnose this? How can I help to locate the bug?
Thanks,
Andrew
------------------------------
Message: 7
Date: Tue, 15 Jun 2004 12:22:34 +0300
From: ast...@ukrtelecom.net
Subject: HA: [backtrace] kernel dump when shutting down
To: del...@frontfree.net, ac...@FreeBSD.org, cur...@FreeBSD.org
Message-ID:
<1152675CA9EDD7118713...@hoexc010.ukrtelecom.net>
Content-Type: text/plain; charset="koi8-r"
Hello Xin,
> I got a strange problem when having HTT enabled on a P4 2.8E
> processor. When rebooting the system, after the disk sync and
> the system is going to restart, it crashes and generates a
> crashdump. Strangely, the panic message seems to be corrupted.
That's exactly what I'm seeing on P4 3.0E (yes, also `E') and Intel
S875WP1-E motherboard
ftp://download.intel.com/support/motherboards/server/s875wp1-e/tps.pdf , but
it even doesn't do crashdump, just freeses. And not each time but maybe 3-4
of 5 reboots. BTW running `halt' instead of reboot worked. Sorry I didn't
had time this night to try a kernel with debugging.
> The system used to crash before sync'ing disks. It seems that
> Nate's recent commit has removed that crash. More information
> available upon request.
Exactly. 5.2.1-R and -CURRENT of late May were also tested, they were
crashing before syncing discs, 20040614 -CURRENT crashes (freeses) after
syncing.
People say that on older P4 CPUs (Northwood core) that do not have this
problem, only on `E'-s (??? Strange enough).
WBR,
Andrew
------------------------------
Message: 8
Date: Tue, 15 Jun 2004 12:29:33 +0200
From: Ian FREISLICH <i...@hetzner.co.za>
Subject: USB woes.
To: cur...@FreeBSD.org
Message-ID: <E1BaBC9-...@hetzner.co.za>
Hi
First off, I'm quite happy to be told that my chipset is old and
buggy and will never work (like the board's ACPI implimentation).
My USB doesn't work. If I plug in a device (that works fine on my
other computer) and run 'usbdevs -v', I get the following:
[brane-dead] ~ # usbdevs -v
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x000
0), rev 1.00
port 1 powered
port 2 addr 0 should never happen!
Followed shortly by this message on the console:
uhub0: device problem, disabling port 2
If I boot with the device attached, 'usbdevs -v' pauses for quite
a long time and gives the correct probe line:
[brane-dead] ~ # usbdevs -v
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x000
0), rev 1.00
port 1 powered
port 2 addr 2: full speed, power 500 mA, config 1, Flash Reader(0xa600), DATA
FAB(0x07c4), rev 1.19
However, the device is still unusable.
The hardware is:
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xe000-0xe01f irq 10 at
device 7.2 on pci0
uhci0: [GIANT-LOCKED]
usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
Do any of the USB gurus have any ideas?
--
Ian Freislich
------------------------------
Message: 9
Date: Tue, 15 Jun 2004 13:18:39 +0200
From: Thorsten Greiner <thor...@tgreiner.net>
Subject: Re: USB woes.
To: Ian FREISLICH <i...@hetzner.co.za>
Cc: cur...@freebsd.org
Message-ID: <2004061511...@tybalt.nev.psi.de>
Content-Type: text/plain; charset="us-ascii"
* Ian FREISLICH <i...@hetzner.co.za> [2004-06-15 12:31]:
> Do any of the USB gurus have any ideas?
I hardly count as a guru, but you may want to try a little patch
derived from the NetBSD usb stack which turns on bus mastering. This
patch is needed on my little ASUS notebook to make USB work
properly. Maybe it works in your case too, since the symptoms are
similar.
The file to patch is /usr/src/sys/dev/usb/uhci_pci.c.
Cheers
-Thorsten
--
Never attribute to malice what can adequately be explained by
incompetence.
This message is digitally signed. To verify its integrity, download a copy
of GnuPG for your operating system from http://www.gnupg.org .
-------------- next part --------------
--- uhci_pci.c.orig Wed Aug 28 22:24:49 2002
+++ uhci_pci.c Wed Jan 15 00:49:13 2003
@@ -224,6 +224,7 @@
uhci_softc_t *sc = device_get_softc(self);
int rid;
int err;
+ u_int32_t csr;
rid = PCI_UHCI_BASE_REG;
sc->io_res = bus_alloc_resource(self, SYS_RES_IOPORT, &rid,
@@ -282,6 +283,11 @@
sc->sc_bus.usbrev = USBREV_UNKNOWN;
break;
}
+
+ /* Enable the device. */
+ csr = pci_read_config(self, PCIR_COMMAND, 4);
+ pci_write_config(self, PCIR_COMMAND,
+ csr | PCIM_CMD_BUSMASTEREN, 4);
err = bus_setup_intr(self, sc->irq_res, INTR_TYPE_BIO,
(driver_intr_t *) uhci_intr, sc, &sc->ih);
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040615/
427b52fc/attachment-0001.bin
------------------------------
Message: 10
Date: Tue, 15 Jun 2004 13:12:18 +0200
From: "Lasse Laursen" <lau...@netgroup.dk>
Subject: Re: Possible Threading problem with -CURRENT / MySQL?
To: "Cedric Tabary" <ced...@carpediem.fr>, freebsd...@freebsd.org
Cc: mike <mi...@mike2k.com>
Message-ID: <045c01c452cb$16f4b0b0$ce01000a@animal>
Content-Type: text/plain; charset="iso-8859-15"
Hi,
Have you had any lockups in MySQL with your setup? We have tried to disable
HTT and hopefully that will solve the problem.
Regards
--
Lasse Laursen ท VP, Hosting Technology ท NetGroup Processing Aps
St. Kongensgade 40H ท DK-1264 Copenhagen K, Denmark
Phone: +45 3370 1526 ท Fax: +45 3313 0066
- Don't be fooled by cheap finnish imitations - BSD is the One True Code
----- Original Message -----
From: "Cedric Tabary" <ced...@carpediem.fr>
To: <freebsd...@freebsd.org>
Cc: "Lasse Laursen" <lau...@netgroup.dk>; <freebsd...@freebsd.org>;
"mike" <mi...@mike2k.com>; "Petri Helenius" <pe...@he.iki.fi>
Sent: Tuesday, June 15, 2004 1:06 PM
Subject: Re: Possible Threading problem with -CURRENT / MySQL?
> On 14/06/2004 17:43, Robert Watson wrote:
> > On Mon, 14 Jun 2004, Lasse Laursen wrote:
> >
> > > Also on a SMP machine? I think that the problem is somehow related to
> > > SMP machines since the problems started when we moved to a SMP box :(
> >
> > If you haven't already, it would certainly be worth removing SMP from
the
> > kernel on that box and just running a UP kernel to confirm that it's a
> > problem using SMP. I don't doubt it's the case, but it's worth checking
> > anyway to be sure.
>
> I have a similar smp config (dell poweredge 2650, dual Xeon 2.8, RAID5)
>
> I have best performance with linux 2.4.21-smp (not tried 2.6),
> but very poor (5x less) with mysqld using libpthreads on CURRENT.
> mysqld process is always in state 'kserel' or sometimes '*Giant'
>
> http://grumly.eu.org/~ced/dmesg.txt
> http://grumly.eu.org/~ced/CED-SMP.txt (no invariants, no witness)
>
> mysqld with linuxthreads seems to work better ...
> and even better with libc_r (but using only 1 cpu)
>
> Everything with HTT disabled in bios. Enabling HTT gives even worst
> performance :/
------------------------------
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"
End of freebsd-current Digest, Vol 65, Issue 5
**********************************************
--
[35mEvariste Galois [m:
[33mฮารวสวบขืำฃฌตซฮารวพซมฆณไลๆฃฌำยอ๙ึฑวฐ...... [m
[31mก๙ ภดิด:กคๅซบฃะวิฦ bbs.ustc.edu.cn [FROM: 210.45.72.234] [m