Re: 6.2 RELEASE - READ_DMA timed out
The reason it works in safe mode is that DMA is not used there. Are you sure it worked with DMA before ? I cant be sure, I never looked it up. But it worked just fine before. The _only_ difference is the soruce-code i compiled NanoBSD from. I was RELENG_6_1 before and now it is RELENG_6_2 I'm using a IDE to CF-card adapter in a ordinary PC if that could be any help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2 RELEASE - READ_DMA timed out
Peter Ankerstål wrote: Pietro Cerutti wrote: On 1/14/07, Peter Ankerstål <[EMAIL PROTECTED]> wrote: ad0: FAILURE - READ_DMA timed out LBA=1000941 This kind of errors usually denote a hardware problem, either at the disk or at the controller level. Check sysutils/smartmontools in the ports. But there was no problem at all before the upgrade, and it works without any problem in "safe mode" and I have done fscks on the CF-card without any errors. The reason it works in safe mode is that DMA is not used there. Are you sure it worked with DMA before ? DMA access on CF cards needs signal lines to the CF slot thats not always implemented, fx on older soekris boards. -Søren ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2 RELEASE - READ_DMA timed out
On Sunday, 14. January 2007 16:27, Pietro Cerutti wrote: > On 1/14/07, Peter Ankerstål <[EMAIL PROTECTED]> wrote: > > ad0: FAILURE - READ_DMA timed out LBA=1000941 > > This kind of errors usually denote a hardware problem, either at the > disk or at the controller level. > Check sysutils/smartmontools in the ports. This is not a hardware problem, this is Flash cards limitation- most of flash cards don't work with DMA at all. You should turn off DMA on every Flash card that is connected directly to IDE channel to boot up any operating system. I know there is some IDE2Flash adapters that can work with DMA but they are twice or even more expensive than el cheapo adapters most devices got. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2 RELEASE - READ_DMA timed out
On 1/14/07, Peter Ankerstål <[EMAIL PROTECTED]> wrote: ad0: FAILURE - READ_DMA timed out LBA=1000941 This kind of errors usually denote a hardware problem, either at the disk or at the controller level. Check sysutils/smartmontools in the ports. -- Pietro Cerutti ICQ: 117293691 PGP: 0x9571F78E - ASCII Ribbon Campaign - against HTML e-mail and proprietary attachments www.asciiribbon.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.2 RELEASE - READ_DMA timed out
Pietro Cerutti wrote: On 1/14/07, Peter Ankerstål <[EMAIL PROTECTED]> wrote: ad0: FAILURE - READ_DMA timed out LBA=1000941 This kind of errors usually denote a hardware problem, either at the disk or at the controller level. Check sysutils/smartmontools in the ports. But there was no problem at all before the upgrade, and it works without any problem in "safe mode" and I have done fscks on the CF-card without any errors. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.2 RELEASE - READ_DMA timed out
I have a router running NanoBSD on a CF-card, 512MB SanDisk and
yesterday when installed 6.2-RELEASE I encountered some problems.
The systems seems to boot properly but when it tries to mount the
filesystem I get errors like this:
ad0: FAILURE - READ_DMA timed out LBA=1000941
When I try to boot without acpi I get the same problem but when I boot
in "Safe Mode" it boots properly and I haven't encountered any problems
at all.
I have'nt compiled any modules, and the acpi.ko is missing, could that
be the problem? It worked fine i 6.1-RELEASE though.
What could be the problem? If there is no "quick" solution to this, are
there any way to make "Safe Mode" the default option at boot?
I've attached my kernconf and configuration for the NanoBSD-build.
#!/bin/sh
# Copyright (c) 2005 Poul-Henning Kamp.
#
# See /usr/share/examples/etc/bsd-style-copyright for license terms.
#
# $FreeBSD: src/tools/tools/nanobsd/nanobsd.sh,v 1.1 2005/07/26 18:52:50 phk
Exp $
#
# Name of this NanoBSD build. (Used to construct workdir names)
NANO_NAME=uchman
NANO_SRC=/usr/src
NANO_PMAKE="make -j 4"
# Options to put in make.conf during buildworld only
CONF_BUILD='
NO_HESIOD_LIBC=YES
NO_KLDLOAD=YES
NO_NETGRAPH=YES
NO_PAM=YES
PPP_NO_NETGRAPH=YES
PPP_NO_RADIOS=YES
'
# Options to put in make.conf during installworld only
CONF_INSTALL='
NO_ACPI=YES
NO_BLUETOOTH=YES
NO_CVS=YES
NO_CXX=YES
NO_DICT=YES
NO_FORTRAN=YES
NO_GCOV=YES
NO_GDB=YES
NO_HTML=YES
NO_LPR=YES
NO_MAN=YES
NO_OBJC=YES
NO_P1003_1B=YES
NO_PROFILE=YES
NO_SENDMAIL=YES
NO_SHAREDOCS=YES
NO_TOOLCHAIN=YES
NO_EXAMPLES=YES
NO_INSTALLLIB=YES
NO_CALENDAR=YES
NO_MISC=YES
#NO_SHARE=YES
NO_MAKE=YES
'
# Options to put in make.conf during both build- & installworld.
CONF_WORLD='
NO_ATM=YES
NO_I4B=YES
NO_BIND=YES
NO_MODULES=YES
NO_IPFILTER=YES
NO_KERBEROS=YES
NO_NIS=YES
NO_RCMDS=YES
NO_GAMES=YES
NO_RESCUE=YES
PPP_NO_NETGRAPH=YES
PPP_NO_RADIUS=YES
NO_LOCALES=YES
NO_SYSCONS=YES
NO_GROFF=YES
NO_NLS=YES
NO_PCVT=YES
NO_IPX=YES
NO_INFO=YES
'
NANO_KERNEL=GW
FlashDevice Sandisk 512MB
NANO_IMAGES=2
NANO_CODESIZE=0
NANO_CONFSIZE=20480
NANO_DATASIZE=0
#customize_cmd cust_comconsole
customize_cmd cust_allow_ssh_root
customize_cmd cust_install_files
customize_cmd phk_pkg
phk_pkg () (
mkdir -p ${NANO_WORLDDIR}/Pkg
cp /usr/src/tools/tools/nanobsd/Pkg/* ${NANO_WORLDDIR}/Pkg
chroot ${NANO_WORLDDIR} sh -c 'pkg_add -v Pkg/*'
rm -rf ${NANO_WORLDDIR}/Pkg
)
machine i386
cpu I686_CPU
ident GW
# To statically compile in device wiring instead of /boot/device.hints
#hints "GENERIC.hints" # Default places to look for devices.
makeoptions DEBUG=-g# Build kernel with gdb(1) debug symbols
device pf
device pflog
device pfsync
device fdescfs
options ALTQ
options ALTQ_CBQ# Class Bases Queuing (CBQ)
options ALTQ_RED# Random Early Detection (RED)
options ALTQ_RIO# RED In/Out
options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC)
options ALTQ_PRIQ # Priority Queuing (PRIQ)
options ALTQ_NOPCC # Required for SMP build
#optionsSCHED_ULE # ULE scheduler
options SCHED_4BSD # 4BSD scheduler
options PREEMPTION # Enable kernel thread preemption
options INET# InterNETworking
options INET6 # IPv6 communications protocols
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options MD_ROOT # MD is a potential root device
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server
options NFS_ROOT# NFS usable as /, requires NFSCLIENT
options MSDOSFS # MSDOS Filesystem
options CD9660 # ISO 9660 Filesystem
options PROCFS # Process filesystem (requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_GPT# GUID Partition Tables.
options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!]
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options COMPAT_FREEBSD5 # Compatible with FreeBSD5
options KTRACE # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time
extensions
options KBD_INSTALL_CDEV
