mpt0 timed out
hi, scsi card connected to a disk array.and get follow error after less than 10 days thanks in advance. mpt0: LSILogic 1030 Ultra4 Adapter port 0xcc00-0xccff mem 0xfcef-0xfce f,0xfcee-0xfcee irq 24 at device 3.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.12.0 Trying to mount root from ufs:/dev/da1s1a mpt0: request 0xc4bf9fd0:2297 timed out for ccb 0xc6d2 (req-ccb 0xc6d2) mpt0: attempting to abort req 0xc4bf9fd0:2297 function 0 mpt0: completing timedout/aborted req 0xc4bf9fd0:2297 mpt0: abort of req 0xc4bf9fd0:0 completed mpt0: request 0xc4bfa450:2321 timed out for ccb 0xc6d17c00 (req-ccb 0xc6d17c00) mpt0: attempting to abort req 0xc4bfa450:2321 function 0 mpt0: completing timedout/aborted req 0xc4bfa450:2321 mpt0: abort of req 0xc4bfa450:0 completed mpt0: request 0xc4bfa4e0:2324 timed out for ccb 0xc4bf2000 (req-ccb 0xc4bf2000) mpt0: attempting to abort req 0xc4bfa4e0:2324 function 0 mpt0: completing timedout/aborted req 0xc4bfa4e0:2324 mpt0: abort of req 0xc4bfa4e0:0 completed mpt0: request 0xc4bfa660:2332 timed out for ccb 0xc6d19000 (req-ccb 0xc6d19000) mpt0: attempting to abort req 0xc4bfa660:2332 function 0 mpt0: completing timedout/aborted req 0xc4bfa660:2332 mpt0: abort of req 0xc4bfa660:0 completed mpt0: request 0xc4bfa780:2338 timed out for ccb 0xc6d0e800 (req-ccb 0xc6d0e800) mpt0: attempting to abort req 0xc4bfa780:2338 function 0 mpt0: completing timedout/aborted req 0xc4bfa780:2338 mpt0: abort of req 0xc4bfa780:0 completed mpt0: request 0xc4bfa810:2342 timed out for ccb 0xc6d2 (req-ccb 0xc6d2) mpt0: attempting to abort req 0xc4bfa810:2342 function 0 mpt0: completing timedout/aborted req 0xc4bfa810:2342 mpt0: abort of req 0xc4bfa810:0 completed mpt0: request 0xc4bfa840:2344 timed out for ccb 0xc6d17c00 (req-ccb 0xc6d17c00) mpt0: attempting to abort req 0xc4bfa840:2344 function 0 mpt0: completing timedout/aborted req 0xc4bfa840:2344 mpt0: abort of req 0xc4bfa840:0 completed mpt0: request 0xc4bfa870:2346 timed out for ccb 0xc4bf2000 (req-ccb 0xc4bf2000) mpt0: attempting to abort req 0xc4bfa870:2346 function 0 mpt0: completing timedout/aborted req 0xc4bfa870:2346 mpt0: abort of req 0xc4bfa870:0 completed mpt0: request 0xc4bfa900:2350 timed out for ccb 0xc6d19000 (req-ccb 0xc6d19000) mpt0: attempting to abort req 0xc4bfa900:2350 function 0 mpt0: completing timedout/aborted req 0xc4bfa900:2350 mpt0: abort of req 0xc4bfa900:0 completed mpt0: request 0xc4bfa930:2352 timed out for ccb 0xc6d0e800 (req-ccb 0xc6d0e800) mpt0: attempting to abort req 0xc4bfa930:2352 function 0 mpt0: completing timedout/aborted req 0xc4bfa930:2352 mpt0: abort of req 0xc4bfa930:0 completed mpt0: request 0xc4bfa9c0:2356 timed out for ccb 0xc6d2 (req-ccb 0xc6d2) mpt0: attempting to abort req 0xc4bfa9c0:2356 function 0 mpt0: completing timedout/aborted req 0xc4bfa9c0:2356 mpt0: abort of req 0xc4bfa9c0:0 completed mpt0: request 0xc4bfa9f0:2358 timed out for ccb 0xc6d17c00 (req-ccb 0xc6d17c00) mpt0: attempting to abort req 0xc4bfa9f0:2358 function 0 mpt0: completing timedout/aborted req 0xc4bfa9f0:2358 mpt0: abort of req 0xc4bfa9f0:0 completed mpt0: request 0xc4bfaa20:2360 timed out for ccb 0xc4bf2000 (req-ccb 0xc4bf2000) mpt0: attempting to abort req 0xc4bfaa20:2360 function 0 mpt0: completing timedout/aborted req 0xc4bfaa20:2360 mpt0: abort of req 0xc4bfaa20:0 completed mpt0: request 0xc4bfaab0:2364 timed out for ccb 0xc6d19000 (req-ccb 0xc6d19000) mpt0: attempting to abort req 0xc4bfaab0:2364 function 0 mpt0: completing timedout/aborted req 0xc4bfaab0:2364 mpt0: abort of req 0xc4bfaab0:0 completed mpt0: request 0xc4bfaae0:2366 timed out for ccb 0xc6d0e800 (req-ccb 0xc6d0e800) mpt0: attempting to abort req 0xc4bfaae0:2366 function 0 mpt0: completing timedout/aborted req 0xc4bfaae0:2366 mpt0: abort of req 0xc4bfaae0:0 completed mpt0: request 0xc4bfab70:2370 timed out for ccb 0xc6d2 (req-ccb 0xc6d2) mpt0: attempting to abort req 0xc4bfab70:2370 function 0 mpt0: completing timedout/aborted req 0xc4bfab70:2370 mpt0: abort of req 0xc4bfab70:0 completed mpt0: request 0xc4bfaba0:2372 timed out for ccb 0xc6d17c00 (req-ccb 0xc6d17c00) mpt0: attempting to abort req 0xc4bfaba0:2372 function 0 mpt0: completing timedout/aborted req 0xc4bfaba0:2372 mpt0: abort of req 0xc4bfaba0:0 completed mpt0: request 0xc4bfabd0:2374 timed out for ccb 0xc4bf2000 (req-ccb 0xc4bf2000) mpt0: attempting to abort req 0xc4bfabd0:2374 function 0 mpt0: completing timedout/aborted req 0xc4bfabd0:2374 mpt0: abort of req 0xc4bfabd0:0 completed mpt0: request 0xc4bfac60:2378 timed out for ccb 0xc6d19000 (req-ccb 0xc6d19000) mpt0: attempting to abort req 0xc4bfac60:2378 function 0 mpt0: completing timedout/aborted req 0xc4bfac60:2378 mpt0: abort of req 0xc4bfac60:0 completed mpt0: request 0xc4bfac90:2380 timed out for ccb 0xc6d0e800 (req-ccb 0xc6d0e800) mpt0: attempting to abort req 0xc4bfac90:2380 function 0 mpt0: completing timedout/aborted req 0xc4bfac90:2380 mpt0: abort of req 0xc4bfac90:0 completed mpt0:
Re: 6.2-PRE: Fatal Trap?
On 30/12/06, Ivan Voras [EMAIL PROTECTED] wrote: Karol Kwiatkowski wrote: This works: FreeBSD 6.2-PRERELEASE #0: Thu Dec 14 11:34:36 CET 2006 This doesn't: FreeBSD 6.2-PRERELEASE #0: Sat Dec 30 11:27:11 CET 2006 I'm not sure it that's all that matters, I can supply more information if needed. Yes, you'll need to send at least a kernel stack backtrace. See here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html Get it to start the debugger on panic and post the backtrace (bt). Is it possible to make it auto run debugger, then auto run backtrace then dump the output to disk so people who have no local access can get backtraces? Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.2-PRE: Fatal Trap?
Yesterda I had also a kernel trap - process (sendmail) on a Compaq Deskpro with the 6.2 Prerelease.. I revert every option in make.conf, tried Generic kernel as well..no success... Awaiting for more info And now compiling today sources On 1/1/07, Chris [EMAIL PROTECTED] wrote: On 30/12/06, Ivan Voras [EMAIL PROTECTED] wrote: Karol Kwiatkowski wrote: This works: FreeBSD 6.2-PRERELEASE #0: Thu Dec 14 11:34:36 CET 2006 This doesn't: FreeBSD 6.2-PRERELEASE #0: Sat Dec 30 11:27:11 CET 2006 I'm not sure it that's all that matters, I can supply more information if needed. Yes, you'll need to send at least a kernel stack backtrace. See here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html Get it to start the debugger on panic and post the backtrace (bt). Is it possible to make it auto run debugger, then auto run backtrace then dump the output to disk so people who have no local access can get backtraces? Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- --- [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: 6.2-PRE: Fatal Trap?
Iantcho Vassilev wrote: Yesterda I had also a kernel trap - process (sendmail) on a Compaq Deskpro with the 6.2 Prerelease.. I revert every option in make.conf, tried Generic kernel as well..no success... Awaiting for more info And now compiling today sources On 1/1/07, Chris [EMAIL PROTECTED] wrote: On 30/12/06, Ivan Voras [EMAIL PROTECTED] wrote: Karol Kwiatkowski wrote: This works: FreeBSD 6.2-PRERELEASE #0: Thu Dec 14 11:34:36 CET 2006 This doesn't: FreeBSD 6.2-PRERELEASE #0: Sat Dec 30 11:27:11 CET 2006 I'm not sure it that's all that matters, I can supply more information if needed. Yes, you'll need to send at least a kernel stack backtrace. See here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html Get it to start the debugger on panic and post the backtrace (bt). Is it possible to make it auto run debugger, then auto run backtrace then dump the output to disk so people who have no local access can get backtraces? I also ran into a trap after yesterday's cvsupdate (rpcbind traps with trap 12). Running the prvious kernel now and it works, compiling just now a new system with the today's cvsupdates (but there was no kernel stuff, so I expect no success on that). The box ist running FreeBSD fauxpas.dyn.org 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #47: Tue Dec 26 14:12:56 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/THOR amd64 The date of this uname output is the date of my last kernel build that works ... Regards, Oliver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mpt0 timed out
wsk wrote: hi, scsi card connected to a disk array.and get follow error after less than 10 days thanks in advance. You did not mentioned which release are you using... BTW. Have you tried if lowering down the connection speed (i.e. use 160M/s instead of 320M/s) would make things better? If that helps, check the cable. Cheers, -- Xin LI [EMAIL PROTECTED] http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
Re: 6.2-PRE: Fatal Trap?
Am 01.01.2007 um 12:31 schrieb Chris: Is it possible to make it auto run debugger, then auto run backtrace then dump the output to disk so people who have no local access can get backtraces? No, but you can enable crashdumps and run the debugger on the dump afterwards. Add dumpdev=AUTO to /etc/rc.conf, then run /etc/rc.d/dumpon start. When the next panic occurs, the kernel will write the dump to the configured swap space, and the system will save the dump to /var/crash on rebooting. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ kerneldebug-gdb.html on how to get a backtrace from that dump. If you're short on space in /var, and/or you have a large amount of RAM, you can set the sysctl debug.minidump to 1 to have the kernel only dump relevant portions of memory, instead of everything. This, however, is experimental in -stable, afaik. Stefan -- Stefan Bethke [EMAIL PROTECTED] Fon +49 170 346 0140 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: drm and i915 issue on Dell Latitude X1 ?
a curious thing... on my Dell Latitude X1 (scanpci -v output
at the end) the drm module did not recognise the video card
until i added this patch:
Index: drm_pciids.h
===
RCS file: /home/ncvs/src/sys/dev/drm/drm_pciids.h,v
retrieving revision 1.2.2.3
diff -u -r1.2.2.3 drm_pciids.h
--- drm_pciids.h17 May 2006 07:40:11 - 1.2.2.3
+++ drm_pciids.h1 Jan 2007 18:04:08 -
@@ -286,6 +286,7 @@
{0x8086, 0x2572, 0, Intel i865G GMCH}, \
{0x8086, 0x2582, 0, Intel i915G}, \
{0x8086, 0x2592, 0, Intel i915GM}, \
+ {0x8086, 0x2792, 0, Intel i915GML}, \
{0x8086, 0x2772, 0, Intel i945G}, \
{0x8086, 0x27A2, 0, Intel i945GM}, \
{0, 0, 0, NULL}
The board has two PCI IDs, 0x2592 (at PCI 0:2:0,
which is the one that drives the LCD screen) and 0x2792
(perhaps this is a dual-head card ?).
Apparently the drm module only looks for the latter even though it is
not the one that drives the LCD screen.
I am not sure what is the appropriate fix here, whether the
drm module should look for all PCI IDs of the card,
or something else.
Further info below: the output of scanpci -v and the relevant
lines from /var/log/Xorg.0.log
cheers
luigi
% scanpci -v
pci bus 0x cardnum 0x00 function 0x00: vendor 0x8086 device 0x2590
Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM
Controller
CardVendor 0x1028 card 0x01a3 (Dell, Card unknown)
STATUS0x2090 COMMAND 0x0006
CLASS 0x06 0x00 0x00 REVISION 0x03
BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x00
BYTE_00x00 BYTE_1 0x50 BYTE_2 0x00 BYTE_3 0xf0
pci bus 0x cardnum 0x02 function 0x00: vendor 0x8086 device 0x2592
Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller
CardVendor 0x1028 card 0x01a3 (Dell, Card unknown)
STATUS0x0090 COMMAND 0x0007
CLASS 0x03 0x00 0x00 REVISION 0x03
BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00
BASE0 0xdff0 addr 0xdff0 MEM
BASE1 0xec39 addr 0xec38 I/O
BASE2 0xc008 addr 0xc000 MEM PREFETCHABLE
BASE3 0xdfec addr 0xdfec MEM
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x10
pci bus 0x cardnum 0x02 function 0x01: vendor 0x8086 device 0x2792
Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller
CardVendor 0x1028 card 0x01a3 (Dell, Card unknown)
STATUS0x0090 COMMAND 0x0007
CLASS 0x03 0x80 0x00 REVISION 0x03
BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00
BASE0 0xdff8 addr 0xdff8 MEM
pci bus 0x cardnum 0x1c function 0x00: vendor 0x8086 device 0x2660
Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1
STATUS0x0010 COMMAND 0x0007
CLASS 0x06 0x04 0x00 REVISION 0x03
HEADER0x81 LATENCY 0x00
PRIBUS0x00 SECBUS 0x01 SUBBUS 0x01
SECLT 0x00 SECSTATUS 0x2000
IOBASE0xf000 IOLIM 0x0fff
NOPREFETCH_MEMBASE 0xdfd0 MEMLIM 0xdfdf
PREFETCH_MEMBASE 0xfff0 MEMLIM 0x000f
NO_FAST_B2B NO_SEC_BUS_RST NO_M_ABRT NO_VGA_EN NO_ISA_EN SERR_EN NO_PERR_EN
pci bus 0x cardnum 0x1d function 0x00: vendor 0x8086 device 0x2658
Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1
CardVendor 0x1028 card 0x01a3 (Dell, Card unknown)
STATUS0x0280 COMMAND 0x0005
CLASS 0x0c 0x03 0x00 REVISION 0x03
BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00
BASE4 0xbf81 addr 0xbf80 I/O
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x10
pci bus 0x cardnum 0x1d function 0x01: vendor 0x8086 device 0x2659
Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2
CardVendor 0x1028 card 0x01a3 (Dell, Card unknown)
STATUS0x0280 COMMAND 0x0005
CLASS 0x0c 0x03 0x00 REVISION 0x03
BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x00
BASE4 0xbf61 addr 0xbf60 I/O
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x02 INT_LINE 0x11
pci bus 0x cardnum 0x1d function 0x02: vendor 0x8086 device 0x265a
Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3
CardVendor 0x1028 card 0x01a3 (Dell, Card unknown)
STATUS0x0280 COMMAND 0x0005
CLASS 0x0c 0x03 0x00 REVISION 0x03
BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x00
BASE4 0xbf41 addr 0xbf40 I/O
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x03 INT_LINE 0x12
pci bus 0x cardnum 0x1d function 0x03: vendor 0x8086 device 0x265b
Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4
CardVendor 0x1028 card 0x01a3 (Dell, Card unknown)
STATUS0x0280 COMMAND 0x0005
CLASS 0x0c 0x03 0x00 REVISION 0x03
BIST 0x00 HEADER 0x00 LATENCY 0x00 CACHE 0x00
BASE4 0xbf21 addr 0xbf20 I/O
MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x04 INT_LINE 0x13
pci bus 0x cardnum 0x1d function 0x07: vendor 0x8086 device
Re: freebsd-stable Digest, Vol 188, Issue 10
Help
--
Stephen Liss
847-858-6549 (mobile)
Yahoo! IM: ic_stephen_liss
-Original Message-
From: [EMAIL PROTECTED]
Date: Mon, 1 Jan 2007 12:00:42
To:freebsd-stable@freebsd.org
Subject: freebsd-stable Digest, Vol 188, Issue 10
Send freebsd-stable mailing list submissions to
freebsd-stable@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than Re: Contents of freebsd-stable digest...
Today's Topics:
1. Audio (Record) not functioning... (record interrupt timeout)
(Ben H.)
2. Re: BIND-9.3.2 (from 5.5-STABLE) segfault under load...
(Chuck Swiger)
3. 6.2-RC2 atkbd0 freezes system (Gardner Bell)
4. mpt0 timed out (wsk)
5. Re: 6.2-PRE: Fatal Trap? (Chris)
--
Message: 1
Date: Sat, 30 Dec 2006 19:51:51 -0800 (PST)
From: Ben H. [EMAIL PROTECTED]
Subject: Audio (Record) not functioning... (record interrupt timeout)
To: questions FBSD freebsd-questions@FreeBSD.ORG, Stable FBSD
freebsd-stable@FreeBSD.ORG
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ascii
Thanks in advance for any help you can provide... On reply please cc my email
address.
http://www.bsdforums.org/forums/showthread.php?t=45514 [HISTORY]
http://lists.freebsd.org/pipermail/...rch/003877.html [Related Link]
I am trying to get Skype or Vonage softphone(via wine) working on my notebook.
My problem is getting the input from the mic to the application.
The mic is working because I can talk and hear the sound via the
external speakers. If (on command line mixer) I turn the rec and
igain to 0 the I CAN still hear any sound I make via the mic on the
attached speakers. If I turn mic to 0 then I cannot hear any sound I
make via the mic on the attached speakers.
Here is the error I am seeing on the system console:
pcm0:record:0:dsp0.0: record interrupt timeout, channel dead
Here are my settings:
[EMAIL PROTECTED] uname -a
FreeBSD sony.family.hom 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #2: Tue Dec 19
16:55:50 EST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SONY01 i386
[EMAIL PROTECTED] cat /dev/sndstat
FreeBSD Audio Driver (newpcm)
Installed devices:
pcm0: Acer Labs M5451 at io 0x1800 irq 9 kld snd_t4dwave (4p/1r/4v channels
duplex default)
[EMAIL PROTECTED] dmesg | grep pcm
pcm0: Acer Labs M5451 port 0x1800-0x18ff mem 0xe810-0xe8100fff at device
6.0 on pci0
pcm0: Yamaha YMF753 AC97 Codec
pcm0: [GIANT-LOCKED]
pcm0:record:0:dsp0.0: record interrupt timeout, channel dead
pcm0:record:0:dsp0.0: record interrupt timeout, channel dead
[EMAIL PROTECTED] sysctl hw.snd
hw.snd.report_soft_formats: 1
hw.snd.targetirqrate: 32
hw.snd.verbose: 1
hw.snd.maxautovchans: 4
hw.snd.unit: 0
hw.snd.pcm0.buffersize: 4096
hw.snd.pcm0.vchans: 4
More info at: http://www.bsdforums.org/forums/showthread.php?t=46469
STRBen
strbenjr{a}yahoo.com
ben_hacker{a}inter-op.net
-- -- --
http://www.coeba.org
http://www.inter-op.net
--
Message: 2
Date: Sun, 31 Dec 2006 11:45:43 -0500
From: Chuck Swiger [EMAIL PROTECTED]
Subject: Re: BIND-9.3.2 (from 5.5-STABLE) segfault under load...
To: Doug Barton [EMAIL PROTECTED]
Cc: FreeBSD mailing list freebsd-stable@freebsd.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Doug Barton wrote:
Chuck Swiger wrote:
Hi--
I had named segfault a day or so ago under high load (adnslogres -c
200 against a webserver logfile) after logging the following:
Hard to tell if your problem here is related to running on 5.5 or not,
but of course recommendation number one is to consider upgrading to
6.x. Recommendation number two is to upgrade BIND to 9.3.3, preferably
by upgrading to 6.2-RC2, or by upgrading to the head of RELENG_5, or
as a last resort by using the port, with or without the option to
replace the base BIND.
Noted, thanks. I've been following 6-STABLE on a pair of test machines, but
I've recently been bitten by whatever the bug was earlier this week or last
which resulted in daemon processes dying early in the boot, so I'd prefer to
be a bit more conservative until 6-STABLE settles down more.
[ ... ]
Dec 28 03:38:56 daemon.notice pi named[1853]: enforced
delegation-only for 'AR' (ctina.ar/A/IN) from 137.39.1.3#53
If you're using this option, please make sure that you know why you
are using it, and what the potential side effects are. That discussion
is off topic for this list, but feel free to take it up on
[EMAIL PROTECTED] if you wish.
The primary function of the machine in question is a SMTP relay; a secondary
Re: drm and i915 issue on Dell Latitude X1 ?
JFYI Luigi Rizzo wrote: a curious thing... on my Dell Latitude X1 (scanpci -v output at the end) the drm module did not recognise the video card until i added this patch: This is odd. I have the same vendor/device IDs on the ThinkPad T43 and yet X.org's DRM loads fine here without this patch: pci bus 0x cardnum 0x02 function 0x00: vendor 0x8086 device 0x2592 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller pci bus 0x cardnum 0x02 function 0x01: vendor 0x8086 device 0x2792 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller With the following difference: CardVendor 0x1014 card 0x0582 (IBM, Card unknown) FreeBSD empiric.lon.incunabulum.net 6.2-RC1 FreeBSD 6.2-RC1 #2: Sun Dec 24 11:20:48 GMT 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/EMPIRIC i386 empiric:/var/log % dmesg | grep drm drmsub0: Intel i915GM: (child of agp_i810.c) on agp0 info: [drm] AGP at 0x9008 0MB info: [drm] Initialized i915 1.4.0 20060119 DRM, GLX modules show up in xdpyinfo. By the way, there doesn't appear to be an 'ident' field for drm_pciids.h in the binaries, though I'm on 1.2.2.3. glxgears runs as expected (~260fps in default scale at 1024x768x32bpp). I tested with an application by running games/gltron, which claims 25-40fps in 512x384 full-screen. It still seemed jerky. [Except after an ACPI suspend/resume via zzz, in which case, it cains the CPU on resume and only achieves 60fps-150fps, and acpi_video cannot attach, and gltron is jerky/doesn't work properly.] Regards, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
twe on amd64 hangs
Hi, We have recently bought some new Supermicro P8SCT boards with 3ware 8006LP2's and are using the amd64 port, however if I put the 3ware in the PCI-X slot it hangs probing the disks (eg at the end of the boot if it's in the kernel, or at load time if I use kldload). If I put it in a 32 bit slot it works fine. I tried reducing the PCI-X clock down to 100MHz but it made no difference. If I boot an i386 kernel it works fine (I tried 6.2RC2). Unfortunately the hang is solid and I can't break into the debugger :( Any help appreciated, I am happy to test patches, etc.. Thanks. -- 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADS UP: FreeBSD 4.11, 6.0 EoLs coming soon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Everyone, On January 31st, FreeBSD 4.11 and FreeBSD 6.0 will have reached their End of Life dates and will no longer be supported by the FreeBSD Security Team. Users of either of these FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5, FreeBSD 6.1, or the upcoming FreeBSD 6.2 before that date. Discussion concerning FreeBSD releases which are no longer supported should take place on the [EMAIL PROTECTED] mailing list. For an explanation of the rationale behind the EoL of FreeBSD 4.11, please see my earlier mailing list post on this subject: http://lists.freebsd.org/pipermail/freebsd-security/2006-October/004111.html The current supported branches and expected EoL dates are: ++ | Branch | Release | Type | Release date | Estimated EoL | |---++++-| |RELENG_4 |n/a |n/a |n/a |January 31, 2007 | |---++++-| |RELENG_4_11|4.11-RELEASE|Extended|January 25, 2005|January 31, 2007 | |---++++-| |RELENG_5 |n/a |n/a |n/a |May 31, 2008 | |---++++-| |RELENG_5_5 |5.5-RELEASE |Extended|May 25, 2006|May 31, 2008 | |---++++-| |RELENG_6 |n/a |n/a |n/a |last release + 2y| |---++++-| |RELENG_6_0 |6.0-RELEASE |Normal |November 4, 2005|January 31, 2007 | |---++++-| |RELENG_6_1 |6.1-RELEASE |Extended|May 9, 2006 |May 31, 2008 | ++ Once it is released, FreeBSD 6.2 will be supported until January 31, 2008. Colin Percival FreeBSD Security Officer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFmd8BFdaIBMps37IRAk3DAKCKK69yVuOce4g2O97XH5OjPWrAvgCeO2sb 1cXUw0P3RUN11PLHmj6kN+Y= =tb5N -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
