Re: panic: page fault - 6.0-RELEASE-p7 (now 6.1-RC2)

2006-05-09 Thread Nick Wood 
 limited to 10 packets/entry by default

rr232x: no controller detected.
acd0: CDROM MATSHITA CR-177/7T0D at ata1-master UDMA33
ses0 at asr0 bus 0 target 6 lun 0
ses0: SUPER GEM318 0 Fixed Processor SCSI-2 device
ses0: SAF-TE Compliant Device
da0 at asr0 bus 0 target 0 lun 0
da0: SEAGATE ST336706LC 4101 Fixed Direct Access SCSI-4 device
da0: Tagged Queueing Enabled
da0: 34687MB (71041007 512 byte sectors: 255H 63S/T 4422C)
da1 at asr0 bus 0 target 1 lun 0
da1: ADAPTEC RAID-1 3B05 Fixed Direct Access SCSI-2 device
da1: Tagged Queueing Enabled
da1: 140014MB (286748672 512 byte sectors: 255H 63S/T 17849C)
Trying to mount root from ufs:/dev/da0s1a
---

Any help will be greatly appreciated.

Nick Wood 


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

panic: page fault - 6.0-RELEASE-p7

2006-05-05 Thread Nick Wood 
 can't assign resources (port)
unknown: PNP0501 can't assign resources (port)
unknown: PNP0700 can't assign resources (port)
Timecounter TSC frequency 2399331312 Hz quality 800
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding 
disabled, default to deny, logging limited to 10 packets/entry by default

acd0: CDROM MATSHITA CR-177/7T0D at ata1-master UDMA33
ses0 at asr0 bus 0 target 6 lun 0
ses0: SUPER GEM318 0 Fixed Processor SCSI-2 device
ses0: SAF-TE Compliant Device
da0 at asr0 bus 0 target 0 lun 0
da0: SEAGATE ST336706LC 8A03 Fixed Direct Access SCSI-3 device
da0: Tagged Queueing Enabled
da0: 34732MB (71132942 512 byte sectors: 255H 63S/T 4427C)
da1 at asr0 bus 0 target 1 lun 0
da1: ADAPTEC RAID-1 3B05 Fixed Direct Access SCSI-2 device
da1: Tagged Queueing Enabled
da1: 140014MB (286748672 512 byte sectors: 255H 63S/T 17849C)
--

Thanks,

Nick Wood

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

More driver errors

2003-02-11 Thread Nick Wood 
I'm hoping this is just info being trapped by developers to help write new 
drivers? :)  Not too optimistic though...

System info is at bottom.  Its running 2 hyperthreaded 2.4Ghz processors.

This started happening when we mounted and started using da2:
Feb 10 10:14:19 mail-da-1 /kernel: da2: SEAGATE ST3146807LC 0003 Fixed 
Direct Access SCSI-3 device
Feb 10 10:14:19 mail-da-1 /kernel: da2: 320.000MB/s transfers (160.000MHz, 
offset 63, 16bit), Tagged Queueing Enabled
Feb 10 10:14:19 mail-da-1 /kernel: da2: 140014MB (286749488 512 byte 
sectors: 255H 63S/T 17849C)

There have been no panics, or anything else noticeable, other than these logs.


Feb 11 10:20:25 mailserver /kernel: Copied 18 bytes of sense data offset 
12: 0x70 0x0 0x0 0x9 0x5d 0x70 0x9f 0xa 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Feb 11 10:24:05 mailserver /kernel: Copied 18 bytes of sense data offset 
12: 0x70 0x0 0x0 0x9 0x5d 0x86 0xbf 0xa 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Feb 11 10:24:05 mailserver /kernel: Copied 18 bytes of sense data offset 
12: 0x70 0x0 0x0 0x9 0x5d 0x86 0xbf 0xa 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Feb 11 10:24:05 mailserver /kernel: Copied 18 bytes of sense data offset 
12: 0x70 0x0 0x0 0x9 0x5d 0x8a 0x63 0xa 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Feb 11 10:24:05 mailserver /kernel: Copied 18 bytes of sense data offset 
12: 0x70 0x0 0x0 0x9 0x5d 0x8a 0x63 0xa 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Feb 11 10:24:05 mailserver /kernel: Copied 18 bytes of sense data offset 
12: 0x70 0x0 0x0 0x9 0x5d 0x8b 0x8f 0xa 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Feb 11 10:24:05 mailserver /kernel: Copied 18 bytes of sense data offset 
12: 0x70 0x0 0x0 0x9 0x5d 0x8f 0x4b 0xa 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Feb 11 10:24:05 mailserver /kernel: Copied 18 bytes of sense data offset 
12: 0x70 0x0 0x0 0x9 0x5d 0x8f 0x4b 0xa 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Feb 11 10:24:05 mailserver /kernel: Copied 18 bytes of sense data offset 
12: 0x70 0x0 0x0 0x9 0x5d 0x8f 0x4b 0xa 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Feb 11 10:25:52 mailserver /kernel: Copied 18 bytes of sense data offset 
12: 0x70 0x0 0x0 0x0 0x0 0x0 0x4f 0xa 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Feb 11 10:26:55 mailserver /kernel: (da2:ahd0:0:2:0): SCB 0x31 - timed out
Feb 11 10:27:11 mailserver /kernel:  Dump Card State 
Begins 
Feb 11 10:27:11 mailserver /kernel: ahd0: Dumping Card State at program 
address 0xd Mode 0x33
Feb 11 10:27:11 mailserver /kernel: Card was paused
Feb 11 10:27:11 mailserver /kernel: SCSISEQ0[0x0] 
SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI)
Feb 11 10:27:11 mailserver /kernel: SEQINTCTL[0x0] 
SCSISIGI[0x0]:(P_DATAOUT) SCSIPHASE[0x0]
Feb 11 10:27:11 mailserver /kernel: SCSIBUS[0x0] 
LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE)
Feb 11 10:27:11 mailserver /kernel: 
SEQ_FLAGS[0xc0]:(NO_CDB_SENT|NOT_IDENTIFIED) SEQ_FLAGS2[0x0]
Feb 11 10:27:11 mailserver /kernel: SSTAT0[0x0] SSTAT1[0x8]:(BUSFREE) 
SSTAT2[0x0] SSTAT3[0x0]
Feb 11 10:27:11 mailserver /kernel: PERRDIAG[0x0] 
SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO)
Feb 11 10:27:11 mailserver /kernel: LQISTAT0[0x0] LQISTAT1[0x0] 
LQISTAT2[0x0] LQOSTAT0[0x0]
Feb 11 10:27:11 mailserver /kernel: LQOSTAT1[0x0] LQOSTAT2[0x0]
Feb 11 10:27:11 mailserver /kernel:
Feb 11 10:27:11 mailserver /kernel: SCB Count = 208 LASTSCB 0xb4 CURRSCB 
0xb4 NEXTSCB 0xff00
Feb 11 10:27:11 mailserver /kernel: qinstart = 57452 qinfifonext = 57452
Feb 11 10:27:11 mailserver /kernel: QINFIFO:
Feb 11 10:27:11 mailserver /kernel: WAITING_TID_QUEUES:
Feb 11 10:27:11 mailserver /kernel: Pending list:
Feb 11 10:27:11 mailserver /kernel: 49 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) 
SCB_SCSIID[0x27] SCB_TAG[0x31]
Feb 11 10:27:11 mailserver /kernel: Kernel Free SCB list: 180 75 16 8 1 78 
2 37 74 30 23 79 50 40 38 11 46 44 17 43 53 27 25 21 52 58 57 45 29 15 54 
12 18 179 3 19 60 132 61 62 26 41 32 14 31 5 39 51 6 4 10 47 20 0 76 77 9 
63 34 28 59 42 48 22 155 156 157 158 159 128 129 130 131 55 148 149 150 151 
152 153 154 147 146 145 144 175 174 173 172 171 170 169 168 167 166 165 164 
163 162 13 161 160 191 190 189 188 187 186 185 184 183 182 181 178 177 176 
207 73 35 133 134 135 136 137 138 139 140 141 142 24 143 112 113 114 115 
116 117 118 119 120 121 122 123 124 125 7 126 127 96 97 98 99 100 101 102 
103 104 105 106 107 108 109 110 33 111 80 81 82 83 84 85 86 87 88 89 90 91 
92 93 94 95 64 65 66 67 68 69 70 71 72 56 36 206 205 204 203 202 201 200 
199 198 197 196 195 194 193 192
Feb 11 10:27:11 mailserver /kernel: Sequencer Complete DMA-inprog list:
Feb 11 10:27:11 mailserver /kernel: Sequencer Complete list:
Feb 11 10:27:11 mailserver /kernel: Sequencer DMA-Up and Complete list:
Feb 11 10:27:11 mailserver /kernel:
Feb 11 10:27:11 mailserver /kernel: ahd0: FIFO0 Free, LONGJMP == 0x80ff, 
SCB 0xb4, LJSCB 0xff00
Feb 11 10:27:11 mailserver /kernel: 
SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) 

Feb 11 10:27:11 mailserver /kernel: SEQINTSRC[0x0] DFCNTRL[0x0]

SUIDDIR - security

2003-01-01 Thread Nick Wood 
I'm thinking of enabling SUIDDIR on a web server that offers CGI -possibly 
even shell access if there's a difference.

This is mentioned in several man pages: It provides security holes for 
shell users and as such should not be used on shell machines, especially on 
home directories.

With regards to creating files/etc, it mentions:  Execute bits are removed 
from the file, and it will not be given to root.

With that in mind, can anyone give me a specific example on how this can 
pose a security risk?

	Nick


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message