Re: ATA seems to lock up the system at boot (KT133A)

2003-01-13 Thread Alexander Leidinger
On Sun, 12 Jan 2003 20:35:41 +0100 (CET)
Soeren Schmidt [EMAIL PROTECTED] wrote:

   Could your Zip disk be missing or bad?
  
  Usually I don't have a zip disk in the drive at boot time... I give it a
  try (tomorrow).
 
 I've tried both here, works just fine on a newly compiled current

It seems I have no luck... not even that you can't reproduce the tagged
queueing problem, you also can't reproduce this problem. Whats wrong
with my system? :-(

I've tried with a disk in the drive, same behavior. I'm going to update
to todays sources, and start from a clean kernel compile directory...
let's see how far I get then.

Bye,
Alexander.

-- 
The dark ages were caused by the Y1K problem.

http://www.Leidinger.net   Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7

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



Re: ATA seems to lock up the system at boot (KT133A)

2003-01-13 Thread Soeren Schmidt
It seems Alexander Leidinger wrote:
 On Sun, 12 Jan 2003 20:35:41 +0100 (CET)
 Soeren Schmidt [EMAIL PROTECTED] wrote:
 
Could your Zip disk be missing or bad?
   
   Usually I don't have a zip disk in the drive at boot time... I give it a
   try (tomorrow).
  
  I've tried both here, works just fine on a newly compiled current
 
 It seems I have no luck... not even that you can't reproduce the tagged
 queueing problem, you also can't reproduce this problem. Whats wrong
 with my system? :-(

Dunno, but it is the 13'th today :)

 I've tried with a disk in the drive, same behavior. I'm going to update
 to todays sources, and start from a clean kernel compile directory...
 let's see how far I get then.

Form a system compile from source 0800 today:

ad0: 13042MB IBM-DPTA-371360 [26500/16/63] at ata0-master UDMA33
afd0: 96MB IOMEGA ZIP 100 ATAPI [32/64/96] at ata0-slave PIO0
acd0: CD-RW Hewlett-Packard DVD Writer 100 at ata1-slave PIO4
pst0: 17385MB PROMISE TECH. I2O RAID DEVICE [2216/255/63] on pstpci0
Mounting root from ufs:/dev/ad0a

Thats without media in the ZIP drive, boots just fine, system in VIA 694
based so that should give me enough trouble :)

-Søren

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



Re: ATA seems to lock up the system at boot (KT133A)

2003-01-13 Thread Alexander Leidinger
On Mon, 13 Jan 2003 11:51:20 +0100 (CET)
Soeren Schmidt [EMAIL PROTECTED] wrote:

  It seems I have no luck... not even that you can't reproduce the tagged
  queueing problem, you also can't reproduce this problem. Whats wrong
  with my system? :-(
 
 Dunno, but it is the 13'th today :)

I don't have a problem with this date:
 calendar -f /usr/share/calendar/calendar.freebsd -t 13.03

My hope is a stale dependency for sys... I'm going to cvsup now.

Bye,
Alexander.

-- 
The dark ages were caused by the Y1K problem.

http://www.Leidinger.net   Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7

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



Re: ATA seems to lock up the system at boot (KT133A)

2003-01-13 Thread Alexander Leidinger
On Mon, 13 Jan 2003 11:51:20 +0100 (CET)
Soeren Schmidt [EMAIL PROTECTED] wrote:

 Thats without media in the ZIP drive, boots just fine, system in VIA 694
 based so that should give me enough trouble :)

I tried with recent sources and a clean (make clean; make clean; make
cleandir; make cleandir; make depend  make -j 4  make install)
kernel compile directory. No luck. :-(

After disabling the second channel - where the zip drive is attached to
- in the BIOS, the system doesn't hang at boot.

Anything I can do to find the cause?

Bye,
Alexander.

-- 
Yes, I've heard of decaf. What's your point?

http://www.Leidinger.net   Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7

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



Re: ATA seems to lock up the system at boot (KT133A)

2003-01-13 Thread marius
On Mon, Jan 13, 2003 at 11:47:14AM +0100, Alexander Leidinger wrote:
 On Sun, 12 Jan 2003 20:35:41 +0100 (CET)
 Soeren Schmidt [EMAIL PROTECTED] wrote:
 
Could your Zip disk be missing or bad?
   
   Usually I don't have a zip disk in the drive at boot time... I give it a
   try (tomorrow).
  
  I've tried both here, works just fine on a newly compiled current
 

I have a LS120 atapi-drive here that doesn't work under FreeBSD if it's
the master on it's channel but works fine if it's a slave to a = UDMA33
hd (the fact that it doesn't work when being slave to  UDMA33 may also
mean that that it doesn't work on 80-pin cables). Depending on the FreeBSD-
version it goes awry when getting probed or probes but doesn't work
afterwards. I noticed it first on 4-stable after a larger ata-code merge
(it worked happily before) a half year ago or so, I dropped Soeren a note
but no reaction. The difference between the configurations you and Soeren
posted is also that you are running the atapi ZIP-drive as master and
Soeren as slave, so maybe this could be a hint that something goes wrong
with initialisation when atapi floppy-drives are attached as masters.


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



Re: ATA seems to lock up the system at boot (KT133A)

2003-01-13 Thread Soeren Schmidt
It seems [EMAIL PROTECTED] wrote:
 posted is also that you are running the atapi ZIP-drive as master and
 Soeren as slave, so maybe this could be a hint that something goes wrong
 with initialisation when atapi floppy-drives are attached as masters.

That makes no difference I still cant get it to fail :(

acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0%
ad0: 13042MB IBM-DPTA-371360 [26500/16/63] at ata0-master UDMA66
afd0: 96MB IOMEGA ZIP 100 ATAPI [32/64/96] at ata1-master PIO0
Mounting root from ufs:/dev/ad0a

-Søren

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



Re: ATA seems to lock up the system at boot (KT133A)

2003-01-13 Thread Guezou Philippe
 Alexander Leidinger wrote:
  Hi,
  
  a dmesg from a working kernel (from Jan 5) shows:
  ---snip---
  acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0%
  ad0: 58644MB IC35L060AVER07-0 [119150/16/63] at ata0-master tagged UDMA100
  afd0: 96MB IOMEGA ZIP 100 ATAPI [32/64/96] at ata1-master PIO0
  Waiting 6 seconds for SCSI devices to settle
  ---snip---
  
  The not working kernel from yesterday locks up after printing the ad0
  line...
 
 Assuming this is the same as I see on my -STABLE box, this started months
 ago.  I have a SCSI Jaz drive (similar to a Zip) which started to hang
 the machine after the ad0 line when I remove the cartridge from the Jaz.

Same here.. with FreeBSD-CURRENT and FreeBSD-RELASE/STABLE.. and since a long time.
my test box is a Pentium III on a ASUS P2B-LS.. (Intel PIIX4 ATA33 controller)
the P2B-LS has an onboard adaptec aic7890 (i think.. will double check if s/o need 
that info)
If the SCSI device is enable on the MoBo (with or without SCSI device plugged), 
FreeBSD-* will 
systematically hang at boot (tried with FreeBSD-* install CDs, and with an already 
installed
FreeBSD) without panicing.. (FreeBSD-* mean 4.[4567] (maybe earlier, can't remember) 
and 
-STABLE/-CURRENT)

The only way i manage to install FreeBSD on that hardware is when i disable on the 
MoBo (via
a jumper) the AIC interface.. Without SCSI devices, the ASUS P2B-LS is ok..

here's the dmesg:
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #1: Fri Jan 10 11:56:35 EST 2003
[EMAIL PROTECTED]:/mnt/space/obj/mnt/space/src/sys/Tulkar
Preloaded elf kernel /boot/kernel/kernel at 0xc041d000.
Preloaded elf module /boot/kernel/acpi.ko at 0xc041d0a8.
Timecounter i8254  frequency 1193182 Hz
Timecounter TSC  frequency 451024514 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0x673  Stepping = 3
  
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real memory  = 268423168 (255 MB)
avail memory = 256282624 (244 MB)
Initializing GEOMetry subsystem
Pentium Pro MTRR support enabled
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: ASUS   P2B-LS   on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
Using $PIR table, 8 entries at 0xc00f0d10
acpi0: power button is handled as a fixed feature programming model.
Timecounter ACPI-safe  frequency 3579545 Hz
acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0
acpi_cpu0: CPU on acpi0
acpi_button0: Power Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xe400-0xe7ff at device 
0.0 on pci0
pcib1: PCIBIOS PCI-PCI bridge at device 1.0 on pci0
pci1: PCI bus on pcib1
pci1: display, VGA at device 0.0 (no driver attached)
isab0: PCI-ISA bridge at device 4.0 on pci0
isa0: ISA bus on isab0
atapci0: Intel PIIX4 ATA33 controller port 0xd800-0xd80f at device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: serial bus, USB at device 4.2 (no driver attached)
pci0: bridge, PCI-unknown at device 4.3 (no driver attached)
fxp0: Intel Pro 10/100B/100+ Ethernet port 0xd000-0xd01f mem 
0xd480-0xd48f,0xd700-0xd7000fff irq 1
0 at device 7.0 on pci0
fxp0: Ethernet address 00:e0:18:98:17:62
inphy0: i82555 10/100 media interface on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci0: multimedia, audio at device 12.0 (no driver attached)
fdc0: Enhanced floppy controller (i82077, NE72065 or clone) port 0x3f7,0x3f2-0x3f5 
irq 6 drq 2 on acpi0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5 drive on fdc0 drive 0
ppc0 port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x300
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounters tick every 10.000 msec
ad0: 19544MB Maxtor 92049U6 [39709/16/63] at ata0-master UDMA33
ad1: 8063MB WDC AC28400R [16383/16/63] at ata0-slave UDMA33
acd0: CDROM LG CD-ROM CRD-8522B at ata1-master PIO4
MBREXT Slice 5 on ad0s2:
   00 01 81 40 0b fe 3f 3f 3f 00 00 00 c1 85 78 01  |...@..???.x.|
[0] f:00 typ:11 s(CHS):64/1/129 e(CHS):63/254/63 s:63 l:24675777
   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ||
[1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
Mounting root from ufs:/dev/ad1s1a


 
 The hang 

ATA seems to lock up the system at boot (KT133A)

2003-01-12 Thread Alexander Leidinger
Hi,

a dmesg from a working kernel (from Jan 5) shows:
---snip---
acpi_cpu: CPU throttling enabled, 2 steps from 100% to 50.0%
ad0: 58644MB IC35L060AVER07-0 [119150/16/63] at ata0-master tagged UDMA100
afd0: 96MB IOMEGA ZIP 100 ATAPI [32/64/96] at ata1-master PIO0
Waiting 6 seconds for SCSI devices to settle
---snip---

The not working kernel from yesterday locks up after printing the ad0
line. A verbose boot shows additionally that ata1-master was set to
PIO0, but nothing more.

The earliest change in todays cvsup is
 Edit src/release/doc/de_DE.ISO8859-1/share/sgml/release.dsl,v
  Add delta 1.1.2.5 2003.01.11.18.23.18 ue
and I can't find a commit after this which seems to be related
to ata.

Bye,
Alexander.

-- 
 The computer revolution is over. The computers won.

http://www.Leidinger.net   Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7

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



Re: ATA seems to lock up the system at boot (KT133A)

2003-01-12 Thread Alexander Leidinger
On Sun, 12 Jan 2003 06:49:18 -0800
walt [EMAIL PROTECTED] wrote:

 Could your Zip disk be missing or bad?

Usually I don't have a zip disk in the drive at boot time... I give it a
try (tomorrow).

Bye,
Alexander.

-- 
 The computer revolution is over. The computers won.

http://www.Leidinger.net   Alexander @ Leidinger.net
  GPG fingerprint = C518 BC70 E67F 143F BE91  3365 79E2 9C60 B006 3FE7

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



Re: ATA seems to lock up the system at boot (KT133A)

2003-01-12 Thread Soeren Schmidt
It seems Alexander Leidinger wrote:
 On Sun, 12 Jan 2003 06:49:18 -0800
 walt [EMAIL PROTECTED] wrote:
 
  Could your Zip disk be missing or bad?
 
 Usually I don't have a zip disk in the drive at boot time... I give it a
 try (tomorrow).

I've tried both here, works just fine on a newly compiled current

-Søren

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