kernel: ad8: FAILURE - READ timed out LBA=234441585
Hi, Whenever I try to boot my desktop workstation with FreeBSD, it suddenly just hangs there forever. When I boot into safe mode, however, I get this in the dmesg: Jun 18 16:01:46 b00b kernel: ad8: 114473MB Seagate ST3120022A 3.06 at ata4-master PIO4 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441585 Jun 18 16:01:46 b00b kernel: ad8: TIMEOUT - READ retrying (1 retry left) LBA=0 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441631 Jun 18 16:01:46 b00b kernel: ad8: TIMEOUT - READ retrying (0 retries left) LBA=0 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441644 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=0 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441585 Jun 18 16:01:46 b00b kernel: ad8: TIMEOUT - READ retrying (1 retry left) LBA=0 The hard drive is connected to an onboard Promise FastTrak (atapci1: Promise PDC20376 SATA150 controller port 0x8000-0x803f,0x7800-0x780f,0x7400-0x747f mem 0xab80-0xab800fff,0xab00-0xab01 irq 11 at device 14.0 on pci0) controller on my Asus p4s8x motherboard. The drive itself is connected to the optional PATA connector, which works wonderfully in Windows. I've currently managed to install Xorg and KDE on the box, all entirely in Safe Mode, but the performance is really bad, or not as good as it should be on a PC with a Pentium IV 2.4GHz and 1GB PC3200 RAM. Googling yields irrelevant results to my case, and search results for freebsd p4s8x (no quotes) indicate that FreeBSD should be working OK with my motherboard and all of its native components. So, does anybody know how to a) Fix this issue (or, if not) b) How to prevent a specific device (atapci1 or ad8) from being loaded during boot time? Again, googling yields no results, but I might be querying the wrong strings. Attached is my dmesg.boot Thanks for any help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel: ad8: FAILURE - READ timed out LBA=234441585
Daniel A. A. wrote: Hi, Whenever I try to boot my desktop workstation with FreeBSD, it suddenly just hangs there forever. When I boot into safe mode, however, I get this in the dmesg: Jun 18 16:01:46 b00b kernel: ad8: 114473MB Seagate ST3120022A 3.06 at ata4-master PIO4 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441585 Jun 18 16:01:46 b00b kernel: ad8: TIMEOUT - READ retrying (1 retry left) LBA=0 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441631 Jun 18 16:01:46 b00b kernel: ad8: TIMEOUT - READ retrying (0 retries left) LBA=0 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441644 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=0 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441585 Jun 18 16:01:46 b00b kernel: ad8: TIMEOUT - READ retrying (1 retry left) LBA=0 The hard drive is connected to an onboard Promise FastTrak (atapci1: Promise PDC20376 SATA150 controller port 0x8000-0x803f,0x7800-0x780f,0x7400-0x747f mem 0xab80-0xab800fff,0xab00-0xab01 irq 11 at device 14.0 on pci0) controller on my Asus p4s8x motherboard. The drive itself is connected to the optional PATA connector, which works wonderfully in Windows. I've currently managed to install Xorg and KDE on the box, all entirely in Safe Mode, but the performance is really bad, or not as good as it should be on a PC with a Pentium IV 2.4GHz and 1GB PC3200 RAM. Googling yields irrelevant results to my case, and search results for freebsd p4s8x (no quotes) indicate that FreeBSD should be working OK with my motherboard and all of its native components. So, does anybody know how to a) Fix this issue (or, if not) b) How to prevent a specific device (atapci1 or ad8) from being loaded during boot time? Again, googling yields no results, but I might be querying the wrong strings. Attached is my dmesg.boot Thanks for any help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Well, go figure. First, I disabled the SATA controller which I thought was the problem, in my BIOS. This didn't give any more different results than booting normally, except that the ad8 device wasn't created. The system just stopped loading after creating the acd0 device. So, that must not have been the problem, I thought. Then I disconnected the power and ATA cable from the problematic hard drive, which yielded the same results. Then, I disconnected my DVD drive, which didn't change the situation at all, except not creating the acd0 device at boot (And just hanging after initiating ad1, which is where I boot FreeBSD from) So I tried booting in verbose mode, which I hoped would give some error, or at least a clue. It didn't. At all. Then, my logic screamed at me, and I was smiling yet again. What if the verbose mode would give me a clue as to how the system manages to boot in safe mode? What if it tells me something like this and that was skipped, proceeding safe boot? After having figured out how to boot in safe AND verbose mode (By editing /boot/beastie.4th a little. Maybe booting in safe mode should be a 'boot' flag?), I happily rebooted the box again. Nothing broke from my edit, and it booted. I watched the screen and the scrolling text in anticipation, like a little boy on Christmas who is hoping that Santa will bring him the bike he's always wanted. As the kernel, very verbosely, complained about not being able to read stuff on the ad8 device, this kids eyes lighted up. He approached the Christmas tree, thinking that he had spotted the bike. And then, BAM. Everything with this boys name on the label under the tree was a soft package. Five packages from Santa; all soft. The kid lost hope, yet again, as his highly anticipated informative error messages were nowhere to find. I've attached the verbose dmesg.boot, in the hopes that someone will bring me a hard package with my name on it - before next Christmas. Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...8 8 4 3 3 0 0 done All buffers synced. Copyright (c) 1992-2006 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.1-RELEASE #0: Sun May 7 04:32:43 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0abe000. Preloaded elf module /boot/kernel/snd_es137x.ko at 0xc0abe188. Preloaded elf module /boot/kernel/sound.ko at 0xc0abe238. Calibrating clock(s) ... i8254 clock: 1193262 Hz
Enabling acpi support renders system unbootable (was: kernel: ad8: FAILURE - READ timed out LBA=234441585)
Daniel A. A. wrote: Daniel A. A. wrote: Hi, Whenever I try to boot my desktop workstation with FreeBSD, it suddenly just hangs there forever. When I boot into safe mode, however, I get this in the dmesg: Jun 18 16:01:46 b00b kernel: ad8: 114473MB Seagate ST3120022A 3.06 at ata4-master PIO4 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441585 Jun 18 16:01:46 b00b kernel: ad8: TIMEOUT - READ retrying (1 retry left) LBA=0 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441631 Jun 18 16:01:46 b00b kernel: ad8: TIMEOUT - READ retrying (0 retries left) LBA=0 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441644 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=0 Jun 18 16:01:46 b00b kernel: ad8: FAILURE - READ timed out LBA=234441585 Jun 18 16:01:46 b00b kernel: ad8: TIMEOUT - READ retrying (1 retry left) LBA=0 The hard drive is connected to an onboard Promise FastTrak (atapci1: Promise PDC20376 SATA150 controller port 0x8000-0x803f,0x7800-0x780f,0x7400-0x747f mem 0xab80-0xab800fff,0xab00-0xab01 irq 11 at device 14.0 on pci0) controller on my Asus p4s8x motherboard. The drive itself is connected to the optional PATA connector, which works wonderfully in Windows. I've currently managed to install Xorg and KDE on the box, all entirely in Safe Mode, but the performance is really bad, or not as good as it should be on a PC with a Pentium IV 2.4GHz and 1GB PC3200 RAM. Googling yields irrelevant results to my case, and search results for freebsd p4s8x (no quotes) indicate that FreeBSD should be working OK with my motherboard and all of its native components. So, does anybody know how to a) Fix this issue (or, if not) b) How to prevent a specific device (atapci1 or ad8) from being loaded during boot time? Again, googling yields no results, but I might be querying the wrong strings. Attached is my dmesg.boot Thanks for any help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Well, go figure. First, I disabled the SATA controller which I thought was the problem, in my BIOS. This didn't give any more different results than booting normally, except that the ad8 device wasn't created. The system just stopped loading after creating the acd0 device. So, that must not have been the problem, I thought. Then I disconnected the power and ATA cable from the problematic hard drive, which yielded the same results. Then, I disconnected my DVD drive, which didn't change the situation at all, except not creating the acd0 device at boot (And just hanging after initiating ad1, which is where I boot FreeBSD from) So I tried booting in verbose mode, which I hoped would give some error, or at least a clue. It didn't. At all. Then, my logic screamed at me, and I was smiling yet again. What if the verbose mode would give me a clue as to how the system manages to boot in safe mode? What if it tells me something like this and that was skipped, proceeding safe boot? After having figured out how to boot in safe AND verbose mode (By editing /boot/beastie.4th a little. Maybe booting in safe mode should be a 'boot' flag?), I happily rebooted the box again. Nothing broke from my edit, and it booted. I watched the screen and the scrolling text in anticipation, like a little boy on Christmas who is hoping that Santa will bring him the bike he's always wanted. As the kernel, very verbosely, complained about not being able to read stuff on the ad8 device, this kids eyes lighted up. He approached the Christmas tree, thinking that he had spotted the bike. And then, BAM. Everything with this boys name on the label under the tree was a soft package. Five packages from Santa; all soft. The kid lost hope, yet again, as his highly anticipated informative error messages were nowhere to find. I've attached the verbose dmesg.boot, in the hopes that someone will bring me a hard package with my name on it - before next Christmas. Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...8 8 4 3 3 0 0 done All buffers synced. Copyright (c) 1992-2006 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.1-RELEASE #0: Sun May 7 04:32:43 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc0abe000. Preloaded elf module /boot/kernel/snd_es137x.ko at 0xc0abe188. Preloaded elf
