RE: Upgrade from 4.6-STABLE (July) to 4.7-STABLE loses SCSI card?
On Thu, 28 Nov 2002, Scott Long wrote: Even though the ServeRAID card isn't supported (yet), it would be interesting to put it in and see what pciconf says about it. If it doesn't show up there either, then it's pretty good proof of a PCI problem. Okay, it doesn't show up either: nemesis# pciconf -vl | wc -l 41 nemesis# wc -l with_serveraid 41 with_serveraid Now, stupid question ... but would I at least see *something* if it was an IRQ conflict? The fact that it doesn't show up in pciconf means that FreeBSD does not see it within the PCI config space at all. This strengthens my suspicion of a PCI problem. Why it worked before and not now is beyond me. Maybe someone with more PCIBIOS experience would have an idea here. Are there any system BIOS settings that have changed recently or could possibly be experimented with? Trying the 5.0-DP2 CD might work also, but I wouldn't advise using it in production yet. Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Overlooking something, but what? (missing 39160 controller)
On Thu, 28 Nov 2002, Justin T. Gibbs wrote: Server is an IBM xSeries 360 ... only slot'd card is the 39160, everything else is onboard ... the card is in the same 64bit slot that it was in when it worked originally, but I have tested other slots and the same results ... Most likely FreeBSD is not enumerating the PCI bus that the card is attached to. Those that have tweaked the chipset drivers may be able to point you in the right direction. You should tell the list what chipset FreeBSD finds on the system. 'K, you'll have to help me out here ... not sure what chipset you are looking for, but my dmesg shows: [..] If you have the box working under linux, could you give us the output of a lspci -v? Wolfgang To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: how to control S.M.A.R.T. under FreeBSD ???
Vladislav, I am in the process of porting the Smartmon tools (http://sourceforge.net/projects/smartmontools/) to FreeBSD. I am currently waiting for Soren Schmidt to commit some changes to the ATA driver to support the SMART ATAPI commands. Then I can finish work on the port. Ed - Original Message - From: Vladislav V. Zhuk [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, November 28, 2002 9:26 AM Subject: how to control S.M.A.R.T. under FreeBSD ??? Hi! Last time IDE HDD often break. And I very need tool for monitoring S.M.A.R.T. my HDD to prevent loss data with broken harddrive. How I can to control S.M.A.R.T. under FreeBSD ??? -- Vladislav V. Zhuk (06267)3-60-03 [EMAIL PROTECTED] 2:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Temporary solution to IBM/PCI issue ...
On a whim, I checked the motherboard in my desktop machine ... she has two 64bit slots, and booting up with the card in recognizes it ... am going to things running with that motherboard to get me past the panic, and then start looking again at the IBM issue ... I have a linux guy here inhouse, so once I get the server back live, I'll get him to give me a hand to get that lsinf command run under Linux and report back on what it says ... The problem isn't fixed, only reduced in priority for a copule of hours ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Help needed debugging hard lock (SMP-related)
On Thu, 2002-11-28 at 12:07, Craig Boston wrote: (kgdb) print pidhashtbl[73508 pidhash].lh_first-p_pid $21 = 73508 Argh! I must be losing my mind or something. I swear there really WAS text above this before I hit send :) Anyway, it SHOULD have read something like the following: Sorry for replying to myself. I decided to try to determine where the one process in the RUN state (PID 73508) might be stuck, if indeed this process is what caused the freeze. After learning the basics of kgdb, I coaxed this out of my vmcore: To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Recreating vinum device ...
Okay, I need to confirm this before I run it, cause if it doesn't work, I'm royally screwed ... The old server, the drives on the controller I couldn't bring up had a vinum RAID5 device on it ... I have the original config file that I used to create that ... If I run 'vinum create -f config file' and don't run newfs, will I still end up toasting the RAID5 array, or is this safe? What happens if I inadvertently reversed the drives? Is there some way that I need to be doing this that I'm not seein gin the vinum man page? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Recreating vinum device ...
Got it *wipe brow* Kudos to he who developed vinum, brow is still a wee damp, but the man page is great and figured out that create is not the way to go :) On Thu, 28 Nov 2002, Marc G. Fournier wrote: Okay, I need to confirm this before I run it, cause if it doesn't work, I'm royally screwed ... The old server, the drives on the controller I couldn't bring up had a vinum RAID5 device on it ... I have the original config file that I used to create that ... If I run 'vinum create -f config file' and don't run newfs, will I still end up toasting the RAID5 array, or is this safe? What happens if I inadvertently reversed the drives? Is there some way that I need to be doing this that I'm not seein gin the vinum man page? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Sendmail question
:: Since sendmail 8.12 (4.6), I couldn't send anymore a mail locally on my :: private network. The mail is redirected to my external router (which have a :: fully qualified domain name). It sounds like you're defining SMART_HOST in your .mc file which sends all outgoing mail to go to a central relay site. However, without actually looking at your .mc file, it's hard to say for sure. Cheers - Erick To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Recreating vinum device ...
On Thursday, 28 November 2002 at 16:26:09 -0400, Marc G. Fournier wrote: On Thu, 28 Nov 2002, Marc G. Fournier wrote: Okay, I need to confirm this before I run it, cause if it doesn't work, I'm royally screwed ... The old server, the drives on the controller I couldn't bring up had a vinum RAID5 device on it ... I have the original config file that I used to create that ... If I run 'vinum create -f config file' and don't run newfs, will I still end up toasting the RAID5 array, or is this safe? What happens if I inadvertently reversed the drives? Is there some way that I need to be doing this that I'm not seein gin the vinum man page? Got it *wipe brow* Kudos to he who developed vinum, brow is still a wee damp, but the man page is great and figured out that create is not the way to go :) JOOI, what happened, and how did you fix it? Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
4.7-release-2002.11.14.02.05.57 - spontaneous reboot possibly related to modem/pccard/ppp
so far i had experienced 2 spontaneous reboots on freebsd 4.7-release-2002.11.14.02.05.57 (on dell inspiron 5000e). after being connected to internet (user ppp) via linksys pcmlm56 modem (on sio1) for say 2-3 minutes, card removed message comes (despite that it's still connected); messages follow indicating that the card has been found (even though card remain untouched through out the process)... moo /kernel: Nov 28 21:32:48 moo pccardd[60]: sio1: Linksys (EtherFast 10100 + 56K PC Card (PCMLM56)) removed. moo /kernel: Nov 28 21:32:54 moo pccardd[60]: Card Linksys(EtherFast 10100 + 56K PC Card (PCMLM56)) [(null)] [( Linksys (EtherFast 10100 + 56K PC Card (PCMLM56)) [(null)] [(null)] moo /kernel: Nov 28 21:32:54 moo pccardd[60]: Found existing driver (sio) for Linksys moo /kernel: Nov 28 21:32:54 moo pccardd[60]: Using I/O addr 0x2f8, size 8 moo /kernel: Nov 28 21:32:54 moo pccardd[60]: Using I/O addr 0x300, size 32 moo /kernel: Nov 28 21:32:54 moo pccardd[60]: Setting config reg at offs 0xffe0 to 0x43, Reset time = 900 ms moo /kernel: Nov 28 21:33:00 moo pccardd[60]: Assigning I/O window 0, start 0x2f8, size 0x8 flags 0x7 moo /kernel: Nov 28 21:33:00 moo pccardd[60]: Assigning I/O window 1, start 0x300, size 0x20 flags 0x7 moo /kernel: Nov 28 21:33:00 moo pccardd[60]: Assign sio1, io 0x2f8-0x2ff, mem 0x0, 0 bytes, irq 11, flags 0 moo /kernel: Nov 28 21:33:00 moo pccardd[60]: sio1: Linksys (EtherFast 10100 + 56K PC Card (PCMLM56)) inserted. ...then machine hangs, preparing for reboot (/tmp is mounted on mfs)... Nov 28 21:38:13 moo /kernel: swapon: adding /dev/ad0s2b as swap device Nov 28 21:38:13 moo /kernel: Automatic boot in progress... Nov 28 21:38:13 moo /kernel: Warning: Block size and bytes per inode restrict cylinders per group to 92. Nov 28 21:38:13 moo /kernel: Warning: inode blocks/cyl group (125) = data blocks (37) in last Nov 28 21:38:13 moo /kernel: cylinder group. This implies 1200 sector(s) cannot be allocated. ...any ideas? i don't know how significant this is, but this type of spontaneous reboot has had happened only when working on 2 batteries. below are possibly relevant files... kernel: http://parv.holy.cow/parv/comp/unix/cf/freebsd/KERNCONF dmesg (2002.10.22.03.43.30, will update asap): http://parv.holy.cow/parv/comp/unix/err/dmesg/delli5000e-dmesg /etc/pccard.conf: http://parv.holy.cow/parv/comp/unix/cf/network/pccard.pcmlm56 - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Recreating vinum device ...
On Fri, 29 Nov 2002, Greg 'groggy' Lehey wrote: On Thursday, 28 November 2002 at 16:26:09 -0400, Marc G. Fournier wrote: On Thu, 28 Nov 2002, Marc G. Fournier wrote: Okay, I need to confirm this before I run it, cause if it doesn't work, I'm royally screwed ... The old server, the drives on the controller I couldn't bring up had a vinum RAID5 device on it ... I have the original config file that I used to create that ... If I run 'vinum create -f config file' and don't run newfs, will I still end up toasting the RAID5 array, or is this safe? What happens if I inadvertently reversed the drives? Is there some way that I need to be doing this that I'm not seein gin the vinum man page? Got it *wipe brow* Kudos to he who developed vinum, brow is still a wee damp, but the man page is great and figured out that create is not the way to go :) JOOI, what happened, and how did you fix it? We had an IBM xSeries server that FreeBSD lost its ability to recognize the 39160 dual channel controller that we had 14 drives sitting on ... we moved the hardware to another, non-IBM machine (ie. my desktop), which all the hardware show'd up on, but, in the excitement, we didn't think to mark the cables as to which channel was which, and, of course, my desktop didn't have the appropriate /dev/vinum devices ... now, I notice(d) that the drives appear to store their own information internally, which the dumpconfig was able to show up ... if I had plugged the channels in wrong (ie. da0 - da7, da7 - d0), what would have happened had I run 'vinum start'? would it know to arrange the drives properly regardless, or would I risk screwin gmy file system? ::( To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 4.7-release-2002.11.14.02.05.57 - spontaneous reboot possibly related to modem/pccard/ppp
in message [EMAIL PROTECTED], wrote parv thusly... so far i had experienced 2 spontaneous reboots on freebsd 4.7-release-2002.11.14.02.05.57 (on dell inspiron 5000e). after being connected to internet (user ppp) via linksys pcmlm56 modem (on sio1) for say 2-3 minutes, card removed message comes (despite that it's still connected); messages follow indicating that the card has been found (even though card remain untouched through out the process)... ... http://parv.holy.cow/parv/comp/unix/cf/freebsd/KERNCONF http://parv.holy.cow/parv/comp/unix/err/dmesg/delli5000e-dmesg http://parv.holy.cow/parv/comp/unix/cf/network/pccard.pcmlm56 sorry, i didn't realise that holy.cow domain exists only in the mind of my machine. below are the correct ones, for sure i promise... kernel: http://www103.pair.com/parv/comp/unix/cf/freebsd/KERNCONF dmesg: http://www103.pair.com/parv/comp/unix/err/dmesg/delli5000e-dmesg /etc/pccard.conf: http://www103.pair.com/parv/comp/unix/cf/network/pccard.pcmlm56 - parv -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
