Re: ATAng raid not being detected

2003-09-02 Thread Petri Helenius 
Soren Schmidt wrote:

Oh, that one :) fixed...

-Søren

 

Do you have an idea why my SMP system would crash under heavy load, like
mysql shutdown, just a reboot, etc.?
The system did not have any issues before ATAng was committed.

This is one of the panics;
Debugger(c03ded4a,100,c03f40e5,dd88fc6c,100) at Debugger+0x55
panic(c03f40e5,bfc2930c,a4c3000,c415120c,c1512800) at panic+0x15f
pmap_remove_pages(c15128b0,0,bfc0,11a,dd88fcbc) at 
pmap_remove_pages+0x9b
exit1(c432e390,0,c03dd197,65,dd88fd40) at exit1+0x59c
sys_exit(c432e390,dd88fd10,c03f4371,3eb,1) at sys_exit+0x41
syscall(2f,839002f,bfa9002f,0,) at syscall+0x253
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (1, FreeBSD ELF32, sys_exit), eip = 0x286196db, esp = 
0xbfbffc5c, eb
p = 0xbfbffc78 ---
db>

Pete

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ATAng raid not being detected

2003-09-02 Thread Soren Schmidt 
It seems Petri Helenius wrote:
> Soren Schmidt wrote:
> >It seems Petri Helenius wrote:>  >>>ATAng does not seem to detect my RAID set, 
> >while ATAold boots it>>fine, first boot -v with ATAng kernel and then 
> >ATAold.Any ideas if raid configs should be compatible between them? 
> >Should>>make sense that they are so people upgrading don't get burned...>>
> >Do you have device ataraid in your config file ? (se UPDATING)>>-Søren>  >I 
> >didn't, sorry about that. Is the failure below because I haven't rebuilt my world 
> >yetbut just the kernel?
> At least it blew my array configuration away. "oversized DMA" doesnot sound like it 
> would be caused by userland utility?

Oh, that one :) fixed...

-Søren

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ATAng raid not being detected

2003-09-02 Thread Petri Helenius 
Soren Schmidt wrote:

It seems Petri Helenius wrote:
 

ATAng does not seem to detect my RAID set, while ATAold boots it
fine, first boot -v with ATAng kernel and then ATAold.
Any ideas if raid configs should be compatible between them? Should
make sense that they are so people upgrading don't get burned...
   

Do you have device ataraid in your config file ? (se UPDATING)

-Søren
 

I didn't, sorry about that. Is the failure below because I haven't 
rebuilt my world yet
but just the kernel?

At least it blew my array configuration away. "oversized DMA" does
not sound like it would be caused by userland utility?
Pete

Timecounter "TSC" frequency 598008457 Hz quality 800
Timecounters tick every 10.000 msec
GEOM: create disk ad4 dp=0xc2670370
ad4: 76319MB  [155061/16/63] at ata2-master UDMA100
GEOM: create disk ad6 dp=0xc2670070
ad6: 76319MB  [155061/16/63] at ata3-master UDMA100
GEOM: create disk ad8 dp=0xc25f4e70
ad8: 76319MB  [155061/16/63] at ata4-master UDMA100
acd0: DVDR  at ata7-master PIO4
GEOM: create disk ar0 dp=0xc25f21e0
ar0: 76319MB  [9729/255/63] status: READY subdisks:
disk0 READY on ad4 at ata2-master
disk1 READY on ad8 at ata4-master
ar1: WARNING - mirror lost
GEOM: create disk ar1 dp=0xc267c1e0
ar1: 76319MB  [9729/255/63] status: DEGRADED subdisks:
disk0 READY on ad6 at ata3-master
disk1 DOWN no device found for this disk
Mounting root from ufs:/dev/ar0s1a
Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point.
ad4: FAILURE - oversized DMA transfer attempted 114688 > 65536
ad4: setting up DMA failed
ar0: WARNING - mirror lost
ad8: FAILURE - oversized DMA transfer attempted 114688 > 65536
ad8: setting up DMA failed
ar0: ERROR - array broken
cat: /bin/ls: Input/output error
swapon: 20: Syntax error: word unexpected (expecting ")")
Starting file system checks:
D: not found
T: not found
: not found
ÐÐÐ: not found

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ATAng raid not being detected

