Re: ATAng panic?
I have been getting a similar panic for several weeks now. I cvsup-ed and built a new kernel yesterday (9/29) and it still doesn't see it. This is with a SIS 630 chipset UDMA controller. --- Tilman Linneweh [EMAIL PROTECTED] wrote: Hi, Updated my -CURRENT yesterday and got the following panic: [...] atapci0: AcerLabs Aladdin UDMA33 controller port 0xb800-0xb80f at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] 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 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold ppbus0: Parallel port bus on ppc0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A, console 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 orm0: Option ROM at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x100 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 400910809 Hz quality 800 Timecounters tick every 10.000 msec IPsec: Initialized Security Association Processing. GEOM: create disk ad0 dp=0xc18eec70 ad0: 8063MB IBM-DHEA-38451 [16383/16/63] at ata0-master UDMA33 ad0: WARNING - READ_DMA recovered from missing interrupt GEOM: create disk ad1 dp=0xc18eee70 ad1: 19541MB Maxtor 92041U4 [39703/16/63] at ata0-slave UDMA33 acd0: CDROM CD-ROM 56X/AKH at ata1-slave PIO4 Waiting 15 seconds for SCSI devices to settle ad0: WARNING - READ_DMA recovered from missing interrupt ad1: WARNING - READ_DMA recovered from missing interrupt ad1: WARNING - READ_DMA recovered from missing interrupt cd0 at sym0 bus 0 target 4 lun 0 cd0: PLEXTOR CD-R PX-R820T 1.06 Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed ad1: WARNING - READ_DMA recovered from missing interrupt Mounting root from ufs:/dev/ad0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input mountroot ? panic: Root mount failed, startup aborted. Debugger(panic) Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 db where Debugger(c041b1ac,c04a4560,c042237c,c8921c8c,100) at Debugger+0x54 panic(c042237c,c0235770,c0b80d3c,c8921d0c,c02357db) at panic+0xd5 vfs_mountroot(c04a28a0,1,c0417f4b,218,0) at vfs_mountroot+0xce start_init(0,c8921d48,c0418c4e,314,0) at start_init+0x6b fork_exit(c0235770,0,c8921d48) at fork_exit+0xcf fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xc8921d7c, ebp = 0 --- A working version looks like this: FreeBSD 5.1-CURRENT #1: Sat Aug 16 10:11:52 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/source/CURRENT/sys/POLLY Preloaded elf kernel /boot/kernel.safe/kernel at 0xc0583000. Preloaded elf module /boot/kernel.safe/acpi.ko at 0xc05831fc. Timecounter i8254 frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x58c Stepping = 12 Features=0x8021bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE,MMX AMD Features=0x8800SYSCALL,3DNow! real memory = 134201344 (127 MB) avail memory = 124452864 (118 MB) K6-family MTRR support enabled (2 registers) npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P5A on motherboard pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00f0d00 acpi0: power button is handled as a fixed feature programming model. acpi_cpu0: CPU port 0x530-0x537 on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib0: slot 9 INTA is routed to irq 9 pcib0: slot 11 INTA is routed to irq 10 pcib0: slot 12 INTA is routed to irq 11 pcib0: slot 13 INTA is routed to irq 9 agp0: Ali M1541 host to AGP bridge mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci0: bridge, PCI-unknown at device 3.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 xl0: 3Com 3c905B-TX Fast Etherlink XL port 0xd800-0xd87f mem 0xdf00-0xdf7f irq 9 at device 9.0 on pci0 xl0: Ethernet
Re: ATAng panic: ATAFD re-using freed memory
On Mon, 8 Sep 2003, Soren Schmidt wrote: It seems Nate Lawson wrote: With a fresh checkout of last night's -current, I cannot boot my laptop. ATAFD panics the box by reusing freed memory. I do not have a floppy drive in the laptop and when I do, it's a legacy floppy, not atapi. Here are the messages: [normal ad0/acd0 probe message] afd0: timeout waiting for ATAPI ready afd0: timeout waiting for ATAPI ready afd0: timeout waiting for ATAPI ready afd0: timeout waiting for ATAPI ready afd0: timeout waiting for ATAPI ready panic: Memory modified after free: 0xc33ed400 (252) Most recently used by AFD driver A working dmesg: http://www.root.org/~nate/acpi/ibm.dmesg From the above I can tell whats going on, please upgrade to the latest -current as I've fixed a couble of things in the probe code there. If it still panic's please include a verbose boot from a atapicam-less kernel... This has been fixed. However, ATAng is still not usable for the reasons in my next email message: Message-ID: [EMAIL PROTECTED] -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng panic: ATAFD re-using freed memory
It seems Nate Lawson wrote: With a fresh checkout of last night's -current, I cannot boot my laptop. ATAFD panics the box by reusing freed memory. I do not have a floppy drive in the laptop and when I do, it's a legacy floppy, not atapi. Here are the messages: [normal ad0/acd0 probe message] afd0: timeout waiting for ATAPI ready afd0: timeout waiting for ATAPI ready afd0: timeout waiting for ATAPI ready afd0: timeout waiting for ATAPI ready afd0: timeout waiting for ATAPI ready panic: Memory modified after free: 0xc33ed400 (252) Most recently used by AFD driver A working dmesg: http://www.root.org/~nate/acpi/ibm.dmesg From the above I can tell whats going on, please upgrade to the latest -current as I've fixed a couble of things in the probe code there. If it still panic's please include a verbose boot from a atapicam-less kernel... -Søren ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATAng panic with large file transfer to HighPoint RAID
To further test if this issue was really caused by ATAng, I have cvsupped
src/sys/dev/ata,
src/sys/conf/files, src/sys/sys/ata.h back to the time just before ATAng committed.
I then
built/installed kernel and found that with this non-ATAng kernel, the pax command
can run
successfully on a directory of around 2.2GB.
Hope that this additional data would help...
Thanks.
--- Shizuka Kudo [EMAIL PROTECTED] wrote:
I think I have reported this two days ago, but look like it wasn't gone through.
Here's my
problem
that I still suffer with build world/kernel about three hours ago (i.e. Aug 28 12:00
UTC)
With the new world/kernel, I tried to pax a subdirectory to the RAID1 drive (two
IBM
DLTA-307030
attached to the two UDMA-100 interface of a HighPoint 370 controller) with the
following command
and immediately with a DMA transfer error followed by a kernel panic.
shizuka# pax -pe -r -w public /raid/
ad6: FAILURE - oversized DMA transfer attempted 131072 65536
ad6: Setting up DMA failed
ar0: WARNING - mirror lost
ad4: FAILURE - oversized DMA transfer attempted 131072 65536
ad4: Setting up DMA failed
ar0: ERROR - array broken
panic: initiate_write_inodeblock_ufs2: already started
Here's the backtrace from gdb
panic: initiate_write_inodeblock_ufs2: already started
panic: from debugger
Uptime: 2m45s
Dumping 511 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352
368 384 400
416
432 448 464 480 496
---
Reading symbols from
/usr/obj/usr/src/sys/SHIZUKA/modules/usr/src/sys/modules/acpi/acpi.ko.debug...done.
Loaded symbols for
/usr/obj/usr/src/sys/SHIZUKA/modules/usr/src/sys/modules/acpi/acpi.ko.debug
Reading symbols from /boot/kernel/logo_saver.ko...done.
Loaded symbols for /boot/kernel/logo_saver.ko
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) where
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc0254380 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc0254768 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
#3 0xc014ba82 in db_panic () at /usr/src/sys/ddb/db_command.c:450
#4 0xc014b9e2 in db_command (last_cmdp=0xc046c120, cmd_table=0x0,
aux_cmd_tablep=0xc0422284, aux_cmd_tablep_end=0xc0422288)
at /usr/src/sys/ddb/db_command.c:346
#5 0xc014bb25 in db_command_loop () at /usr/src/sys/ddb/db_command.c:472
#6 0xc014eb45 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_trap.c:73
#7 0xc03b5d4c in kdb_trap (type=3, code=0, regs=0xdc39ea3c)
at /usr/src/sys/i386/i386/db_interface.c:171
#8 0xc03c75aa in trap (frame=
{tf_fs = -831782888, tf_es = 16, tf_ds = 16, tf_edi = 1, tf_esi = -1069454141,
tf_ebp =
-600184184, tf_isp = -600184216, tf_ebx = 0, tf_edx = 0, tf_ecx = -1068875680,
tf_eax = 18,
tf_trapno = 3, tf_err = 0, tf_eip = -1069850620, tf_cs = 8, tf_eflags = 642, tf_esp =
-1069434333,
tf_ss = -1069505986})
at /usr/src/sys/i386/i386/trap.c:577
#9 0xc03b76f8 in calltrap () at {standard input}:102
#10 0xc02546a5 in panic (
fmt=0xc0416cc3 initiate_write_inodeblock_ufs2: already started)
at /usr/src/sys/kern/kern_shutdown.c:534
#11 0xc035e2e6 in initiate_write_inodeblock_ufs2 (inodedep=0xc42b6800, bp=0x0)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:3893
---Type return to continue, or q return to quit---
#12 0xc035d46d in softdep_disk_io_initiation (bp=0xce641830)
at /usr/src/sys/ufs/ffs/ffs_softdep.c:3459
#13 0xc0214954 in spec_xstrategy (vp=0xc41dfdb0, bp=0xce641830)
at /usr/src/sys/sys/buf.h:413
#14 0xc0214aab in spec_specstrategy (ap=0x0)
at /usr/src/sys/fs/specfs/spec_vnops.c:529
#15 0xc0213c18 in spec_vnoperate (ap=0x0)
at /usr/src/sys/fs/specfs/spec_vnops.c:122
#16 0xc029da9b in bwrite (bp=0xce641830) at vnode_if.h:1141
#17 0xc029ffd9 in vfs_bio_awrite (bp=0xce641830)
at /usr/src/sys/kern/vfs_bio.c:1709
#18 0xc02a0e16 in flushbufqueues (flushdeps=0)
at /usr/src/sys/kern/vfs_bio.c:2171
#19 0xc02a097c in buf_daemon () at /usr/src/sys/kern/vfs_bio.c:2072
#20 0xc023d091 in fork_exit (callout=0xc02a0840 buf_daemon, arg=0x0,
frame=0x0) at /usr/src/sys/kern/kern_fork.c:796
Is anyone found the same error
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
__
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
