Re: No interrupts coming to device driver.

2005-11-13 Thread Alexander Nedotsukov

Warner,

Unfortunately my BIOS do not allow IRQ reservation for ISA devices. But 
in I noticed Interrupt Mode menu with PIC/APIC options. This pushed me 
to go through another round of tests. First with PIC mode and back again 
with APIC but now with device apic added to kernel config. After  few 
attempts to use different IRQs I finally got interrupts on IRQ9. Well. 
This is good and I can move forward with driver. Though I still confused 
the way it done. I will be really appreciated if some good will explain 
me what is behind all this woodoo I did. Is it necessary to have device 
apic today? And still what is the nature of those ?lost in hardware? 
interrupts?

BTW. Here is a quote from dmesg which may be connected to the case.

ACPI APIC Table: ASUS   P4SQ
ioapic0 Version 8.0 irqs 0-23 on motherboard
acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20

Another bits of info. Windows automagically assigns IRQ7 to device and 
works fine. But I can not use IRQ7 on FreeBSD even with device apic in 
kernel. I do have hardware which is not in use ATM (PCI TV card). But I 
do not have any driver installed on Windows too. So if this is the case 
Windows somehow makes better guess of what driver can use.


Anyway thanks everyone who tried to help!

All the best,
Alexander.

M. Warner Losh wrote:

In message: [EMAIL PROTECTED]
Alexander Nedotsukov [EMAIL PROTECTED] writes:
: I trying to create small lirc (www.lirc.org) compatible CIR driver for 
: it8705 chip (sits on ISA bus). My problem is I can not get interrupts 
: coming to driver. I believe I configured chip (carrier freq. + baudrate 
: divisor) and enabled interrupt mode the same way it windows driver does. 
: It also seems to be correct according to chip specs. But nothing. vmstat 
: -i shows zeros for assigned irq. And my IRS stay cold. I wrote small 
: userland program which polls CIRs IIR (interrupt identefication 
: register) and it shows interrupt pending bit set on right after I press 
: key on remote control. Looks like I missed something fundamental. Does 
: anyone can give me a hint where to look?


If it is on the ISA bus, then you can look at the IRQ line that you
are using for this card on the scope.  Set it to trigger on an edge
(either falling if the signal is high or rising if the signal is low,
usually it is high).

Make sure that the IRQ that you are using is not shared with anything
else, even hardware you aren't using.  That's forbidden in the ISA
world (although some hacks exist to do interrupt sharing with two
devices on the ISA bus, (a) almost nobody does them and (b) they don't
work when sharing with pci).

Make sure that the IRQ is set in the BIOS as Legacy/ISA rather than
ISAPNP/PCI (or some variants of those phrases).

See if there's a way to force an interrupt on the chip by writing to a
register of some sort.  It doesn't matter if you are going to use
this, but it will be good for testing.

It almost certainly isn't an unacknowledged interrupt (unless it is
left over from before your chip reset).  In my experience, those cause
vmstat of 1.  It might be worth checking the chip initialization
sequence to make sure that you clear any possible interrupts AFTER
you've done the bus_setup_inter() call to register your interrupt
handler.

That's all I can think of at the moment, but it should keep you busy
for a few hours :-)

Warner
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
  

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: UFS2 max limits?

2005-11-13 Thread John-Mark Gurney
Joseph Koshy wrote this message on Sat, Nov 12, 2005 at 11:05 +0530:
 The Wikipedia page referenced below says that UFS2 supports a
 filesystem size of 2^80 Bytes (1YiB) with the limit on a given
 file being 2^55 bytes (32 PiB).

Those sound correct, as UFS2 uses 64bit frag addresses, which when
combined with a frag size of 16 (for 65536 bytes per frag) gives you
2^80 for total file system size

as for the file size, The approximate max can be calculated by
(blocksize / sizeof(ufs2_daddr_t)) ^ 3 * blocksize
the real max would add in addition:
(blocksize / sizeof(ufs2_daddr_t)) ^ 2 * blocksize + 
(blocksize / sizeof(ufs2_daddr_t)) * blocksize + 
9 * blocksize 

