Re: mpt: Unable to memory map registers
On 6/7/12 10:02 PM, Andrey Zonov wrote: Hi, I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-STABLE (r234600) and now they can't find any disk because SAS controller cannot initialize with the following diagnostic: mpt0: port 0xd000-0xd0ff irq 26 at device 3.0 on pci6 mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). mpt0: Unable to memory map registers. mpt0: Giving Up. pciconf -lv: mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 hdr=0x00 vendor = 'LSI Logic / Symbios Logic' device = 'SAS1068 PCI-X Fusion-MPT SAS' class = mass storage subclass = SCSI I tried to boot to latest HEAD and found the same problem. I also tried to build kernel with mpt driver from my 8.2. Controller didn't initialize with the same diagnostic. So it looks like the problem is not in mpt driver. Any help would be appreciated. +jhb@ Hi John, Could you please help me with the problem above? It looks like the problem is in PCI code and you changed things there. -- Andrey Zonov ___ 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: Documenting 'make config' options
Dan Daley wrote: > I usually use portmaster to install ports. The options dialogs that pop > up are often for dependencies. The options dialog gives the name of the > port for which the options are being selected, but no description or > indication as to why this is being installed (this could be a dependency > of a dependency of some dependency of the port I am installing). It's > probably too much for this dialog to show why this port is being > installed (what other port required this port that is being installed), > but a description of what this current port is would be helpful. > > But, if possible, some breadcrumb across the top showing the > dependencies which prompted this install would be great: > > Port A --> Port B --> Port C --> Current Port for which options are > being chosen You might want to have a look at my "portup" script. It can be used to install ports, and the -w option causes it to use a split-screen display: The bottom 80% contain the usual output from "make", and the top 20% show the progress of the build, including information about dependencies. This might be exactly the "breadcrumb across the top" that you requested. You can download the current version from here: http://www.secnetix.de/olli/scripts/portup For FreeBSD >= 8.x, the -w option requires the "window" port to be installed (from /usr/ports/misc/window) which was removed from the base system in FreeBSD 8.x. Usage for installing ports is simple: # cd /usr/ports/category/foo # portup -wy . Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd I suggested holding a "Python Object Oriented Programming Seminar", but the acronym was unpopular. -- Joseph Strout ___ 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: 9-stabe: cd device gone, ATA_CAM panics
Sergey Kandaurov wrote: > This is a wild guess, but see below. > [...] > Probably the way to fix this is to modify > cam_periph_release_locked_buses() to test CAM_PERIPH_INVALID either. > > how about this patch? > (beware: it was not compile tested, just speculating) Thanks for your detailed analysis! I'm afraid the patch is not correct. With that patch, the following page fault occurs (same output as before until "removing device entry"): (cd0:ata2:0:0:0): removing device entry (cd0:nobus:X:X): removing device entry Fatal trap 12: page fault while in kernel mode cpuid = 4; apic id = 04 fault virtual address = 0x20 fault code = supervisor read data, page not present instruction pointer = 0x20:0x807a0d03 stack pointer = 0x28:0xff80002a9270 frame pointer = 0x28:0xff80002a9290 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 = 12 (g_event) trap number = 12 panic: page fault cpuid = 4 KDB: stack backtrace: #0 0x807a3ca6 at kdb_backtrace+0x66 #1 0x8076d75e at panic+0x1ce #2 0x809b7400 at trap_fatal+0x290 #3 0x809b773d at trap_pfault+0x1ed #4 0x809b7d5e at trap+0x3ce #5 0x809a282f at calltrap+0x8 #6 0x806d6a16 at disk_destroy+0x26 #7 0x802ba687 at cdcleanup+0x97 #8 0x802a1e79 at camperiphfree+0x99 #9 0x802a203e at cam_periph_release_locked+0x1e #10 0x802a2f62 at cam_periph_release+0x52 #11 0x802babdd at cdclose+0xbd #12 0x806d7342 at g_disk_access+0x242 #13 0x806db628 at g_access+0x188 #14 0x806fc353 at g_raid_md_taste_ddf+0x1f3 #15 0x806e96e6 at g_raid_taste+0x126 #16 0x806db0dd at g_new_provider_event+0x6d #17 0x806d8c18 at g_run_events+0x1e8 Uptime: 48s Automatic reboot in 15 seconds - press any key on the console to abort By the way, there is a long delay (~20s) before the two "ata2: reset tp1" lines. I guess something hangs here and causes a time-out. I didn't have such delays with 8.x. I need a working DVD drive, so I'm now considering to downgrade to 8-stable. But then again, TMPFS didn't work a well for me as it does in 9-stable (which was the main reason for me to upgrade), so I'm kind of stuck in a difficult situation. I'm willing to test more patches, of course. :-) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > Can the denizens of this group enlighten me about what the > advantages of Python are, versus Perl ? "python" is more likely to pass unharmed through your spelling checker than "perl". -- An unknown poster and Fredrik Lundh ___ 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"
How can I boot the second hard drive without proper BIOS or boot manager ?
Hello list, I was a happy user of boot0cfg and the boot0 boot manager until I converted my MBR+UFS disks to GPT+ZFS. Now I use gptzfsboot but sometimes I'd like to boot the second hard drive, and my crappy BIOS won't allow me to do that, it only allows to boot from the first hard drive (sic...). I'd like to avoid installing a full boot manager like grub2 (and I don't know if the FreeBSD port supports ZFS). Is there anything I can do at the "boot:" prompt to "chainload" the 2nd hard drive boot block ? Or can I use the boot0 boot manager and boot0cfg to boot the "freebsd-boot" GPT partition if it's mirrored in the protective MBR, like I used to do on my old MBR layout ? Thanks -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ 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"
Experience with Intel SATA and fbsd 8.3-amd64 ?
Hi! I have a problem with some host: If I put heavy IO load on that system, write errors happen, and then it crashes. CPU: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz RAM: 8 GB RAM with the following SATA controller: OS: 8.3-REL amd64 Board (from dmidecode): Manufacturer: Intel Corporation Product Name: IRONLAKE & IBEX PEAK Chipset The controller: ahci0: port 0x1840-0x1847,0x1814-0x1817,0x1818-0x181f,0x1810-0x1813,0x1820-0x183f mem 0xf4d04000-0xf4d047ff irq 19 at device 31.2 on pci0 pciconf -lvb says: ahci0@pci0:0:31:2: class=0x010601 card=0x3b208086 chip=0x3b228086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'IBEX AHCI Controller(6Port) (Intel Q57 Express)' class = mass storage subclass = SATA bar [10] = type I/O Port, range 32, base 0x1840, size 8, enabled bar [14] = type I/O Port, range 32, base 0x1814, size 4, enabled bar [18] = type I/O Port, range 32, base 0x1818, size 8, enabled bar [1c] = type I/O Port, range 32, base 0x1810, size 4, enabled bar [20] = type I/O Port, range 32, base 0x1820, size 32, enabled bar [24] = type Memory, range 32, base 0xf4d04000, size 2048, enabled AHCI is enabled. This device is connected: ada0 at ahcich2 bus 0 scbus2 target 0 lun 0 ada0: ATA-8 SATA 3.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) I disabled soft-updates, and forced the filesystems to sync, the errors still occure. I tried different SATA cables, different ports on the board, different drives, always the same. So I suspect the controller -- has anyone experience with that controller ? -- p...@opsec.eu+49 171 3101372 8 years to go ! ___ 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: mpt: Unable to memory map registers
On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote: > On 6/7/12 10:02 PM, Andrey Zonov wrote: > > Hi, > > > > I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-STABLE > > (r234600) and now they can't find any disk because SAS controller cannot > > initialize with the following diagnostic: > > > > mpt0: port 0xd000-0xd0ff irq 26 at device > > 3.0 on pci6 > > mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). > > mpt0: Unable to memory map registers. > > mpt0: Giving Up. > > > > pciconf -lv: > > mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 > > hdr=0x00 > > vendor = 'LSI Logic / Symbios Logic' > > device = 'SAS1068 PCI-X Fusion-MPT SAS' > > class = mass storage > > subclass = SCSI > > > > I tried to boot to latest HEAD and found the same problem. I also tried > > to build kernel with mpt driver from my 8.2. Controller didn't > > initialize with the same diagnostic. So it looks like the problem is not > > in mpt driver. > > > > Any help would be appreciated. > > > > +jhb@ > > Hi John, > > Could you please help me with the problem above? It looks like the > problem is in PCI code and you changed things there. Can you get a verbose dmesg? -- 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"
Re: ULE Scheduler
Am Fri, 8 Jun 2012 08:04:12 +0200 schrieb Andreas Nilsson : > My t61p also had overheating problems with fbsd, but never in linux. > For me the fan control was somewhat broken: I had to turn off > auto-mode and set max myself to get any heavy usage out of it. > > You might want to check that as well. > > Regards > Andreas I checked this and my fan was already at full speed (all the time). Linux has got voltage regulation in fglrx as far as I know. As soon as the GPU was using power saving functions on MS-Windows the GPU temperature was far below 50°C. With FreeBSD it was always at 70°C! I don't have the T60p anymore (thanks god). It was an awful laptop. So I cannot give more precise information about this anymore. Martin signature.asc Description: PGP signature
Re: ULE Scheduler
Did anyone ever file a PR for this kind of thing? Adrian On 8 June 2012 10:07, Martin Sugioarto wrote: > Am Fri, 8 Jun 2012 08:04:12 +0200 > schrieb Andreas Nilsson : > >> My t61p also had overheating problems with fbsd, but never in linux. >> For me the fan control was somewhat broken: I had to turn off >> auto-mode and set max myself to get any heavy usage out of it. >> >> You might want to check that as well. >> >> Regards >> Andreas > > I checked this and my fan was already at full speed (all the time). > Linux has got voltage regulation in fglrx as far as I know. As soon as > the GPU was using power saving functions on MS-Windows the GPU > temperature was far below 50°C. With FreeBSD it was always at 70°C! > > I don't have the T60p anymore (thanks god). It was an awful laptop. So > I cannot give more precise information about this anymore. > > Martin ___ 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 Are You NOT Using FreeBSD ?
On Fri, Jun 1, 2012 at 8:43 AM, Pierre-Luc Drouin wrote: > For me it is the lack of support for suspend/resume on laptops. I don't > want to turn off my laptop when I am in the middle of doing something but > need to put the laptop aside. I love using FreeBSD on servers, workstations > and even a computer I have hooked to the TV at home for multimedia purpose, > but not having suspend/resume working on my laptops is a major source of > annoyance for me. So I have been trying various Linux distributions instead > and I am currently using Gentoo, which is not that bad, although I find > that system configuration and maintenance is always more painful with Linux > than FreeBSD no matter the distribution I use... +1000. (I understand this may not be feasible given the number of developers, by the way) Steve ___ 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: mpt: Unable to memory map registers
On Friday, June 08, 2012 11:48:50 am Andrey Zonov wrote: > On Fri, Jun 8, 2012 at 7:19 PM, John Baldwin wrote: > > On Friday, June 08, 2012 3:14:19 am Andrey Zonov wrote: > >> On 6/7/12 10:02 PM, Andrey Zonov wrote: > >> > Hi, > >> > > >> > I just upgraded a few machines from 8.2-STABLE (r221983) to 9.0-STABLE > >> > (r234600) and now they can't find any disk because SAS controller cannot > >> > initialize with the following diagnostic: > >> > > >> > mpt0: port 0xd000-0xd0ff irq 26 at device > >> > 3.0 on pci6 > >> > mpt0: 0x4000 bytes of rid 0x14 res 3 failed (0, 0x). > >> > mpt0: Unable to memory map registers. > >> > mpt0: Giving Up. > >> > > >> > pciconf -lv: > >> > mpt0@pci0:6:3:0: class=0x01 card=0x81dd1043 chip=0x00541000 rev=0x02 > >> > hdr=0x00 > >> > vendor = 'LSI Logic / Symbios Logic' > >> > device = 'SAS1068 PCI-X Fusion-MPT SAS' > >> > class = mass storage > >> > subclass = SCSI > >> > > >> > I tried to boot to latest HEAD and found the same problem. I also tried > >> > to build kernel with mpt driver from my 8.2. Controller didn't > >> > initialize with the same diagnostic. So it looks like the problem is not > >> > in mpt driver. > >> > > >> > Any help would be appreciated. > >> > > >> > >> +jhb@ > >> > >> Hi John, > >> > >> Could you please help me with the problem above? It looks like the > >> problem is in PCI code and you changed things there. > > > > Can you get a verbose dmesg? > > > > Yes, it's in attach. Can you get the output of 'devinfo -u' and 'devinfo -rv' from a broken kernel? Can you also try setting 'debug.acpi.disable=sysres' in the loader? -- 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"
Re: Documenting 'make config' options
Thanks. I'll check this script out. From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG; Dan Daley ; Charles Sprickman ; Warren Block ; Vincent Hoffman Sent: Fri, June 8, 2012 2:47:37 AM Subject: Re: Documenting 'make config' options Dan Daley wrote: > I usually use portmaster to install ports. The options dialogs that pop > up are often for dependencies. The options dialog gives the name of the > port for which the options are being selected, but no description or > indication as to why this is being installed (this could be a dependency > of a dependency of some dependency of the port I am installing). It's > probably too much for this dialog to show why this port is being > installed (what other port required this port that is being installed), > but a description of what this current port is would be helpful. > > But, if possible, some breadcrumb across the top showing the > dependencies which prompted this install would be great: > > Port A --> Port B --> Port C --> Current Port for which options are > being chosen You might want to have a look at my "portup" script. It can be used to install ports, and the -w option causes it to use a split-screen display: The bottom 80% contain the usual output from "make", and the top 20% show the progress of the build, including information about dependencies. This might be exactly the "breadcrumb across the top" that you requested. You can download the current version from here: http://www.secnetix.de/olli/scripts/portup For FreeBSD >= 8.x, the -w option requires the "window" port to be installed (from /usr/ports/misc/window) which was removed from the base system in FreeBSD 8.x. Usage for installing ports is simple: # cd /usr/ports/category/foo # portup -wy . Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd I suggested holding a "Python Object Oriented Programming Seminar", but the acronym was unpopular. -- Joseph Strout ___ 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 Are You NOT Using FreeBSD ?
I think XOrg 7.2 or 7.3 or whatever was the straw that broke the camel's back for me, but it's just an example. Every time libjpeg or perl or python bumps the rev, I have to explain to my boss that I won't be using my computer for 48 hours. You can say "don't follow the bleeding edge", but it seems like a weekly excersise that I need some port that wasn't built with a key option enabled, so pkg_add is really not an answer. If you have all the freetime in the world, reading /usr/ports/UPDATING back far enough will usually keep you out of trouble, but for a production system, it's a touch frustrating as soon as you touch the ports tree. That said, having been a linux user for a couple years now, I'm starting to think they are even worse: at least on F.B. you can rebuild the entire system in straightforward fashion if you do need an option that wasn't turned on, and go get a really big cup of coffee. The linux guys (or *buntu and derivatives at least) expect you never to upgrade a package/port unless you upgrade the whole OS (I think it was a ploy to get everyone locked-in to the abject failure that is gnome 3.0). I've got systems with 3-y.o. versions of everything on them, because there is no good way to upgrade an ap w/o upgrading the whole system, (at least past the couple of wannabe backports that they usually do the first year after a release. After that, you'd better really like the versions of everything that existed when you installed origonally.) That aside, you can clone a linux system with dpkg really really fast from a text list of previously installed packages (which is, however, unnecessary on freebsd because dump/restore works so well - never got it to clone a linux system into a functional state - so F.B wins again). So, conceptually and freedom-to-choose-wise, I prefer FreeBSD, it's just that mechanically, day-to-day, it has brought my capacity to use the computer effectively to a halt for such extended periods that I can't often justify it on the desktop. My server on the other hand has been running 7.x for years, and shows no sign of giving out. Just keep sticking new HDD's in periodically. For a server that you rarely add new apps to, it's stellar. Mind you, it's probably chock full of security holes due to it's age... I guess the bottom line is when it comes to package management, you can't have it all, and you can rarely even have very much, and OS guys really don't get much excitement from coding on pkg managers, so we're gonna all be out of luck indefinitely no matter the platform. Steve ___ 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: 8.2 EoL Schedule?
On Fri, Jan 13, 2012 at 12:00:53PM +0100, Gót András thus spake:
Hi,
8.3 is on the way IMHO, but anyway RELENG_8 will be supported until
2013 febr 24, by the current status.
Regards,
Andras
But if RELENG_8_{1,2}, aren't updated then that would follow EOL, right?
Meaning, they won't be updated past July 31, 2012, unless there is an
extension.
Any clarity would be great on this.
-jgh
--
Jason Helfman
FreeBSD Committer | http://people.freebsd.org/~jgh | The Power To Serve
___
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: 8.2 EoL Schedule?
On 8. Jun 2012, at 20:58 , Jason Helfman wrote:
> On Fri, Jan 13, 2012 at 12:00:53PM +0100, Gót András thus spake:
>> Hi,
>>
>> 8.3 is on the way IMHO, but anyway RELENG_8 will be supported until
>> 2013 febr 24, by the current status.
>>
>> Regards,
>> Andras
>
> But if RELENG_8_{1,2}, aren't updated then that would follow EOL, right?
> Meaning, they won't be updated past July 31, 2012, unless there is an
> extension.
>
> Any clarity would be great on this.
The current expected EOL dates are available at
http://www.freebsd.org/security/#sup
8.1 and 8.2 will drop out of security support July 31 this year, given
8.3 has been available for at least 3 months then. Also 8.3 is an
extended release supported until 2014.
/bz
--
Bjoern A. Zeeb You have to have visions!
It does not matter how good you are. It matters what good you do!
___
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: How can I boot the second hard drive without proper BIOS or boot manager ?
I wouldn't use grub as well but there are alternatives. You might want to try GAG - http://gag.sourceforge.net/ It's a tiny piece of software, written in assembler. ___ 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 Are You NOT Using FreeBSD ?
On 6/9/2012 3:34, Steve Franks wrote: Every time libjpeg or perl or python bumps the rev, I have to explain to my boss that I won't be using my computer for 48 hours. Why is this? And why are you updating every time there is a rev bump? It almost sounds like you're recompiling everything just for the heck of it, though I don't get how even that takes 48 hours. Even make buildworld is done in multi-user mode and so you could use your workstation during the build. And we're talking about ports here so ... Just curious! -- Adam Strohl http://www.ateamsystems.com/ ___ 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: Boot hangs on v9 system at CD device probe
On Thu, May 31, 2012 at 9:10 AM, Kevin Oberman wrote: > On Thu, May 31, 2012 at 4:02 AM, Marius Strobl > wrote: >> On Wed, May 30, 2012 at 05:13:44PM -0600, Ian Lepore wrote: >>> On Wed, 2012-05-30 at 14:54 -0700, Kevin Oberman wrote: >>> > I sent a note about this a couple of weeks ago, but have not heard >>> > anything. I'm really getting a bit desperate. >>> > >>> > I have a system that I am trying to upgrade from 8.2 to 9.0. I have >>> > built it and installed the kernel, but it fails to boot. The boot >>> > freezes after probing for my hard drives during the probe of the >>> > CDROM. It just sits there, seemingly forever, though I have never >>> > waited longer then a few minutes. >>> > >>> > The system is a SuperMicro C25BX mother board. The DVD is PATA, >>> > reported on boot of 8-Stable as: >>> > acd0: DVDR at ata2-master UDMA66 >>> > >>> > If I unplug the CDROM, it boots fine, but I really need the device on >>> > the system, so I really can't leave it unplugged. Also, after the 9 >>> > kernel is installed, my Mk file have been updated so that I can't >>> > build some ports if I boot the 8.2 kernel. Does anyone remember this >>> > being reported by others? It was most likely on current, as it was >>> > probably prior to the release of 9. I googled around, but could not >>> > find it. >>> > >>> > I'd really appreciate it if anyone can point me toward a solution. >>> > >>> > Thanks, >>> >>> When faced with a mystery like this I sometimes go into the mode of >>> "poke it with a stick and see if it twitches." If you can get it to >>> twitch at all, maybe that's a starting point. In this case, I guess I >>> might start with seeing if setting hw.ata.atapi_dma=0 in the loader >>> makes any difference. >>> >> >> Note that hw.ata.atapi_dma isn't honored by 9.0 with options ATA_CAM >> (default in GENERIC). Support for that loader tuneable was only >> resurrected rather recently (but is available in stable/9). The >> equivalent for 9.0 would be setting hint.ata.X.mode to PIO4 where >> X is the number of the ata(4) device attached for the channel the >> CDROM is connected to. >> ATA_CAM is indeed known to break ATAPI DMA for some ATA controllers >> though. What's the `pciconf -lv` output for this one? > > Good point. I had forgotten about the hw.ata.atapi_dma removal and was > not even awarethat it had been recently re-enabled. > My controller is: > atapci0@pci0:17:4:0: class=0x010185 card=0x82131283 chip=0x82131283 > rev=0x00 hdr=0x00 > vendor = 'Integrated Technology Express (ITE) Inc' > device = 'IDE Controller (IT8213F)' > class = mass storage > subclass = ATA > > It is used ONLY for the CD/DVD as all other disks use the 3ware RAID > controller. > > Unfortunately, the system is not located where I am, so I can't really > try anything until I get over there. Maybe later today I can run into > that office and try some of the suggestions. I can certainly build a > kernel without ATA_CAM. I just did the obvious as suggested and built a kernel without ATA_CAM and with atapicam. It boots fine and I have my CD/DVD working on 9.0. Clearly, there is some issue with ATAPI drives with ATA_CAM as others have seen the same thing. It is entirely possible that a serial connected drives don't have this issue. It does look like there is some locking issue between CAM and GEOM under some circumstances. I worry that 10 will lose support for other than ATA_CAM and that the work-around will no longer be available. Of course, if ahci fixes it, the problem will go away on systems that support it. Next time I get to the system I will try putting ATA_CAM back and adding ahci and report on the results. Thanks for the suggestions! -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ 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"
