Re: ahc fails to attach in -current (was: snapshot installation woes)
+---[ Gordon Tetlow ]-- | On Sat, 4 Aug 2001, Gordon Tetlow wrote: | | Sure enough, that fixed the kernel panic, but here's the next odd piece, | my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 | dmesg reports that ahc0 is there. The lines from the dmesg are (hand | typed): | | ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff |irq 15 at device 15.0 on pci0 | aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs | | Since -stable and -current are using the exact same driver, there is | something more subtle (and sinister?) going on that I can't figure out. At | this point, I'm throwing my hands up in the air unless someone can give me | a better idea as to what the possible problem could be. I'd really like to | try -current on this box as it's a dual proc PPro 200. You'll probably need to use DEVFS to get booted. I can't boot -current from ahc using a standard /dev/ (or couldn't around the time DEVFS switched from being default disabled, to default enabled, so I've been running DEVFS ever since). This from either a 2940UW, or from dual onboard 7895's. So if you can get it installed, try building a new kernel with DEVFS enabled. I can't run SMP with ahc either, the machine locks up and I get messages about interrupts being off for too long (it was a while ago, but, I try an SMP build every month or so, and it still locks up (don't get to see the messages in X though)). Somtimes I do get more than 2-3 mins of uptime before it locks, and I can see that /dev/smb0 is no longer 'configured' (lmmon et. al. stop working). So if you do get it booted, be prepared for some torrid times d8) -- Totally Holistic Enterprises Internet| | Andrew Milton The Internet (Aust) Pty Ltd | | ACN: 082 081 472 ABN: 83 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068|[EMAIL PROTECTED]| To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ahc fails to attach in -current (was: snapshot installation woes)
Gordon Tetlow wrote: On Sat, 4 Aug 2001, Gordon Tetlow wrote: Sure enough, that fixed the kernel panic, but here's the next odd piece, my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 dmesg reports that ahc0 is there. The lines from the dmesg are (hand typed): ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 device_probe_and_attach: ahc0 attach returned 12 errno.h says ENOMEM is 12, so it seems that something in the ahc driver is unable to allocate memory. Dunno where or why, but something is fouling it up. By contrast 4.3-RELEASE doesn't have any issues (I'll try a recent snapshot if that would help). Sorry I can't help out any more, but the debugging tools in the installation disks seem to lacking (understandably). Okay, I tried with a 4.4-PRERELEASE bootdisk that was available on current.jp.freebsd.org and dmesg came up with the following: ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs Since -stable and -current are using the exact same driver, there is something more subtle (and sinister?) going on that I can't figure out. At this point, I'm throwing my hands up in the air unless someone can give me a better idea as to what the possible problem could be. I'd really like to try -current on this box as it's a dual proc PPro 200. I don't know if -current and -stable are using the same driver. Something *IS* different. Please see my post from about a month or so back in the aic7xxx group. Nobody responded to this. Where it would boot, with both controllers [3940UW on the MB] under -stable, it came up with the same message on ahc0 then after probing ahc1 and finding something there, reassigning ahc1 to ahc0. I ended up solving my own problem on this, although it did cause yet other problems. I had, because of IRQ issues, disabled the secondary IDE controller in the BIOS, to allow for both SCSI controller sides to have independant IRQs. This was causing the exact same message you note [see the dmesg output in the aic7xxx list]. Interesting to note that even with the secondary IDE controller disabled on the MB, -current failed to recognize this, and then in turn enabled it. Once I turned on the second IDE controller, this whole thing cleared up, albeit, with side-effects [now my Hauppauge WinTV/Theatre card is in conflict, and will cause a spontaneous reboot in both winblowz and fbsd when the TV is activated, although radio works fine]. Are you disabling motherboard IRQs in a similar fashion? Play with your IRQs, and have Plug and Play set in your BIOS. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ahc fails to attach in -current (was: snapshot installation woes)
Andrew Kenneth Milton wrote: +---[ Gordon Tetlow ]-- | On Sat, 4 Aug 2001, Gordon Tetlow wrote: | | Sure enough, that fixed the kernel panic, but here's the next odd piece, | my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 | dmesg reports that ahc0 is there. The lines from the dmesg are (hand | typed): | | ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 | aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs | | Since -stable and -current are using the exact same driver, there is | something more subtle (and sinister?) going on that I can't figure out. At | this point, I'm throwing my hands up in the air unless someone can give me | a better idea as to what the possible problem could be. I'd really like to | try -current on this box as it's a dual proc PPro 200. You'll probably need to use DEVFS to get booted. I can't boot -current from ahc using a standard /dev/ (or couldn't around the time DEVFS switched from being default disabled, to default enabled, so I've been running DEVFS ever since). This from either a 2940UW, or from dual onboard 7895's. So if you can get it installed, try building a new kernel with DEVFS enabled. I can't run SMP with ahc either, the machine locks up and I get messages about interrupts being off for too long (it was a while ago, but, I try an SMP build every month or so, and it still locks up (don't get to see the messages in X though)). Somtimes I do get more than 2-3 mins of uptime before it locks, and I can see that /dev/smb0 is no longer 'configured' (lmmon et. al. stop working). So if you do get it booted, be prepared for some torrid times d8) As far as DEVFS goes, isn't that config option now depreciated, and everything is in devfs? By the way, I think I see his problem right now! Exactly as I said in my last message on this topic... What does his dmesg say for ata1? irq 15? Same shit I ran into... ata isn't reading if the controller is disabled in BIOS. Under -stable, this is being read, and no conflict exists. Could this actually be related to changes in ata? SMP and ahc0/1 work fine here... Tyan S1696-DLUA MoBo, 2 P2-333's, Linksys 10/100 on dc0, DEC DEFPA SAS UTP-PMD, SB Live!, and WinTV/Theatre. Copyright (c) 1992-2001 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 5.0-CURRENT #12: Tue Jul 31 16:18:35 CDT 2001 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/WAHOO Timecounter i8254 frequency 1192995 Hz CPU: Pentium II/Pentium II Xeon/Celeron (333.00-MHz 686-class CPU) Origin = GenuineIntel Id = 0x650 Stepping = 0 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 536870912 (524288K bytes) avail memory = 516796416 (504684K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 IOAPIC #0 intpin 16 - irq 11 IOAPIC #0 intpin 17 - irq 9 IOAPIC #0 intpin 18 - irq 5 IOAPIC #0 intpin 19 - irq 10 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 [...] ahc0: Adaptec aic7895 Ultra SCSI adapter port 0xe000-0xe0ff mem 0xfebfd000-0xfebfdfff irq 10 at device 15.0 on pci0 ahc0: Using left over BIOS settings ahc1: Adaptec aic7895 Ultra SCSI adapter port 0xec00-0xecff mem 0xfebff000-0xfebf irq 11 at device 15.1 on pci0 ahc1: Using left over BIOS settings jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ahc fails to attach in -current (was: snapshot installation woes)
On Sat, 4 Aug 2001, Gordon Tetlow wrote: Sure enough, that fixed the kernel panic, but here's the next odd piece, my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 dmesg reports that ahc0 is there. The lines from the dmesg are (hand typed): ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 device_probe_and_attach: ahc0 attach returned 12 errno.h says ENOMEM is 12, so it seems that something in the ahc driver is unable to allocate memory. Dunno where or why, but something is fouling it up. By contrast 4.3-RELEASE doesn't have any issues (I'll try a recent snapshot if that would help). Sorry I can't help out any more, but the debugging tools in the installation disks seem to lacking (understandably). Okay, I tried with a 4.4-PRERELEASE bootdisk that was available on current.jp.freebsd.org and dmesg came up with the following: ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs Since -stable and -current are using the exact same driver, there is something more subtle (and sinister?) going on that I can't figure out. At this point, I'm throwing my hands up in the air unless someone can give me a better idea as to what the possible problem could be. I'd really like to try -current on this box as it's a dual proc PPro 200. Thanks, -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: snapshot installation woes
On Sat, 4 Aug 2001, John Baldwin wrote: On 04-Aug-01 Gordon Tetlow wrote: I decided I was going to brave 5.0-CURRENT and give the snapshots available on current.jp.freebsd.org a try. I found a couple issues with installation disks (FWIW, I tried it on the lastest snapshot avail on current.freebsd.org. I got the same results). Anyway, I go through the standard kern/mfsroot floppy deal and when it boots the kernel, everything seems to be going fine until I get the following kernel panic: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffab That's a NULL pointer deref. fault code= supervisor write, page not present instruction pointer = 0x8:0xc0a75ac0 Hmmm... Can you look in the bin dist for the kernel.debug and do a 'gdb -k' on it to look up this address to see what line it is dying on? No idea on the ahc0 error. :( A little more information, if I disable the on-board audio (pnpscan shows it to be CSCe835 IBM Audio Feature) the kernel panic goes away. I'm still working on getting the line it's dying on. -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: snapshot installation woes
On 04-Aug-01 Gordon Tetlow wrote: I decided I was going to brave 5.0-CURRENT and give the snapshots available on current.jp.freebsd.org a try. I found a couple issues with installation disks (FWIW, I tried it on the lastest snapshot avail on current.freebsd.org. I got the same results). Anyway, I go through the standard kern/mfsroot floppy deal and when it boots the kernel, everything seems to be going fine until I get the following kernel panic: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffab That's a NULL pointer deref. fault code= supervisor write, page not present instruction pointer = 0x8:0xc0a75ac0 Hmmm... Can you look in the bin dist for the kernel.debug and do a 'gdb -k' on it to look up this address to see what line it is dying on? No idea on the ahc0 error. :( -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
snapshot installation woes
I decided I was going to brave 5.0-CURRENT and give the snapshots available on current.jp.freebsd.org a try. I found a couple issues with installation disks (FWIW, I tried it on the lastest snapshot avail on current.freebsd.org. I got the same results). Anyway, I go through the standard kern/mfsroot floppy deal and when it boots the kernel, everything seems to be going fine until I get the following kernel panic: Fatal trap 12: page fault while in kernel mode fault virtual address = 0xffab fault code = supervisor write, page not present instruction pointer = 0x8:0xc0a75ac0 stack pointer = 0x10:0xc6978f68 frame pointer = 0x10:0xc6978f80 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupts enabled, resume, IOPL = 0 current process = 26 (irq10:sn0) trap number = 12 panic: page fault syncing disks... done Uptime: 2s FWIW, it's 5.0-20010804-JPSNAP #0 available off of current.jp.freebsd.org. I noticed it said it was in sn0. So being industrious, I interrupted the autoboot and did: ok set hint.sn.0.disabled=1 Sure enough, that fixed the kernel panic, but here's the next odd piece, my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940 dmesg reports that ahc0 is there. The lines from the dmesg are (hand typed): ahc0: Adaptec 2940 Ultra SCSI adapter port 0x5000-0x50ff mem 0x5000-0x5fff irq 15 at device 15.0 on pci0 device_probe_and_attach: ahc0 attach returned 12 errno.h says ENOMEM is 12, so it seems that something in the ahc driver is unable to allocate memory. Dunno where or why, but something is fouling it up. By contrast 4.3-RELEASE doesn't have any issues (I'll try a recent snapshot if that would help). Sorry I can't help out any more, but the debugging tools in the installation disks seem to lacking (understandably). Any help? -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
