Re: PATCH for ATAng

2003-10-16 Thread Hidetoshi Shimokawa
At Thu, 16 Oct 2003 23:17:47 +0900,
Hiroyuki Aizu wrote:
 
 [1  text/plain; US-ASCII (7bit)]
 Hi.
 
 The original ata_reset() lost ATA-master drive and remove main file system
 after suspend/resume. Of cource it occors panic!
 I think that the ata_reset() in ata-lowlevel.c is bogus and I can not
 understand the code. So I study ATA and rewrite ata_reset() completely.
 
 New device detect algorism using ata command ATA_IDENTIFY_DEVICE and
 ATA_IDENTIFY_PACKET_DEVICE for judge ATA and ATAPI devices.
 
 This patch works fine with my TOSHIBA Libretto L5. 
 But not yet test ATAPI devices and ATA-slave channel.
 Maybe there is need to adjust wait DELAY time.
 
 Please test and replace ata_reset().
 
 I hope this solve ATAng troubles.
 
 --
 Hiroyuki Aizu
 [2 ata-lowlevel.c.diff application/octet-stream (base64)]

This patch fixes resume problem of my laptop (Toshiba Tecra).

Thanks,

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: [current tinderbox] failure on alpha/alpha

2003-08-02 Thread Hidetoshi Shimokawa
At Sat, 02 Aug 2003 00:47:45 -0600,
Scott Long wrote:
 
 Is anyone willing to fix this?  The warning is bogus as it's quite 
 obvious that the variable is being initialized.  Strange that it doesn't
 show up on other platforms.
 
 Scott

I have already committed a workaround for this.

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: firewire hangs on Thinkpad

2003-02-09 Thread Hidetoshi Shimokawa
Warner-san,

I confirmed that the following problem occurs not only for fwochi
but also for if_rl, if_xl, if_dc and ahc_pci.

