ATA boot hang
After I did a buildworld (10/13), I'm getting a hang on boot on a Compaq DeskPro Workstation: ata1: spurious interrupt - status=0x00 error=0x01 ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ad0: setting UDMA100 on Intel ICH4 chip GEOM: create disk ad0 dp=0xc62c5570 ad0: Maxtor 57040H4/TAH71DPO ATA-6 disk at ata0-master ad0: 38166MB (78165360 sectors), 77545 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 GEOM: new disk ad0 ata1-slave: pio=0x0c wdma=0x22 udma=0x cable=40pin ata1-master: WARNING - ATA_IDENTITY soft error (ECC corrected)[0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:78156162 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 40015954944 end 40015987199 GEOM: Configure ad0s1a, start 0 length 268435456 end 268435455 GEOM: Configure ad0s1b, start 268435455 length 1588903936 end 1857339391 GEOM: Configure ad0s1c, start 0 length 40015954944 end 40015954943 GEOM: Configure ad0s1d, start 1857339391 length 268435456 end 2125774847 GEOM: Configure ad0s1e, start 2125774847 length 268435456 end 2394210303 GEOM: Configure ad0s1f, start 2394210304 length 27621744640 end 40015954943 I tried to set hw.ata.ata_dma=0 and hw.ata.atapi_dma=0, thinking it might be related. It's not, or at least it still hangs: ata1: spurious interrupt - status=0x00 error=0x01 ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ad0: setting PIO4 on Intel ICH4 chip GEOM: create disk ad0 dp=0xc62c5570 ad0: Maxtor 57040H4/TAH71DPO ATA-6 disk at ata0-master ad0: 38166MB (78165360 sectors), 77545 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, PIO4 GEOM: new disk ad0 ata1-slave: pio=0x0c wdma=0x22 udma=0x cable=40pin ata1-master: WARNING - ATA_IDENTITY soft error (ECC corrected)[0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:78156162 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure ad0s1, start 32256 length 40015954944 end 40015987199 GEOM: Configure ad0s1a, start 0 length 268435456 end 268435455 GEOM: Configure ad0s1b, start 268435455 length 1588903936 end 1857339391 GEOM: Configure ad0s1c, start 0 length 40015954944 end 40015954943 GEOM: Configure ad0s1d, start 1857339391 length 268435456 end 2125774847 GEOM: Configure ad0s1e, start 2125774847 length 268435456 end 2394210303 GEOM: Configure ad0s1f, start 2394210304 length 27621744640 end 40015954943 And it hangs there. Takes a hard reset to start back up. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ATA_IDENTITY soft error
Did a -CURRENT buildworld this AM, and restarted on the new kernel. On detecting ad0, it throws an error: ad0: 38166MB Maxtor 5T040H4 [77545/16/63] at ata0-master UDMA 100 ata1-master: WARNING - ATA_IDENTITY soft error (ECC corrected) What's this? Patrick ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Fatal Trap 3?
I'm used to seeing fatal traps 1, 11 and 12, but 3 is a new one to me. Before I go digging into code to try to find out what's wrong, could someone *briefly* explain what a "fatal trap 3: Breakpoint instruction fault" is? I don't want to waste a lot of time on a hardware problem... Patrick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: hang when making port
moving to -current Tobias Roth wrote: Hi I just built a new stable on wednesday. Now, when making ports, the process sometimes hangs after the source is downloaded and I have to do a ctrl-c and another make to continue. Is this known and will it be fixed soon (or is already)? On a side note, this also occurs on -current, since I saw it happening right after I installed -current on a new laptop. (Fresh build). I'll dig into it today to see if I can figure out what's causing it. I'd hate to see this happen when 4.2 is released. Patrick -- Patrick Gardella [EMAIL PROTECTED] The Power to Serve shall not be infringed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
XFree86 3.3.6_3 build dies on -current
I built and installed -current on a laptop yesterday (10/23/00), and went to build XFree86 3.3.6_3 today from the ports directory. It built fine, but when you run make install, it dies, complaining of syntax errors in machine/endian.h: In file included from /usr/include/sys/wait.h:93, from vgaHW.c:44: /usr/include/machine/endian.h:72: syntax error before `__uint16_swap_unit32' /usr/include/machine/endian.h:72: syntax error before `__x' snip I've not seen this reported before, nor a work around. I was only building the VGA and SVGA servers and took the defaults on every thing else. Patrick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree86 3.3.6_3 build dies on -current
"Rogier R. Mulhuijzen" wrote: In file included from /usr/include/sys/wait.h:93, from vgaHW.c:44: /usr/include/machine/endian.h:72: syntax error before `__uint16_swap_unit32' /usr/include/machine/endian.h:72: syntax error before `__x' snip I've not seen this reported before, nor a work around. I don't know which is "the right thing" but adding '#include sys/types.h' in front of either the '#include sys/wait.h' in vgaHW.c or in front of the '#include machine/endian.h' in /usr/include/sys/wait.h should fix your blues. I'm guessing one is the fix and the other is a workaround, but don't know which is which =) . I'm not up to speed on include rules... sys/types.h is already defined in front of sys/wait.h in vgaHW.c :( Patrick To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Kernel panic on fxp
I've been working for a while to try to figure out a problem I'm having here. I did a buildworld Sunday, and started to get kernel panics on boot when it probed fxp. So I removed fxp from my kernel and loaded it as a module (via loader.conf.local). It paniced. Then I unloaded the if_fxp.ko on startup, and it booted. But if I load the fxp module now, after a full boot, everything is great. Rebooting with fxp in the kernel or loading the module on boot will cause a panic *every* time. Thinking it might be build problem, I redid the build/install/kernel again on Monday, and am having the same problems. The panics only started on the upgrade from a -current dated sometime in early July. As you will see from below, this is an SMP machine (dual P200) with 256 Megs RAM. I am also using NETGRAPH to run PPPoE. Any ideas? Patrick The panic is: Fatal trap 12: page fault while in kernel mode mp_lock=0005; cpuid = 0; lapic.id= fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc034e304 stack pointer = 0x10:0xc038bea8 frame pointer = 0x10=0xc038bebc code segment= base 0x0, limit 0xf, type 0x1b = DPC 0, pres 1, def 32 1, gran 1 processor eflag = interrupt enabled, resume, IOPC=0 current process = 0 (swapper) interrupt mask = net tty bio cam - SMP:XXX trap number = 12 panic: page fault To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Burned by config changes?
Indeed, this was the problem. I, at some time, switched it to -O2. Thanks for all the suggestions! Patrick Dan Papasian wrote: What optimizations did you use when compiling your kernel? (COPTFLAGS) If it's anything more than -O -pipe, then that may very well be your problem. -Dan On Tue, Jul 11, 2000 at 09:28:44PM -0400, Patrick Gardella wrote: I've somehow been burned by the config changes when I build world yesterday. The build went fine, and then I followed the instructions on: http://people.freebsd.org/~imp/config-upd.html But when I rebooted, it freezes right when I type "boot". Typing "boot -v" does not reveal anything more. I've gone in with an old kernel which lets me boot, and tried building a new GENERIC one, with no luck. It freezes at the same place. I have in place my /boot/device.hints, and it looks right. Any pointers to get the system back up and running? (I do have a backup, but I'd rather learn how to fix this!) Patrick Gardella To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Patrick -- Patrick Gardella [EMAIL PROTECTED] The Power to Serve shall not be infringed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Burned by config changes?
I've somehow been burned by the config changes when I build world yesterday. The build went fine, and then I followed the instructions on: http://people.freebsd.org/~imp/config-upd.html But when I rebooted, it freezes right when I type "boot". Typing "boot -v" does not reveal anything more. I've gone in with an old kernel which lets me boot, and tried building a new GENERIC one, with no luck. It freezes at the same place. I have in place my /boot/device.hints, and it looks right. Any pointers to get the system back up and running? (I do have a backup, but I'd rather learn how to fix this!) Patrick Gardella To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -CURRENT make world broken
I build world this morning, and it built fine. Patrick - Original Message - From: Kenneth Wayne Culver [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 30, 1999 12:23 PM Subject: -CURRENT make world broken I was just wondering if anyone else was having a problem making the world on -CURRENT right now? I don't remember the exact error I got because I'm at work, and my machine is at home, but for the last 3 weeks whenever I try to make world, it dies in a different place, I've tried every day, so I'm thinking maybe it's a problem with my computer's setup, or maybe I forgot to update something. What updates that I'm missing could be causing this? (for example, once I had this problem, and reinstalling the mk files in /usr/share/mk fixed it, is there something simple like this that I missed?) I will be sending the exact error as soon as I have a chance to reproduce it. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