so, with a blocksize of 65536, and ufs2_daddr_t's size being 8 bytes,
you end up with:
(2^16 / 2^3) ^ 3 * 2^16
(2^13)^3 * 2^16
2^(13*3) * 2^16
2^39 * 2^16
2^(39 + 16)
2^55

but if you add the additional blocks, you'll end up with larger, but
not enough to go to 2^56 for file sizes...

 Are these numbers correct?  I somehow remember the limits as
 being much lower (of the order of 16TB or so).

You might be thinking of UFS1...  Now there is a funny thing that
I found out about UFS2 and UFS1...  UFS1 supports larger file
sizes (not file system sizes) due to the fact that the ufs_daddr_t
is smaller (32bits), means it can get more out of the indirect blocks
than UFS2 can... UFS1 can have files of 2^58 compared to UFS2's 2^55...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 All that I will do, has been done, All that I have, has not.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: UFS2 max limits?

2005-11-13 Thread John-Mark Gurney
John-Mark Gurney wrote this message on Sun, Nov 13, 2005 at 10:17 -0800:
 as for the file size, The approximate max can be calculated by
 (blocksize / sizeof(ufs2_daddr_t)) ^ 3 * blocksize
 the real max would add in addition:
 (blocksize / sizeof(ufs2_daddr_t)) ^ 2 * blocksize + 
 (blocksize / sizeof(ufs2_daddr_t)) * blocksize + 
 9 * blocksize 
  ^
ack, I miss remebered, I knew I needed to check this before I sent the
email:
!!grep define.*N[DI]ADDR /usr/include/ufs/ufs/dinode.h
#define NDADDR  12  /* Direct addresses in inode. */
#define NIADDR  3   /* Indirect addresses in inode. */

The 9 above should be 12...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 All that I will do, has been done, All that I have, has not.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: SSH From within a Jail

2005-11-13 Thread Koen Martens
Koen Martens wrote:
 d c wrote:
 
Greetings:

I currently am running Freebsd 6.0 Release.

I am experimenting with jails and have run into a
problem.  I need to ssh from within my jail to another
server.  Actually I need to use scp.  WHen I try it I
get the error:  Host key verification failed.
 
 
 This could also be something related to permissions on the .ssh
 directory, but you cleared that out of the way if i understand the
 rest of this thread correctly. I remember having this problem once,
 but can't remember right now what i did to solve it.. I usually
 compile openssh from source anyway, so you might try that. If that
 works, it would probably be interesting to see what is the
 difference between your own hand-rolled openssh and the one that
 came with your world.

Just remembered something else: do you jexec into the jail, or do
you do a proper logon (eg. ssh into the jail). I think that if you
jexec into the jail and then try to ssh, you might have a problem
because you aren't really logged in to the jail and thus have no
(psuedo) tty associated with your session..

Koen

-- 
K.F.J. Martens, Sonologic, http://www.sonologic.nl/
Networking, hosting, embedded systems, unix, artificial intelligence.
Public PGP key: http://www.metro.cx/pubkey-gmc.asc
Wondering about the funny attachment your mail program
can't read? Visit http://www.openpgp.org/
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Help: Asus P5WD2 mobo and ITE IDE controller problem

2005-11-13 Thread Murray Taylor
Hi all,

I have had a system configured using this mobo and have hit a
showstopper.

The HDD (a seagate 330GB IDE) have been connected to the ITE IDE
controller
while the DVDrom has been connected to the primary IDE controller. 

It seems that the ITE device is a RAID controller, and the BIOS and
the 5.4 FreeBSD installer dont see the HDD at all.  Which is not very
useful!

The mobo has a SATA port as well, and the question is

Does 5.4 support SATA drives for install? 

I think I can tell the BIOS to make a SATA drive 'look like' an IDE 
drive.

(sent to hackers also for this followup question)
As a followup - Does anyone know of any support re the ITE device?


CPU Intel Pentium 4 640 3.2Ghz 2MB 775
M/B Asus P5WD2 -  Premium M/B
Ram 2.048GB (2x-1.024GB) CL3.0 DDR2 533
HDD Seagate 300GB 7200RPM 8MB
Optical Drive   Pioneer 110-D 16 x DVD/RW Black w/NERO
FDD 1.44MB Floppy Drive Black
TapeCertance DDS5 Tape Drive
SCSI Card   Adaptec  19160 SCSI Card
PSU 600Watt


