DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Installation and Upgrading

OpenBSD Installation and Upgrading Installing and upgrading OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 4th May 2008
s2scott's Avatar
s2scott s2scott is offline
Package Pilot
 
Join Date: May 2008
Location: Toronto, Ontario Canada
Posts: 198
Thanked 9 Times in 8 Posts
Default CF, as wd0, 4.3 dmesg "DMA error"

Upgraded to 4.3, from 4.2, and all is good; however, the 4.3 dmesg newly reports the following, with regard to the COMPACT FLASH card, wd0,
Code:
...
softraid0 at root
wd0(pciide0:0:0): timeout
        type: ata
        c_bcount: 512
        c_skip: 0
pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21
wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
wd0(pciide0:0:0): timeout
        type: ata
        c_bcount: 512
        c_skip: 0
pciide0:0:0: bus-master DMA error: missing interrupt, status=0x21
wd0: transfer error, downgrading to PIO mode 4
wd0(pciide0:0:0): using PIO mode 4
wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying
wd0: soft error (corrected)
root on wd0a swap on wd0b dump on wd0b
...
None of this dmesg lines were in the 4.2 dmesg.

System is booted and running fine. Anyone with thoughts or suggestions? I was thinking about perhaps the wd flags 1111 1111 1100, or the like.

Also, the softraid0 is especially new dmesg inclusion.

/S
__________________
Never argue with an idiot. They will bring you down to their level and beat you with experience.
Reply With Quote
  #2   (View Single Post)  
Old 4th May 2008
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

softraid0 is part of every 4.3 dmesg, it's simply a stating support is enabled in-kernel.

As for your CF problem, not a clue, a change 4.3 enabled DMA on 1-sector devices, but it shouldn't be enabled if you device doesn't support it.

In the boot UKC, change the flags for wd* devices to 0xcff, this will force a PIO 4 mode and leave DMA/UDMA disabled.

If that doesn't help, the problem lies elsewhere.. hope it helps.
Reply With Quote
  #3   (View Single Post)  
Old 4th May 2008
s2scott's Avatar
s2scott s2scott is offline
Package Pilot
 
Join Date: May 2008
Location: Toronto, Ontario Canada
Posts: 198
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by BSDfan666 View Post
... 4.3 enabled DMA on 1-sector devices, but it shouldn't be enabled if you device doesn't support it.
The machine's BIOS shows this CF as a 1-sector device .

Quote:
Originally Posted by BSDfan666 View Post
In the boot UKC, change the flags for wd* devices to 0xcff, this will force a PIO 4 mode and leave DMA/UDMA disabled.
That's my thinking too.

openBSD seems ok; it just momentarily stalls the boot while it times out, and then figures it out.

Moral of the story... use transcend brand cf ... true ide and udma rocks! (This particular cf is an off brand gifted to me.)

Thanks,
/S
__________________
Never argue with an idiot. They will bring you down to their level and beat you with experience.
Reply With Quote
  #4   (View Single Post)  
Old 5th May 2008
s2scott's Avatar
s2scott s2scott is offline
Package Pilot
 
Join Date: May 2008
Location: Toronto, Ontario Canada
Posts: 198
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by BSDfan666 View Post
In the boot UKC, change the flags for wd* devices to 0xcff, this will force a PIO 4 mode and leave DMA/UDMA disabled.
Should it not be 0xffc???

/S
__________________
Never argue with an idiot. They will bring you down to their level and beat you with experience.
Reply With Quote
  #5   (View Single Post)  
Old 5th May 2008
s2scott's Avatar
s2scott s2scott is offline
Package Pilot
 
Join Date: May 2008
Location: Toronto, Ontario Canada
Posts: 198
Thanked 9 Times in 8 Posts
Default

With the wd* flags set to 0xffc, the boot is stall-free and dmesg is clean
Code:
...
pciide0 at pci0 dev 31 function 1 "Intel 82801BA IDE" rev 0x02: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 0: <>
wd0: 1-sector PIO, LBA, 967MB, 1981728 sectors
wd0(pciide0:0:0): using PIO mode 4
atapiscsi0 at pciide0 channel 1 drive 0
...
softraid0 at root
root on wd0a swap on wd0b dump on wd0b
...
Thanks,
/S
__________________
Never argue with an idiot. They will bring you down to their level and beat you with experience.
Reply With Quote
  #6   (View Single Post)  
Old 5th May 2008
BSDfan666 BSDfan666 is offline
Real Name: N/A, this is the interweb.
Helpful companion
 
Join Date: Apr 2008
Location: Ontario, Canada
Posts: 2,223
Thanked 193 Times in 184 Posts
Default

Quote:
Originally Posted by s2scott View Post
Should it not be 0xffc???

/S
Correct, my sincere apologies.
Reply With Quote
  #7   (View Single Post)  
Old 5th May 2008
s2scott's Avatar
s2scott s2scott is offline
Package Pilot
 
Join Date: May 2008
Location: Toronto, Ontario Canada
Posts: 198
Thanked 9 Times in 8 Posts
Default

FYI ... the default flag is 0x0, and, when set as such, it fails softly and self-adjusts. You will boot successfully.

When the flags are manually set, if they're incorrect, then the boot just loops in the timeout-retry cycle. It's not a hard failure, but it won't self-adjust and won't boot. Manual intervention is required.

