Re: ATA error on 6.0-BETA4

Thanks for your feedback Soren.

Enabling some debug features in kernel dont offer more information,
unfortunally. But, booting with 5.4 Kernel, this drive is working
correctly:

atapci0: <VIA 8235 UDMA133 controller> port
0xa800-0xa80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
ad0: 38172MB <MAXTOR 6L040J2/A93.0500> [77557/16/63] at ata0-master
UDMA133
acd0: CDRW <CREATIVE CD-RW RW8438E/FC02> at ata1-slave PIO4

Here's the dmesg from 6.0-BETA4:

FreeBSD 6.0-BETA4 #0: Sun Sep 11 08:29:43 BRT 2005
    wgentine_at_powerplant:/usr/src/sys/i386/compile/POWERPLANT
WARNING: WITNESS option enabled, expect reduced performance.
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(TM) XP 2400+ (2000.08-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x681  Stepping = 1

Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
  AMD Features=0xc0400800<SYSCALL,MMX+,3DNow+,3DNow>
real memory  = 268419072 (255 MB)
ioapic0: Changing APIC ID to 2
ioapic0 <Version 0.3> irqs 0-23 on motherboard
npx0: [FAST]
acpi0: <ASUS A7V8X-X> on motherboard
acpi0: Power Button (fixed)
pci_link0: <ACPI PCI Link LNKA> irq 11 on acpi0
pci_link1: <ACPI PCI Link LNKB> irq 0 on acpi0
pci_link2: <ACPI PCI Link LNKC> irq 0 on acpi0
pci_link3: <ACPI PCI Link LNKD> irq 0 on acpi0
pci_link4: <ACPI PCI Link LNKE> irq 3 on acpi0
pci_link5: <ACPI PCI Link LNKF> irq 15 on acpi0
pci_link6: <ACPI PCI Link LNKG> irq 9 on acpi0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <32-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
cpu0: <ACPI 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: <VIA 8377 (Apollo KT400/KT400A/KT600) host to PCI bridge> mem
0xf8000000-0xfbffffff at device 0.0 on pci0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pci1: <display, VGA> at device 0.0 (no driver attached)
fxp0: <Intel 82559 Pro/100 Ethernet> port 0xd800-0xd83f mem
0xf1800000-0xf1800fff,0xf1000000-0xf10fffff irq 16 at device 13.0 on
pci0
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> on miibus0
pci0: <multimedia, audio> at device 14.0 (no driver attached)
pci0: <input device> at device 14.1 (no driver attached)
uhci0: <VIA 83C572 USB controller> port 0xb800-0xb81f at device 16.0 on
pci0
uhci0: [GIANT-LOCKED]
usb0: <VIA 83C572 USB controller> on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <VIA 83C572 USB controller> port 0xb400-0xb41f at device 16.1 on
pci0
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhci2: [GIANT-LOCKED]
usb2: <VIA 83C572 USB controller> on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ehci0: <VIA VT6202 USB 2.0 controller> mem 0xf0800000-0xf08000ff at
device 16.3
on pci0
usb3: companion controllers, 2 ports each: usb0 usb1 usb2
usb3: <VIA VT6202 USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub3: 6 ports with 6 removable, self powered
isab0: <PCI-ISA bridge> at device 17.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 8235 UDMA133 controller> port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xa800-0xa80f at device 17.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
vr0: <VIA VT6102 Rhine II 10/100BaseTX> port 0xa400-0xa4ff mem
0xf0000000-0xf00000ff at device 18.0 on pci0
miibus1: <MII bus> on vr0
rlphy0: <RTL8201L 10/100 media interface> on miibus1
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr0: Ethernet address: 00:0c:6e:29:c4:62
fdc0: <floppy drive controller> port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on
acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on
acpi0
sio0: type 16550A
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xd0000-0xd5fff,0xd8000-0xd8fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on
isa0
ums0: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM), rev
1.10/3.00, addr 2, iclass 3/1
ums0: 3 buttons and Z dir.
Timecounter "TSC" frequency 2000084233 Hz quality 800
Timecounters tick every 1.000 msec
ad0: 38172MB <MAXTOR 6L040J2 A93.0500> at ata0-master UDMA133
unknown: timeout waiting for read DRQTrying to mount root from
ufs:/dev/ad0s1a

Thanks,

Wesley Gentine



On Wed, 2005-09-07 at 08:55 +0200, Søren Schmidt wrote:
> On 07/09/2005, at 1:04, Wesley Gentine wrote:
> 
> > Dear Colleagues,
> >
> >         After I updated my system from 5.4-RELEASE to 6-BETA2 my cdrom
> > device
> > isnt recognized and I received the following message in the end of
> > dmesg:
> >
> > Timecounter "TSC" frequency 2000081623 Hz quality 800
> > Timecounters tick every 1.000 msec
> > ad0: 38172MB <MAXTOR 6L040J2 A93.0500> at ata0-master UDMA133
> > unknown: timeout waiting for read DRQTrying to mount root from
> > ufs:/dev/ad0s1a
> >
> > my controller is:
> > atapci0: <VIA 8235 UDMA133 controller> port
> > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xa800-0xa80f at device 17.1 on  
> > pci0
> > ata0: <ATA channel 0> on atapci0
> > ata1: <ATA channel 1> on atapci0
> >
> > What´s happening?
> 
> You tell me with a dmesg from a verbose bootet system, and what CDROM  
> drive you have and where it is connected :)
> Then I'll look into it...
> 
> Søren Schmidt
> sos_at_FreeBSD.org
> 
> 
>