-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

Murray Taylor
Bytecraft Systems
P: +61 3 8710 2555
F: +61 3 8710 2599
D: +61 3 9238 4275
E: [EMAIL PROTECTED]
---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

***This Email has been scanned for Viruses by MailMarshal.***
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Help: Asus P5WD2 mobo and ITE IDE controller problem

2005-11-13 Thread Roland Smith
On Mon, Nov 14, 2005 at 10:13:51AM +1100, Murray Taylor wrote:
 Hi all,
 
 I have had a system configured using this mobo and have hit a
 showstopper.
 
 The HDD (a seagate 330GB IDE) have been connected to the ITE IDE
 controller
 while the DVDrom has been connected to the primary IDE controller. 
 
 It seems that the ITE device is a RAID controller, and the BIOS and
 the 5.4 FreeBSD installer dont see the HDD at all.  Which is not very
 useful!

The ASUS site doesn't mention what type the ITE controller is. According
to the ata(4) manual page, only the IT8211F and IT8212F are supported.

But according to the motherboard layout drawing in the manual, it is
indeed a IT8211F, so it should be supported. Are you sure it is enabled?

 The mobo has a SATA port as well, and the question is
 
 Does 5.4 support SATA drives for install? 

Yes.

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


pgpaiIBfSmg12.pgp
Description: PGP signature


RE: Help: Asus P5WD2 mobo and ITE IDE controller problem

2005-11-13 Thread Murray Taylor
 -Original Message-
 From: Roland Smith [mailto:[EMAIL PROTECTED] 
 
 On Mon, Nov 14, 2005 at 10:13:51AM +1100, Murray Taylor wrote:
  Hi all,
  
  I have had a system configured using this mobo and have hit a
  showstopper.
  
  The HDD (a seagate 330GB IDE) have been connected to the ITE IDE
  controller
  while the DVDrom has been connected to the primary IDE controller. 
  
  It seems that the ITE device is a RAID controller, and the BIOS and
  the 5.4 FreeBSD installer dont see the HDD at all.  Which 
  is not very useful!
 
 The ASUS site doesn't mention what type the ITE controller 
 is. According
 to the ata(4) manual page, only the IT8211F and IT8212F are supported.
 
 But according to the motherboard layout drawing in the manual, it is
 indeed a IT8211F, so it should be supported. Are you sure it 
 is enabled?
 

I believe that it is 'enabled' in that there is a momentary flash
of the ITE scanning and I think the disk is found as I reckon I
can catch something like this

??? 0: ST3300  UDMA?
??? 1:
??? 2:
??? 3:

where the ? are characters I havent caught.

But it never appears in the BIOS report. And the installer certainly 
doesnt talk to it at all.


  The mobo has a SATA port as well, and the question is
  
  Does 5.4 support SATA drives for install? 
 
 Yes.
 
 Roland
 -- 

mjt
---
The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.
---

***This Email has been scanned for Viruses by MailMarshal.***
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: poor fdc(4) performance

2005-11-13 Thread Pyun YongHyeon
On Sat, Nov 12, 2005 at 10:14:22AM -0600, Matthew D. Fuller wrote:
  On Sat, Nov 12, 2005 at 04:44:18PM +0900 I heard the voice of
  Pyun YongHyeon, and lo! it spake thus:
   
   Yes, it could be. But I think the machine is fast enough to read
   sequential blocks.
  
  Try running it without SMP.  There may be enough happening in the MP
  locking bit that you end up falling behind.  I remember noticing crap
  fdc performance (without larger block sizes) on my dual PPro a little
  while back.
  
Hmm, I think this is not the case as interrupt handler on fdc was
registered with FAST handler. In addition, the handler just invokes
wakeup(9), without any lock operations, to wake up kernel floppy
worker thread.

Note, I see the same issue on UP sparc64 too.
-- 
Regards,
Pyun YongHyeon
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]