Adjust with care and do so with a back out at the ready.

Code:
# config -o /bsd.pio -e /bsd
OpenBSD 4.3 (GENERIC) #698: Wed Mar 12 11:07:05 MDT 2008
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
Enter 'help' for information
ukc> change wd*
 44 wd* at wdc0|wdc1|wdc*|wdc*|pciide*|pciide* channel -1 flags 0x0
change [n] y
channel [-1] ? 
flags [0] ? 0xffc
 44 wd* changed
 44 wd* at wdc0|wdc1|wdc*|wdc*|pciide*|pciide* channel -1 flags 0xffc
ukc>quit
I reboot, hit space to intercept the boot, then type
Code:
boot> boot /bsd.pio 
If /bsd.pio should happen to be bad, then a reset button gets me back to /bsd (original).

Once I know bsd.pio is good, then,
  1. mv bsd bsd.orig
  2. mv bsd.pio bsd
/S
__________________
Never argue with an idiot. They will bring you down to their level and beat you with experience.
Reply With Quote
  #8   (View Single Post)  
Old 5th May 2008
s2scott's Avatar
s2scott s2scott is offline
Package Pilot
 
Join Date: May 2008
Location: Toronto, Ontario Canada
Posts: 198
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by BSDfan666 View Post
Correct, my sincere apologies.
Not at all problem .
__________________
Never argue with an idiot. They will bring you down to their level and beat you with experience.
Reply With Quote
  #9   (View Single Post)  
Old 9th May 2008
Zmyrgel Zmyrgel is offline
Port Guard
 
Join Date: May 2008
Posts: 26
Thanked 0 Times in 0 Posts
Default

I will try this too. I tried to install OpenBSD 4.3 on my soekris CF and got similar errors when creating partitions.

Update: Didn't help in my case. I got 4-sector SanDisk CF. Dmesg that I get to climpse seems OK but when installer tries to create the partiotions it still gives me errors like "wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying"

Last edited by Zmyrgel; 9th May 2008 at 03:47 PM. Reason: Update
Reply With Quote
Old 9th May 2008
s2scott's Avatar
s2scott s2scott is offline
Package Pilot
 
Join Date: May 2008
Location: Toronto, Ontario Canada
Posts: 198
Thanked 9 Times in 8 Posts
Default

Quote:
Originally Posted by Zmyrgel View Post
I will try this too. I tried to install OpenBSD 4.3 on my soekris CF and got similar errors when creating partitions.

Update: Didn't help in my case. I got 4-sector SanDisk CF. Dmesg that I get to glimpse seems OK but when installer tries to create the partitions it still gives me errors like "wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying"
  1. In machine BIOS, if configurable, try turning IDE bus mastering to OFF;
  2. In machine BIOS, for the IDE drive that the CF enumerates to, try changing from type "AUTO" to a different but logical choice -- some BIOSs have a type "REMOVABLE IDE".
  3. or, combination of the above.
SanDisk I know is internally flagged as removable, not fixed, and maybe openBSD and your BIOS settings are giving mixed messages.
__________________
Never argue with an idiot. They will bring you down to their level and beat you with experience.

Last edited by s2scott; 10th May 2008 at 12:17 AM. Reason: Added, bullet #3 for clarity
Reply With Quote
Old 9th May 2008
Zmyrgel Zmyrgel is offline
Port Guard
 
Join Date: May 2008
Posts: 26
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by s2scott View Post
  1. In machine BIOS, if configurable, try turning IDE bus mastering to OFF;
  2. In machine BIOS, for the IDE drive that the CF enumerates to, try changing from type "AUTO" to a different but logical choice -- some BIOSs have a type "REMOVABLE IDE".
SanDisk I know is internally flagged as removable, not fixed, and maybe openBSD and your BIOS settings are giving mixed messages.
Ok, I'll check the BIOS options after a nights sleep and little Soekris manual reading.
Reply With Quote
Old 10th May 2008
Zmyrgel Zmyrgel is offline
Port Guard
 
Join Date: May 2008
Posts: 26
Thanked 0 Times in 0 Posts
Default

Ok, didn't help.

Code:
pciide:0:0:0: timeout waiting for DRQ, st=0x51 <DRDY,DSC,ERR>, err=0x00
wd0e: device timeout writing fsbn 47908 (wd0 bn 2100672, cn 521 tn 0 sn 0) retrying
...
newfs: wtfs: write error on block 47908 Input/Output error
First two lines loop ... apparently for each partition and then gives the write error and aborts installer.

I tested with 4.2,4.3 and -current but all gave same result. I also updated my Soekris BIOS.

Is my card broken or is there something else I could try? I didn't find any IDE BIOS options.

Last edited by Zmyrgel; 10th May 2008 at 08:34 AM.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Fixed "xinit" after _7 _8, "how" here in case anyones' "X" breaks... using "nvidia" jb_daefo Guides 0 5th October 2009 09:31 PM
"Thanks" and "Edit Tags". diw Feedback and Suggestions 2 29th March 2009 12:06 AM
"No package available in the PKG_PATH" error Nk2Network OpenBSD Packages and Ports 19 12th January 2009 09:22 PM
Scripted sysinstall fails with "Command 'system' failed" PeterSteele FreeBSD Installation and Upgrading 0 13th November 2008 11:31 PM


All times are GMT. The time now is 07:24 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick