Re: Panic on 8-STABLE at boot
thx pluknet. my second panic appear today on 3 recent 8-stable amd64 machine after doing 8 ~ 10h of zfs receive. 2010/6/30 pluknet : > On 29 June 2010 19:58, Mickaël Maillot wrote: >> i've got a panic with zfs only machine so i decided to build a witness kernel >> and just after the first reboot: >> http://img190.imageshack.us/img190/3314/panicflowtable2.jpg >> >> the second boot: no prob >> >> uname -a >> FreeBSD cg196.security-mail.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE >> #8: Tue Jun 29 14:30:12 CEST 2010 >> r...@cg196.security-mail.net:/usr/obj/usr/src/sys/SECUMAIL amd64 >> >> dmesg: http://freelooser.fr/freebsd/dmesg.cg196.2010-06-29.log >> conf:http://freelooser.fr/freebsd/SECUMAIL.txt > > This afaik was fixed a while ago in CURRENT: > http://svn.freebsd.org/viewvc/base?view=revision&revision=207303 > > I wonder it's not MFC'ed yet. > > -- > wbr, > pluknet > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Why is NFSv4 so slow? (root/toor)
On Wed, 30 Jun 2010, Ian Smith wrote:
I wondered whether this might be a Linux thing. On my 7.2 system,
% find /usr/src -name "*.[ch]" -exec grep -Hw getpwuid {} \; > file
returns 195 lines, many in the form getpwuid(getuid()), in many base and
contrib components - including id(1), bind, sendmail etc - that could be
nondeterministic if getpwuid(0) ever returned other than root.
Just one mention of 'toor' in /usr/src/usr.sbin/makefs/compat/pwcache.c
Not claiming to know how the lookups in /usr/src/lib/libc/gen/getpwent.c
work under the hood, but this does seem likely a non-issue on FreeBSD.
I remember it causing some confusion while testing, but I can't remember
when or where. It might have been Linux or I might have been logged in as
"toor" or
I think I will hardcode the "root" case in nfsuserd, just to be safe.
(I also migt have editted /etc/passwd and reordered entries without
paying attention to it.)
rick
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with ATA_CAM support in RELENG_8
xc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with ATA_CAM support in RELENG_8
On Wed, Jun 30, 2010 at 04:52:22PM -0400, Paul Mather wrote: > I thought ICH8 supported AHCI, but maybe it's only ICH8R that does? No, not necessarily. There are ICHxx (non-ICHxxR) models which definitely provide AHCI (ex. ICHxxM for their Mobile chipsets; yes, many laptops do have AHCI capability). Thus there are many different sub-models of ICH8, in addition to different perf/chip revisions of ICH8. Specification details: http://www.intel.com/assets/pdf/datasheet/313056.pdf http://www.intel.com/design/chipsets/specupdt/313057.htm Dell very likely chose not to engineer this particular motherboard to not provide AHCI capability (Option ROM space (usually included with the system BIOS), PCI and ICH8 register setups (done by the BIOS), etc.)). I know Gigabyte has done this with some of their boards as well. If you have concerns that your motherboard provides features that you can't use, you need to contact Dell. > I'm assuming that "subclass = ATA" means the controller can't operate > in AHCI mode. The BIOS setting is also confusing. It has two > options, "Normal" and "Legacy." "Normal" mode says, "The hard drive > controller is configured for native mode. This mode provides the > highest drive performance and most flexibility." I guess I > misinterpreted "native mode" to be AHCI mode. "Native", "Normal", and "Enhanced" are all terms used to describe the controller operating in standard SATA (non-AHCI) fashion. Dell's in-BIOS description is nothing but schmooze; it's not the same as AHCI. "Legacy" just means the controller appears and operates purely in PATA-esque mode, so that you can use SATA drives on systems which don't have SATA chipset drivers (ex. MS-DOS). To get an idea of what an AHCI-capable board offers via the BIOS, you should review the following manual for a Supermicro ICH7-based system. This chipset is older than yours, chosen for sake of example. See Chapter 7-3, section "Main Setup Features": http://www.supermicro.com/manuals/superserver/1U/MNL-0813.pdf Furthermore, I can assure you that the Dell OptiPlex 745 Mini-Tower offers AHCI capability, and toggling its use via the system BIOS. You won't find it mentioned in Dell's "Tech Specs" PDF about this though. I realise this is not the system you have, but I'm simply pointing out that it's a board manufacturer decision whether or not to provide the capability, and that their decision obviously changed over the years. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with ATA_CAM support in RELENG_8
Paul Mather wrote: >> PS: ATA_STATIC_ID is useless when ATA_CAM option enabled. > > Thank you (and Jeremy Chadwick) for the help and information. The kernel > configuration options I used above were taken from a VirtualBox FreeBSD/amd64 > install I have that I converted over to ATA_CAM when the code first went into > RELENG_8 and it wasn't exactly clear at the time what options were absolutely > required. (I'm not even sure that "options ATA_CAM" is needed any more, > given "device ahci" implies it.) `options ATA_CAM` enables CAM wrapper for legacy drivers, which gave you adaX devices instead of adX. It doesn't give major benefits, just unifies behavior. > I thought ICH8 supported AHCI, but maybe it's only ICH8R that does? All ICH8 support AHCI, though not all BIOSes initialize them respectively. The only benefit of ICH8R is a port multipliers support, though it also seems to be artificial limitation - I've seen BIOS allowing it on regular ICH8. > I'm assuming that "subclass = ATA" means the controller can't operate in AHCI > mode. Yes. At least it is not configured to do so. > The BIOS setting is also confusing. It has two options, "Normal" and > "Legacy." "Normal" mode says, "The hard drive controller is configured for > native mode. This mode provides the highest drive performance and most > flexibility." I guess I misinterpreted "native mode" to be AHCI mode. "Native" mode means that ATA controllers works as normal PCI device. In "Legacy" mode controller uses legacy ISA I/O ports and IRQs. -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with ATA_CAM support in RELENG_8
On Jun 30, 2010, at 1:38 PM, Alexander Motin wrote: >> To enable ATA_CAM AHCI support, I included this in my kernel config file: >> >> # ATA and ATAPI devices >> options ATA_CAM >> device ahci >> device atacore >> device atapci >> options ATA_STATIC_ID # Static device numbering >> >> Is this the correct way to enable ATA_CAM AHCI support? I tried >> initially including just "options ATA_CAM" and "device ahci" but the >> resultant kernel would not probe my disk drive as ada0. > > Your controller seems to not report AHCI support. In such case legacy > mode driver attaches to it. But as soon as you have no `device ataintel` > line, only generic driver was there, limited by UDMA2 mode. > > PS: ATA_STATIC_ID is useless when ATA_CAM option enabled. Thank you (and Jeremy Chadwick) for the help and information. The kernel configuration options I used above were taken from a VirtualBox FreeBSD/amd64 install I have that I converted over to ATA_CAM when the code first went into RELENG_8 and it wasn't exactly clear at the time what options were absolutely required. (I'm not even sure that "options ATA_CAM" is needed any more, given "device ahci" implies it.) >> Does my problem lie with my kernel config or is the Dell Optiplex 745 >> BIOS brain dead when it comes to AHCI native support? The only option >> it appears to have in the BIOS is "Normal" and "Legacy" when it comes >> to the SATA controller mode. > > Your controller is not identified as AHCI: > >> atapci0: port >> 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf,0xecc0-0xeccf >> irq 20 at device 31.2 on pci0 >> atapci0: [ITHREAD] >> ata2: on atapci0 >> ata2: [ITHREAD] >> ata3: on atapci0 >> ata3: [ITHREAD] >> atapci1: port >> 0xfe40-0xfe47,0xfe50-0xfe53,0xfe60-0xfe67,0xfe70-0xfe73,0xfed0-0xfedf,0xecd0-0xecdf >> irq 20 at device 31.5 on pci0 >> atapci1: [ITHREAD] >> ata4: on atapci1 >> ata4: [ITHREAD] >> ata5: on atapci1 >> ata5: [ITHREAD] > > You may check `pciconf -lvcb` output. For ICH8 with AHCI you should see > there something like: > ah...@pci0:0:31:2: class=0x010601 card=0xa00c14ff chip=0x28298086 > rev=0x03 hdr=0x00 >vendor = 'Intel Corporation' >device = 'Mobile SATA AHCI Controller' >class = mass storage >subclass = SATA >bar [10] = type I/O Port, range 32, base 0xe880, size 8, enabled >bar [14] = type I/O Port, range 32, base 0xe800, size 4, enabled >bar [18] = type I/O Port, range 32, base 0xe480, size 8, enabled >bar [1c] = type I/O Port, range 32, base 0xe400, size 4, enabled >bar [20] = type I/O Port, range 32, base 0xe080, size 32, enabled >bar [24] = type Memory, range 32, base 0xfeaff800, size 2048, enabled >cap 05[80] = MSI supports 4 messages enabled with 4 messages >cap 01[70] = powerspec 3 supports D0 D3 current D0 >cap 12[a8] = SATA Index-Data Pair > > Pay attention to "subclass = SATA". Then that's where my problem lies: atap...@pci0:0:31:2:class=0x01018f card=0x01da1028 chip=0x28208086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'SATA IDE Controller:4 port (82801HB/HR/HH/HO)' class = mass storage subclass = ATA bar [10] = type I/O Port, range 32, base 0xfe00, size 8, enabled bar [14] = type I/O Port, range 32, base 0xfe10, size 4, enabled bar [18] = type I/O Port, range 32, base 0xfe20, size 8, enabled bar [1c] = type I/O Port, range 32, base 0xfe30, size 4, enabled bar [20] = type I/O Port, range 32, base 0xfec0, size 16, enabled bar [24] = type I/O Port, range 32, base 0xecc0, size 16, enabled cap 01[70] = powerspec 3 supports D0 D3 current D0 atap...@pci0:0:31:5:class=0x010185 card=0x01da1028 chip=0x28258086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801H (ICH8 Family) 2 port SATA Controller' class = mass storage subclass = ATA bar [10] = type I/O Port, range 32, base 0xfe40, size 8, enabled bar [14] = type I/O Port, range 32, base 0xfe50, size 4, enabled bar [18] = type I/O Port, range 32, base 0xfe60, size 8, enabled bar [1c] = type I/O Port, range 32, base 0xfe70, size 4, enabled bar [20] = type I/O Port, range 32, base 0xfed0, size 16, enabled bar [24] = type I/O Port, range 32, base 0xecd0, size 16, enabled cap 01[70] = powerspec 3 supports D0 D3 current D0 I thought ICH8 supported AHCI, but maybe it's only ICH8R that does? I'm assuming that "subclass = ATA" means the controller can't operate in AHCI mode. The BIOS setting is also confusing. It has two options, "Normal" and "Legacy." "Normal" mode says, "The hard drive controller is configured for native mode. This mode provides the highest drive performance and most flexibility." I guess I misinterpreted "native mode" to be AHCI mode. Thanks again for the help and for clearing things up. Cheer
Re: Fwd: Problems with ATA_CAM support in RELENG_8
Garrett Cooper wrote: > I am running FreeBSD/amd64 RELENG_8 on a Dell Optiplex 745. The hard > drive in the system is SATA and I have "Normal", not "Legacy" SATA > support enabled in the BIOS. (BIOS is V2.6.4.) I am assuming this > will enable native AHCI mode for the drive. > > I built a kernel with ATA_CAM support, but for some reason the SATA > drive is probing at slow, UDMA2, speeds: > > ada0 at ata2 bus 0 scbus0 target 0 lun 0 > ada0: ATA-7 SATA 2.x device > ada0: 33.300MB/s transfers (UDMA2, PIO 8192bytes) > ada0: 152587MB (31250 512 byte sectors: 16H 63S/T 16383C) > When I run "camcontrol identify" on the drive, it states the drive is > capable of UDMA6 speeds: > > backup# camcontrol identify ada0 > PIO supported PIO4 > DMA supported WDMA2 UDMA6 > Native Command Queuing (NCQ) yes 32 tags > > So, why the slower speed? Also, "camcontrol identify" states the > drive supports NCQ with up to 32 tags supported, yet "camcontrol tags > ada0" reports only 1 device opening, not 32 as I would expect: > > backup# camcontrol tags ada0 > (pass0:ata2:0:0:0): device openings: 1 Speed, number of tags and other options limited by lowest of device and controller capabilities. > To enable ATA_CAM AHCI support, I included this in my kernel config file: > > # ATA and ATAPI devices > options ATA_CAM > device ahci > device atacore > device atapci > options ATA_STATIC_ID # Static device numbering > > Is this the correct way to enable ATA_CAM AHCI support? I tried > initially including just "options ATA_CAM" and "device ahci" but the > resultant kernel would not probe my disk drive as ada0. Your controller seems to not report AHCI support. In such case legacy mode driver attaches to it. But as soon as you have no `device ataintel` line, only generic driver was there, limited by UDMA2 mode. PS: ATA_STATIC_ID is useless when ATA_CAM option enabled. > Does my problem lie with my kernel config or is the Dell Optiplex 745 > BIOS brain dead when it comes to AHCI native support? The only option > it appears to have in the BIOS is "Normal" and "Legacy" when it comes > to the SATA controller mode. Your controller is not identified as AHCI: > atapci0: port > 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf,0xecc0-0xeccf > irq 20 at device 31.2 on pci0 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > atapci1: port > 0xfe40-0xfe47,0xfe50-0xfe53,0xfe60-0xfe67,0xfe70-0xfe73,0xfed0-0xfedf,0xecd0-0xecdf > irq 20 at device 31.5 on pci0 > atapci1: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ata5: on atapci1 > ata5: [ITHREAD] You may check `pciconf -lvcb` output. For ICH8 with AHCI you should see there something like: ah...@pci0:0:31:2: class=0x010601 card=0xa00c14ff chip=0x28298086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile SATA AHCI Controller' class = mass storage subclass = SATA bar [10] = type I/O Port, range 32, base 0xe880, size 8, enabled bar [14] = type I/O Port, range 32, base 0xe800, size 4, enabled bar [18] = type I/O Port, range 32, base 0xe480, size 8, enabled bar [1c] = type I/O Port, range 32, base 0xe400, size 4, enabled bar [20] = type I/O Port, range 32, base 0xe080, size 32, enabled bar [24] = type Memory, range 32, base 0xfeaff800, size 2048, enabled cap 05[80] = MSI supports 4 messages enabled with 4 messages cap 01[70] = powerspec 3 supports D0 D3 current D0 cap 12[a8] = SATA Index-Data Pair Pay attention to "subclass = SATA". -- Alexander Motin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with ATA_CAM support in RELENG_8
On Wed, Jun 30, 2010 at 12:07:54PM -0400, Paul Mather wrote: > I am running FreeBSD/amd64 RELENG_8 on a Dell Optiplex 745. The hard drive > in the system is SATA and I have "Normal", not "Legacy" SATA support enabled > in the BIOS. (BIOS is V2.6.4.) I am assuming this will enable native AHCI > mode for the drive. That isn't correct. Some Dell OptiPlex systems explicitly have an AHCI option in their BIOS for enabling/disabling AHCI. I do not believe the 745 offers this capability, which means no AHCI is available. (We use these OptiPlex models at my workplace so I'm familiar with them) > I built a kernel with ATA_CAM support, but for some reason the SATA drive is > probing at slow, UDMA2, speeds: I don't know anything about this option, but the "common" way to get ATA to utilise SCSI CAM is to enable AHCI in one's system BIOS and load the ahci.ko (not ataahci.ko) driver using /boot/loader.conf (ahci_load="yes") or "load ahci" from the loader "OK" prompt. That's literally all you need. In your case since you don't have AHCI available, you're probably going to have to stick to using standard ata(4) (read: remove ATA_CAM and ahci from your kernel configuration). Be aware ahci.ko IS NOT the same thing as ataahci.ko. The latter adds AHCI support but via the classic ata(4) layer (meaning: AHCI without SCSI CAM. This also lacks NCQ support, but does gain you hot-swap capability). > Does my problem lie with my kernel config or is the Dell Optiplex 745 > BIOS brain dead when it comes to AHCI native support? The only option > it appears to have in the BIOS is "Normal" and "Legacy" when it comes > to the SATA controller mode. It's not "brain dead". "Normal" is not the same thing as AHCI. "Normal" tells the controller to run in standard SATA mode, "Legacy" causes the controller to emulate classic PATA (literally you'll see PATA controllers show up on IRQs 14 and 15, etc.). Validation that your system doesn't have AHCI enabled/doesn't have AHCI available is here: > atapci0: port > 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf,0xecc0-0xeccf > irq 20 at device 31.2 on pci0 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > atapci1: port > 0xfe40-0xfe47,0xfe50-0xfe53,0xfe60-0xfe67,0xfe70-0xfe73,0xfed0-0xfedf,0xecd0-0xecdf > irq 20 at device 31.5 on pci0 > atapci1: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ata5: on atapci1 > ata5: [ITHREAD] An AHCI-enabled controller, with a system using ahci.ko, will look like this: ahci0: port 0x1c50-0x1c57,0x1c44-0x1c47,0x1c48-0x1c4f,0x1c40-0x1c43,0x18e0-0x18ff mem 0xdc000800-0xdc000fff irq 17 at device 31.2 on pci0 ahci0: [ITHREAD] ahci0: AHCI v1.20 with 6 3Gbps ports, Port Multiplier supported ahcich0: at channel 0 on ahci0 ahcich0: [ITHREAD] ahcich1: at channel 1 on ahci0 ahcich1: [ITHREAD] ahcich2: at channel 2 on ahci0 ahcich2: [ITHREAD] ahcich3: at channel 3 on ahci0 ahcich3: [ITHREAD] ahcich4: at channel 4 on ahci0 ahcich4: [ITHREAD] ahcich5: at channel 5 on ahci0 ahcich5: [ITHREAD] -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Problems with ATA_CAM support in RELENG_8
I am running FreeBSD/amd64 RELENG_8 on a Dell Optiplex 745. The hard drive in the system is SATA and I have "Normal", not "Legacy" SATA support enabled in the BIOS. (BIOS is V2.6.4.) I am assuming this will enable native AHCI mode for the drive. I built a kernel with ATA_CAM support, but for some reason the SATA drive is probing at slow, UDMA2, speeds: ada0 at ata2 bus 0 scbus0 target 0 lun 0 ada0: ATA-7 SATA 2.x device ada0: 33.300MB/s transfers (UDMA2, PIO 8192bytes) ada0: 152587MB (31250 512 byte sectors: 16H 63S/T 16383C) When I run "camcontrol identify" on the drive, it states the drive is capable of UDMA6 speeds: backup# camcontrol identify ada0 pass0: ATA-7 SATA 2.x device pass0: 33.300MB/s transfers (UDMA2, PIO 8192bytes) protocol ATA/ATAPI-7 SATA 2.x device model ST3160812AS firmware revision 3.ADJ serial number 5LS8PPDD cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 268435455 sectors LBA48 supported 31250 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 Feature Support EnableValue Vendor read ahead yes yes write cacheyes yes flush cacheyes yes overlapno Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 65278/0xFEFE automatic acoustic management yes yes 254/0xFE208/0xD0 media status notification no no power-up in Standbyno no write-read-verify no no 0/0x0 unload no no free-fall no no data set management (TRIM) no So, why the slower speed? Also, "camcontrol identify" states the drive supports NCQ with up to 32 tags supported, yet "camcontrol tags ada0" reports only 1 device opening, not 32 as I would expect: backup# camcontrol tags ada0 (pass0:ata2:0:0:0): device openings: 1 To enable ATA_CAM AHCI support, I included this in my kernel config file: # ATA and ATAPI devices options ATA_CAM device ahci device atacore device atapci options ATA_STATIC_ID # Static device numbering Is this the correct way to enable ATA_CAM AHCI support? I tried initially including just "options ATA_CAM" and "device ahci" but the resultant kernel would not probe my disk drive as ada0. Does my problem lie with my kernel config or is the Dell Optiplex 745 BIOS brain dead when it comes to AHCI native support? The only option it appears to have in the BIOS is "Normal" and "Legacy" when it comes to the SATA controller mode. I've attached my full kernel config and dmesg at the end of this e-mail. Cheers, Paul. Kernel config: # # GENERIC -- Generic kernel configuration file for FreeBSD/amd64 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/amd64/conf/GENERIC,v 1.531.2.13 2010/05/02 06:24:17 imp Exp $ cpu HAMMER ident VPN # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. # Use the following to compile in values accessible to the kernel # through getenv() (or kenv(1) in userland). The format of the file # is 'variable=value', see kenv(1) # # env "GENERIC.env" #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for
Re: kernel issues with 8 STABLE
On Wed, Jun 30, 2010 at 01:16:34PM +0100, Free BSD wrote: > Dear List Members > > I have recently installed 8 STABLE and built my custom kernel, but > still getting these in my pciconf list > > no...@pci0:0:3:0: class=0x078000 card=0x02761028 > chip=0x2e148086 rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel Active Client Manager HECI Device > (PCIVEN_8086&DEV_2E14&SUBSYS_3035103C&REV_03B1B68)' > class = simple comms > > > no...@pci0:0:3:3: class=0x070002 card=0x02761028 > chip=0x2e178086 rev=0x03 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel PCI Serial Port (CC_0700)' > class = simple comms > subclass = UART > > > I have > device uart# Generic UART driver > in my custom kernel, so I would expect uart devices to be detected > and usable -- however, they are not. Are you including "device puc" in your device list? puc connects PCI-based serial/parallel devices to uart/sio and ppc. Please see the uart(4) man page. > Also, even though I have custom keyboard in my kernel configuration, > whenever I boot into single user mode I get US layout (it works fine > when in multi-user mode). This is probably normal. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
kernel issues with 8 STABLE
Dear List Members I have recently installed 8 STABLE and built my custom kernel, but still getting these in my pciconf list no...@pci0:0:3:0: class=0x078000 card=0x02761028 chip=0x2e148086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Active Client Manager HECI Device (PCIVEN_8086&DEV_2E14&SUBSYS_3035103C&REV_03B1B68)' class = simple comms no...@pci0:0:3:3: class=0x070002 card=0x02761028 chip=0x2e178086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel PCI Serial Port (CC_0700)' class = simple comms subclass = UART I have device uart# Generic UART driver in my custom kernel, so I would expect uart devices to be detected and usable -- however, they are not. Also, even though I have custom keyboard in my kernel configuration, whenever I boot into single user mode I get US layout (it works fine when in multi-user mode). I am using a Dell Optiplex 960 series machine. I have googled as much as I can, and also visited the intel website for further information -- no luck so far. Any pointer to possible solution is highly appreciated Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: pde.demotions counts even if pg_ps disabled
On Wednesday 30 June 2010 7:28:50 am pluknet wrote: > HI. > > This is 7.3-RELEASE-p1 right after boot. > Looks like pmap_demote_pde is not properly protected w/ pg_ps_enabled. The direct map always uses superpages, but we may demote a superpage in the direct map due to conflict caching attributes (all PCI BARs are mapped UC for example). -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Kernel panic in pppoe_findsession (ng_pppoe.c)
Hello!
Yestarday I've got 4 kernel panics with the same problem - page fault
while in kernel mode, in netgraph pppoe module.
I've defined, that fault produce pppoe_findsession() function - see below.
Here is the contents of /var/crash/info.5 file:
Dump header from device /dev/gpt/swap
Architecture: amd64
Architecture Version: 2
Dump Length: 1490821120B (1421 MB)
Blocksize: 512
Dumptime: Tue Jun 29 14:35:53 2010
Hostname: cloud
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 8.1-PRERELEASE #18: Sun Jun 6 00:32:09 EEST 2010
r...@cloud:/usr/obj/usr/src/sys/CLOUD
Panic String: page fault
Dump Parity: 4273635620
Bounds: 5
Dump Status: good
I can give more information, if you need (core.txt.5 file, kernel
config file, etc).
And here is kgdb log:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x8064ed050
fault code = supervisor read data, page not present
instruction pointer = 0x20:0x803c2869
stack pointer = 0x28:0xff803bee7880
frame pointer = 0x28:0xff803bee78c0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 0 (nfe0 taskq)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 19d12h24m25s
Physical memory: 2024 MB
Dumping 1421 MB: 1406 1390 1374 1358 1342 1326 1310 1294 1278 1262
1246 1230 1214 1198 1182 1166 1150 1134 1118 1102 1086 1070 1054 1038
1022 1006 990 974 958 942 926 910 894 878 862 846 830 814 798 782 766
750 734 718 702 686 670 654 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
Reading symbols from /boot/kernel/vesa.ko...Reading symbols from
/boot/kernel/vesa.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/vesa.ko
Reading symbols from /boot/kernel/linux.ko...Reading symbols from
/boot/kernel/linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/kernel/sound.ko...Reading symbols from
/boot/kernel/sound.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/sound.ko
Reading symbols from /boot/kernel/snd_hda.ko...Reading symbols from
/boot/kernel/snd_hda.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/snd_hda.ko
Reading symbols from /boot/kernel/acpi_asus.ko...Reading symbols from
/boot/kernel/acpi_asus.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi_asus.ko
Reading symbols from /boot/kernel/acpi_aiboost.ko...Reading symbols
from /boot/kernel/acpi_aiboost.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi_aiboost.ko
Reading symbols from /boot/modules/nvidia.ko...done.
Loaded symbols for /boot/modules/nvidia.ko
Reading symbols from /boot/kernel/procfs.ko...Reading symbols from
/boot/kernel/procfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/procfs.ko
Reading symbols from /boot/kernel/pseudofs.ko...Reading symbols from
/boot/kernel/pseudofs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/pseudofs.ko
Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from
/boot/kernel/linprocfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linprocfs.ko
Reading symbols from /boot/kernel/linsysfs.ko...Reading symbols from
/boot/kernel/linsysfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linsysfs.ko
Reading symbols from /boot/kernel/blank_saver.ko...Reading symbols
from /boot/kernel/blank_saver.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/blank_saver.ko
Reading symbols from /usr/local/modules/rtc.ko...done.
Loaded symbols for /usr/local/modules/rtc.ko
Reading symbols from /boot/kernel/if_gif.ko...Reading symbols from
/boot/kernel/if_gif.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/if_gif.ko
#0 doadump () at pcpu.h:223
223 __asm __volatile("movq %%gs:0,%0" : "=r" (td));
(kgdb) list *0x803c2869
0x803c2869 is in pppoe_findsession
(/usr/src/sys/netgraph/ng_pppoe.c:567).
562 uint16_thash = SESSHASH(session);
563 sessp sp = NULL;
564
565 mtx_lock(&privp->sesshash[hash].mtx);
566 LIST_FOREACH(sp, &privp->sesshash[hash].head, sessions) {
567 if (sp->Session_ID == session &&
568 bcmp(sp->pkt_hdr.eh.ether_dhost,
569 wh->eh.ether_shost, ETHER_ADDR_LEN) == 0) {
570 break;
571 }
(kgdb) backtrace
#0 doadump () at pcpu.h:223
#1 0x802e7cd9 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:416
#2 0x802e810c in panic (fmt=0x80581c64 "%s") at
/usr/src/sys/kern/kern_shutdown.c:590
#3 0x8051dfd8 in trap_fatal (frame=0xff0002415ba0,
eva=Variable "eva" is not available.
) at /usr/src/sys/amd64/amd64/tra
pde.demotions counts even if pg_ps disabled
HI. This is 7.3-RELEASE-p1 right after boot. Looks like pmap_demote_pde is not properly protected w/ pg_ps_enabled. # sysctl vm.pmap vm.pmap.pmap_collect_active: 0 vm.pmap.pmap_collect_inactive: 0 vm.pmap.pv_entry_spare: 1421 vm.pmap.pv_entry_allocs: 686316 vm.pmap.pv_entry_frees: 675473 vm.pmap.pc_chunk_tryfail: 0 vm.pmap.pc_chunk_frees: 5392 vm.pmap.pc_chunk_allocs: 5465 vm.pmap.pc_chunk_count: 73 vm.pmap.pv_entry_count: 10843 vm.pmap.pde.promotions: 0 vm.pmap.pde.p_failures: 0 vm.pmap.pde.mappings: 0 vm.pmap.pde.demotions: 5 vm.pmap.shpgperproc: 200 vm.pmap.pv_entry_max: 4264612 vm.pmap.pg_ps_enabled: 0 # uptime 3:25PM up 19 mins, 2 users, load averages: 0.00, 0.00, 0.01 -- wbr, pluknet ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic on 8-STABLE at boot
On 29 June 2010 19:58, Mickaël Maillot wrote: > i've got a panic with zfs only machine so i decided to build a witness kernel > and just after the first reboot: > http://img190.imageshack.us/img190/3314/panicflowtable2.jpg > > the second boot: no prob > > uname -a > FreeBSD cg196.security-mail.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE > #8: Tue Jun 29 14:30:12 CEST 2010 > r...@cg196.security-mail.net:/usr/obj/usr/src/sys/SECUMAIL amd64 > > dmesg: http://freelooser.fr/freebsd/dmesg.cg196.2010-06-29.log > conf:http://freelooser.fr/freebsd/SECUMAIL.txt This afaik was fixed a while ago in CURRENT: http://svn.freebsd.org/viewvc/base?view=revision&revision=207303 I wonder it's not MFC'ed yet. -- wbr, pluknet ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Panic on 8-STABLE at boot
and after 9 hours, another panic: http://freelooser.fr/freebsd/deadlock.jpg any help is appreciated 2010/6/29 Mickaël Maillot : > i've got a panic with zfs only machine so i decided to build a witness kernel > and just after the first reboot: > http://img190.imageshack.us/img190/3314/panicflowtable2.jpg > > the second boot: no prob > > uname -a > FreeBSD cg196.security-mail.net 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE > #8: Tue Jun 29 14:30:12 CEST 2010 > r...@cg196.security-mail.net:/usr/obj/usr/src/sys/SECUMAIL amd64 > > dmesg: http://freelooser.fr/freebsd/dmesg.cg196.2010-06-29.log > conf:http://freelooser.fr/freebsd/SECUMAIL.txt > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