After kldload if_rl, I got wi0 timeout.
(I don't even have those hardware.)

All drivers above supports both pci and cardbus...
Do you have any idea?

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

At Thu, 30 Jan 2003 01:25:19 +0900,
Hidetoshi Shimokawa wrote:
 
 At Wed, 29 Jan 2003 12:49:51 +0100,
 Andrea Campi wrote:
  
  On Sat, Jan 25, 2003 at 11:55:01AM -0700, M. Warner Losh wrote:
   This sounds like it might be an interrupt storm.  I'm not sure if the
   fwohci driver is failing to clear an interrupt source, or if the
   cardbus bridge is failing.  Have you connected a fw device to the
   firewire card?
  
  I've been able to run a few more tests, even though I've not done abused
  it in every way I have in my mind yet...
  
  The evidence I currently have is:
   - if I load the modules at loader time everything is fine, with or without
  a device attached
   - if I load the modules later on, the kldload doesn't return and the system
  stops responding; I can still enter DDB. The only way to recover from that is
  to eject the card; at that point, the system is usable BUT as soon as there
  is network activity, the system freezes hard (can't get to DDB).
  
  IMHO this is 100% an interrupt problem. Does this ring a bell with one of you,
  or should I provide more info?
 
 I have another strange firewire and cardbus/pccard interaction.
 If I load firewire module while I'm using wi0 in cardbus slot,
 the wi0 stop its work and output following messages.
 (In my laptop, fwohci is on PCI.)
 
 wi0: xmit failed
 wi0: timeout in wi_cmd 0x010b; event status 0x
 ...
 
 
 Even if I replace fwochi_pci_attach() with one line 'return EIO'
 (i.e. the doesn't anything), the problem still happens.
 
 I think this is not a problem of fwohci.
 Maybe PCI or Cardbus/PCcard or kldload problem?
 
 
 
 /\ Hidetoshi Shimokawa
 \/  [EMAIL PROTECTED]
 PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: firewire hangs on Thinkpad

2003-02-09 Thread Hidetoshi Shimokawa
At Sun, 09 Feb 2003 10:06:54 -0700 (MST),
M. Warner Losh wrote:
 Feb  9 09:52:40 hammer kernel: cbb_pcic_socket_enable:
 Feb  9 09:52:40 hammer kernel: cbb1: cbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
 Feb  9 09:52:40 hammer kernel: cbb1: cbb_power: CARD_VCC_5V and CARD_VPP_VCC [15
 ]
 Feb  9 09:52:40 hammer kernel: an0: RID access failed
 
 Most cards do *NOT* like being turned off.

Aha, that explains why my card's LED turns off when I load modules.

 Maybe something more like the following would be closer to correct:
 
 static void
 cardbus_driver_added(device_t cbdev, driver_t *driver)
 {
   int numdevs;
   device_t *devlist;
   int tmp;
   struct cardbus_devinfo *dinfo;
 
   DEVICE_IDENTIFY(driver, cbdev);
   device_get_children(cbdev, devlist, numdevs);
   for (tmp = 0; tmp  numdevs; tmp++) {
   if (device_get_state(devlist[tmp]) != DS_NOTPRESENT)
   continue;
   dinfo = device_get_ivars(devlist[tmp]);
   cardbus_print_verbose(dinfo);
   resource_list_init(dinfo-pci.resources);
   cardbus_do_cis(cbdev, dinfo-pci.cfg.dev);
   if (device_probe_and_attach(dinfo-pci.cfg.dev) != 0)
   cardbus_release_all_resources(cbdev, dinfo);
   }
   free(devlist, M_TEMP);
 }
 
 Warner

Thanks, this fixed my problem.

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: firewire hangs on Thinkpad

2003-02-09 Thread Hidetoshi Shimokawa
At Sun, 09 Feb 2003 10:06:54 -0700 (MST),
M. Warner Losh wrote:
 Feb  9 09:52:40 hammer kernel: cbb_pcic_socket_enable:
 Feb  9 09:52:40 hammer kernel: cbb1: cbb_power: CARD_VCC_0V and CARD_VPP_0V [44]
 Feb  9 09:52:40 hammer kernel: cbb1: cbb_power: CARD_VCC_5V and CARD_VPP_VCC [15
 ]
 Feb  9 09:52:40 hammer kernel: an0: RID access failed
 
 Most cards do *NOT* like being turned off.

Aha, that explains why my card's LED turns off when I load modules.

 Maybe something more like the following would be closer to correct:
 
 static void
 cardbus_driver_added(device_t cbdev, driver_t *driver)
 {
   int numdevs;
   device_t *devlist;
   int tmp;
   struct cardbus_devinfo *dinfo;
 
   DEVICE_IDENTIFY(driver, cbdev);
   device_get_children(cbdev, devlist, numdevs);
   for (tmp = 0; tmp  numdevs; tmp++) {
   if (device_get_state(devlist[tmp]) != DS_NOTPRESENT)
   continue;
   dinfo = device_get_ivars(devlist[tmp]);
   cardbus_print_verbose(dinfo);
   resource_list_init(dinfo-pci.resources);
   cardbus_do_cis(cbdev, dinfo-pci.cfg.dev);
   if (device_probe_and_attach(dinfo-pci.cfg.dev) != 0)
   cardbus_release_all_resources(cbdev, dinfo);
   }
   free(devlist, M_TEMP);
 }
 
 Warner

Thanks, this fixed my problem.

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: -current, IBM A30p 2 external FW-disks

2003-02-07 Thread Hidetoshi Shimokawa
At Thu, 6 Feb 2003 12:15:38 +0100 (CET),
Michael Reifenberger wrote:
 
 On Wed, 5 Feb 2003, Michael Reifenberger wrote:
 ...
   I have improved recovery code after timeout in -current.
   Could you try that?
 
  Is scheduled for this evening.
  Thanks so far!
 
 ...
 - fwcontorl -g 20
 - sysctl hw.firewire.sbp.max_speed=0
 - change SBP_QUEUE_LEN in sbp.c to 1 and rebuld module.
 - sysctl machdep.cpu_idle_hlt=0
 - sysctl debug.sbp_debug=1 and send me a dmesg.
 
 Ok, I did some extensive tests overnight.
 Essentially I still had `fwcontorl -g 20` and
 SBP_QUEUE_LEN=1 and maxopenings=1 and `debug.sbp_debug=1`.
 hw.firewire.sbp.max_speed started at 0 and got 2 at the end.
 After treating two `iozone -s 51200m -r1024k` on the platters
 overnight without problems I started with a plain sbp.c and
 no `fwcontorl -g 20`. I get constant rates of 13MB/s on each disk.
 No problems so far.
 Seems you got it. Thanks!

Do you have any timeout while the test?
I think SBP_QUEUE_LEN or maxopenings is the important parameter.
Can you try to change thoes values?

 BTW: switching on debug.firewire_debug gives zillions of 'kick'...
 Is this just a notification about the code-path?

Yes, but it doesn't seem necessary anymore, removed.

Thanks,

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: -current, IBM A30p 2 external FW-disks

2003-02-07 Thread Hidetoshi Shimokawa
At Fri, 7 Feb 2003 10:56:33 +0100 (CET),
Michael Reifenberger wrote:
 
 On Fri, 7 Feb 2003, Hidetoshi Shimokawa wrote:
 
 ...
  Do you have any timeout while the test?
 No. Not any longer.
  I think SBP_QUEUE_LEN or maxopenings is the important parameter.
  Can you try to change thoes values?
 
 The are at their defaults at the moment.
 Do you want me to increase them?

hmm, I had changed the process AFTER timeout and I suppose
I don't change the behavior BEFORE timeout...

Anyway it works :-)
If you have any problem later, please let me know.

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: -current, IBM A30p EPSON scanner

2003-02-07 Thread Hidetoshi Shimokawa
Try SANE-patch included in:

http://people.freebsd.org/~simokawa/firewire/firewire-20030205.tar.gz

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html


At Fri, 7 Feb 2003 12:13:25 +0100 (CET),
Michael Reifenberger wrote:
 
 Hi,
 next phenomen :-)
 
 I have an 'Epson perfection 2450 Photo' scanner which gets found using firewire  as:
 pass0 at sbp0 bus 0 target 0 lun 0
 pass0: EPSON GT-9700 1.05 Fixed Processor SCSI-4 device
 pass0: 50.000MB/s transfers

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: -current, IBM A30p 2 external FW-disks

2003-02-04 Thread Hidetoshi Shimokawa
I have improved recovery code after timeout in -current.
Could you try that?

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

At Sun, 2 Feb 2003 13:28:33 +0200,
mike wrote:
 
 [1  text/plain; iso-8859-1 (7bit)]
 On Thu, 30 Jan 2003 14:41:59 +0900, Hidetoshi Shimokawa wrote 
  Do you get timeout only for sbp0:0:0? 
  Is the other drive still working? 
   
  I have no problem with concurrent accesses with `iozone -s 102400m -r 
  1024k`. 
 ... 
  try some of the following: 
   
  - fwcontorl -g 20 
  - sysctl hw.firewire.sbp.max_speed=0 
  - change SBP_QUEUE_LEN in sbp.c to 1 and rebuld module. 
  - sysctl machdep.cpu_idle_hlt=0 
  - sysctl debug.sbp_debug=1 and send me a dmesg. 
  
 with all of the above I get the attached dmesg soon after 
 setting up two concurrent iozones (one per disk): 
...

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: -current, IBM A30p 2 external FW-disks

2003-02-02 Thread Hidetoshi Shimokawa
At Sun, 2 Feb 2003 13:28:33 +0200,
mike wrote:
  try some of the following: 
   
  - fwcontorl -g 20 
  - sysctl hw.firewire.sbp.max_speed=0 
  - change SBP_QUEUE_LEN in sbp.c to 1 and rebuld module. 
  - sysctl machdep.cpu_idle_hlt=0 
  - sysctl debug.sbp_debug=1 and send me a dmesg. 
  
 with all of the above I get the attached dmesg soon after 
 setting up two concurrent iozones (one per disk): 

Hmm,
Are you sure that you have chaned SBP_QUEUE_LEN to 1 and
rebuild and reinstalled it?

I suppose 'unordered execution' shouldn't happen for SBP_QUEUE_LEN=1
case.

Anyway, how about change 'maxopenings' for cam_simq_alloc() in sbp.c
to 1?

BTW, after timeout message, did the transfer resume?

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: firewire hangs on Thinkpad

2003-01-29 Thread Hidetoshi Shimokawa
At Wed, 29 Jan 2003 12:49:51 +0100,
Andrea Campi wrote:
 
 On Sat, Jan 25, 2003 at 11:55:01AM -0700, M. Warner Losh wrote:
  This sounds like it might be an interrupt storm.  I'm not sure if the
  fwohci driver is failing to clear an interrupt source, or if the
  cardbus bridge is failing.  Have you connected a fw device to the
  firewire card?
 
 I've been able to run a few more tests, even though I've not done abused
 it in every way I have in my mind yet...
 
 The evidence I currently have is:
  - if I load the modules at loader time everything is fine, with or without
 a device attached
  - if I load the modules later on, the kldload doesn't return and the system
 stops responding; I can still enter DDB. The only way to recover from that is
 to eject the card; at that point, the system is usable BUT as soon as there
 is network activity, the system freezes hard (can't get to DDB).
 
 IMHO this is 100% an interrupt problem. Does this ring a bell with one of you,
 or should I provide more info?

I have another strange firewire and cardbus/pccard interaction.
If I load firewire module while I'm using wi0 in cardbus slot,
the wi0 stop its work and output following messages.
(In my laptop, fwohci is on PCI.)

wi0: xmit failed
wi0: timeout in wi_cmd 0x010b; event status 0x
...


Even if I replace fwochi_pci_attach() with one line 'return EIO'
(i.e. the doesn't anything), the problem still happens.

I think this is not a problem of fwohci.
Maybe PCI or Cardbus/PCcard or kldload problem?



/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: -current, IBM A30p 2 external FW-disks

2003-01-29 Thread Hidetoshi Shimokawa
Do you get timeout only for sbp0:0:0?
Is the other drive still working?

I have no problem with concurrent accesses with `iozone -s 102400m -r
1024k`.

  tty ad0  da0  da1
 tin tout  KB/t tps  MB/s   KB/t tps  MB/s   KB/t tps  MB/s
  21  360  0.00   0  0.00  63.76 199 12.39  64.00 249 15.54
   3 1431  1.00   1  0.00  64.00 213 13.34  64.00 228 14.27
   0  153  0.00   0  0.00  64.00 214 13.38  64.00 199 12.45
   0  154  0.00   0  0.00  64.00 234 14.61  63.76 200 12.44
   0  154  0.00   0  0.00  63.74 188 11.68  64.00 241 15.09
   6  154  0.00   0  0.00  64.00 214 13.36  64.00 213 13.30


try some of the following:

- fwcontorl -g 20
- sysctl hw.firewire.sbp.max_speed=0
- change SBP_QUEUE_LEN in sbp.c to 1 and rebuld module.
- sysctl machdep.cpu_idle_hlt=0
- sysctl debug.sbp_debug=1 and send me a dmesg.


At Tue, 28 Jan 2003 20:42:41 +0100 (CET),
Michael Reifenberger wrote:
 fwohci0: vendor=1180, dev=522
 fwohci0: 1394 Open Host Controller Interface mem 0xc0201000-0xc02017ff irq 11 at 
device 0.2 on pci2

It's new to me. dev=522 is not listed in /usr/share/misc/pci_vendors...

 system power profile changed to 'economy'

Can you chane it to 'performance' mode?

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: firewire hangs on Thinkpad

2003-01-25 Thread Hidetoshi Shimokawa
hmm, I have no problem with my FireWire CardBus card.
If you can get traceback in DDB, please send it to me.

cardbus0: Resource not specified in CIS: id=10, size=800
cardbus0: Resource not specified in CIS: id=14, size=4000
fwohci1: Texas Instruments TSB43AA22 mem 0x88004000-0x88007fff,0x88008000-0x880087ff 
irq 9 at device 0.0 on cardbus0
fwohci1: PCI bus latency was changing to 250.
fwohci1: OHCI version 1.0 (ROM=1)
fwohci1: No. of Isochronous channel is 4.
fwohci1: EUI64 00:c0:d0:00:00:f8:56:6a
fwohci1: Phy 1394a available S400, 2 ports.
fwohci1: Link S400, max_rec 2048 bytes.
firewire1: IEEE1394(FireWire) bus on fwohci1
if_fwe1: Ethernet over FireWire on firewire1
if_fwe1: Fake Ethernet address: 02:c0:d0:f8:56:6a
fwohci1: BUS reset
fwohci1: node_id = 0x8800ffc0, non CYCLEMASTER mode
firewire1: 3 nodes, maxhop = 2, cable IRM = 2
firewire1: new bus manager 2 
firewire1: New S400 device ID:00d03200a412006a
firewire1: New S400 device ID:00a0b00a00060633
firewire1: Device SBP-II

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

At Fri, 24 Jan 2003 15:48:23 +0100,
Andrea Campi wrote:
 
 Hi all,
 
 I'm having a bad time trying to get a firewire cardbus adapter to work.
 First of all, let me say that I'm under no pressure - I just bought
it to
 test our firewire implementation  but I have no pressing need for it.
 
 Anyway, new kernel from last night, when I insert the card I get the following:
 
 cardbus0: Expecting link target, got 0x42
 cardbus0: Resource not specified in CIS: id=10, size=800
 cardbus0: Resource not specified in CIS: id=14, size=4000
 cardbus0: Resource not specified in CIS: id=18, size=800
 fwohci0: Texas Instruments TSB43AB22/A mem 0x880 
08000-0x880087ff,0x88004000-0x88007fff,0x88008800-0x88008fff irq 11 at device 0.0 on 
cardbus0
 fwohci0: PCI bus latency was changing to 250.
 fwohci0: OHCI version 1.10 (ROM=1)
 fwohci0: No. of Isochronous channel is 4.
 fwohci0: EUI64 00:01:fb:00:00:00:00:6e
 fwohci0: Phy 1394a available S400, 2 ports.
 fwohci0: Link S400, max_rec 2048 bytes.
 firewire0: IEEE1394(FireWire) bus on fwohci0
 fwohci0: BUS reset
 fwohci0: BUS reset
 fwohci0: node_id = 0xc000ffc0, CYCLEMASTER mode
 firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me)
 
 
 Sometimes it hangs the machine solid to the point I can't enter DDB, other
 times it takes a few seconds during which the machine is responsive, other
 times DDB is usable. I wasn't able to determine any rule to explain the
 different behaviors, but if anybody has any idea, I can try go get to DDB
 again and get any required info.
 
 Bye,
   Andrea
 
 -- 
 Where do you think you're going today?
 
 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



Re: firewire disk dowsn't work

2002-11-10 Thread Hidetoshi Shimokawa
At Sat, 9 Nov 2002 22:20:16 +0100 (CET),
Michael Reifenberger wrote:
 
 Hi,
 attached is the /var/log/messages excerpt after booting
 with a 120G Maxtor disk in a IceCube USB 2.0/Firewire Combo case.
 The messages at the end are from an attempt to fdisk da0.
 Booting with a USB cable works (as USB 1.0).
 Firewire doesn't.
 Any clues?
 
 Thanks in advance!

Could you power up the HDD first and connect it to the machine after a
while?

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Can't resolve hosts via dns on the command line with latest -current

2002-11-04 Thread Hidetoshi Shimokawa
At Tue, 5 Nov 2002 03:12:05 +0200,
Giorgos Keramidas wrote:
 The curious thing is that Sendmail or ssh fail to look up hostnames,
 while running host(1) works.  I don't know if this is of any help, but
 if you need more data about the local setup let me know.

host(or dig, nslookup) doesn't use resolver in libc.
The change affects processes which uses kevent().

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Can't resolve hosts via dns on the command line with latest -current

2002-11-03 Thread Hidetoshi Shimokawa
I have the same problem and reverting rev. 1.134 of
/sys/kern/uipc_socket.c fixes the problem.
The change might have something wrong with a loopback interface.

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html

Index: uipc_socket.c
===
RCS file: /home/ncvs/src/sys/kern/uipc_socket.c,v
retrieving revision 1.135
diff -u -r1.135 uipc_socket.c
--- uipc_socket.c   2 Nov 2002 05:14:30 -   1.135
+++ uipc_socket.c   3 Nov 2002 14:45:16 -
@@ -1784,7 +1784,11 @@
 {
struct socket *so = (struct socket *)kn-kn_fp-f_data;
 
+#if 0
kn-kn_data = so-so_rcv.sb_cc - so-so_rcv.sb_ctl;
+#else
+   kn-kn_data = so-so_rcv.sb_cc;
+#endif
if (so-so_state  SS_CANTRCVMORE) {
kn-kn_flags |= EV_EOF;
kn-kn_fflags = so-so_error;


At Sun, 03 Nov 2002 05:39:48 -0800,
Doug Barton wrote:
 
 Howdy,
 
 With -current built from sources updated at around 8pm PST, I can't
 resolve hosts on the command line if /etc/resolv.conf points to a name
 server running on the local host. The local name server itself is
 working fine, and I can reach any host in /etc/hosts as well.
 
 ktrace /sbin/ping hub.freebsd.org
 ^C
 
 kdump
651 ktrace   RET   ktrace 0
651 ktrace   CALL  execve(0xbfbffb03,0xbfbff9e4,0xbfbff9f0)
651 ktrace   NAMI  /sbin/ping
 
 /etc/nsswitch.conf is unchanged, and contains only:
 hosts: files dns 
 
 It doesn't matter if /etc/resolv.conf points to 127.0.0.1, or the IP of
 the box. As soon as I point /etc/resolv.conf at a name server on another
 host, it works.
 
 My -current system from last weekend worked just fine. 
 
 Doug
 
 -- 
We have known freedom's price. We have shown freedom's power.
   And in this great conflict, ...  we will see freedom's victory.
   - George W. Bush, President of the United States
   State of the Union, January 28, 2002
 
  Do YOU Yahoo!?
 
 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



Re: HEADS UP: module build process changed

2002-02-19 Thread Hidetoshi Shimokawa

At Thu, 10 Jan 2002 17:35:00 -0800,
Mike Smith wrote:
 In order to deal with this problem, I have changed the module build
 process so that symbols global to the module are converted to local
 symbols when the module is linked into the .kld/,ko file.  In order
 to allow modules that intentionally export symbols to continue to do
 so, a new module makefile variable 'EXPORT_SYMS' has been implemented.

Hi Mike,

I don' think EXPORT_SYMS works right.

EXPORT_SYMS= fw_asybusy \
fw_asyreq   \
fw_bindadd  \
getcsrdata  \
fw_xfer_alloc   \
fw_xfer_free\


By this configuration, /sys/conf/kmod.mk generates space separated
list to export_syms like this:

fw_asybusy fw_asyreq fw_bindadd getcsrdata fw_xfer_alloc fw_xfer_free

But /sys/conf/kmod_syms.awk expects 'line break' separated list.
And we cannot export any symbols.

For example, 
Remove ppbus/plip/lpt/ppi/ppc from you kernel config.
Can you load ppbus and it's childen by kldload?

Even if this problem is fixed, I suppose another problem there.
Even if I set EXPORT_SYMS=YES, I cannot resolv module symbols.
e.g.

kldload module1
kldload module2

module2 cannnot resolv symbols in module1.

-stable doesn't have this problem.

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: HEADS UP: module build process changed

2002-02-19 Thread Hidetoshi Shimokawa

At Tue, 19 Feb 2002 21:41:11 -0800,
Peter Wemm wrote:
  e.g.
  
  kldload module1
  kldload module2
  
  module2 cannnot resolv symbols in module1.
  
  -stable doesn't have this problem.
 
 module2 cannot resolve symbols in module1 unless there is a declared
 dependency.  This is intentional, otherwise there is no way to check that
 module1 is not unloaded while module2 is using it.  Stable is lacking this
 enforcement.

Thanks for the information.
Could you point me an example code how to declare dependency?

In my environment module1 is firewire bus drivier, module2 is sbp
driver.

module1:
DRIVER_MODULE(firewire,fwohci,firewire_driver,firewire_devclass,0,0);
module2:
DRIVER_MODULE(sbp, firewire, sbp_driver, sbp_devclass, 0, 0);

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: http://www.sat.t.u-tokyo.ac.jp/~simokawa/pgp.html


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Is current.freebsd.org running Linux?

2000-04-05 Thread Hidetoshi Shimokawa

From: Visigoth [EMAIL PROTECTED]
Subject: Re: Is current.freebsd.org running Linux?
Date: Wed, 5 Apr 2000 09:32:21 -0500 (CDT)
Message-ID: [EMAIL PROTECTED]

visigoth 
visigoth  current.jp.freebsd.org is another stable/current build machine.
visigoth 
visigoth  /\ Hidetoshi Shimokawa
visigoth 
visigoth Thanks Hidetoshi, but I think my meager 3 years of nihongo in highschool
visigoth are not going to be enough to run a Japanese snapshot just yet...

There is not so much differece from snapshot built on current.freebsd.org
except that crypto library source comes from cvsup.internat.freebsd.org.
See http://current.jp.freebsd.org for detail.

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: finger -l [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Is current.freebsd.org running Linux?

2000-04-04 Thread Hidetoshi Shimokawa


current.jp.freebsd.org is another stable/current build machine.

/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: finger -l [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: cd writer recommendation?

1999-08-18 Thread Hidetoshi Shimokawa

At Tue, 17 Aug 1999 17:47:42 -0700 (PDT),
Matthew Dillon [EMAIL PROTECTED] wrote:
 
 One thing www.buy.com is really good for, even if you don't buy from them,
 is to get pricing information on a general search.  You can then use it
 to do comparison shopping.
 
   http://www.buy.com/
   click on "comp"
   Search for "rewritable"
 
 And there you have it.  The smart-and-friendly lists for $460 (yowzer!).
 The older Yahama models (SCSI) list for $325.   The lowest cost one
 appears to be the HP or Yamaha IDE versions for $200, too bad FreeBSD
 can't use it under IDE (but personally I think SCSI is the only way to
 go).  Hmm.  Plexor lists a SCSI one for $268 but I dunno if it works.
 Hi-Val lists a SCSI one ofr $282.  Again, dunno if it works.
 
 
   -Matt

For backup, I bought DVD-RAM drive for $400.
5.2GB(double side) media is around $35, you can use them as 2.3GB x 2
disks.

Enabling raw-write in scsi_cd.c, you can newfs/mount DVD-RAM as UFS.
Write speed is around 500KB/s, and read speed is around 1.4MB/s.

-- 
/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: finger -l [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: cd writer recommendation?

1999-08-18 Thread Hidetoshi Shimokawa

At Wed, 18 Aug 1999 08:40:59 -0700 (PDT),
Matthew Dillon [EMAIL PROTECTED] wrote:
 
 :For backup, I bought DVD-RAM drive for $400.
 :5.2GB(double side) media is around $35, you can use them as 2.3GB x 2
 :disks.
 :
 :Enabling raw-write in scsi_cd.c, you can newfs/mount DVD-RAM as UFS.
 :Write speed is around 500KB/s, and read speed is around 1.4MB/s.
 :
 :-- 
 :/\ Hidetoshi Shimokawa
 
 Isn't that the drive with the enclosed DVD disk -- kinda like a permanent
 caddy?  I've avoided the DVD-RAM drives because of that and because the 

Type I(double side) is with a permanent caddy, but TypeII(single side)
can be pulled out from the enclosure and supposed to be read by
DVD-ROM drives.

 standard is still going through major changes.  I expect those drives 
 to become obsolete very quickly once the technology settles down.  But in
 a year or two when the DVD-writers come down in price I'll probably 
 start using them.

Right. Another standard is already proposed, but as for backup device,
it's not so much problem.

   -Matt
   Matthew Dillon 
   [EMAIL PROTECTED]

-- 
/\ Hidetoshi Shimokawa
\/  [EMAIL PROTECTED]
PGP public key: finger -l [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message