2003-09-02 Thread Petri Helenius 
ATAng does not seem to detect my RAID set, while ATAold boots it
fine, first boot -v with ATAng kernel and then ATAold.
Any ideas if raid configs should be compatible between them? Should
make sense that they are so people upgrading don't get burned...
ata2-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin
ad4: setting UDMA100 on Promise PDC20619 chip
GEOM: create disk ad4 dp=0xc2670370
ad4:  ATA-5 disk at ata2-master
ad4: 76319MB (156301488 sectors), 155061 C, 16 H, 63 S, 512 B
ad4: 16 secs/int, 1 depth queue, UDMA100
GEOM: new disk ad4
ata3-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin
ad6: setting UDMA100 on Promise PDC20619 chip
GEOM: create disk ad6 dp=0xc2670170
ad6:  ATA-5 disk at ata3-master
ad6: 76319MB (156301488 sectors), 155061 C, 16 H, 63 S, 512 B
ad6: 16 secs/int, 1 depth queue, UDMA100
[0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:156296322
[1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
[2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
[3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
GEOM: Configure ad4s1, start 32256 length 80023716864 end 80023749119
ata4-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin
GEOM: new disk ad6
GEOM: Configure ad4s1a, start 0 length 268435456 end 268435455
GEOM: Configure ad4s1b, start 268435456 length 2147483648 end 2415919103
GEOM: Configure ad4s1c, start 0 length 80023716864 end 80023716863
GEOM: Configure ad4s1d, start 2415919104 length 536870912 end 2952790015
GEOM: Configure ad4s1e, start 2952790016 length 1073741824 end 4026531839
GEOM: Configure ad4s1f, start 4026531840 length 75997185024 end 80023716863
ad8: setting UDMA100 on Promise PDC20619 chip
GEOM: create disk ad8 dp=0xc25f4e70
ad8:  ATA-5 disk at ata4-master
ad8: 76319MB (156301488 sectors), 155061 C, 16 H, 63 S, 512 B
ad8: 16 secs/int, 1 depth queue, UDMA100
[0] f:80 typ:165 s(CHS):0/1/1 e(CHS):512/254/63 s:63 l:156296322
[1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
[2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
[3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
GEOM: Configure ad6s1, start 32256 length 80023716864 end 80023749119
ata7-master: pio=0x0c wdma=0x22 udma=0x42 cable=40pin
acd0: setting PIO4 on Promise PDC20269 chip
acd0:  DVDR drive at ata7 as master
acd0: read 2705KB/s (2705KB/s) write 2705KB/s (2705KB/s), 2048KB buffer, PIO4
acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet
acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof
acd0: Audio: play, 256 volume levels
acd0: Mechanism: ejectable tray, unlocked
acd0: Medium: 120mm data disc
GEOM: new disk ad8
[0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:156296322
[1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
[2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
[3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0
GEOM: Configure ad8s1, start 32256 length 80023716864 end 80023749119
GEOM: Configure ad8s1a, start 0 length 268435456 end 268435455
GEOM: Configure ad8s1b, start 268435456 length 2147483648 end 2415919103
GEOM: Configure ad8s1c, start 0 length 80023716864 end 80023716863
GEOM: Configure ad8s1d, start 2415919104 length 536870912 end 2952790015
GEOM: Configure ad8s1e, start 2952790016 length 1073741824 end 4026531839
GEOM: Configure ad8s1f, start 4026531840 length 75997185024 end 80023716863
Mounting root from ufs:/dev/ar0s1a
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6
Manual root filesystem specification:
  :  Mount  using filesystem 
   eg. ufs:da0s1a
  ?  List valid disk boot devices
 Abort manual input


ad4: success setting UDMA100 on Promise PDC20619 chip
ad4:  ATA-5 disk at ata2-master
ad4: 76319MB (156301488 sectors), 155061 C, 16 H, 63 S, 512 B
ad4: 16 secs/int, 1 depth queue, UDMA100
ad4: piomode=12 dmamode=34 udmamode=69 cblid=1
GEOM: new disk ad4
ad6: success setting UDMA100 on Promise PDC20619 chip
ad6:  ATA-5 disk at ata3-master
ad6: 76319MB (156301488 sectors), 155061 C, 16 H, 63 S, 512 B
ad6: 16 secs/int, 1 depth queue, UDMA100
ad6: piomode=12 dmamode=34 udmamode=69 cblid=1
ad8: success setting UDMA100 on Promise PDC20619 chip
ad8:  ATA-5 disk at ata4-master
ad8: 76319MB (156301488 sectors), 155061 C, 16 H, 63 S, 512 B
ad8: 16 secs/int, 1 depth queue, UDMA100
ad8: piomode=12 dmamode=34 udmamode=69 cblid=1
ata7-master: piomode=12 dmamode=34 udmamode=66 dmaflag=1
ata7-master: success setting PIO4 on Promise PDC20269 chip
acd0:  DVD-R drive at ata7 as master
acd0: read 2705KB/s (52509KB/s) write 2705KB/s (2705KB/s), 2048KB buffer, PIO4
acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R, DVD-RAM, packet
acd0: Writes: CD-R, CD-RW, DVD-R, DVD-RAM, test write, burnproof
acd0: Audio: play, 256 volume levels
acd0: Mechanism: ejectable tray, unlocked
acd0: Medium: 120mm data disc
lun 0
magic_0 0x6629
magic_1 0x
flags   0x1102 1102
total_disks 2
generation  10
width   1
heads   255
sectors 63
cylinders   9729
total_sector

Re: ATAng raid not being detected

2003-09-01 Thread Soren Schmidt 
It seems Petri Helenius wrote:
> ATAng does not seem to detect my RAID set, while ATAold boots it
> fine, first boot -v with ATAng kernel and then ATAold.
> 
> Any ideas if raid configs should be compatible between them? Should
> make sense that they are so people upgrading don't get burned...

Do you have device ataraid in your config file ? (se UPDATING)

-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"