Re: panic() in devfs_makelink() with recent -current
Quoting Louis A. Mamakos (lo...@transsys.com): I recently tried building a new kernel after quite a bit, and I get a panic while the system's booting in devfs_makelink, apparently being called from fd_attach(). Is DEVFS and the new-bus code hopelessly incompatable, and should I just unconfigure DEVFS? Or is this something that I can dig into a bit more and find a relatively simple fix? I copied down some of what the trace command spewed in ddb, and it appears that the first argument to devfs_makelink is 0, which is sorta weird.. Can I say me too here. My panics were happening in the swapper process. After reading your message I commented out the DEVFS option and voila! the new kernel booted without a hitch. I'm up for doing some kernel digging ... louie To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message #;^) -- natty rebel harder than the rest ... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Lastest ATA/ATAPI driver boots with kernel.debug only.
Hello Soren and other -current users, I've used your new ATA/ATAPI driver flawlessly through the 4th version. I was not able to get past the 'changing root device to wd0s1a' message with version 5, so I just went back to the wd driver. Last nigh I tried version 6 and ran into the same problem. I finally decided to do a little investigating. First I found that I could do a 'ctrl-alt-del' to reboot. I then decided to install the debug kernel doing a 'make install.debug' in my kernel build directory. Lo! and behold! to my surprise my box booted flawlessly. The questions I have are 1) Why did the debug kernel boot and not the kernel without debug symbols? 2) What procedures/tools should I use to investigate this further? Of course any help/pointers are appreciated ... Thanxs. #;^) i'khala -- natty rebel harder than the rest ... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
System hangs when booting with (update5) of ata/atapi driver
my system hangs when booting with update5 of the ata/atapi driver with the following in my kernel config: controller ata0 device atadisk0# ATA disks device atapifd0# ATAPI floppy drives the boot messages: Probing for devices on PCI bus 0: chip0: Host to PCI bridge (vendor=1039 device=5591) rev 0x02 on pci0.0.0 ata-pci0: Unknown PCI IDE Controller rev 0xd0 int a irq 14 on pci0.0.1 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq on ata-pci0 chip1: SiS 85c503 rev 0x01 on pci0.1.0 chip2: PCI to PCI bridge (vendor=1039 device=0001) rev 0x00 on pci0.2.0 [snippage ...] ata0: master: setting up generic WDMA2 mode OK ad0: FUJITSU MPB3032ATU/2011 ATA-3 disk at ata0 as master ad0: 3039MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode changing root device to wd0s1a and then the system hangs. pressing reset and booting /kernel.old brings it back to life. now with the following entries in my kernel config: controller wdc0at isa? port IO_WD1 bio irq 14 flags 0x80ff80ff disk wd0 at wdc0 drive 0 optionsATAPI#Enable ATAPI support for IDE bus optionsATAPI_STATIC #Don't do it as an LKM i get the following on boot and all is well ... Probing for devices on PCI bus 0: chip0: Host to PCI bridge (vendor=1039 device=5591) rev 0x02 on pci0.0.0 ide_pci0: SiS 5591 Bus-master IDE Controller rev 0xd0 int a irq 14 on pci0.0.1 chip1: SiS 85c503 rev 0x01 on pci0.1.0 chip2: PCI to PCI bridge (vendor=1039 device=0001) rev 0x00 on pci0.2.0 [snip ...] wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): FUJITSU MPB3032ATU, 32-bit, multi-block-16 wd0: 3093MB (6335280 sectors), 6704 cyls, 15 heads, 63 S/T, 512 B/S my motherboard is a gigabyte ga-5sg11 with SIS 5591/5595 chipset.. hope this info is helpful ... #;^) -- natty rebel harder than the rest ... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Using Soren's new ATA driver
Quoting Steve Price (spr...@hiwaay.net): What are the steps one needs to take in order to help test Soren's new ATA driver? I tweaked the MAKEDEV script to create /dev/ad0* and added the lines to my kernel config file as suggested in Soren's commit message. Both my HD and CD are found but when it goes to set the root device I get this: ... changing root device to ad0s1a ad0s2: cannot find label (no disk label) ad0s3: cannot find label (no disk label) ad0s4: cannot find label (no disk label) /: bad dir ino 2 at offset 0: mangled entry panic: ufs_dirbad: bad dir The obvious answer would be to edit the label for each of these slices to change the wd0* disk entries (which do exist) to say ad0* instead, but is that what I really need to do? I don't think you need to do this just yet ... :) Or did I miss a step? Back out your changes to MAKEDEV. The new driver understands the wd0* entries ... Sorry for being so dense, but this change should most definitely make it into src/UPDATING along with the list of required steps. I have to say though it was a glorious feeling to see the probe for my CD not take its usual 20+ seconds. :) Thanks, Steve #;^) -- natty rebel harder than the rest ... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
