Re: Panic: sched_add: kse 0xc1c40f60 (named) already in run queue
On 07/08/05 18:52, Marcin wrote: I've seen posts about this issue on current@, but without any solution. Maybe my case will help to shed some light on this one. 2 Cpu 5.4 STABLE (from today 09.07.05) running without any problems. The kernel is almost a GENERIC, except: Enabled: SMP SHCED_ULE IPSEC IPSEC_ESP INVARIANTS INVARIANT_SUPPORT some devices disabled, some added (scbus,da,snp,pf,pflog) Do you have problems with SCHED_4BSD? I think SMP+ULE causes problems even on CURRENT, although I may have missed more recent developments: http://lists.freebsd.org/pipermail/freebsd-current/2005-June/thread.html#50882 http://lists.freebsd.org/pipermail/freebsd-current/2005-June/051311.html -- Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195 signature.asc Description: OpenPGP digital signature
rcorder dumps core for a circular dependency
I am wondering if I should file a PR on /sbin/rcorder dumping core? This is a reproducible core dump. I am using FreeBSD 5-Stable dated July 2, I think. SMP, i386, custom kernel. First, try this. Make a file that looks like this: #!/bin/sh # # PROVIDE: hello_world # REQUIRE: hello_world Now, save it, and let's call it "hello_world.sh" Now, try and order this one file. #rcorder hello_world.sh rcorder: Circular dependency on file `hello_world.sh'. rcorder: Circular dependency on provision `hello_world' in file `hello_world.sh'. rcorder in free(): error: chunk is already free Abort (core dumped) Exit 134 Whoops, that's not nice, is it?!?? Since rcorder normally only runs at bootup, I smell a big problem if such a problem existed in a startup script. I know that this file does indeed have a circular dependency, but let's please not dump core because of it. The impending other problem is that 6-current will soon be released, and there will be eventually a stable, and in that branch everything in /usr/local/etc/rc.d/*.sh is sent to rcorder. Putting "rcorder" into our world of ports maintainers, some of which could write some insane rcng startup files ouch. Perhaps we need to ensure that things of this sort can't happen -- and we need a strenuous sanity check on the files in /usr/local/etc/rc.d between now and 6-release. I know, admins should check these files, but in many cases they may not, and then get a big *surprise* when their machine dumps core during boot. I guess it's one thing for 6-Current, but another thing for the stable tree. We may have a lot of time in the 5.x tree, but as sure as I say that, the new /etc/rc.d/localpkg hack will get backported to 5.x and something may start going wrong. Back to the circular dependency, I have one example of this happening in a port's rc.d script, but I don't want to mention any names... I found this out when a port I had installed kept crashing rcorder when I tried running rcorder on /usr/local/etc/rc.d/*.sh. So now that I found this, I was going to write a PR, but hey, I figured I'd say something here first. Can someone verify this on 6-Current, anyway? If so, it is definitely a major bug for that branch. For 5.x, rcorder is only run on a small set of files in /etc, most of which don't get edited much, minimizing its impact. But still a bug nevertheless. One other thing: I know nothing about NetBSD, but should this be reported to them, too? Okay, one more shot at this bug. Try this shell script: #!/bin/sh # # PROVIDE: hello_world # BEFORE: hello_world Save it as hello1.sh. # rcorder hello1.sh rcorder: Circular dependency on file `hello1.sh'. rcorder: Circular dependency on provision `fake_prov_' in file `hello1.sh'. rcorder in free(): error: chunk is already free Abort (core dumped) Exit 134 Whoops again. Billy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Panic: sched_add: kse 0xc1c40f60 (named) already in run queue
I've seen posts about this issue on current@, but without any solution.
Maybe my case will help to shed some light on this one.
2 Cpu 5.4 STABLE (from today 09.07.05) running without any problems.
The kernel is almost a GENERIC, except:
Enabled:
SMP
SHCED_ULE
IPSEC
IPSEC_ESP
INVARIANTS
INVARIANT_SUPPORT
some devices disabled, some added (scbus,da,snp,pf,pflog)
Today I wanted to move a service to this machine which uses a lot
(about 70) network aliases from a few subnets.
First, I have experienced spontaneous reboots, mostly during the rc phase,
but sometimes a little bit later, i.e. after the system is up with simple
services (httpd, named, sshd) and I log in and do something network related.
(but not sure if this is not something else.).
However, the machine was not under even medium load.
When i reduce the number of aliases to about 30, instead of hard reboot
I get a panic:
sched_add: kse 0xc1c40f60 (named) already in run queue
This might be some trail; the panic usually occurs when the named is used -
during
the rc phase of setting up network services or after, when doing something
network
oriented. Unfortunately, I didn't make any tests without named enabled
(I should have thought of that :(( )
The named is bound to all the ip's of the interface, sshd to only on of them,
httpd to
a wildcard address (so said sockstat)
setting kern.smp.disabled in bootloader fixes both issues (but wastes one cpu
;( )
I have a core dump and a kernel with debugging symbols, so please e-mail me if
it
needs to me shared. The problem with it is that it is big (500mb) so If You
would rather
download a movie from e-mule instead, please request for any info i can dig
with kgdb
You need. I'd really like this to be fixed, so I'm eager to help!
Here's a backtrace:
(kgdb) bt
#0 doadump () at pcpu.h:160
#1 0xc055165a in boot (howto=260) at ../../../kern/kern_shutdown.c:410
#2 0xc0551a05 in panic (fmt=0xc0783970 "sched_add: kse %p (%s) already in run
queue")
at ../../../kern/kern_shutdown.c:566
#3 0xc0565699 in sched_add_internal (td=0xc1c40e10, preemptive=0)
at ../../../kern/sched_ule.c:1706
#4 0xc05655df in sched_add (td=0x0, flags=1) at ../../../kern/sched_ule.c:1676
#5 0xc0565db9 in slot_fill (kg=0xc19a8070) at kern_switch.c:217
#6 0xc05d in sched_thread_exit (td=0x0) at kern_switch.c:1035
#7 0xc055d6b0 in thread_exit () at ../../../kern/kern_thread.c:547
#8 0xc053e4cb in thread_userret (td=0xc1d82640, frame=0xd8a16d38)
at ../../../kern/kern_kse.c:1296
#9 0xc0577345 in userret (td=0xc1d82640, frame=0xd8a16d38, oticks=0)
at ../../../kern/subr_trap.c:120
#10 0xc07447d6 in syscall (frame=
{tf_fs = 137494575, tf_es = 137429039, tf_ds = -1079115729, tf_edi =
136541440, tf_esi = 0, tf_ebp = -1079059000, tf_isp = -660509340, tf_ebx = 0,
tf_edx = 136541440, tf_ecx = -1079059088, tf_eax = 2, tf_trapno = 0, tf_err =
2, tf_eip = 674795967, tf_cs = 31, tf_eflags = 642, tf_esp = -1079059364, tf_ss
= 47}) at ../../../i386/i386/trap.c:1059
#11 0xc072f37f in Xint0x80_syscall () at ../../../i386/i386/exception.s:201
#12 0x0832002f in ?? ()
#13 0x0831002f in ?? ()
#14 0xbfae002f in ?? ()
#15 0x08237500 in ?? ()
#16 0x in ?? ()
#17 0xbfaeddc8 in ?? ()
#18 0xd8a16d64 in ?? ()
#19 0x in ?? ()
#20 0x08237500 in ?? ()
#21 0xbfaedd70 in ?? ()
---Type to continue, or q to quit---
#22 0x0002 in ?? ()
#23 0x in ?? ()
#24 0x0002 in ?? ()
#25 0x283891bf in ?? ()
#26 0x001f in ?? ()
#27 0x0282 in ?? ()
#28 0xbfaedc5c in ?? ()
#29 0x002f in ?? ()
#30 0x in ?? ()
#31 0x in ?? ()
#32 0x in ?? ()
#33 0x in ?? ()
#34 0x1f38f000 in ?? ()
#35 0xc1cdc960 in ?? ()
#36 0xc1d82790 in ?? ()
#37 0xd8a16b18 in ?? ()
#38 0xd8a16af0 in ?? ()
#39 0xc1d82640 in ?? ()
#40 0xc0564bf0 in sched_switch (td=0x0, newtd=0x8237500, flags=Cannot access
memory at address 0xbfaeddd8
)
at ../../../kern/sched_ule.c:1300
Previous frame inner to this frame (corrupt stack?)
(kgdb)
(kgdb) f 3
#3 0xc0565699 in sched_add_internal (td=0xc1c40e10, preemptive=0)
at ../../../kern/sched_ule.c:1706
1706../../../kern/sched_ule.c: No such file or directory.
in ../../../kern/sched_ule.c
(kgdb) p *td
$1 = {td_proc = 0xc1cdd000, td_ksegrp = 0xc19a8070, td_plist = {tqe_next =
0xc1c43640,
tqe_prev = 0xc1d82648}, td_kglist = {tqe_next = 0x0, tqe_prev =
0xc1d82650}, td_slpq = {
tqe_next = 0x0, tqe_prev = 0xc1aa03e0}, td_lockq = {tqe_next = 0x0,
tqe_prev = 0x0},
td_runq = {tqe_next = 0x0, tqe_prev = 0xc19a8084}, td_selq = {tqh_first = 0x0,
tqh_last = 0xc1c40e40}, td_sleepqueue = 0xc1aa03e0, td_turnstile =
0xc1c0d640,
td_tid = 100089, td_flags = 0, td_inhibitors = 0, td_pflags = 128, td_dupfd =
0,
td_wchan = 0x0, td_wmesg = 0x0, td_lastcpu = 1 '\001', td_oncpu = 255 '˙',
td_locks = 0,
td_blocked = 0x0, td_ithd = 0x0, td_lockname = 0x0, td_contested = {lh_first
= 0x0},
td_sleeplocks = 0x0, td_intr_nesting_level = 0, td_p
Re: gmirror, sparc and SCSI problems
On Fri, Jul 08, 2005 at 03:48:52PM +0100, Chris Hodgins wrote: > Hi all, > > Experiencing a few difficulties setting up raid mirroring across two > SCSI disks on a sparc based server. Disk da0 contains a working and > recent install of FreeBSD 5-4 RELEASE and da1 is blank. We have been > following the guidance given in the first part of > http://people.freebsd.org/~rse/mirror/ but have hit numerous problems. Chris, These instructions are useful if you don't want to boot into recovery console to set things up offline. You can save a lot of fancy footwork if you have physical access and a CD-ROM, and don't mind about 15 minutes of downtime. My crib sheet is at http://dannyman.toldme.com/2005/01/24/freebsd-howto-gmirror-system/ . If it does work for you, plesae let me know. I'd be plased to hear that it can handle Sparc. :) Sincerely, -danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to set polling for printer upon startup
On Sat, Jul 09, 2005 at 09:39:17AM +1200, Jonathan Chen wrote: > On Fri, Jul 08, 2005 at 02:53:25PM -0500, Stephen Montgomery-Smith wrote: > > My printer doesn't work very well unless I type > > lpcontrol -p > > What is the "correct" way to make this happen when the computer first > > boots up - is there some setting in device.hints or something I can put > > in the kernel config so that it defaults to this? > > I've got: > > hint.ppc.0.flags="0x28" > > in my /boot/device.hints to do this. Using 0x28 also puts the port in ECP mode. To put it in polling mode only, use 0x20. Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgprQ3giFmQF8.pgp Description: PGP signature
Re: How to set polling for printer upon startup
On Fri, Jul 08, 2005 at 02:53:25PM -0500, Stephen Montgomery-Smith wrote:
> My printer doesn't work very well unless I type
> lpcontrol -p
> What is the "correct" way to make this happen when the computer first
> boots up - is there some setting in device.hints or something I can put
> in the kernel config so that it defaults to this?
I've got:
hint.ppc.0.flags="0x28"
in my /boot/device.hints to do this.
Cheers.
--
Jonathan Chen <[EMAIL PROTECTED]>
--
char *p="char *p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How to set polling for printer upon startup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Jul 08, 2005 at 02:53:25PM -0500, Stephen Montgomery-Smith wrote: > My printer doesn't work very well unless I type > lpcontrol -p > What is the "correct" way to make this happen when the computer first boots > up > - is there some setting in device.hints or something I can put in the kernel > config so that it defaults to this? Well, I have a very complex and esoteric script that I load. However, perhaps with years of study, you can duplicate it. #!/bin/sh lpcontrol -e (Which is what I need in my case for a similar problem) Just put it into /usr/local/etc/rc.d and make it executable, changing the -p to an -e of course. Call it whatever you wish, but be sure to add an sh extension, e.g. call it lptcontrol.sh That should do it. - -- Scott GPG KeyID EB3467D6 ( 1B848 077D 66F6 9DB0 FDC2 A409 FA54 D575 EB34 67D6) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Buffy: Have I ever let you down? Giles: Do you want me to answer that, or shall I just glare? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCzuPE+lTVdes0Z9YRAmztAJ48gCcwd0QlTkAkSMKbJNLxTeiy7gCdFA6f Vrd0I0AKNT4KYomP9QE7QrA= =SZBs -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to set polling for printer upon startup
My printer doesn't work very well unless I type lpcontrol -p What is the "correct" way to make this happen when the computer first boots up - is there some setting in device.hints or something I can put in the kernel config so that it defaults to this? Thanks, Stephen -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA HDD installer issue
Kevin Oberman wrote: Don't forget that any "modern" BIOS and HD will be using LBA, not CHS, for addressing the disk and disks have not had the same number of sectors per track on all cylinders for a long time, so the numbers are bogus in any case. CHS does not allow properly addressing any modern drive and BIOS always "makes up" the values reported (but not used, to the best of my knowledge) and those work fine in every case I have encountered. I'd just ignore the warning and proceed. I did that. I don't know if that's part of the problem (I have AthlonXP 2200 with a Via KT266A chipset), I get the same types of complaints from sysinstall, I ignore the warning, it leaves a good size chunk of disk at the end unused, then I get error messages about failing to initialize various slices and structures. Check screen #2, lots of WRITE_DMA error messages while doing the superblocks. Tried booting the install kernel in safe mode. Still get the warnings about the values reported by the BIOS (which is set to auto-detect the drives), but it successfully creates the disk and goes through the install. My BIOS reports the values of Cyn 38309, heads 16, Sectors 255. It's a WD800, 80GB ATA100. So I'm getting the same errors on install as the OP, and it appears that I have the same problems with the controller & drivers that other VIA users are... So far, if I boot the install using safe mode, I can install. However, on reboot, the log goes crazy with WRITE_DMA errors, and things start getting flaky (don't know exactly what is happening, I gave up on it for a few days...) Are the two problems related? Will installing the ATA III patch set ### fix any of this? Oh, yeah, Obligatory whine... WinXP installed into a partition on this machine without a problem... John FreeBSD since 2.0.2 Starting on a 486/50 -- John T. FarmerOwner & CTOGoldSword Systems [EMAIL PROTECTED] 865-691-6498 Knoxville TN Consulting, Design, & Development of Networks & Software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA HDD installer issue
Don't forget that any "modern" BIOS and HD will be using LBA, not CHS, for addressing the disk and disks have not had the same number of sectors per track on all cylinders for a long time, so the numbers are bogus in any case. CHS does not allow properly addressing any modern drive and BIOS always "makes up" the values reported (but not used, to the best of my knowledge) and those work fine in every case I have encountered. I'd just ignore the warning and proceed. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 > Date: Fri, 08 Jul 2005 19:56:49 +0200 > From: Pascal Groenen <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > I noticed a similar thing with a similar HD. I went with the FreeBSD > suggestion and it resulted in a corrupted HD. I would just go with the > Disk/BIOS settings. I did that before for other disks and never had issues > then. > > > - Original Message - > From: "J. Nyhuis" <[EMAIL PROTECTED]> > To: > Sent: Friday, July 08, 2005 7:38 PM > Subject: Q: ATA HDD installer issue > > > > Greetings, > > > > I am installing FreeBSD 5.4 on a system using a Seagate Barracuda (Model > > ST380011A) 80GB drive. This drive has 38297 cylinders, 16 heads, and 255 > > sectors (this is identified both on a label on the drive and by the BIOS > > IDE auto-detect). > > The FreeBSD installer make it to the disk partitioning screen, and > > produces an error stating that my drive parameters are wrong, and that I > > should manually correct them. When I enter the parameters 38297/16/255 > > (cylinders/heads/sectors), it tells me that the parameters are wrong and > > refuses to take my input. > > The hardware manual states that the drive parameters for fdisk should be > > what is reported in the BIOS (which they are, in this case). > > > > Ideas? > > > > Thanks, > > > > John H. Nyhuis > > Sr. Computer Specialist > > Dept. of Pediatrics > > HS RR349B, Box 356320 > > University of Washington > > Desk: (206)-685-3884 > > [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA HDD installer issue
Well, the FreeBSD default partition setting fails to complete a format. It won't accept the 'real settings', and I can't seem to figure out a way to force them. I'll have to poke about under advanced install to see if it will let me force FDISK paremeters. Thanks, John H. Nyhuis Sr. Computer Specialist Dept. of Pediatrics HS RR349B, Box 356320 University of Washington Desk: (206)-685-3884 [EMAIL PROTECTED] On Fri, 8 Jul 2005, Pascal Groenen wrote: I noticed a similar thing with a similar HD. I went with the FreeBSD suggestion and it resulted in a corrupted HD. I would just go with the Disk/BIOS settings. I did that before for other disks and never had issues then. - Original Message - From: "J. Nyhuis" <[EMAIL PROTECTED]> To: Sent: Friday, July 08, 2005 7:38 PM Subject: Q: ATA HDD installer issue Greetings, I am installing FreeBSD 5.4 on a system using a Seagate Barracuda (Model ST380011A) 80GB drive. This drive has 38297 cylinders, 16 heads, and 255 sectors (this is identified both on a label on the drive and by the BIOS IDE auto-detect). The FreeBSD installer make it to the disk partitioning screen, and produces an error stating that my drive parameters are wrong, and that I should manually correct them. When I enter the parameters 38297/16/255 (cylinders/heads/sectors), it tells me that the parameters are wrong and refuses to take my input. The hardware manual states that the drive parameters for fdisk should be what is reported in the BIOS (which they are, in this case). Ideas? Thanks, John H. Nyhuis Sr. Computer Specialist Dept. of Pediatrics HS RR349B, Box 356320 University of Washington Desk: (206)-685-3884 [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.8.11/44 - Release Date: 8-7-2005 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATA HDD installer issue
I noticed a similar thing with a similar HD. I went with the FreeBSD suggestion and it resulted in a corrupted HD. I would just go with the Disk/BIOS settings. I did that before for other disks and never had issues then. - Original Message - From: "J. Nyhuis" <[EMAIL PROTECTED]> To: Sent: Friday, July 08, 2005 7:38 PM Subject: Q: ATA HDD installer issue Greetings, I am installing FreeBSD 5.4 on a system using a Seagate Barracuda (Model ST380011A) 80GB drive. This drive has 38297 cylinders, 16 heads, and 255 sectors (this is identified both on a label on the drive and by the BIOS IDE auto-detect). The FreeBSD installer make it to the disk partitioning screen, and produces an error stating that my drive parameters are wrong, and that I should manually correct them. When I enter the parameters 38297/16/255 (cylinders/heads/sectors), it tells me that the parameters are wrong and refuses to take my input. The hardware manual states that the drive parameters for fdisk should be what is reported in the BIOS (which they are, in this case). Ideas? Thanks, John H. Nyhuis Sr. Computer Specialist Dept. of Pediatrics HS RR349B, Box 356320 University of Washington Desk: (206)-685-3884 [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.8.11/44 - Release Date: 8-7-2005 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Q: ATA HDD installer issue
Greetings, I am installing FreeBSD 5.4 on a system using a Seagate Barracuda (Model ST380011A) 80GB drive. This drive has 38297 cylinders, 16 heads, and 255 sectors (this is identified both on a label on the drive and by the BIOS IDE auto-detect). The FreeBSD installer make it to the disk partitioning screen, and produces an error stating that my drive parameters are wrong, and that I should manually correct them. When I enter the parameters 38297/16/255 (cylinders/heads/sectors), it tells me that the parameters are wrong and refuses to take my input. The hardware manual states that the drive parameters for fdisk should be what is reported in the BIOS (which they are, in this case). Ideas? Thanks, John H. Nyhuis Sr. Computer Specialist Dept. of Pediatrics HS RR349B, Box 356320 University of Washington Desk: (206)-685-3884 [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ata problem !!
On Fri, July 8, 2005 1:39 pm, Dani Popa said: > # ip stack options > options INET > #optionsINET6 > options IPSTEALTH > options TCP_DROP_SYNFIN > options ZERO_COPY_SOCKETS > options IPFILTER > options IPFILTER_LOG > options DEVICE_POLLING > options ACCEPT_FILTER_DATA > options ACCEPT_FILTER_HTTP > options LIBMCHAIN > options ALTQ > options ALTQ_CBQ > options ALTQ_RED > options ALTQ_RIO > options ALTQ_HFSC > options ALTQ_PRIQ > One question here, probably unrelated to your problem :P. I know ALTQ doesn't explicitely cite pf as a requirement, but is it possible to use ALTQ in combination with IPFILTER? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ata problem !!
sorry!! bash-2.05b# uname -v FreeBSD 5.4-STABLE #0: Wed Jul 6 17:06:55 EEST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/COSMIC kernel conf: # general options machine i386 cpu I686_CPU ident ALPHA maxusers0 options CPU_SUSP_HLT options CPU_ENABLE_SSE options HZ=1000 options INCLUDE_CONFIG_FILE # kernel/vm options #optionsSCHED_ULE options SCHED_4BSD options COMPAT_FREEBSD4 options COMPAT_43 options KTRACE options _KPOSIX_PRIORITY_SCHEDULING options P1003_1B_SEMAPHORES options ADAPTIVE_GIANT #optionsPREEMPTION #optionsFULL_PREEMPTION options BLKDEV_IOSIZE=8192 options DFLDSIZ="(128*1024*1024)" options MAXDSIZ="(160*1024*1024)" options MAXSSIZ="(160*1024*1024)" options SYSVSHM options SHMMAXPGS=4096 options SHMMAX="(SHMMAXPGS*PAGE_SIZE)+1" options SHMALL="(SHMMAXPGS*PAGE_SIZE)+1" options SHMMIN=2 options SHMMNI=33 options SHMSEG=257 options SYSVSEM options SEMMNI=257 options SEMMNS=513 options SEMMNU=257 options SEMMAP=257 options SEMMSL=97 options SEMOPM=129 options SEMUME=33 options SYSVMSG options MSGMNB=1024 options MSGMNI=128 options MSGSEG=4097 options MSGSSZ=1024 options MSGTQL=409601 options LIBICONV # ip stack options options INET #optionsINET6 options IPSTEALTH options TCP_DROP_SYNFIN options ZERO_COPY_SOCKETS options IPFILTER options IPFILTER_LOG options DEVICE_POLLING options ACCEPT_FILTER_DATA options ACCEPT_FILTER_HTTP options LIBMCHAIN options ALTQ options ALTQ_CBQ options ALTQ_RED options ALTQ_RIO options ALTQ_HFSC options ALTQ_PRIQ # filesystems options FFS options SOFTUPDATES options UFS_ACL options UFS_DIRHASH options UFS_EXTATTR options UFS_EXTATTR_AUTOSTART options CD9660 options CD9660_ICONV options UDF options PSEUDOFS options PROCFS options QUOTA # MAC framework #optionsMAC #optionsMAC_BIBA #optionsMAC_BSDEXTENDED #optionsMAC_LOMAC #optionsMAC_MLS #optionsMAC_PARTITION #optionsMAC_PORTACL #optionsMAC_SEEOTHERUIDS # hardware (&options) # northbridge device npx device apic device acpi device pmtimer device atkbdc device atkbd device psm device vga device sc device sio device speaker device fdc # southbridge device isa device pci device agp device ata device atadisk device ataraid options ATA_STATIC_ID device sym device scbus device pass device atapicam device da device cd device miibus device sk device fxp device xl # pseudo devices device md device loop device mem device io device random device ether device vlan device gif device gre device tun device tap device bpf device pf device pflog device pfsync #device ipl device pty device snp dmesg before build and install every thing: Copyright (c) 1992-2004 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.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (644.83-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x387fbff real memory = 268435456 (256 MB) avail memory = 253030400 (241 MB) ioapic0: Assuming intbase of 0 ioapic0 irqs 0-31 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0xf400-0xf7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci0: at device 2.0 (no driver attached) pcib2: at device 3.0 on pci0 pci2: on pcib2 pci2: at device 0.0 (no driver attached) sym0: <895> port 0x2400-0x24ff mem 0xf0301000-0xf0301fff,0xf0302000-0xf03020ff irq 11 at device 1.0 on pci2 sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: [GIANT-LOCKED] fxp0: port
Re: ata problem !!
hi all, my freebsd not recognize ata hard-disk. i have 3 scsi hard-disk and 1 ata hard-disk. After i make buildworld and build/install kernel and install world my freebsd don't recognize ata hard-disk. before install new kernel some dmesg: Please attach your uname -v , kernel conf file, full dmesg I never seen any mind (or cpu) reader on this list. U. Timecounters tick every 10.000 msec Interrupt storm detected on "irq10: uhci0"; throttling interrupt source ad0: 28629MB [58168/16/63] at ata0-master UDMA33 Waiting 15 seconds for SCSI devices to settle after install new kernel some dmesg: Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = enabled Waiting 2 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. in my kernel conf: device ata device atadisk with some weeks before i was install the same kernel on the same machine and every thing was ok, but now???... i have a problem. can anyone tell me what it's my problem ? 10x (thanks)! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ata problem !!
hi all, my freebsd not recognize ata hard-disk. i have 3 scsi hard-disk and 1 ata hard-disk. After i make buildworld and build/install kernel and install world my freebsd don't recognize ata hard-disk. before install new kernel some dmesg: Timecounters tick every 10.000 msec Interrupt storm detected on "irq10: uhci0"; throttling interrupt source ad0: 28629MB [58168/16/63] at ata0-master UDMA33 Waiting 15 seconds for SCSI devices to settle after install new kernel some dmesg: Timecounters tick every 1.000 msec IP Filter: v3.4.35 initialized. Default = pass all, Logging = enabled Waiting 2 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. in my kernel conf: device ata device atadisk with some weeks before i was install the same kernel on the same machine and every thing was ok, but now???... i have a problem. can anyone tell me what it's my problem ? 10x (thanks)! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gmirror, sparc and SCSI problems
Hi all, Experiencing a few difficulties setting up raid mirroring across two SCSI disks on a sparc based server. Disk da0 contains a working and recent install of FreeBSD 5-4 RELEASE and da1 is blank. We have been following the guidance given in the first part of http://people.freebsd.org/~rse/mirror/ but have hit numerous problems. The first problem is that the system is lacking fdisk. From reading around on various newsgroups, this appears to be due to the sparc architecture. It seems that we can probably miss this step out anyway though although it may be related to our next problem. The next step requires us to run bsdlabel (or in our case sunlabel) on /dev/mirror/gm0s1. In our /dev/mirror directory we only have a single gm0 node so we can't run these steps either. We managed to assemble da1 with the partitions we wanted using sysinstall and had thought that by creating the mirror on da1 it would generate the appropriate gm0a, gm0b...etc. Unfortunately this did not work. Here is the output of sunlabel: # sunlabel -c mirror/gm0 # /dev/mirror/gm0: text: FreeBSD34G cyl 4425 alt 2 hd 255 sec 63 bytes/sectors: 512 sectors/cylinder: 16065 sectors/unit: 71087625 8 partitions: # # Size is in cylinders. # Offset is in cylinders. #size offset #-- -- b:262131 c: 4425 0 d:131 0 e:653393 f:262 1046 Straight after we ran sysinstall we ran sunlabel -e da1 and added the offset of 16, as you can see from the above output our offset has now gone again. Now this also brings us onto another interesting problem. Our two scsi disks are identical. Same size, manufacturer and part number. However running sunlabel -c on both of them gives very different sizes in regards to cyclinders and sectors: # sunlabel -c da0 # /dev/da0: text: FreeBSD34G cyl 24620 alt 2 hd 27 sec 107 bytes/sectors: 512 sectors/cylinder: 2889 sectors/unit: 71127180 8 partitions: # # Size is in cylinders. # Offset is in cylinders. #size offset #-- -- a:726 0 b: 1452726 c: 24620 0 d: 3630 2178 e: 1452 5808 # sunlabel -c da1 # /dev/da1: text: FreeBSD34G cyl 4425 alt 2 hd 255 sec 63 bytes/sectors: 512 sectors/cylinder: 16065 sectors/unit: 71087625 8 partitions: # # Size is in cylinders. # Offset is in cylinders. #size offset #-- -- b:262131 c: 4425 0 d:131 0 e:653393 f:262 1046 dmesg shows our disks like this: da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabledda0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabledda1: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) dmesg also shows the mirror being completed: GEOM_MIRROR: Device gm0 created (id=2793795997). GEOM_MIRROR: Device gm0: provider da1 detected. GEOM_MIRROR: Device gm0: provider da1 activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. Does anyone have any information that may help us resolve any of these problems? Many thanks Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA support in 5.x ... ?
On Fri, 8 Jul 2005, Igor Robul wrote: Marc G. Fournier wrote: I'm looking at upgrading my only SATA server to 5.x, since the 4.x that is currently running on it is getting hangs whenever load is put onto the drives :( IIRC you are using 3Ware hardware RAID with SATA drives, which is NOT same as using SATA drives. Your OS does not access SATA drives directly, and so SATA stabolity is not cause of your problems. There must be another cause. Check other hardware parts. I took a look at the 'latest driver' available from 3ware for the 4.x line, which is not what the 4.x line current has committed, and there were a couple of items that *might* apply ... specifically, one deal with 256k stripe size (which we're using) and one deaing with the Intel 7520 chipset (which, again, I believe we aer using ... its an SE7520 motherboard) ... From what I can tell, the hangs are "file system", since when it does hang, I can login via SSH and get the MOTD stuff, but nothing past that (no shell prompt) .. We're going to move that server to 5.x over the next couple of days and see if that corrects the problem, since its the 'route of least resistance' and then work from a "supported operating system" ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems to compile 4-stable jail
I'm trying to compile a 4-stable jail on my 5.4-release-p3 box, and got this error: ===> lib/libedit cc -O -pipe -I. -I/var/tinderbox/jails/4-i386/src/lib/libedit-c editline.c -o editline.o In file included from /var/tinderbox/jails/4-i386/src/lib/libedit/chared.h:134, from /var/tinderbox/jails/4-i386/src/lib/libedit/el.h:97, from /var/tinderbox/jails/4-i386/src/lib/libedit/chared.c:47, from editline.c:4: fcns.h:94: warning: missing white space after `#define VI_' In file included from editline.c:9: help.c:51: `VI_ZERO' undeclared here (not in a function) help.c:51: initializer element is not constant help.c:51: (near initialization for `el_func_help[23].func') In file included from editline.c:12: /var/tinderbox/jails/4-i386/src/lib/libedit/map.c:667: `VI_ZERO' undeclared here (not in a function) /var/tinderbox/jails/4-i386/src/lib/libedit/map.c:667: initializer element is no t constant /var/tinderbox/jails/4-i386/src/lib/libedit/map.c:667: (near initialization for `el_map_vi_command[48]') *** Error code 1 Stop in /var/tinderbox/jails/4-i386/src/lib/libedit. *** Error code 1 Stop in /var/tinderbox/jails/4-i386/src/lib. *** Error code 1 Stop in /var/tinderbox/jails/4-i386/src. *** Error code 1 Stop in /var/tinderbox/jails/4-i386/src. *** Error code 1 Stop in /var/tinderbox/jails/4-i386/src. *** Error code 1 Stop in /var/tinderbox/jails/4-i386/src. -- Renato Botelho ICQ: 54596223 AIM: RBGargaBR ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Another ata and dma problem - maybe because INTEL
Vinny Abello wrote: At 09:49 PM 7/7/2005, you wrote: Hi, i`m using freebsd releng_5 and got weird problem with AtA_DMA... I bought mobo with i865PE chipset and when I allow DMA transfer in BIOS for my TEAC cd-540E drive, freebsd fails to boot with: ATA_INTERRUPT was seen but timeout fired out with LBA=0.. I also tried applying a ATA mkIII with no luck(it tells me that ata_if.h is missing). When I remove teac from my system, it boots correctly. I tried also in loader.conf typing hw.ata.atapi_dma=0, but still the same...fails to boot. I`ve before this mobo with VIA kt333 chipset, and it allows me to set PIO4 for drive (with no problemo at freebsd boot) Any ideas or patches? Just out of curiosity, check to make sure you have the latest firmware for the Teac drive. I recall encountering problems with a Teac CD-ROM drive on a new motherboard with a fairly new chipset on the market (this was a long time ago) until I updated the firmware in the drive. I couldn't boot any OS off the drive, yet it worked fine on other motherboards. It's worth a shot. You might have similar problems with any OS on that motherboard and CD-ROM drive. Vinny Abello Network Engineer Server Management [EMAIL PROTECTED] (973)300-9211 x 125 (973)940-6125 (Direct) PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A Tellurian Networks - The Ultimate Internet Connection http://www.tellurian.com (888)TELLURIAN "Courage is resistance to fear, mastery of fear - not absence of fear" -- Mark Twain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" Hi, I`ve my bios upgraded before 3 years to newest version (v3.0A). Maybe teac knows about it and doesn`t want to solve this kind of issues (no old drive support :( ). But why is hw.ata.atapi_dma unusable? If I set it at startup to 0, it means that I don`t want an DMA for atapi interface... but it`s always enabled. I tried booting SLAX and it goes well from my cdrom. Windows performs well too. Any ideas? Jan Sebosik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
