freebsd-amd64 Digest, Vol 119, Issue 5
Lin, Shih-Min
sl151 at waikato.ac.nz
Fri Sep 16 14:27:24 PDT 2005
-----Original Message-----
From: owner-freebsd-amd64 at freebsd.org on behalf of freebsd-amd64-request at freebsd.org
Sent: Sat 9/17/2005 12:00 AM
To: freebsd-amd64 at freebsd.org
Subject: freebsd-amd64 Digest, Vol 119, Issue 5
Send freebsd-amd64 mailing list submissions to
freebsd-amd64 at freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
or, via email, send a message with subject or body 'help' to
freebsd-amd64-request at freebsd.org
You can reach the person managing the list at
freebsd-amd64-owner at freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-amd64 digest..."
Today's Topics:
1. amd64 Radeon 9000 nForce3 250 agp support - Yes and No
(K. Wieland)
2. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
(Ganael Laplanche)
3. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
(Jung-uk Kim)
4. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
(Adam Gregoire)
5. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
(John-Mark Gurney)
6. building/porting linux SIS965L driver (Jeff D. Hamann)
7. acpi/ohci/rsdt wtf? (Jeff D. Hamann)
8. Re: acpi/ohci/rsdt wtf? (John Baldwin)
9. [PATCH] agp(4) for ULi M1689/nVidia nForce3 (Jung-uk Kim)
10. amd64/86199: Missed AMD64 motherboard (Mike Smith)
11. Problem with hp zv6000 (pier)
12. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
(Ganael Laplanche)
13. Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
(Ganael Laplanche)
14. Re: amd64/86199: Missed AMD64 motherboard (Adriaan de Groot)
15. Re: acpi/ohci/rsdt wtf? (Bruno Ducrot)
16. Re: FAST_IPSEC on EMT64 / AMD64 (Michael VInce)
----------------------------------------------------------------------
Message: 1
Date: Thu, 15 Sep 2005 09:22:26 -0500
From: K. Wieland <wieland.k at gmail.com>
Subject: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
To: Jung-uk Kim <jkim at FreeBSD.org>
Cc: freebsd-amd64 at freebsd.org
Message-ID: <4efa8eff718166b299f7d6a317011a37 at gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Jung-uk and fellow amd64 subscribers,
I tried upgrading to 6.0B4 last night, after spending several nights
reading the documentation. I have been reading and am subscribed to
the amd64 list, so I figure I might as well try it!
First, I mounted the new 6.0_B4 CD under 5.4 and tried to run the
sysinstall that way as outlined in the docs (I don't remember where,
but I can get the reference). sysinstall (v6.0 B4) would not run,
complaining about some libraries not being present (I had a previous
version of the libraries it was looking for, so I made sym links (bad,
I know!) but it failed looking for the next library, so I deleted the
symlink, and decided to reboot with the CD.
I rebooted, went into fixit and did a dmesg. AGP was there, and the
device /dev/agpart existed. I was happy, and decided to upgrade to 6.0
beta4 using the upgrade option in sysinstall. I didn't remember the
mount points for the various file systems so I had to boot back into
5.4 and write it all down (it would be nice if this was in the
documentation)!
Anyway, I upgraded and rebooted. The first thing I noticed was the
generic kernel detected my com port, but didn't create a /dev/cuaa0 (I
dial up for internet). And, because I want sound and my TV card (bktr)
I decided to customize the kernel like I had done in 5.4.
So, I did a diff of the GENERIC to the custom kernel, MYKERNEL, and
found that it was basically the same (MYKERNEL had the sound, bktr, and
agp with several extraneous things commented out). I built the new
kernel, installed it and rebooted. AGP was gone! I thought, well
maybe you don't need "device agp" in the kernel (I didn't see it in the
GENERIC, and agp loaded with that), so I tried that...still no AGP.
Then, I decided to use the GENERIC and see if that worked---still no
AGP. But, if I boot up with the CD, AGP is back!
The confusing part to me is that the uname -a still gives me RELENG5.4
-p7. That seems strange to me. The ps command also didn't work as
expected (just prints the headers, none of the processes).
I read that if your sources don't match your kernel, you can get weird
stuff like this, so I went to cvsup to the most recent. BUT, in the
/usr/share/examples/standard-cvsup files it still had RELENG 5.4. I
went ahead and cvsup'ed anyway.
I don't have anything critical on the drive, so I am tempted to wipe it
clean and reinstall (ala windows style) but I would really like to
understand what is going on here.
I am CCing the freebsd-amd64 list in case they have some insights, too.
Thanks,
Kristopher Wieland
Graduate Student
Washington University in St. Louis
Dept. of Physics- Compton Hall
On Sep 13, 2005, at 11:40 AM, Jung-uk Kim wrote:
> On Tuesday 13 September 2005 12:19 pm, K Wieland wrote:
>> Thanks again for the quick reply.
>
> No problem.
>
>> Is there a "best method" for installing another version? I would
>> rather not loose the kernel config, etc. Is it best to just wipe
>> everything and start over?
>
> cvsup, buildworld, installworld, mergemaster... But it's quite a
> hassle for new users. First of all, if the only problem for you is
> the agp, try booting from the ISO, select Fixit, select CD/DVD, then
> you will get shell. You can see if agp is probed/attached from
> there. If that's there, you have two choices:
>
> 1. Upgrade.
> 2. Patch kernel to add support for the AGP device.
>
> If you choose option 2, the only thing you really need is this:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_amd64.c.diff?
> r1=1.6&r2=1.7
>
> Good luck,
>
> JK
>
>> I'll give it a try and see how it goes!
>>
>> Kristopher
>>
>> On Sep 13, 2005, at 10:17 AM, Jung-uk Kim wrote:
>>> On Tuesday 13 September 2005 11:06 am, K. Wieland wrote:
>>>> Thank you for your quick reply!
>>>>
>>>> Yes, I am using 5.4 Release. I guess since I was just starting
>>>> out with Freebsd, I'd go with "release" vs. stable or current.
>>>>
>>>> Do you know an ftp site for getting the images for 6.0 beta4?
>>>> Or should I just cvsup to it? You can tell I am new, new new!
>>>
>>> ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/6.0/
>>>
>>> JK
>>>
>>>> Thanks,
>>>>
>>>> Kristopher
>>>>
>>>> On Sep 13, 2005, at 9:54 AM, Jung-uk Kim wrote:
>>>>> On Tuesday 13 September 2005 10:42 am, K. Wieland wrote:
>>>>>> Hello Jung-uk!
>>>>>>
>>>>>> I was reading through the archives of the freebsd-amd64
>>>>>> archives (I am a new Freebsd user) and I have the exact same
>>>>>> problem that you and Geneal talked about.
>>>>>>
>>>>>> I also have a radeon 9000 with a nForce3 250 chipset that does
>>>>>> not detect the agp, even though it is in the kernel.
>>>>>>
>>>>>> Did you ever get this issue resolved?
>>>>>
>>>>> Are you using FreeBSD 5.4 or something? Try 6.0BETA4. It
>>>>> should be fine.
>>>>>
>>>>> JK
>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>> Kristopher Wieland
>
------------------------------
Message: 2
Date: Thu, 15 Sep 2005 15:53:13 +0000
From: "Ganael Laplanche" <ganael.laplanche at martymac.com>
Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
To: K.Wieland <wieland.k at gmail.com>, Jung-uk Kim <jkim at FreeBSD.org>
Cc: freebsd-amd64 at freebsd.org
Message-ID: <20050915155131.M39844 at martymac.com>
Content-Type: text/plain; charset=iso-8859-1
Hi all,
I tried beta-1 with Radeon 9000 pro and nforce3-250gb, but system hangs during X
bootup. I had to go back to the goold old driver from 5.x :(
The PR is here : http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84015
Any clue ?
Ganaël LAPLANCHE
ganael.laplanche at martymac.com
http://www.martymac.com
Tel : (+33)6.84.03.57.24.
---------- Original Message -----------
From: K.Wieland <wieland.k at gmail.com>
To: Jung-uk Kim <jkim at FreeBSD.org>
Cc: freebsd-amd64 at freebsd.org
Sent: Thu, 15 Sep 2005 09:22:26 -0500
Subject: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
> Jung-uk and fellow amd64 subscribers,
>
> I tried upgrading to 6.0B4 last night, after spending several nights
> reading the documentation. I have been reading and am subscribed to
> the amd64 list, so I figure I might as well try it!
>
> First, I mounted the new 6.0_B4 CD under 5.4 and tried to run the
> sysinstall that way as outlined in the docs (I don't remember where,
> but I can get the reference). sysinstall (v6.0 B4) would not run,
> complaining about some libraries not being present (I had a previous
> version of the libraries it was looking for, so I made sym links (bad,
> I know!) but it failed looking for the next library, so I deleted the
> symlink, and decided to reboot with the CD.
>
> I rebooted, went into fixit and did a dmesg. AGP was there, and the
> device /dev/agpart existed. I was happy, and decided to upgrade to
> 6.0 beta4 using the upgrade option in sysinstall. I didn't remember
> the mount points for the various file systems so I had to boot back
> into
> 5.4 and write it all down (it would be nice if this was in the
> documentation)!
>
> Anyway, I upgraded and rebooted. The first thing I noticed was the
> generic kernel detected my com port, but didn't create a /dev/cuaa0 (I
> dial up for internet). And, because I want sound and my TV card
> (bktr) I decided to customize the kernel like I had done in 5.4.
>
> So, I did a diff of the GENERIC to the custom kernel, MYKERNEL, and
> found that it was basically the same (MYKERNEL had the sound, bktr,
> and agp with several extraneous things commented out). I built the
> new kernel, installed it and rebooted. AGP was gone! I thought,
> well maybe you don't need "device agp" in the kernel (I didn't see it
> in the GENERIC, and agp loaded with that), so I tried that...still no
> AGP. Then, I decided to use the GENERIC and see if that worked---
> still no AGP. But, if I boot up with the CD, AGP is back!
>
> The confusing part to me is that the uname -a still gives me RELENG5.4
> -p7. That seems strange to me. The ps command also didn't work as
> expected (just prints the headers, none of the processes).
>
> I read that if your sources don't match your kernel, you can get weird
> stuff like this, so I went to cvsup to the most recent. BUT, in the
> /usr/share/examples/standard-cvsup files it still had RELENG 5.4. I
> went ahead and cvsup'ed anyway.
>
> I don't have anything critical on the drive, so I am tempted to wipe
> it clean and reinstall (ala windows style) but I would really like to
> understand what is going on here.
>
> I am CCing the freebsd-amd64 list in case they have some insights, too.
>
> Thanks,
>
> Kristopher Wieland
> Graduate Student
> Washington University in St. Louis
> Dept. of Physics- Compton Hall
> On Sep 13, 2005, at 11:40 AM, Jung-uk Kim wrote:
>
> > On Tuesday 13 September 2005 12:19 pm, K Wieland wrote:
> >> Thanks again for the quick reply.
> >
> > No problem.
> >
> >> Is there a "best method" for installing another version? I would
> >> rather not loose the kernel config, etc. Is it best to just wipe
> >> everything and start over?
> >
> > cvsup, buildworld, installworld, mergemaster... But it's quite a
> > hassle for new users. First of all, if the only problem for you is
> > the agp, try booting from the ISO, select Fixit, select CD/DVD, then
> > you will get shell. You can see if agp is probed/attached from
> > there. If that's there, you have two choices:
> >
> > 1. Upgrade.
> > 2. Patch kernel to add support for the AGP device.
> >
> > If you choose option 2, the only thing you really need is this:
> >
> > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_amd64.c.diff?
> > r1=1.6&r2=1.7
> >
> > Good luck,
> >
> > JK
> >
> >> I'll give it a try and see how it goes!
> >>
> >> Kristopher
> >>
> >> On Sep 13, 2005, at 10:17 AM, Jung-uk Kim wrote:
> >>> On Tuesday 13 September 2005 11:06 am, K. Wieland wrote:
> >>>> Thank you for your quick reply!
> >>>>
> >>>> Yes, I am using 5.4 Release. I guess since I was just starting
> >>>> out with Freebsd, I'd go with "release" vs. stable or current.
> >>>>
> >>>> Do you know an ftp site for getting the images for 6.0 beta4?
> >>>> Or should I just cvsup to it? You can tell I am new, new new!
> >>>
> >>> ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-amd64/6.0/
> >>>
> >>> JK
> >>>
> >>>> Thanks,
> >>>>
> >>>> Kristopher
> >>>>
> >>>> On Sep 13, 2005, at 9:54 AM, Jung-uk Kim wrote:
> >>>>> On Tuesday 13 September 2005 10:42 am, K. Wieland wrote:
> >>>>>> Hello Jung-uk!
> >>>>>>
> >>>>>> I was reading through the archives of the freebsd-amd64
> >>>>>> archives (I am a new Freebsd user) and I have the exact same
> >>>>>> problem that you and Geneal talked about.
> >>>>>>
> >>>>>> I also have a radeon 9000 with a nForce3 250 chipset that does
> >>>>>> not detect the agp, even though it is in the kernel.
> >>>>>>
> >>>>>> Did you ever get this issue resolved?
> >>>>>
> >>>>> Are you using FreeBSD 5.4 or something? Try 6.0BETA4. It
> >>>>> should be fine.
> >>>>>
> >>>>> JK
> >>>>>
> >>>>>> Thank you,
> >>>>>>
> >>>>>> Kristopher Wieland
> >
>
> _______________________________________________
> freebsd-amd64 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe at freebsd.org"
------- End of Original Message -------
------------------------------
Message: 3
Date: Thu, 15 Sep 2005 12:19:53 -0400
From: Jung-uk Kim <jkim at FreeBSD.org>
Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
To: "Ganael Laplanche" <ganael.laplanche at martymac.com>
Cc: freebsd-amd64 at FreeBSD.org, "K.Wieland" <wieland.k at gmail.com>
Message-ID: <200509151219.55989.jkim at FreeBSD.org>
Content-Type: text/plain; charset="utf-8"
On Thursday 15 September 2005 11:53 am, Ganael Laplanche wrote:
> Hi all,
>
> I tried beta-1 with Radeon 9000 pro and nforce3-250gb, but system
> hangs during X bootup. I had to go back to the goold old driver
> from 5.x :(
The 'good old' driver uses generic nForce AGP interface. If the
driver really works, I will be surprised. I admit agp_amd64.c
requires more work (esp. chipset-specific handling including nForce)
but I had no time/hardware.
Anyway you have to make sure agp(4) really works for you.
http://docs.freebsd.org/cgi/mid.cgi?200405181244.28716.jkim
> The PR is here :
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84015
>
> Any clue ?
Have you tried xorg-server-snap? If it doesn't work, can you try
this?
http://people.freebsd.org/~jkim/xorg-server-snap.diff
Thanks,
Jung-uk Kim
> Gana�l LAPLANCHE
> ganael.laplanche at martymac.com
> http://www.martymac.com
> Tel : (+33)6.84.03.57.24.
------------------------------
Message: 4
Date: Thu, 15 Sep 2005 12:29:37 -0400
From: Adam Gregoire <ebola at psychoholics.org>
Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
To: freebsd-amd64 at freebsd.org
Cc: "K.Wieland" <wieland.k at gmail.com>
Message-ID:
<1126801777.7412.7.camel at S0106c0ffeec0ffee.su.shawcable.net>
Content-Type: text/plain
Hello, this chipset is not supported for agpgart, the nforce3 250
chipset has the code needed to detect the gart but is missing
functionality needed for proper operation.
See also, PR amd64/71753 and the following thread
http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004300.html
Regards,
--
Adam Gregoire <ebola at psychoholics.org>
------------------------------
Message: 5
Date: Thu, 15 Sep 2005 10:19:04 -0700
From: John-Mark Gurney <gurney_j at resnet.uoregon.edu>
Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
To: "K. Wieland" <wieland.k at gmail.com>
Cc: freebsd-amd64 at FreeBSD.org, Jung-uk Kim <jkim at FreeBSD.org>
Message-ID: <20050915171904.GT793 at funkthat.com>
Content-Type: text/plain; charset=us-ascii
K. Wieland wrote this message on Thu, Sep 15, 2005 at 09:22 -0500:
> Anyway, I upgraded and rebooted. The first thing I noticed was the
> generic kernel detected my com port, but didn't create a /dev/cuaa0 (I
> dial up for internet). And, because I want sound and my TV card (bktr)
> I decided to customize the kernel like I had done in 5.4.
These have been renamed to match the tty versions.. look for /dev/cuad0
instead...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
------------------------------
Message: 6
Date: Thu, 15 Sep 2005 10:27:16 -0700
From: "Jeff D. Hamann" <jeff.hamann at forestinformatics.com>
Subject: building/porting linux SIS965L driver
To: <freebsd-questions at freebsd.org>, <freebsd-amd64 at freebsd.org>
Message-ID: <001d01c5ba1a$bc83fdd0$0a00a8c0 at rodan>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
I'm building (or trying to build) an amd64 FreeBSD machine to replace my
FreeBSD 4.4 server. I purchased an ASUS Vintage-AE1 MB that uses the
following chipsets:
Northbridge: SiS760GX
Southbridge: SiS965L
I've not been able to get the on-board NIC to light up, so I purchased
another NIC which works alright. It's bothering me too much that the chipset
isn't supported (http://www.freebsd.org/platforms/amd64/motherboards.html)
but many of the other ASUS MB chipsets are. This seems like a great machine
and I suspect there are plenty more machines that will be using this
barebones box as a starting place (of course, I'll be wrong in a year
anyways). I've found the linux driver for the on-board NIC and since I've
never ported a driver for FreeBSD, I'm trying to figure out how much work it
will be to port the driver to FreeBSD-6.0? I've snooped around in the
/usr/src/sys/pci/if_sis.c
/usr/src/sys/pci/if_sisreg.h
6.0Beta4 files to simply examine the bsd code. To my novice eyes, the files
look completely different from the linux drivers and I'm not sure I can
takle this myself since I've never done anything like this. Can someone help
me through this process, or is this not worth the trouble?
Jeff.
---
Jeff D. Hamann
Forest Informatics, Inc.
PO Box 1421
Corvallis, Oregon USA 97339-1421
541-754-1428
jeff.hamann at forestinformatics.com
www.forestinformatics.com
------------------------------
Message: 7
Date: Thu, 15 Sep 2005 12:41:18 -0700
From: "Jeff D. Hamann" <jeff.hamann at forestinformatics.com>
Subject: acpi/ohci/rsdt wtf?
To: <freebsd-amd64 at freebsd.org>
Message-ID: <000b01c5ba2d$7a6fa940$0a00a8c0 at rodan>
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
reply-type=original
I'm curious what the
acpi_perf0: invalid _PSS package
messages are all about and why there are so many? I'm also curious about the
EHCI stuff. My bios has some settings which state:
"stop ehci in ohci handler handover"
the comments for the setting stats:
"stops the ehci host controller during ohci handvoer call. the is needed for
installing Oses that does not support ehci host controllers"
and I'm not sure what it means and I don't know if FreeBSD-6beta4 supports
it.
Also, there's another setting about "acpi apic support" where the hint
states:
"include acpi apic table pointer to rsdt pointer list"
Wha?
I've included my dmesg output for diagnostics.
$ dmesg
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 6.0-BETA4 #1: Fri Sep 16 06:41:12 PDT 2005
root at bobby.forestinformatics.com:/usr/obj/usr/src/sys/GENERIC
WARNING: WITNESS option enabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3000+ (1995.01-MHz K8-class CPU)
Origin = "AuthenticAMD" Id = 0xf4a Stepping = 10
Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
AMD Features=0xe0500800<SYSCALL,NX,MMX+,LM,3DNow+,3DNow>
real memory = 1039400960 (991 MB)
avail memory = 991444992 (945 MB)
ACPI APIC Table: <A M I OEMAPIC >
ioapic0 <Version 1.4> irqs 0-23 on motherboard
acpi0: <A M I OEMRSDT> on motherboard
acpi0: Power Button (fixed)
pci_link0: <ACPI PCI Link LNKA> irq 0 on acpi0
pci_link1: <ACPI PCI Link LNKB> irq 11 on acpi0
pci_link2: <ACPI PCI Link LNKC> irq 5 on acpi0
pci_link3: <ACPI PCI Link LNKD> irq 10 on acpi0
pci_link4: <ACPI PCI Link LNKE> irq 11 on acpi0
pci_link5: <ACPI PCI Link LNKF> irq 5 on acpi0
pci_link6: <ACPI PCI Link LNKG> irq 11 on acpi0
pci_link7: <ACPI PCI Link LNKH> irq 5 on acpi0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
acpi_perf0: invalid _PSS package
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 2.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <SiS 965 UDMA133 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.5 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pci0: <multimedia, audio> at device 2.7 (no driver attached)
ohci0: <SiS 5571 USB controller> mem 0xfbefc000-0xfbefcfff irq 20 at device
3.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: <SiS 5571 USB controller> on ohci0
usb0: USB revision 1.0
uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1: <SiS 5571 USB controller> mem 0xfbefd000-0xfbefdfff irq 21 at device
3.1 on pci0
ohci1: [GIANT-LOCKED]
usb1: OHCI version 1.0, legacy support
usb1: <SiS 5571 USB controller> on ohci1
usb1: USB revision 1.0
uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ohci2: <SiS 5571 USB controller> mem 0xfbefe000-0xfbefefff irq 22 at device
3.2 on pci0
ohci2: [GIANT-LOCKED]
usb2: OHCI version 1.0, legacy support
usb2: <SiS 5571 USB controller> on ohci2
usb2: USB revision 1.0
uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfbeff000-0xfbefffff irq 23
at device 3.3 on pci0
ehci0: [GIANT-LOCKED]
usb3: EHCI version 1.0
usb3: companion controllers, 3 ports each: usb0 usb1 usb2
usb3: <EHCI (generic) USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: SiS EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub3: 8 ports with 8 removable, self powered
pci0: <network, ethernet> at device 4.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> at device 7.0 on pci0
pci3: <ACPI PCI bus> on pcib3
rl0: <D-Link DFE-530TX+ 10/100BaseTX> port 0xa800-0xa8ff mem
0xfbefb800-0xfbefb8ff irq 17 at device 10.0 on pci0
miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> on miibus0
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:11:95:24:60:b3
acpi_button0: <Power Button> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
fdc0: <floppy drive controller (FDE)> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on
acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: <ECP parallel printer port> port 0x378-0x37f,0x778-0x77f irq 7 drq 3
on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
orm0: <ISA Option ROM> at iomem 0xc0000-0xc7fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 1995008941 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 190782MB <WDC WD2000JB-00GVA0 08.02D08> at ata0-master UDMA100
acd0: DVDR <SONY DVD RW DW-Q28A/KYS2> at ata1-master UDMA66
Trying to mount root from ufs:/dev/ad0s1a
$
jeff.
---
Jeff D. Hamann
Forest Informatics, Inc.
PO Box 1421
Corvallis, Oregon USA 97339-1421
541-754-1428
jeff.hamann at forestinformatics.com
www.forestinformatics.com
------------------------------
Message: 8
Date: Thu, 15 Sep 2005 16:00:49 -0400
From: John Baldwin <jhb at FreeBSD.org>
Subject: Re: acpi/ohci/rsdt wtf?
To: freebsd-amd64 at freebsd.org, "Jeff D. Hamann"
<jeff.hamann at forestinformatics.com>
Message-ID: <200509151600.50793.jhb at FreeBSD.org>
Content-Type: text/plain; charset="iso-8859-1"
On Thursday 15 September 2005 03:41 pm, Jeff D. Hamann wrote:
> I'm curious what the
>
> acpi_perf0: invalid _PSS package
>
> messages are all about and why there are so many? I'm also curious about
> the EHCI stuff. My bios has some settings which state:
>
> "stop ehci in ohci handler handover"
>
> the comments for the setting stats:
>
> "stops the ehci host controller during ohci handvoer call. the is needed
> for installing Oses that does not support ehci host controllers"
Leave it off. FreeBSD 6 includes the ehci(4) driver by default as you can see
in your dmesg.
> and I'm not sure what it means and I don't know if FreeBSD-6beta4 supports
> it.
>
> Also, there's another setting about "acpi apic support" where the hint
> states:
>
> "include acpi apic table pointer to rsdt pointer list"
>
> Wha?
Leave that on. It looks like it already is. Having this on is what let's us
find the ACPI APIC Table as mentioned here:
> ACPI APIC Table: <A M I OEMAPIC >
> ioapic0 <Version 1.4> irqs 0-23 on motherboard
--
John Baldwin <jhb at FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve" = http://www.FreeBSD.org
------------------------------
Message: 9
Date: Thu, 15 Sep 2005 19:57:04 -0400
From: Jung-uk Kim <jkim at FreeBSD.org>
Subject: [PATCH] agp(4) for ULi M1689/nVidia nForce3
To: freebsd-amd64 at FreeBSD.org
Message-ID: <200509151957.24837.jkim at FreeBSD.org>
Content-Type: text/plain; charset="us-ascii"
If you have any of these, please test and let me know.
http://people.freebsd.org/~jkim/agp_amd64.diff
FYI, agp(4) GART test is here:
http://people.freebsd.org/~jkim/testgart.c
Thanks,
Jung-uk Kim
------------------------------
Message: 10
Date: Fri, 16 Sep 2005 03:48:18 GMT
From: Mike Smith <perlfu at gmail.com>
Subject: amd64/86199: Missed AMD64 motherboard
To: freebsd-gnats-submit at FreeBSD.org
Message-ID: <200509160348.j8G3mIH5015714 at www.freebsd.org>
>Number: 86199
>Category: amd64
>Synopsis: Missed AMD64 motherboard
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-amd64
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Sep 16 03:50:08 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Mike Smith
>Release: FreeBSD 5.4-STABLE
>Organization:
none
>Environment:
FreeBSD insomnia.localnet.net 5.4-STABLE FreeBSD 5.4-STABLE #5: Thu Sep 15 15:24:53 CDT 2005 perlfu at insomnia.localnet.net:/usr/obj/usr/src/sys/INSOMNIA amd64
>Description:
MSI K8M NEO-V is not listed in the section covering amd64 compatible motherboards. Also there seems to be a lack of support for the VT8237 SATA Raid controller. I can use the drive, but there seems to be some shaky behavior coming from it. I've seen random kernel panics related to the drive, (don't have them to paste currently, but if you give me some time I'm sure it will randomly pop up some time soon). It also defers for background fsck'ing even if the drives were properly unmounted. The onboard sound also results in hard locks, randomly, especially when vchans are enabled. I'm using the VT8237 Audio as well. Any help with this would be greatly appreciated.
>How-To-Repeat:
Errors occur fairly randomly, and present themselves in different manners each time. The drive can do everything from cause a panic, (same one each time, seems to indicate inconsistancies on the drive). Also shows itself by constantly appearing as improperly dismounted, even when shutdown, or reboot was called. Sound causes hard locks quite frequently and randomly as far as I can tell. It only hard locks when I try to play multiple sounds at once. Have tried with and without hw.snd.maxautovchans=4, tried a few of the patches that came out on the lists to no avail, no error messages, or logs can be found with anything pertaining to the sound issue, apparently it is generally a 100% hard lock, keyboard failure and all.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
------------------------------
Message: 11
Date: Fri, 16 Sep 2005 07:58:04 +0200
From: pier <pierg75 at yahoo.it>
Subject: Problem with hp zv6000
To: freebsd-amd64 at freebsd.org
Message-ID: <432A5EEC.9020202 at yahoo.it>
Content-Type: text/plain; charset="iso-8859-15"
Hi all.
I'm having so many troubles that i have almost gave up to install
FreeBSD on this notebook (amd64 3500+, chipset ATI Xpress200).
I tried all the releases, from 5.3 to 6.0-BETA4 but no one works.
I read something here that could be interesting:
http://forums.bit-tech.net/showthread.php?t=94652
I tried to look for this functions in the code, but it looks like in
the new releases they don't exist.
So...now i can boot with the kernel installed with this personalized
boot-cd
(http://blackk.union.edu/~black/freebsd/5_3_30Dec2004-amd64-miniinst.iso)
but i can't update my kernel with a newer one.
What can I do?
Thank you
Pier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 256 bytes
Desc: OpenPGP digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20050916/9b858fc7/signature-0001.bin
------------------------------
Message: 12
Date: Fri, 16 Sep 2005 08:04:28 +0000
From: "Ganael Laplanche" <ganael.laplanche at martymac.com>
Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
To: Jung-uk Kim <jkim at FreeBSD.org>
Cc: freebsd-amd64 at FreeBSD.org, "K.Wieland" <wieland.k at gmail.com>
Message-ID: <20050916080048.M77239 at martymac.com>
Content-Type: text/plain; charset=iso-8859-1
> On Thursday 15 September 2005 11:53 am, Ganael Laplanche wrote:
> > Hi all,
> >
> > I tried beta-1 with Radeon 9000 pro and nforce3-250gb, but system
> > hangs during X bootup. I had to go back to the goold old driver
> > from 5.x :(
>
> The 'good old' driver uses generic nForce AGP interface. If the
> driver really works, I will be surprised. I admit agp_amd64.c
> requires more work (esp. chipset-specific handling including nForce)
> but I had no time/hardware.
>
> Anyway you have to make sure agp(4) really works for you.
>
Hi again,
No, I have no agp support, but using the old driver allows me to start X... I
remember using the new driver made a /dev/agpgart appear, but the system crashes
at X startup...
> http://docs.freebsd.org/cgi/mid.cgi?200405181244.28716.jkim
>
> > The PR is here :
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84015
> >
> > Any clue ?
>
> Have you tried xorg-server-snap? If it doesn't work, can you try
> this?
No, I didn't, but I think I'll have the same pb since agp code for nforce3-250
is not correct in the kernel :(
> http://people.freebsd.org/~jkim/xorg-server-snap.diff
>
> Thanks,
Thanks to you,
Regards,
Ganael.
> Jung-uk Kim
>
> > [UTF-8?]Gana�l LAPLANCHE
> > ganael.laplanche at martymac.com
> > http://www.martymac.com
> > Tel : (+33)6.84.03.57.24.
------- End of Original Message -------
------------------------------
Message: 13
Date: Fri, 16 Sep 2005 08:08:54 +0000
From: "Ganael Laplanche" <ganael.laplanche at martymac.com>
Subject: Re: amd64 Radeon 9000 nForce3 250 agp support - Yes and No
To: Adam Gregoire <ebola at psychoholics.org>, freebsd-amd64 at freebsd.org
Cc: "K.Wieland" <wieland.k at gmail.com>
Message-ID: <20050916080443.M8613 at martymac.com>
Content-Type: text/plain; charset=iso-8859-1
> Hello, this chipset is not supported for agpgart, the nforce3 250
> chipset has the code needed to detect the gart but is missing
> functionality needed for proper operation.
>
> See also, PR amd64/71753 and the following thread
> http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004300.html
I'm the author of this post... I tried to write a small patch to see what's
happening with it, but it made my system hang as described here
http://lists.freebsd.org/pipermail/freebsd-amd64/2005-April/004315.html ! And It
looks like this code has been included in the 6-0 branch :(, that's why you
should use the old 5.x drivers...
> Regards,
>
> --
> Adam Gregoire <ebola at psychoholics.org>
>
> _______________________________________________
> freebsd-amd64 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe at freebsd.org"
------- End of Original Message -------
------------------------------
Message: 14
Date: Fri, 16 Sep 2005 11:37:14 +0200
From: Adriaan de Groot <groot at kde.org>
Subject: Re: amd64/86199: Missed AMD64 motherboard
To: freebsd-amd64 at freebsd.org
Message-ID: <200509161137.14570.groot at kde.org>
Content-Type: text/plain; charset="iso-8859-1"
On Friday 16 September 2005 05:48, Mike Smith wrote:
> MSI K8M NEO-V is not listed in the section covering amd64 compatible
> motherboards.
That's one issue, which should be PR-ed as described on the motherboards page.
> Also there seems to be a lack of support for the VT8237 SATA
> Raid controller.
Er, you mean
atapci1 at pci0:15:0: class=0x010400 card=0x80ed1043 chip=0x31491106
rev=0x80 hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT8237 VT6410 SATA RAID Controller'
class = mass storage
subclass = RAID
That one? It works just fine on Asus & Gigabyte boards.
> onboard sound also results in hard locks, randomly, especially when vchans
> are enabled. I'm using the VT8237 Audio as well. Any help with this would
> be greatly appreciated.
I've managed to lock my Asus board once with mpg123 foo.mp3 & mpg123 foo.mp3,
but sound in general is fine as well.
--
These are your friends - Adem
GPG: FEA2 A3FE Adriaan de Groot
------------------------------
Message: 15
Date: Fri, 16 Sep 2005 12:12:57 +0200
From: Bruno Ducrot <ducrot at poupinou.org>
Subject: Re: acpi/ohci/rsdt wtf?
To: "Jeff D. Hamann" <jeff.hamann at forestinformatics.com>
Cc: freebsd-amd64 at freebsd.org
Message-ID: <20050916101257.GA12562 at poupinou.org>
Content-Type: text/plain; charset=us-ascii
On Thu, Sep 15, 2005 at 12:41:18PM -0700, Jeff D. Hamann wrote:
> I'm curious what the
>
> acpi_perf0: invalid _PSS package
>
> messages are all about and why there are so many?
Could you send to me the output from acpidump -dt
It's rather large. Please send it to me privately or better
provide some link.
Cheers,
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
------------------------------
Message: 16
Date: Fri, 16 Sep 2005 20:16:24 +1000
From: Michael VInce <mv at roq.com>
Subject: Re: FAST_IPSEC on EMT64 / AMD64
To: "Bjoern A. Zeeb" <bzeeb-lists at lists.zabbadoz.net>
Cc: freebsd-amd64 at FreeBSD.org, Kris Kennaway <kris at obsecurity.org>
Message-ID: <432A9B78.8020906 at roq.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Michael VInce wrote:
> Bjoern A. Zeeb wrote:
>
>> On Mon, 12 Sep 2005, Kris Kennaway wrote:
>>
>>
>>
>>> On Mon, Sep 12, 2005 at 11:56:58AM +1000, Michael VInce wrote:
>>>
>>>
>>>> Hi guys,
>>>> I am getting a Intel Xeon based EMT64 server as a gateway that may in
>>>> the future do some VPN,
>>>> I wondered if the EMT64 servers could run FAST_IPSEC under AMD64
>>>> FreeBSD.
>>>> With these options below compiled into the kernel I was able to boot
>>>> FreeBSD with no panics if I booted into single user mode and then just
>>>> did 'exit' to go back to regular boot, otherwise it would panic as if
>>>> it was an AMD64 CPU.
>>>>
>>>
>>> You forgot to include details of the panic.
>>>
>>
>>
>> That would be really good to know.
>>
>> Then we'd finally know more than was given in
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/73211
>>
>>
>
> Sorry instead of getting a core dump I grabbed a FreeBSD AMD64 beta4
> 6.0 ISO and put it on this server.
> But I do have some good news in what I found.
> Recompiled FAST_IPSEC into the kernel and rebooted it, it came up fine..
> So then put in some ipsec security policies into /etc/ipsec.conf
> ipsec_enable="YES"
> and ran /etc/rc.d/ipsec start
> and it ran fine.
> I then installed ipsec-tools and loaded up the racoon daemon this also
> triggers a panic on my FreeBSD AMD64 6.0 laptop with out FAST_IPSEC
> being compiled into the kernel and its loaded up fine.
> This looks all completely solid. I haven't been able to panic the
> server with a full VPN configuration activated.
> The only thing I haven't done is tested if the IPSEC VPN actually can
> work.
>
> This is no mistake this is AMD64 kernel FreeBSD with FAST_IPSEC I just
> cheated using the Intel EMT64
>
> Regards,
> Mike
>
> beast# /sbin/sysctl -a | grep ipsec
> ipsecpolicy 16 4K - 520 256
> ipsecrequest 2 1K - 4 256
> ipsec-reg 3 1K - 24 32
> net.inet.ipsec.def_policy: 1
> net.inet.ipsec.esp_trans_deflev: 1
> net.inet.ipsec.esp_net_deflev: 1
> net.inet.ipsec.ah_trans_deflev: 1
> net.inet.ipsec.ah_net_deflev: 1
> net.inet.ipsec.ah_cleartos: 1
> net.inet.ipsec.ah_offsetmask: 0
> net.inet.ipsec.dfbit: 0
> net.inet.ipsec.ecn: 0
> net.inet.ipsec.debug: 0
> net.inet.ipsec.esp_randpad: -1
> net.inet.ipsec.crypto_support: 0
> net.inet6.ipsec6.def_policy: 1
> net.inet6.ipsec6.esp_trans_deflev: 1
> net.inet6.ipsec6.esp_net_deflev: 1
> net.inet6.ipsec6.ah_trans_deflev: 1
> net.inet6.ipsec6.ah_net_deflev: 1
> net.inet6.ipsec6.ecn: 0
> net.inet6.ipsec6.debug: 0
> net.inet6.ipsec6.esp_randpad: -1
> beast# uname -a
> FreeBSD beast 6.0-BETA4 FreeBSD 6.0-BETA4 #0: Mon Sep 12 20:40:05 UTC
> 2005 root at beast:/usr/obj/usr/src/sys/GENERIC_IPSEC amd64
>
> _______________________________________________
> freebsd-amd64 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
> To unsubscribe, send any mail to "freebsd-amd64-unsubscribe at freebsd.org"
I am back,
I still would like to see this bug fixed (and I assume other people do
as well :)
The server in my above email appears to be working fine using FAST_IPSEC
on AMD64 is a Dell 2850 (Beast)
But on a Dell 1850 it crashes as usual, here is a dump on AMD64 6.0
Beta4 cvsuped from beta3 ISO install. I still don't know why it appears
to be working fine on a 2850 but not on any other machine in the world?
This machine below is a Dell 1850 EMT64 with FAST_IPSEC compiled into it
with some rules in /etc/ipsec.conf
I can get panics from starting ipsec or starting racoon ipsec-tools. The
I have listed 2 dumps here the first one is from racoon and the one
below is from setkey ( starting ipsec )
I don't really know much about doing this stuff so I have just run some
of the commands in the kernel debug handbook example. This dump was
triggered from starting racoon.
This is from a usb2serial console output from the server.
cd /usr/obj/usr/src/sys/GENERIC_IPSEC/
tank# kgdb kernel.debug /usr/crash/vmcore.7
[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 "amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 591 (racoon)
panic: from debugger
cpuid = 0
Uptime: 4m23s
Dumping 2047 MB (2 chunks)
chunk 0: 1MB (156 pages) ... ok
chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935 1919
1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695
1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471
1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247
1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023
1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735
719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447
431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159
143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:172
172 __asm __volatile("movq %%gs:0,%0" : "=r" (td));
(kgdb) list
167 static __inline struct thread *
168 __curthread(void)
169 {
170 struct thread *td;
171
172 __asm __volatile("movq %%gs:0,%0" : "=r" (td));
173 return (td);
174 }
175 #define curthread (__curthread())
176
(kgdb) backtrace
#0 doadump () at pcpu.h:172
#1 0xffffffff803b8ccc in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:399
#2 0xffffffff803b876b in panic (fmt=0xffffffff805faac2 "from debugger")
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xffffffff801aa1c2 in db_panic (addr=0, have_addr=0, count=0,
modif=0x0) at /usr/src/sys/ddb/db_command.c:435
#4 0xffffffff801aa705 in db_command_loop () at
/usr/src/sys/ddb/db_command.c:349
#5 0xffffffff801ac573 in db_trap (type=-1270872608, code=0) at
/usr/src/sys/ddb/db_main.c:221
#6 0xffffffff803d5799 in kdb_trap (type=12, code=0,
tf=0xffffffffb44007a0) at /usr/src/sys/kern/subr_kdb.c:473
#7 0xffffffff8059bf0e in trap_fatal (frame=0xffffffffb44007a0,
eva=18446742975788145024) at /usr/src/sys/amd64/amd64/trap.c:656
#8 0xffffffff8059c2a3 in trap_pfault (frame=0xffffffffb44007a0,
usermode=0) at /usr/src/sys/amd64/amd64/trap.c:581
#9 0xffffffff8059c4b9 in trap (frame=
{tf_rdi = -2140943745, tf_rsi = 256, tf_rdx = -1270871712, tf_rcx
= -2142535110, tf_r8 = 64, tf_r9 = -1097921406592, tf_rax = 0, tf_rbx =
2152432187, tf_rbp = -1270871728, tf_r10 = -2139154144, tf_r11 =
-1270871552, tf_r12 = 57, tf_r13 = 0, tf_r14 = 0, tf_r15 = 0, tf_trapno
= 12, tf_addr = -3413406822, tf_flags = -2140901446, tf_err = 0, tf_rip
= -2142535096, tf_cs = 8, tf_rflags = 66178, tf_rsp = -1270871968, tf_ss
= 16})
at /usr/src/sys/amd64/amd64/trap.c:360
#10 0xffffffff80589dfb in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:168
#11 0xffffffff8063ca7f in wi_pccard_products ()
#12 0x0000000000000100 in ?? ()
#13 0xffffffffb4400960 in ?? ()
#14 0xffffffff804b823a in kdebug_mbuf (m0=0x0) at
/usr/src/sys/netipsec/key_debug.c:670
#15 0xffffffff80442d60 in raw_usend (so=0x0, flags=0, m=0x0, nam=0x0,
control=0x0, td=0x0) at /usr/src/sys/net/raw_usrreq.c:263
#16 0xffffffff804b8d2a in key_send (so=0x0, flags=0, m=0x0, nam=0x0,
control=0x0, td=0x0) at /usr/src/sys/netipsec/keysock.c:532
#17 0xffffffff803fdde4 in sosend (so=0xffffff005f41dc08, addr=0x0,
uio=0xffffffffb4400a80, top=0xffffff006076e700, control=0x0, flags=0,
td=0xffffff005ec8d980) at /usr/src/sys/kern/uipc_socket.c:829
#18 0xffffffff80404d54 in kern_sendit (td=0xffffff005ec8d980, s=5,
mp=0xffffffffb4400b50, flags=0, control=0x0, segflg=16)
at /usr/src/sys/kern/uipc_syscalls.c:772
#19 0xffffffff80405f16 in sendit (td=0xffffff005ec8d980, s=5,
mp=0xffffffffb4400b50, flags=0) at /usr/src/sys/kern/uipc_syscalls.c:712
#20 0xffffffff804062d4 in sendto (td=0x0, uap=0x0) at
/usr/src/sys/kern/uipc_syscalls.c:830
#21 0xffffffff8059cc72 in syscall (frame=
{tf_rdi = 5, tf_rsi = 5677936, tf_rdx = 16, tf_rcx = 0, tf_r8 = 0,
tf_r9 = 0, tf_rax = 133, tf_rbx = 5677952, tf_rbp = 2, tf_r10 = 4,
tf_r11 = 582, tf_r12 = 5677936, tf_r13 = 7, tf_r14 = 5, tf_r15 = 0,
tf_trapno = 12, tf_addr = 4292816, tf_flags = 0, tf_err = 2, tf_rip =
34372796060, tf_cs = 43, tf_rflags = 582, tf_rsp = 140737488349928,
tf_ss = 35}) at /usr/src/sys/amd64/amd64/trap.c:797
#22 0xffffffff80589f98 in Xfast_syscall () at
/usr/src/sys/amd64/amd64/exception.S:270
#23 0x0000000000000005 in ?? ()
#24 0x000000000056a370 in ?? ()
#25 0x0000000000000010 in ?? ()
#26 0x0000000000000000 in ?? ()
#27 0x0000000000000000 in ?? ()
#28 0x0000000000000000 in ?? ()
#29 0x0000000000000085 in ?? ()
#30 0x000000000056a380 in ?? ()
#31 0x0000000000000002 in ?? ()
#32 0x0000000000000004 in ?? ()
#33 0x0000000000000246 in ?? ()
#34 0x000000000056a370 in ?? ()
#35 0x0000000000000007 in ?? ()
#36 0x0000000000000005 in ?? ()
#37 0x0000000000000000 in ?? ()
#38 0x000000000000000c in ?? ()
#39 0x00000000004180d0 in ?? ()
#40 0x0000000000000000 in ?? ()
#41 0x0000000000000002 in ?? ()
#42 0x0000000800c73e9c in ?? ()
#43 0x000000000000002b in ?? ()
#44 0x0000000000000246 in ?? ()
#45 0x00007fffffffeae8 in ?? ()
#46 0x0000000000000023 in ?? ()
#47 0x00007fffffff5b50 in ?? ()
#48 0x0000000000000023 in ?? ()
#49 0x0000000000000000 in ?? ()
#50 0x0000000000000000 in ?? ()
#51 0x0000000000000000 in ?? ()
#52 0x0000000000000000 in ?? ()
#53 0x0000000000000000 in ?? ()
#54 0x0000000000000000 in ?? ()
#55 0x0000000000000000 in ?? ()
#56 0x0000000000000000 in ?? ()
#57 0x000000005f4dd000 in ?? ()
#58 0x0000000000000001 in ?? ()
#59 0x0000000000000000 in ?? ()
#60 0xffffff005e696340 in ?? ()
#61 0xffffff007b9b74c0 in ?? ()
#62 0xffffffffb4400260 in ?? ()
#63 0xffffffffb4400238 in ?? ()
#64 0xffffff005ec8d980 in ?? ()
#65 0xffffffff803cd10a in sched_switch (td=0x56a380, newtd=0x56a370,
flags=5) at /usr/src/sys/kern/sched_4bsd.c:973
Previous frame inner to this frame (corrupt stack?)
Here is the serial console output from doing '/etc/rc.d/ipsec start'
with some rules in /etc/ipsec.conf
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0xffffffff3489ab9a
fault code = supervisor read, page not present
instruction pointer = 0x8:0xffffffff804b8248
stack pointer = 0x10:0xffffffffb43e2850
frame pointer = 0x10:0xffffffffb43e2950
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 615 (setkey)
[thread pid 615 tid 100159 ]
Stopped at kdebug_mbuf+0x88:
db> panic
panic: from debugger
cpuid = 0
Uptime: 14m39s
Dumping 2047 MB (2 chunks)
chunk 0: 1MB (156 pages) ... ok
chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935 1919
1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695
1679 1663 16k
Dump complete
tank# kgdb kernel.debug /usr/crash/vmcore.8
kgdb kernel.debug /usr/crash/vmcore.8
[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 "amd64-marcel-freebsd".
Unread portion of the kernel message buffer:
fff804b8248
stack pointer = 0x10:0xffffffffb43e2850
frame pointer = 0x10:0xffffffffb43e2950
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 615 (setkey)
panic: from debugger
cpuid = 0
Uptime: 14m39s
Dumping 2047 MB (2 chunks)
chunk 0: 1MB (156 pages) ... ok
chunk 1: 2047MB (523968 pages) 2031 2015 1999 1983 1967 1951 1935 1919
1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695
1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471
1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247
1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023
1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735
719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447
431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159
143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:172
172 __asm __volatile("movq %%gs:0,%0" : "=r" (td));
(kgdb) list
167 static __inline struct thread *
168 __curthread(void)
169 {
170 struct thread *td;
171
172 __asm __volatile("movq %%gs:0,%0" : "=r" (td));
173 return (td);
174 }
175 #define curthread (__curthread())
176
(kgdb) backtrace
#0 doadump () at pcpu.h:172
#1 0xffffffff803b8ccc in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:399
#2 0xffffffff803b876b in panic (fmt=0xffffffff805faac2 "from debugger")
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xffffffff801aa1c2 in db_panic (addr=0, have_addr=0, count=0,
modif=0x0) at /usr/src/sys/ddb/db_command.c:435
#4 0xffffffff801aa705 in db_command_loop () at
/usr/src/sys/ddb/db_command.c:349
#5 0xffffffff801ac573 in db_trap (type=-1270995488, code=0) at
/usr/src/sys/ddb/db_main.c:221
#6 0xffffffff803d5799 in kdb_trap (type=12, code=0,
tf=0xffffffffb43e27a0) at /usr/src/sys/kern/subr_kdb.c:473
#7 0xffffffff8059bf0e in trap_fatal (frame=0xffffffffb43e27a0,
eva=18446742975772514688) at /usr/src/sys/amd64/amd64/trap.c:656
#8 0xffffffff8059c2a3 in trap_pfault (frame=0xffffffffb43e27a0,
usermode=0) at /usr/src/sys/amd64/amd64/trap.c:581
#9 0xffffffff8059c4b9 in trap (frame=
{tf_rdi = -2140943745, tf_rsi = 256, tf_rdx = -1270994592, tf_rcx
= -2142535110, tf_r8 = 64, tf_r9 = -1097937036928, tf_rax = 0, tf_rbx =
2152432187, tf_rbp = -1270994608, tf_r10 = -2139154144, tf_r11 =
-1270994432, tf_r12 = 57, tf_r13 = 0, tf_r14 = 0, tf_r15 = 0, tf_trapno
= 12, tf_addr = -3413529702, tf_flags = -2140901446, tf_err = 0, tf_rip
= -2142535096, tf_cs = 8, tf_rflags = 66178, tf_rsp = -1270994848, tf_ss
= 16})
at /usr/src/sys/amd64/amd64/trap.c:360
#10 0xffffffff80589dfb in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:168
#11 0xffffffff8063ca7f in wi_pccard_products ()
#12 0x0000000000000100 in ?? ()
#13 0xffffffffb43e2960 in ?? ()
#14 0xffffffff804b823a in kdebug_mbuf (m0=0x0) at
/usr/src/sys/netipsec/key_debug.c:670
#15 0xffffffff80442d60 in raw_usend (so=0x0, flags=0, m=0x0, nam=0x0,
control=0x0, td=0x0) at /usr/src/sys/net/raw_usrreq.c:263
#16 0xffffffff804b8d2a in key_send (so=0x0, flags=0, m=0x0, nam=0x0,
control=0x0, td=0x0) at /usr/src/sys/netipsec/keysock.c:532
#17 0xffffffff803fdde4 in sosend (so=0xffffff005ef219a0, addr=0x0,
uio=0xffffffffb43e2a80, top=0xffffff00608a0e00, control=0x0, flags=0,
td=0xffffff005dda5980) at /usr/src/sys/kern/uipc_socket.c:829
#18 0xffffffff80404d54 in kern_sendit (td=0xffffff005dda5980, s=4,
mp=0xffffffffb43e2b50, flags=0, control=0x0, segflg=16)
at /usr/src/sys/kern/uipc_syscalls.c:772
#19 0xffffffff80405f16 in sendit (td=0xffffff005dda5980, s=4,
mp=0xffffffffb43e2b50, flags=0) at /usr/src/sys/kern/uipc_syscalls.c:712
#20 0xffffffff804062d4 in sendto (td=0x0, uap=0x0) at
/usr/src/sys/kern/uipc_syscalls.c:830
#21 0xffffffff8059cc72 in syscall (frame=
{tf_rdi = 4, tf_rsi = 5320768, tf_rdx = 16, tf_rcx = 0, tf_r8 = 0,
tf_r9 = 0, tf_rax = 133, tf_rbx = 5320784, tf_rbp = 0, tf_r10 = 4,
tf_r11 = 5320704, tf_r12 = 5320768, tf_r13 = 7, tf_r14 = 4, tf_r15 = 0,
tf_trapno = 12, tf_addr = 5320704, tf_flags = 0, tf_err = 2, tf_rip =
34367663772, tf_cs = 43, tf_rflags = 514, tf_rsp = 140737488349848,
tf_ss = 35}) at /usr/src/sys/amd64/amd64/trap.c:797
#22 0xffffffff80589f98 in Xfast_syscall () at
/usr/src/sys/amd64/amd64/exception.S:270
#23 0x0000000000000004 in ?? ()
#24 0x0000000000513040 in ?? ()
#25 0x0000000000000010 in ?? ()
#26 0x0000000000000000 in ?? ()
#27 0x0000000000000000 in ?? ()
#28 0x0000000000000000 in ?? ()
#29 0x0000000000000085 in ?? ()
#30 0x0000000000513050 in ?? ()
#31 0x0000000000000000 in ?? ()
#32 0x0000000000000004 in ?? ()
#33 0x0000000000513000 in ?? ()
#34 0x0000000000513040 in ?? ()
#35 0x0000000000000007 in ?? ()
#36 0x0000000000000004 in ?? ()
#37 0x0000000000000000 in ?? ()
#38 0x000000000000000c in ?? ()
#39 0x0000000000513000 in ?? ()
#40 0x0000000000000000 in ?? ()
---Type <return> to continue, or q <return> to quit---
#41 0x0000000000000002 in ?? ()
#42 0x000000080078ee9c in ?? ()
#43 0x000000000000002b in ?? ()
#44 0x0000000000000202 in ?? ()
#45 0x00007fffffffea98 in ?? ()
#46 0x0000000000000023 in ?? ()
#47 0x00007fffffffd4d8 in ?? ()
#48 0x0000000000000023 in ?? ()
#49 0x0000000000000000 in ?? ()
#50 0x0000000000000000 in ?? ()
#51 0x0000000000000000 in ?? ()
#52 0x0000000000000000 in ?? ()
#53 0x0000000000000000 in ?? ()
#54 0x0000000000000000 in ?? ()
#55 0x0000000000000000 in ?? ()
#56 0x0000000000000000 in ?? ()
#57 0x000000005f9ba000 in ?? ()
#58 0x0000000000000001 in ?? ()
#59 0x0000000000000000 in ?? ()
#60 0xffffff005e4aa9c0 in ?? ()
#61 0xffffff007b9b74c0 in ?? ()
#62 0xffffffffb43e2260 in ?? ()
#63 0xffffffffb43e2238 in ?? ()
#64 0xffffff005dda5980 in ?? ()
#65 0xffffffff803cd10a in sched_switch (td=0x513050, newtd=0x513040,
flags=4) at /usr/src/sys/kern/sched_4bsd.c:973
Previous frame inner to this frame (corrupt stack?)
Here is my dmesg for the Dell 1850
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 6.0-BETA4 #0: Fri Sep 16 01:52:30 UTC 2005
root at tank:/usr/obj/usr/src/sys/GENERIC_IPSEC
WARNING: WITNESS option enabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.22-MHz K8-class CPU)
Origin = "GenuineIntel" Id = 0xf43 Stepping = 3
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0x641d<SSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,<b14>>
AMD Features=0x20100800<SYSCALL,NX,LM>
Hyperthreading: 2 logical CPUs
real memory = 2147221504 (2047 MB)
avail memory = 2062241792 (1966 MB)
ACPI APIC Table: <DELL PE BKC >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0: Changing APIC ID to 2
ioapic1: Changing APIC ID to 3
ioapic1: WARNING: intbase 32 != expected base 24
ioapic2: Changing APIC ID to 4
ioapic2: WARNING: intbase 64 != expected base 56
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 32-55 on motherboard
ioapic2 <Version 2.0> irqs 64-87 on motherboard
acpi0: <DELL PE BKC> on motherboard
acpi0: Power Button (fixed)
pci_link0: <ACPI PCI Link LNKA> irq 11 on acpi0
pci_link1: <ACPI PCI Link LNKB> irq 3 on acpi0
pci_link2: <ACPI PCI Link LNKC> irq 7 on acpi0
pci_link3: <ACPI PCI Link LNKD> irq 10 on acpi0
pci_link4: <ACPI PCI Link LNKE> on acpi0
pci_link5: <ACPI PCI Link LNKF> on acpi0
pci_link6: <ACPI PCI Link LNKG> on acpi0
pci_link7: <ACPI PCI Link LNKH> irq 5 on acpi0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci1
pci2: <ACPI PCI bus> on pcib2
amr0: <LSILogic MegaRAID 1.51> mem
0xd80f0000-0xd80fffff,0xdfde0000-0xdfdfffff irq 46 at device 14.0 on pci2
amr0: <LSILogic PERC 4e/Si> Firmware 521S, BIOS H430, 256MB RAM
pcib3: <ACPI PCI-PCI bridge> at device 0.2 on pci1
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci4: <ACPI PCI bus> on pcib4
pcib5: <PCI-PCI bridge> at device 0.0 on pci4
pci5: <PCI bus> on pcib5
em0: <Intel(R) PRO/1000 Network Connection, Version - 2.1.7> port
0xecc0-0xecff mem 0xdfae0000-0xdfafffff irq 16 at device 4.0 on pci5
em0: Ethernet address: 00:0e:0c:73:d4:f2
em0: Speed:N/A Duplex:N/A
em1: <Intel(R) PRO/1000 Network Connection, Version - 2.1.7> port
0xec80-0xecbf mem 0xdfac0000-0xdfadffff irq 17 at device 4.1 on pci5
em1: Ethernet address: 00:0e:0c:73:d4:f3
em1: Speed:N/A Duplex:N/A
pcib6: <PCI-PCI bridge> at device 0.2 on pci4
pci6: <PCI bus> on pcib6
pcib7: <ACPI PCI-PCI bridge> at device 5.0 on pci0
pci7: <ACPI PCI bus> on pcib7
pcib8: <ACPI PCI-PCI bridge> at device 0.0 on pci7
pci8: <ACPI PCI bus> on pcib8
em2: <Intel(R) PRO/1000 Network Connection, Version - 2.1.7> port
0xdcc0-0xdcff mem 0xdf7e0000-0xdf7fffff irq 64 at device 7.0 on pci8
em2: Ethernet address: 00:14:22:15:ff:4b
em2: Speed:N/A Duplex:N/A
pcib9: <ACPI PCI-PCI bridge> at device 0.2 on pci7
pci9: <ACPI PCI bus> on pcib9
em3: <Intel(R) PRO/1000 Network Connection, Version - 2.1.7> port
0xccc0-0xccff mem 0xdf5e0000-0xdf5fffff irq 65 at device 8.0 on pci9
em3: Ethernet address: 00:14:22:15:ff:4c
em3: Speed:N/A Duplex:N/A
pcib10: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci10: <ACPI PCI bus> on pcib10
uhci0: <Intel 82801EB (ICH5) USB controller USB-A> port 0xace0-0xacff
irq 16 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
usb0: <Intel 82801EB (ICH5) USB controller USB-A> 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
uhci1: <Intel 82801EB (ICH5) USB controller USB-B> port 0xacc0-0xacdf
irq 19 at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
usb1: <Intel 82801EB (ICH5) USB controller USB-B> on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <Intel 82801EB (ICH5) USB controller USB-C> port 0xaca0-0xacbf
irq 18 at device 29.2 on pci0
uhci2: [GIANT-LOCKED]
usb2: <Intel 82801EB (ICH5) USB controller USB-C> on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xdff00000-0xdff003ff irq
23 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
usb3: EHCI version 1.0
usb3: companion controllers, 2 ports each: usb0 usb1 usb2
usb3: <EHCI (generic) USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub3: 6 ports with 6 removable, self powered
uhub4: vendor 0x413c product 0xa001, class 9/0, rev 2.00/0.00, addr 2
uhub4: multiple transaction translators
uhub4: 2 ports with 2 removable, self powered
pcib11: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci11: <ACPI PCI bus> on pcib11
pci11: <display, VGA> at device 13.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH5 UDMA100 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A, console
orm0: <ISA Option ROMs> at iomem
0xc0000-0xcafff,0xcb000-0xcbfff,0xce800-0xcf7ff,0xec000-0xeffff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
ppc0: cannot reserve I/O port range
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ucom0: Prolific Technology Inc. USB-Serial Controller, rev 1.10/3.00, addr 2
Timecounters tick every 1.000 msec
Fast IPsec: Initialized Security Association Processing.
acd0: DVDROM <HL-DT-STDVD-ROM GDR8082N/0106> at ata0-master UDMA33
amrd0: <LSILogic MegaRAID logical drive> on amr0
amrd0: 139900MB (286515200 sectors) RAID 1 (optimal)
ses0 at amr0 bus 0 target 6 lun 0
ses0: <PE/PV 1x2 SCSI BP 1.0> Fixed Processor SCSI-2 device
ses0: SAF-TE Compliant Device
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/amrd0s1a
WARNING: / was not properly dismounted
em2: link state changed to UP
em3: link state changed to UP
Cheers,
Mike
------------------------------
_______________________________________________
freebsd-amd64 at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscribe at freebsd.org"
End of freebsd-amd64 Digest, Vol 119, Issue 5
*********************************************
More information about the freebsd-amd64
mailing list