Re: ATA/ACHI Jmicron broken up
Thanks! Patch helped.
2015-09-22 12:27 GMT+03:00 Alexander Motin <m...@freebsd.org>:
> On 22.09.2015 12:19, Michael BlackHeart wrote:
> > dmesg from updated system is a little bit tricky right now. I can
> > provide working system dmesg and say what's missing in it's output when
> > I try to boot new kernel.
> >
> > Here goes pciconf
> >
> > atapci0@pci0:2:0:0: class=0x010400 card=0x75121462 chip=0x2363197b
> > rev=0x03 hdr=0x00
> > vendor = 'JMicron Technology Corp.'
> > device = 'JMB363 SATA/IDE Controller'
> > class = mass storage
> > subclass = RAID
> > bar [24] = type Memory, range 32, base 0xf7dfe000, size 8192,
> enabled
> > cap 01[68] = powerspec 2 supports D0 D3 current D0
> > cap 10[50] = PCI-Express 1 legacy endpoint IRQ 1 max data 128(128)
> > link x1(x1)
> > speed 2.5(2.5) ASPM disabled(L0s)
>
> OK, I see the problem -- it is reported as RAID, but not as AHCI, as
> devices that I had before, and so ahci(4) driver does not attach. Could
> you test the attached patch? I should allow driver attachment to such
> devices.
>
> --
> Alexander Motin
>
--
amd_miek
Think different.
Just superior.
Index: ahci_pci.c
===
--- ahci_pci.c (revision 288021)
+++ ahci_pci.c (working copy)
@@ -327,6 +327,9 @@ ahci_probe(device_t dev)
pci_get_subclass(dev) == PCIS_STORAGE_SATA &&
pci_get_progif(dev) == PCIP_STORAGE_SATA_AHCI_1_0)
valid = 1;
+ else if (pci_get_class(dev) == PCIC_STORAGE &&
+ pci_get_subclass(dev) == PCIS_STORAGE_RAID)
+ valid = 2;
/* Is this a known AHCI chip? */
for (i = 0; ahci_ids[i].id != 0; i++) {
if (ahci_ids[i].id == devid &&
@@ -343,7 +346,7 @@ ahci_probe(device_t dev)
return (BUS_PROBE_DEFAULT);
}
}
- if (!valid)
+ if (valid != 1)
return (ENXIO);
device_set_desc_copy(dev, "AHCI SATA controller");
return (BUS_PROBE_DEFAULT);
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: freebsd-stable Digest, Vol 635, Issue 1
Hello there. I've reverted to 10.2 RELEASE revision 28, recompile kernel and my JMicron 363 still works. So problem appears after deleting some achi-relative stuff from ata driver. Or I just do not figure out how to configure this setup. By the way tried GENERIC kernel from 287988 revision - same stuff. No disks, no raid. 2015-09-21 18:09 GMT+03:00 Michael BlackHeart <amdm...@gmail.com>: > I can defenetly say that this thing is missing with a new kernel in boot > log: > > atapci0: AHCI called from vendor specific driver > atapci0: AHCI v1.00 controller with 2 3Gbps ports, PM supported > > >> Hello there. >> I've just tried to update from FreeBSD 10.2-PRERELEASE #0 r285303: to >> >> URL: svn://svn.freebsd.org/base/stable/10 >> Relative URL: ^/stable/10 >> Repository Root: svn://svn.freebsd.org/base >> Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f >> Revision: 287988 >> >> And everything goes wrong. GEOM RAID didn't start at boot time. It has to >> be connected with recent ata and achi driver workaround but I didn't get >> how to get it back working. >> >> Box configuration and setup. >> >> 6 HDD on intel ACHI-mode ICH10R - they're irrelevant. >> >> 2HDD (SATA interface) on JMicron JMB363 RAID enabled controller. This >> controller has 2 SATA ports and 2 IDE ports(Or it's 2 controllers with >> common interface) and works in RAID mode. It seems that previously it >> worked with atajmicron kernel module. There was a GEOM RAID control to >> handle hardware RAID and this 2 HDD holds on an entire system in UFS >> booted >> by label. >> >> Here's kernel configuration and boot log from working set. >> >> diablo.miekoff.local#/var/log/>kldstat -vvv >> Id Refs AddressSize Name >> 1 10 0x8020 eab5c0 kernel (/boot/kernel/kernel) >> Contains modules: >> Id Name >> 278 newreno >> 228 if_lo >> 266 ng_socket >> 283 pfsync >> 208 shell >> 207 elf32 >> 206 elf64 >> 177 pseudofs >> 222 bridgestp >> 230 if_tun >> 223 if_bridge >> 227 if_gre >> 225 if_faith >> 281 mld >> 226 if_gif >> 276 igmp >> 280 ip6_mroute >> 288 cryptodev >> 282 pflog >> 231 if_vlan >> 269 ng_tcpmss >> 268 ng_tag >> 255 ng_iface >> 267 ng_sppp >> 245 ng_bpf >> 254 ng_gif_demux >> 242 ng_netflow >> 265 ng_rfc1490 >> 277 ip_mroute >> 264 ng_pptpgre >> 263 ng_pppoe >> 253 ng_gif >> 262 ng_ppp >> 252 ng_framerelay >> 261 ng_pipe >> 251 ng_ether >> 250 ng_eiface >> 260 ng_one2many >> 259 ng_mppc >> 249 ng_echo >> 248 ng_device >> 247 ng_deflate >> 258 ng_lmi >> 257 ng_l2tp >> 246 ng_bridge >> 256 ng_ksocket >> 243 ng_UI >> 272 ng_vlan >> 271 ng_vjc >> 270 ng_tee >> 284 pf >> 214 sysvmsg >> 215 sysvsem >> 216 sysvshm >> 171 nfscommon >> 217 aio >> 287 nfslockd >> 174 nfsd >> 290 krpc >> 286 nfssvc >> 179 udf >> 175 nullfs >> 204 cd9660 >> 170 msdosfs >> 291 ufs >> 180 tmpfs >> 172 nfs >> 167 devfs >> 168 fdescfs >> 176 procfs >> 173 nfscl >> 211 acl_posix1e >> 210 acl_nfs4 >> 15 ctltpc >> 12 ctlcfcs >> 14 ctlcfiscsi >> 11 cbr >> 13 ctlcfi >> 16 ctlfe >&g
Re: freebsd-stable Digest, Vol 635, Issue 1
I can defenetly say that this thing is missing with a new kernel in boot log: atapci0: AHCI called from vendor specific driver atapci0: AHCI v1.00 controller with 2 3Gbps ports, PM supported 2015-09-21 15:00 GMT+03:00 <freebsd-stable-requ...@freebsd.org>: > Send freebsd-stable mailing list submissions to > freebsd-stable@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > or, via email, send a message with subject or body 'help' to > freebsd-stable-requ...@freebsd.org > > You can reach the person managing the list at > freebsd-stable-ow...@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-stable digest..." > > > Today's Topics: > >1. Re: fat32 question (Julian H. Stacey) >2. Re: fat32 question (Zoran Kolic) >3. ZFS UEFI boot? (Rainer Duffner) >4. Re: fat32 question (Erich Dollansky) >5. FreeBSD 10.2 Stable JMicron RIAD update problem > (Michael BlackHeart) > > > -- > > Message: 1 > Date: Sun, 20 Sep 2015 14:12:31 +0200 > From: "Julian H. Stacey" <j...@berklix.com> > To: Zoran Kolic <zko...@sbb.rs> > Cc: freebsd-stable@freebsd.org > Subject: Re: fat32 question > Message-ID: <201509201212.t8kccvw7068...@fire.js.berklix.net> > > Tomoaki AOKI wrote: > > According to "Real Hardware Gotchas" section in [1], FAT32 fs creation > > of FreeBSD seems to have some problems. > > > > Try formatting by the hardware you're going to transfer files from > > FreeBSD, if available. Once formatted by other OS, read/write/delete > > files in FAT32 formatted media would be OK with FreeBSD. > > > > If not, and if the file you want to transfer is small enough, partition > > the media and use FAT16. (The safest maximum is 32MB, but maybe under > > 2GB would be OK.) > > > > [1] https://wiki.freebsd.org/UEFI > > Zoran, re Brandon's "won't understand it any more." > Dont despair & discard stick, you can rebuild the MBR: man fdisk > from memory start with fdisk -i -B /dev/da0 > > sometimes I then remove & reinsert or even reboot, to make certain > the OS has the new numbers. I don't recall I've needed to reduce > from FAT32 to FAT16. > > Ive not read the uefi page as happily no boxes are uefi here, > but I've often created FAT32 partitions, my notes at > > http://www.berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/jhs/etc/devd/berklix.conf > > The advice about letting the other native MS FAT device format if it will, > is quickest solution though. > > PS Max size of FAT32 = 2TB > https://en.wikipedia.org/wiki/File_Allocation_Table#FAT32 > > > > > > > On Sun, 20 Sep 2015 06:55:19 +0200 > > Zoran Kolic <zko...@sbb.rs> wrote: > > > > > I have a device to which I'd like to connect otg cable > > > and insert 16gb usb stick. Tried "newfs_msdos -F32 /dev/da0". > > > Mounted, copied files. The device does not see the file > > > system at all. > > > Any idea what to do further? Another option might be extfs. > > > Best regards > > > > > > Zoran > > > > > Cheers, > Julian > -- > Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich > http://berklix.com > Reply after previous text, like a play - Not before, which looses context. > Indent previous text with "> " Insert new lines before 80 chars. > Send plain text, Not quoted-printable, Not HTML, Not ms.doc, Not base64. > > > -- > > Message: 2 > Date: Sun, 20 Sep 2015 16:23:42 +0200 > From: Zoran Kolic <zko...@sbb.rs> > To: "Julian H. Stacey" <j...@berklix.com> > Cc: allber...@gmail.com, bruc...@austin.rr.com, > freebsd-stable@freebsd.org > Subject: Re: fat32 question > Message-ID: <20150920142342.ga...@faust.sbb.rs> > Content-Type: text/plain; charset=us-ascii > > > Zoran, re Brandon's "won't understand it any more." > > Dont despair & discard stick, you can rebuild the MBR: man fdisk > > from memory start with fdisk -i -B /dev/da0 > > First, thanks all for replies! > After a bit of puzzling, I found that the problem was every Transcend > usb stick I have. They are all fine for mundane tasks and newfs_msdos > makes it able to work on freebsd. My music player was picky and has > something to say against. When I inserted old and forgoten Verbatim > d
FreeBSD 10.2 Stable JMicron RIAD update problem
Hello there. I've just tried to update from FreeBSD 10.2-PRERELEASE #0 r285303: to URL: svn://svn.freebsd.org/base/stable/10 Relative URL: ^/stable/10 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 287988 And everything goes wrong. GEOM RAID didn't start at boot time. It has to be connected with recent ata and achi driver workaround but I didn't get how to get it back working. Box configuration and setup. 6 HDD on intel ACHI-mode ICH10R - they're irrelevant. 2HDD (SATA interface) on JMicron JMB363 RAID enabled controller. This controller has 2 SATA ports and 2 IDE ports(Or it's 2 controllers with common interface) and works in RAID mode. It seems that previously it worked with atajmicron kernel module. There was a GEOM RAID control to handle hardware RAID and this 2 HDD holds on an entire system in UFS booted by label. Here's kernel configuration and boot log from working set. diablo.miekoff.local#/var/log/>kldstat -vvv Id Refs AddressSize Name 1 10 0x8020 eab5c0 kernel (/boot/kernel/kernel) Contains modules: Id Name 278 newreno 228 if_lo 266 ng_socket 283 pfsync 208 shell 207 elf32 206 elf64 177 pseudofs 222 bridgestp 230 if_tun 223 if_bridge 227 if_gre 225 if_faith 281 mld 226 if_gif 276 igmp 280 ip6_mroute 288 cryptodev 282 pflog 231 if_vlan 269 ng_tcpmss 268 ng_tag 255 ng_iface 267 ng_sppp 245 ng_bpf 254 ng_gif_demux 242 ng_netflow 265 ng_rfc1490 277 ip_mroute 264 ng_pptpgre 263 ng_pppoe 253 ng_gif 262 ng_ppp 252 ng_framerelay 261 ng_pipe 251 ng_ether 250 ng_eiface 260 ng_one2many 259 ng_mppc 249 ng_echo 248 ng_device 247 ng_deflate 258 ng_lmi 257 ng_l2tp 246 ng_bridge 256 ng_ksocket 243 ng_UI 272 ng_vlan 271 ng_vjc 270 ng_tee 284 pf 214 sysvmsg 215 sysvsem 216 sysvshm 171 nfscommon 217 aio 287 nfslockd 174 nfsd 290 krpc 286 nfssvc 179 udf 175 nullfs 204 cd9660 170 msdosfs 291 ufs 180 tmpfs 172 nfs 167 devfs 168 fdescfs 176 procfs 173 nfscl 211 acl_posix1e 210 acl_nfs4 15 ctltpc 12 ctlcfcs 14 ctlcfiscsi 11 cbr 13 ctlcfi 16 ctlfe 10 cbb 9 ctl 2 cam 45 ata 205 cd9660_iconv 20 enc 7 ch 19 sa 4 pmp 221 iconv_xlat16 220 iconv_xlat 219 iconv_ucs 5 probe 18 pass 178 udf_iconv 189 g_part_mbr 188 g_part_gpt 187 g_part_ebr 186 g_part_bsd 8 ada 17 da 1 xpt 229 sppp 3 aprobe 6 cd 169 msdosfs_iconv 76 drmn/fbd 75 fb/fbd 74 cpu/ichss 148 pci/uhci 39 cpu/acpi_throttle 25 acpi/acpi_cmbat 341 isa/sysresource 340 nexus/ram 339 root/nexus 147 pci/ohci 38 acpi/acpi_tz 146 pci/ehci 37 acpi/acpi_smbat 30 acpi/acpi_lid 36 acpi/acpi_sysresource 23 acpi/acpi_acad 29 acpi/acpi_isab 73 pci/ath_pci 72 pci/ata_via 338 legacy/cpu 337 nexus/legacy 145 puc/uart 336 nexus/apic 335 pci/ioapic 144 pci/uart 143 isa/uart 142 acpi/uart 334 qpi/pcib 333 nexus/qpi 71 pci/ata_sis
Re: Need help with diagnostics
Thanks. I do really have in kernel options ATH_DEBUG options ATH_DIAGAPI and I've got D-Link WiFi card with Atheros chip ath0@pci0:3:0:0:class=0x028000 card=0x3a7e1186 chip=0x0030168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9300 Wireless LAN adaptor' class = network bar [10] = type Memory, range 64, base 0xf7ee, size 131072, enabled cap 01[40] = powerspec 3 supports D0 D1 D3 current D0 cap 05[50] = MSI supports 4 messages, 64 bit, vector masks cap 10[70] = PCI-Express 2 endpoint max data 128(128) link x1(x1) speed 2.5(2.5) ASPM disabled(L0s/L1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0002[140] = VC 1 max VC0 ecap 0003[300] = Serial 1 If you say that's nothing bad than OK. I just get a little worried 'cos I never expieirnced this debug output for at least 2 years of using this card. Probably last kernel/system update to 1001510 r280164 stable bring this up. 2015-04-24 9:32 GMT+03:00 Victor Balada Diaz vic...@bsdes.net: On Sun, Apr 12, 2015 at 12:11:42PM +0300, Michael BlackHeart wrote: In a log Apr 11 10:10:23 diablo kernel: Seq: 17600 swtry: 0 ADDBAW?: 1 DOBAW?: 1 [ lots of trimmed log entries ] First time I see this and do not know what is it and how to handle it. There's no kernel debug symbols. Do you have ATH_DEBUG enabled in your kernel? This seems to be printed by an Atheros card[1] where the driver is compiled with debug support. As this seems to be debugging information, I don't think there is anything you need to do with it. [1]: http://fxr.watson.org/fxr/source/dev/ath/if_ath_debug.c#L161 -- amd_miek Think different. Just superior. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Need help with diagnostics
In a log Apr 11 10:10:23 diablo kernel: Q1[ 0] (nseg=2) (DS.V:0xfe0121174a00 DS.P:0x2f74a00) I: 168cc117 L:02fc6300 F:0004 Apr 11 10:10:23 diablo kernel: (D[0] = a7174ed2(002c), D[1] = 03016000(05c8) Apr 11 10:10:23 diablo kernel: (D[2] = (), D[3] = () Apr 11 10:10:23 diablo kernel: Seq: 17600 swtry: 0 ADDBAW?: 1 DOBAW?: 1 Apr 11 10:10:23 diablo kernel: 4ba99c7e 407c05fe 6000c000 04348000 00858687 81bf8197 Apr 11 10:10:23 diablo kernel: 81f1 08f00cf6 709039ce 2000 Apr 11 10:10:23 diablo kernel: [end] Apr 11 10:10:23 diablo kernel: (DS.V:0xfe01211c6300 DS.P:0x2fc6300) I: 168cc117 L: F:0004 Apr 11 10:10:23 diablo kernel: (D[0] = 29cd87d2(002c), D[1] = 81646004(05c8) Apr 11 10:10:23 diablo kernel: (D[2] = (), D[3] = () Apr 11 10:10:23 diablo kernel: Seq: 17616 swtry: 0 ADDBAW?: 1 DOBAW?: 1 Apr 11 10:10:23 diablo kernel: 4baa709f 403c05fe 4000c000 04348000 00858687 86058572 Apr 11 10:10:23 diablo kernel: 86c4 0800 2000 Apr 11 10:10:23 diablo kernel: [end] Apr 11 10:10:23 diablo kernel: Q1[ 0] (nseg=2) (DS.V:0xfe0121174a00 DS.P:0x2f74a00) I: 168cc117 L:02fc6300 F:0004 Apr 11 10:10:23 diablo kernel: (D[0] = a7174ed2(002c), D[1] = 03016000(05c8) Apr 11 10:10:23 diablo kernel: (D[2] = (), D[3] = () Apr 11 10:10:23 diablo kernel: Seq: 17600 swtry: 1 ADDBAW?: 1 DOBAW?: 1 Apr 11 10:10:23 diablo kernel: 4ba99c7e 407c05fe 6000c000 04348000 00858687 829a825a Apr 11 10:10:23 diablo kernel: 82ea 08f013ea 709039ce 2000 Apr 11 10:10:23 diablo kernel: [end] Apr 11 10:10:23 diablo kernel: (DS.V:0xfe01211c6300 DS.P:0x2fc6300) I: 168cc117 L:02f48400 F:0004 Apr 11 10:10:23 diablo kernel: (D[0] = 29cd87d2(002c), D[1] = 81646004(05c8) Apr 11 10:10:23 diablo kernel: (D[2] = (), D[3] = () Apr 11 10:10:23 diablo kernel: Seq: 17616 swtry: 1 ADDBAW?: 1 DOBAW?: 1 Apr 11 10:10:23 diablo kernel: 4baaf794 403c05fe 6000c000 04348000 00858687 86058572 Apr 11 10:10:23 diablo kernel: 86c4 08f0 2000 Apr 11 10:10:23 diablo kernel: [end] Apr 11 10:10:23 diablo kernel: (DS.V:0xfe0121148400 DS.P:0x2f48400) I: 168cc117 L: F:0014 Apr 11 10:10:23 diablo kernel: (D[0] = aebe6dd2(002c), D[1] = 7f960804(05c8) Apr 11 10:10:23 diablo kernel: (D[2] = (), D[3] = () Apr 11 10:10:23 diablo kernel: Seq: 17648 swtry: 0 ADDBAW?: 1 DOBAW?: 1 Apr 11 10:10:23 diablo kernel: 4bac81c2 403c05fe 4000c000 24348000 81858687 80e380d1 Apr 11 10:10:23 diablo kernel: 837a80fc 0800 2000 Apr 11 10:10:23 diablo kernel: [end] Apr 11 10:10:23 diablo kernel: Q1[ 0] (nseg=2) (DS.V:0xfe0121174a00 DS.P:0x2f74a00) I: 168cc117 L:02fc6300 F:0004 Apr 11 10:10:23 diablo kernel: (D[0] = a7174ed2(002c), D[1] = 03016000(05c8) Apr 11 10:10:23 diablo kernel: (D[2] = (), D[3] = () Apr 11 10:10:23 diablo kernel: Seq: 17600 swtry: 2 ADDBAW?: 1 DOBAW?: 1 Apr 11 10:10:23 diablo kernel: 4ba99c7e 407c05fe 6000c000 04348000 00858687 852a84ac Apr 11 10:10:23 diablo kernel: 85cc 08f028c6 709039ce 2000 Apr 11 10:10:23 diablo kernel: [end] Apr 11 10:10:23 diablo kernel: (DS.V:0xfe01211c6300 DS.P:0x2fc6300) I: 168cc117 L:02f48400 F:0004 Apr 11 10:10:23 diablo kernel: (D[0] = 29cd87d2(002c), D[1] = 81646004(05c8) Apr 11 10:10:23 diablo kernel: (D[2] = (), D[3] = () Apr 11 10:10:23 diablo kernel: Seq: 17616 swtry: 2 ADDBAW?: 1 DOBAW?: 1 Apr 11 10:10:23 diablo kernel: 4baaf794 403c05fe 6000c000 04348000 00858687 86058572 Apr 11 10:10:23 diablo kernel: 86c4 08f0 2000 Apr 11 10:10:23 diablo kernel: [end] Apr 11 10:10:23 diablo kernel: (DS.V:0xfe0121148400 DS.P:0x2f48400) I: 168cc117 L:02f3df00 F:0014 Apr 11 10:10:23 diablo kernel: (D[0] = aebe6dd2(002c), D[1] = 7f960804(05c8) Apr 11 10:10:23 diablo kernel: (D[2] = (), D[3] = () Apr 11 10:10:23 diablo kernel: Seq: 17648 swtry: 1 ADDBAW?: 1 DOBAW?: 1 Apr 11 10:10:23 diablo kernel: 4bac63b6 403c05fe 6000c000 24348000 81858687 80e380d1 Apr 11 10:10:23 diablo kernel: 837a80fc 08f0 2000 Apr 11 10:10:23 diablo kernel: [end] Apr 11 10:10:23 diablo kernel: (DS.V:0xfe012113df00 DS.P:0x2f3df00) I: 168cc117 L:02f74f00 F:0004 Apr 11 10:10:23 diablo kernel: (D[0] = 832a9cd2(002c), D[1] = 1aa35004(05c8) Apr 11 10:10:23 diablo kernel: (D[2] = (), D[3] = () Apr 11 10:10:23 diablo kernel: Seq: 17696 swtry: 0 ADDBAW?: 1 DOBAW?: 1 Apr 11 10:10:23 diablo kernel: 4bafba32 403c05fe 6000c000 24348000 81858687 80e380d1 Apr 11 10:10:23 diablo
savecore problem
Hello there. I've got a problem. Recently my personal server issued a kernel panic. Then there's a dump and so on. But there's no dump information after reboot. I do not know what was really the panic cause but assume that savecore failed because of RAID. Problem - minidump was done (I saw it was) but was not recovered by savecore after reboot into /var/vrash Filesystem is UFS FreeBSD diablo.miekoff.local 10.1-STABLE FreeBSD 10.1-STABLE #0 r277169: Thu Jan 15 10:22:34 MSK 2015 amd_miek@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 amd64 rc.conf configuration dumpdev=AUTO dumpdir=/var/crash/ RAID 1 via graid configuration (JMicron based) graid list Geom name: JMicron-6e1c79e State: OPTIMAL Metadata: JMicron Providers: 1. Name: raid/r0 Mediasize: 120024203264 (112G) Sectorsize: 512 Mode: r6w6e16 Subdisks: ada0 (ACTIVE), ada1 (ACTIVE) Dirty: No State: OPTIMAL Strip: 1024 Components: 2 Transformation: RAID1 RAIDLevel: RAID1 Label: SYSMIRROR descr: JMicron RAID1 volume Consumers: 1. Name: ada0 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(SYSMIRROR):0@0 State: ACTIVE (ACTIVE) 2. Name: ada1 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(SYSMIRROR):1@0 State: ACTIVE (ACTIVE) /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/ufs/rootfs / ufs rw,noatime 1 1 /dev/raid/r0p3 noneswapsw 0 0 /dev/ufs/varfs /varufs rw,noatime 2 2 /dev/ufs/tmpfs /tmpufs rw,noatime 2 2 /dev/ufs/usrfs /usrufs rw,noatime 2 2 /dev/ufs/configfs /config ufs rw,noatime 2 2 tmpfs /usr/tmpfs tmpfs rw 0 0 proc/proc procfs rw 0 0 fdesc /dev/fd fdescfs rw 0 0 In kernel configuration DEBUG -g is disabled. -- amd_miek Think different. Just superior. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: savecore problem
I've tried to run manually savecore. I tried before RAID get OPTIMAL and after that. dumpmon says: dumpon -l raid/r0p3 savecore -vvf /var/crash /dev/raid/r0p3 worked now but... It extracted another dump from october 2014. On my box swap used just a little so I blieve that there might be that dump but where's dump from march,15 2015? I'd like to figure out what happend with savecore and kernel dumps. Is there a safe way to test this functional? Some test kernel panics? 2015-03-16 18:33 GMT+03:00 Konstantin Kulikov k.kulik...@gmail.com: Hello, have you tried to run savecore manually, like savecore -vvf /var/crash /dev/raid/r0p3 Also check that your dump device is working (dumpon -l) On Mon, Mar 16, 2015 at 4:40 PM, Michael BlackHeart amdm...@gmail.com wrote: Hello there. I've got a problem. Recently my personal server issued a kernel panic. Then there's a dump and so on. But there's no dump information after reboot. I do not know what was really the panic cause but assume that savecore failed because of RAID. Problem - minidump was done (I saw it was) but was not recovered by savecore after reboot into /var/vrash Filesystem is UFS FreeBSD diablo.miekoff.local 10.1-STABLE FreeBSD 10.1-STABLE #0 r277169: Thu Jan 15 10:22:34 MSK 2015 amd_miek@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 amd64 rc.conf configuration dumpdev=AUTO dumpdir=/var/crash/ RAID 1 via graid configuration (JMicron based) graid list Geom name: JMicron-6e1c79e State: OPTIMAL Metadata: JMicron Providers: 1. Name: raid/r0 Mediasize: 120024203264 (112G) Sectorsize: 512 Mode: r6w6e16 Subdisks: ada0 (ACTIVE), ada1 (ACTIVE) Dirty: No State: OPTIMAL Strip: 1024 Components: 2 Transformation: RAID1 RAIDLevel: RAID1 Label: SYSMIRROR descr: JMicron RAID1 volume Consumers: 1. Name: ada0 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(SYSMIRROR):0@0 State: ACTIVE (ACTIVE) 2. Name: ada1 Mediasize: 120034123776 (112G) Sectorsize: 512 Mode: r1w1e1 ReadErrors: 0 Subdisks: r0(SYSMIRROR):1@0 State: ACTIVE (ACTIVE) /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/ufs/rootfs / ufs rw,noatime 1 1 /dev/raid/r0p3 noneswapsw 0 0 /dev/ufs/varfs /varufs rw,noatime 2 2 /dev/ufs/tmpfs /tmpufs rw,noatime 2 2 /dev/ufs/usrfs /usrufs rw,noatime 2 2 /dev/ufs/configfs /config ufs rw,noatime 2 2 tmpfs /usr/tmpfs tmpfs rw 0 0 proc/proc procfs rw 0 0 fdesc /dev/fd fdescfs rw 0 0 In kernel configuration DEBUG -g is disabled. -- amd_miek Think different. Just superior. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org -- amd_miek Think different. Just superior. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Running a script via PHP
Hello there, It's quite off-topic, but I'm using freebsd-stable,so The priblem is - running a script that requires root privileges via PHP (or probably CGI - I do not care, just want it to be secure and working). It's all about minidlna service (I use upnp to so mediatomb and other are no options). On FreeBSD it should be resync-ed manually, so I've got a simple script placed in /etc/periodic/daily: more 957.dlna_update #!/bin/sh #Script to daily update minidlna DB a=$* if (/usr/local/etc/rc.d/minidlna stop 1/dev/null);then sleep 10 if /usr/local/etc/rc.d/minidlna rescan;then /usr/bin/logger -t minidlna DB updated. exit 0 else /usr/bin/logger -t minidlna Error. Failed to update DB. exit 1 fi else /usr/bin/logger -t minidlna Error. Failed to update DB. exit 1 fi And it's working fine to me. But it uses service infrastructure. So when I'm trying to run via PHP it fails. For example running under unprivileged user: id uid=1001(amd_miek) gid=0(wheel) groups=0(wheel),5(operator) -rwsr-sr-x 1 root wheel 394 27 сен 10:58 957.dlna_update* sh -x 957.dlna_update + a='' + /usr/local/etc/rc.d/minidlna stop kill: 10786: Operation not permitted + /usr/bin/logger -t minidlna 'Error. Failed to update DB.' + exit 1 What is the best way to run it via WEB? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ZFS pool with 4k sector size
Hello, I'd like to know what is the best way to convert my pool from 512b sector size to 4k sector size. Hardware: 2 x2Tb WD Green with 4k physical sector size Model Family: Western Digital Caviar Green (AF, SATA 6Gb/s) Device Model: WDC WD20EARX-00PASB0 Serial Number: WD-WCAZA8280575 LU WWN Device Id: 5 0014ee 206032063 Firmware Version: 51.0AB51 User Capacity: 2 000 398 934 016 bytes [2,00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Aug 22 11:33:16 2013 MSK SMART support is: Available - device has SMART capability. SMART support is: Enabled They're running in a mirror pool: storage state: ONLINE scan: resilvered 48K in 0h0m with 0 errors on Thu Jul 25 19:18:01 2013 config: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada3 ONLINE 0 0 0 ada7 ONLINE 0 0 0 zdb info storage: version: 5000 name: 'storage' state: 0 txg: 1292269 pool_guid: 18442220950447532371 hostid: 708219113 hostname: 'diablo.miekoff.local' vdev_children: 1 vdev_tree: type: 'root' id: 0 guid: 18442220950447532371 create_txg: 4 children[0]: type: 'mirror' id: 0 guid: 4289294206539029185 metaslab_array: 33 metaslab_shift: 34 ashift: 9 asize: 2000394125312 is_log: 0 create_txg: 4 children[0]: type: 'disk' id: 0 guid: 16348588566764560218 path: '/dev/ada3' phys_path: '/dev/ada3' whole_disk: 1 DTL: 95 create_txg: 4 children[1]: type: 'disk' id: 1 guid: 7655198429866445090 path: '/dev/ada7' phys_path: '/dev/ada7' whole_disk: 1 DTL: 97 create_txg: 4 features_for_read: As you see ashift is 9 (512b). I know a common solution with gnop and export-mport pool, but how should I manage mirror this way? Should I create a mirror on gnop-ed devices and then export-import? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: A few problems
2013/3/18 YongHyeon PYUN pyu...@gmail.com: On Sat, Mar 16, 2013 at 01:08:06PM +0400, Michael BlackHeart wrote: Hello there. I've got a couple of things I don't get or can't handle. [...] re0@pci0:4:0:0: class=0x02 card=0x512c1462 chip=0x816810ec rev=0x02 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network subclass = ethernet bar [10] = type I/O Port, range 32, base 0xd800, size 256, enabled bar [18] = type Memory, range 64, base 0xfeaff000, size 4096, enabled bar [20] = type Prefetchable Memory, range 64, base 0xf8ff, size 65536, enabled cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit cap 10[70] = PCI-Express 1 endpoint IRQ 1 max data 128(256) link x1(x1) speed 2.5(2.5) cap 11[b0] = MSI-X supports 2 messages in map 0x20 enabled cap 03[d0] = VPD ecap 0001[100] = AER 1 0 fatal 0 non-fatal 2 corrected ecap 0002[140] = VC 1 max VC0 ecap 0003[160] = Serial 1 0100684ce000 re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 description: ToISP options=8218bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWCSUM,TSO4,WOL_MAGIC,LINKSTATE ether 00:21:85:1c:24:fa media: Ethernet autoselect (100baseTX full-duplex) status: active [...] One is that re0 doesn't neogatiate direct link with a connected PC (using non-crossover UTP), but sk0 does that easy. It seems to me that according to RTL8111 chip specification there shouldn't be any problem, probably it's a driver problem? What is your link parter for re0? I don't remember whether the PHY hardware really supports automatic MDI crossover detection. Even if the PHY hardware does not support it, the link partner would be able to do that. And could you show me the output of dmesg(re(4) and rgephy(4) only) and devinfo -rv | grep rgephy? Here's info: re0: RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet port 0xd800-0xd8ff mem 0xfeaff000-0xfeaf,0xf8ff-0xf8ff irq 17 at device 0.0 on pci4 re0: Using 1 MSI-X message re0: Chip rev. 0x3c00 re0: MAC rev. 0x0040 miibus0: MII bus on re0 rgephy0: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 00:21:85:1c:24:fa devinfo -rv | grep rgephy rgephy0 pnpinfo oui=0xe04c model=0x11 rev=0x2 at phyno=1 This link connected to Realtek 8111E under Win7. I'll repeat that when it's connected to sk0, everything works. Of course when I'm switching links, I change IPs and other configuration in rc.conf and reboots system. For example I'll provide info for sk0 (Dlink DGE-530T): skc0: D-Link DGE-530T Gigabit Ethernet port 0xe800-0xe8ff mem 0xfebec000-0xfebe irq 17 at device 1.0 on pci5 skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:19:5b:86:3b:53 miibus1: MII bus on sk0 e1000phy0: Marvell 88E1011 Gigabit PHY PHY 0 on miibus1 e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto e1000phy0 pnpinfo oui=0xac2 model=0x2 rev=0x5 at phyno=0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: A few problems
2013/3/18 Chuck Swiger cswi...@mac.com: Hi-- On Mar 18, 2013, at 11:16 AM, Jeremy Chadwick wrote: You've got an Intel P45 northbridge controller which supports dual-channel mode, but that only works for DIMMs of the same size. You might be able to get 6GB if you place the DIMMs in slots 1 and 2 instead of 1 3 or 2 4. Otherwise, try getting another 4GB DIMM and using 4GB + 4GB instead. Off-list: Except that Michael said, re: his dmidecode output: As you see it says that in DIMM4 there's 4Gb module, but it's 2Gb actualy. It's a Kit of 2x2Gb. BIOS says that there's only 4Gb but FreeBSD see 6Gb. I'll try later to switch modules into DIMM1 DIMM3 but I'm not expecting any difference. So let's recap: - DIMMs are operating in single-channel mode (vs. dual-channel) Are they? (I didn't see info one way or the other, but perhaps off-list communication confirmed that.) - DIMM2 claims to be 2GB - DIMM4 claims to be 4GB - Intel P45 supports up to 16GB RAM (4GB maximum per DIMM) - OS is amd64 If he did have 4GB+2GB installed, since he's using amd64, ideally he would be seeing FreeBSD report avail memory = (around 6GB), which isn't the case. So something isn't making sense here. Right. If one DIMM really is 4GB, then putting them into slots 1 2 should make a difference; or just install only one at a time to double-check. Possibly the SMBIOS/DMI data claims to have a 4GB DIMM, yet in actuality chip-wise only has 2GB on it. In which case, the SMBIOS/DMI data is wrong, or the DIMM manufacturer is shady. I would not be surprised if the user had two DIMMs bought at different times (even if they're the same model), or that one is just manufactured wrong/badly. Maybe. If you put different sized DIMMs into slots paired up for dual-channel mode, IIRC that era of Intel chipsets would work in dual-channel mode using the smaller memory size. That resembles the current situation rather closely-- ie, 6GB installed but only 4GB available. But I suppose it could be a DIMM which claims to be the wrong size in DMI info Regards, -- -Chuck I checked out. It's a kit of 2x2Gb as I said before. And I moved them to 1 and 3 slots and nothing changed. currently do not have any DDR2 modules to make some more tests. Here's proof: http://www.miekoff.ru/wp-content/uploads/P1020858.jpg And for the record, I used this memory on two other motherboards, one was running WinXP and another FreeBSD 8.3 and later 9.1. And all of them reported about 4Gb installed. Just like BIOS does. So it seems to me like some weird thing. On the one side it could be a FreeBSD's DMI mis-interpretating. On the other side as far as I know Corssair do not produce something, but just tunes and overclocks memory chips. And because of the radiators I can't visually compare chips one of them easily could be a 4Gb module locked to 2Gb or something like that. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
A few problems
Hello there. I've got a couple of things I don't get or can't handle. I'm running: FreeBSD diablo.miekoff.local 9.1-STABLE FreeBSD 9.1-STABLE #0 r248347: Sat Mar 16 03:20:58 MSK 2013 root@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 amd64 1st of all, on dmesg there's something strange. It says: real memory = 6442450944 (6144 MB) avail memory = 4092743680 (3903 MB) So real memory is about 6Gb, but localy installed only 4Gb. I tried to disable swap and reboot but it's still the same output. And here goes dmidecode: SMBIOS 2.5 present. 72 structures occupying 2730 bytes. Table at 0x000FB710. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: V3.4 Release Date: 03/09/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 4096 kB Characteristics: ISA is supported PCI is supported PNP is supported APM is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25/1.2 MB floppy services are supported (int 13h) 3.5/720 kB floppy services are supported (int 13h) 3.5/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported LS-120 boot is supported ATAPI Zip drive boot is supported BIOS boot specification is supported Targeted content distribution is supported BIOS Revision: 8.15 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: MICRO-STAR INTERNATIONAL CO.,LTD Product Name: MS-7512 Version: 1.0 Serial Number: To Be Filled By O.E.M. UUID: ----0021851C24FA Wake-up Type: Power Switch SKU Number: To Be Filled By O.E.M. Family: To Be Filled By O.E.M. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: MICRO-STAR INTERNATIONAL CO.,LTD Product Name: P45 Neo2-FR (MS-7512) Version: 1.0 Serial Number: To be filled by O.E.M. Asset Tag: To Be Filled By O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To Be Filled By O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0003, DMI type 3, 21 bytes Chassis Information Manufacturer: MICRO-STAR INTERNATIONAL CO.,LTD Type: Desktop Lock: Not Present Version: 1.0 Serial Number: To Be Filled By O.E.M. Asset Tag: To Be Filled By O.E.M. Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 Handle 0x0004, DMI type 4, 40 bytes Processor Information Socket Designation: CPU 1 Type: Central Processor Family: Core 2 Duo Manufacturer: Intel ID: 7A 06 01 00 FF FB EB BF Signature: Type 0, Family 6, Model 23, Stepping 10 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) DS (Debug store) ACPI (ACPI supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) SS (Self-snoop) HTT (Multi-threading) TM
Old ICH7 SATA-2 question
Hello there, I've got a question about SATA. I've got ASUS P5GC-MX/1333 with ICH7. (SATA2 support) A few HDD with SATA2. system: uname -a FreeBSD diablo.miekoff.local 9.1-STABLE FreeBSD 9.1-STABLE #1 r24: Tue Feb 12 00:19:07 MSK 2013 root@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 amd64 camcontrol info camcontrol iden ada2 pass2: ST3500320AS SD1A ATA-8 SATA 2.x device pass2: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes) protocol ATA/ATAPI-8 SATA 2.x device model ST3500320AS firmware revision SD1A serial number 5QM3LB0N WWN 5000c50011db1e03 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 268435455 sectors LBA48 supported 976773168 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM 7200 Feature Support Enabled Value Vendor read ahead yes yes write cacheyes yes flush cacheyes yes overlapno Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no automatic acoustic management no no media status notification no no power-up in Standbyno no write-read-verify yes yes 2/0x2 unload no no free-fall no no data set management (TRIM) no smartmontools info smartctl -a /dev/ada2 | more smartctl 6.0 2012-10-10 r3643 [FreeBSD 9.1-STABLE amd64] (local build) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.11 Device Model: ST3500320AS Serial Number:5QM3LB0N LU WWN Device Id: 5 000c50 011db1e03 Firmware Version: SD1A User Capacity:500 107 862 016 bytes [500 GB] Sector Size: 512 bytes logical/physical Rotation Rate:7200 rpm Device is:In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is:Sun Feb 24 00:29:47 2013 MSK SMART support is: Available - device has SMART capability. SMART support is: Enabled At this point all seems SATA2 capatible. But at loading: atapci0: Intel ICH7 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: ATA channel at channel 0 on atapci0 atapci1: Intel ICH7 SATA300 controller port 0xb800-0xb807,0xb400-0xb403,0xb000-0xb007,0xa800-0xa803,0xa400-0xa40f irq 23 at device 31.2 on pci0 ata2: ATA channel at channel 0 on atapci1 ata3: ATA channel at channel 1 on atapci1 Looks like it's also SATA2 (SATA300) But HDD says this: ada2 at ata2 bus 0 scbus1 target 0 lun 0 ada2: ST3500320AS SD1A ATA-8 SATA 2.x device ada2: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes) ada2: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C) ada2: Previously was known as ad2 At this point I've a quiestion - what's the real operation speed and why's that. And for the record - I can't switch ICH 7 to ahci due to bios limitations. And one more, I've got netbook with ICH7 (NM-10 mb). It uses achi driver, and HDD says it's ahci0: Intel ICH7 ACHI SATA controller ... ahic0: AHCI v1.10 with 4 3Gbs ports ... ... ada0: vendor blah-blah-blah ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled As far as I remember without AHCI there's no NCQ support. But why with SATA300 controller on P5GC-MX/1333 I've got only 150 transfers? Is it's a limitations of this driver for old chip? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Old ICH7 SATA-2 question
2013/2/24 Jeremy Chadwick j...@koitsu.org: On Sun, Feb 24, 2013 at 12:46:43AM +0400, Michael BlackHeart wrote: Hello there, I've got a question about SATA. I've got ASUS P5GC-MX/1333 with ICH7. (SATA2 support) A few HDD with SATA2. system: uname -a FreeBSD diablo.miekoff.local 9.1-STABLE FreeBSD 9.1-STABLE #1 r24: Tue Feb 12 00:19:07 MSK 2013 root@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 amd64 camcontrol info camcontrol iden ada2 pass2: ST3500320AS SD1A ATA-8 SATA 2.x device pass2: 150.000MB/s transfers (SATA, UDMA5, PIO 8192bytes) protocol ATA/ATAPI-8 SATA 2.x device model ST3500320AS firmware revision SD1A serial number 5QM3LB0N WWN 5000c50011db1e03 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 268435455 sectors LBA48 supported 976773168 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM 7200 Feature Support Enabled Value Vendor read ahead yes yes write cacheyes yes flush cacheyes yes overlapno Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no automatic acoustic management no no media status notification no no power-up in Standbyno no write-read-verify yes yes 2/0x2 unload no no free-fall no no data set management (TRIM) no The protocol line in camcontrol identify output indicates the maximum capability the device can support, not what the current negotiated PHY speed is. Let me clarify by being more technical: camcontrol identify issues the ATA IDENTIFY (0xec) command to the underlying disk; all the output you get back is information that the disk itself returns (not the controller). For example, SATA signalling speed capability is returned in word 76 of the output (ref T13/2015-D rev 3 WD spec). smartctl -a /dev/ada2 | more smartctl 6.0 2012-10-10 r3643 [FreeBSD 9.1-STABLE amd64] (local build) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.11 Device Model: ST3500320AS Serial Number:5QM3LB0N LU WWN Device Id: 5 000c50 011db1e03 Firmware Version: SD1A User Capacity:500 107 862 016 bytes [500 GB] Sector Size: 512 bytes logical/physical Rotation Rate:7200 rpm Device is:In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is:Sun Feb 24 00:29:47 2013 MSK SMART support is: Available - device has SMART capability. SMART support is: Enabled The SATA Version is line in smartmontools 6.0 can indicate both operational PHY speed **as well** as disk capability. For example, a drive which has SATA600 capability but has negotiated SATA300 speed will show something like this: SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Lines lacking (current: xxx) notation indicate either lack of a way to determine current PHY speed with the OS, or, the maximum capability matches the negotiated speed. In other words, there's no point to saying something like SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s); the author feels its redundant. However, I have seen this reporting mechanism in smartmontools work incorrectly in some cases. In those cases, from what I've seen, the SATA Version line indicates **only** what the maximum capability is of the device. At this point all seems SATA2 capatible. But at loading: atapci0: Intel ICH7 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: ATA channel at channel 0 on atapci0 atapci1: Intel ICH7 SATA300 controller port 0xb800-0xb807,0xb400-0xb403,0xb000-0xb007,0xa800-0xa803,0xa400-0xa40f irq 23 at device 31.2 on pci0 ata2: ATA channel at channel 0 on atapci1 ata3: ATA channel at channel 1 on atapci1 Looks like it's also SATA2 (SATA300) Your ICH7 controller is SATA300 capable. However, what you have not provided is output from pciconf -lvbc. The exact revision of controller matters greatly here. Wikipedia sums this up -- read the first paragraph fully: http://en.wikipedia.org/wiki/I/O_Controller_Hub#ICH7 But HDD says this: ada2 at ata2 bus 0 scbus1 target 0 lun 0 ada2: ST3500320AS SD1A ATA-8 SATA 2.x device ada2: 150.000MB/s transfers (SATA, UDMA5, PIO
ath patch from the head
Hello there, May be I've missed something or just can't find in the web, but As I see in HEAD there're some movement around ath driver and it seems to me that there's driver for AR93xx, especially AR938x, chip 0030. Is there any patches to stable to check this driver out, 'cause I just can't compile in this driver from the HEAD on 9.stable? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
AHCI powersaving issue
Hello, I've a trouble with new achi driver on currently 9 release, but it was the same on 8-stable. I've have an: smartctl -a /dev/ada0 === START OF INFORMATION SECTION === Model Family: Western Digital Scorpio Blue Serial ATA Device Model: WDC WD3200BEVT-22A23T0 Serial Number:WD-WXL1AB086780 And there's an idle state disabled by wdidle3 v1.05. But it constantly goes to power saving mode. I can see it 'cos I'm hearing a sound of spinning up HDD and SMART param 193 Load_Cycle_Count rises VERY frequently, something insane about one per few minutes. This thing solves the problem: camcontrol cmd ada0 -a EF 85 00 00 00 00 00 00 00 00 00 00 and everything goes fine from that moment. Output with disabled APM. camcontrol identify ada0 pass0: WDC WD3200BEVT-22A23T0 01.01A01 ATA-8 SATA 2.x device pass0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) protocol ATA/ATAPI-8 SATA 2.x device model WDC WD3200BEVT-22A23T0 firmware revision 01.01A01 serial number WD-WXL1AB086780 WWN 50014ee6565acc41 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 268435455 sectors LBA48 supported 625142448 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM 5400 Feature Support Enabled Value Vendor read ahead yes yes write cacheyes yes flush cacheyes yes overlapno Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes no 254/0xFE automatic acoustic management yes no 254/0xFE128/0x80 media status notification no no power-up in Standbyno no write-read-verify no no unload yes yes free-fall no no data set management (TRIM) no And finally i've got in /boot/loader.conf: hint.ahcich.0.pm_level=0 I'd like to know how to permanently disable this APM mode because it's killing my HDD. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
global make -s
Hello, I'd like to know is there any good way to implement make -s behaivor as a default, 'cos in man make.conf examplet/etc/make.conf there's no anything about it. In most cases I just don't want to see echo output of make. I've added an alias to .cshrc like this^ alias make make -s \!:1 but I don't know could be there any negativity. Any advices? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: root mount error
You were right about SATA mode, I should miss something when I try switch it first time or may be there're some other reasons, like previously I tried i386. Anyway there's HDD. But it's all doesn't find HDD with SATA native disabled, but I'd like to have this working old way for some reasons. I've not tried to enble labeling, but i think that it wouldn't work because with disabled native mode there's no any entry about HDD like with native mode enabled. And when I get promted to enter new boot point and pressing '?' there's only acd drive with enabled native mode, but with enabled native mode there's acd, hdd and also automaticaly created labels. I'm still thinking that the some of the drivers or one of them is broken or maybe some modules are no longer included. Now I've got two kernels, is there a way to find out where's the problem, 'cos I think I can just put old driver source code and recompile kernel to get things working back in old way? And as you ask me - dmesg logs. With SATA native enabled there's a slightly different controller strings and I think there's the problem Working good at all points - 8.1 RELEASE kernel, dunno REVISION Default configuration working with SATA native disabled: Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:36:49 UTC 2010 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) Dual CPU T2410 @ 2.00GHz (1995.02-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6fd Family = 6 Model = f Stepping = 13 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe39dSSE3,DTES64,MON,DS_CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 2147483648 (2048 MB) avail memory = 2047451136 (1952 MB) ACPI APIC Table: HP 30D8 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: HPQOEM SLIC-MPC on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 7f70 (3) failed Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_ec0: Embedded Controller: GPE 0x16 port 0x62,0x66 on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 vgapci0: VGA-compatible display port 0x4000-0x4007 mem 0xe440-0xe44f,0xd000-0xdfff irq 16 at device 2.0 on pci0 agp0: Intel GME965 SVGA controller on vgapci0 agp0: detected 7676k stolen memory agp0: aperture size is 256M vgapci1: VGA-compatible display mem 0xe450-0xe45f at device 2.1 on pci0 em0: Intel(R) PRO/1000 Network Connection 7.0.5 port 0x4020-0x403f mem 0xe460-0xe461,0xe462-0xe4620fff irq 22 at device 25.0 on pci0 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:1f:29:9c:7a:12 uhci0: Intel 82801H (ICH8) USB controller USB-D port 0x4040-0x405f irq 16 at device 26.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x2f00 usbus0: Intel 82801H (ICH8) USB controller USB-D on uhci0 ehci0: Intel 82801H (ICH8) USB 2.0 controller USB2-B mem 0xe4621000-0xe46213ff irq 18 at device 26.7 on pci0 ehci0: [ITHREAD] usbus1: EHCI version 1.0 usbus1: Intel 82801H (ICH8) USB 2.0 controller USB2-B on ehci0 pci0: multimedia, HDA at device 27.0 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci8: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 17 at device 28.1 on pci0 pci16: ACPI PCI bus on pcib2 siba_bwn0: Broadcom BCM4312 802.11a/b/g Wireless mem 0xe400-0xe4003fff irq 17 at device 0.0 on pci16 siba_bwn0: unsupported coreid (USB 1.1 Host) bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4311 rev 13) PHY (analog 4 type 2 rev 9) RADIO (manuf 0x17f ver 0x2050 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] pcib3: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci40: ACPI PCI bus on pcib3 uhci1: Intel 82801H (ICH8) USB controller USB-A port 0x4060-0x407f irq 20 at device 29.0 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x2f00 usbus2: Intel 82801H (ICH8) USB
Re: root mount error
I'm no looking for help neither instructions how to build kernel. I'm just installing 8.1 RELEASE and svn it up to last week 8-stable. And going step-by-step of handbook installing kernel I'm having a trouble - it seems than new kenel doesn't recognize my HDD. I'm not doing something special, in that case I'm for shure mentioned it. I'm just building GENERIC kernel without any configuration of system after installation, to tweaks, no tunes, nothing. It's a new GENERIC kernel and it can't find my HDD but 8.1 i386/amd64 releases works well and as I remember something about month ago stable too. Now, a likely cause of your problem is the installation of a custom kernel with removed support for whatever your hard disk drive or raid controller is recognized as. When it works it's just and ad0 hdd, no raid or special driver I'm jsut trying to say than recent changes in kernel or kernel-modules broke up my HDD support and I'd like to notice developres to check where the problem is. And of couse I've tried to switch SATA native mode and it doesn't change anything. Loader on it's own stage easily detects HDD and root partition so I can just select old kernel and boot up, but I'm not shure how he gain access to HDD to mfke any conclusion, probably through BIOS interrupts but it's out of piont. And for my pity I don't know how to dump demsg without having any serial connection or usable disk drive, maybe to flash drive, but I don't know how. And anyway there's no real kernel painc, it just asks for root mountpoint. And for shure I've got an 2.5 Hitachi HTS542516K9A300 160Gb SATA HDD If you need any aditional info I'll give it all, just ask. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
root mount error
Hello I've got trouble with FreeBSD 8 Stable First I've put on notebook 8.2 RELEASE amd64, then SVN'ed src's to yesterday revision I don't remember exact number, but I've have this problem aobut week or two so it's not so important, also as it doesn't work on i386 too. After installing new kernel I've just build - indeed it always was GENERIC for both arch's on clean system - I've got an a kernel painc caused by disability to mount root partition because kernel couldn't see the drive. By pressing '?' I've sen only acd0 that represents CD-ROM. In debug messages I haven't found anything about ad0 - than hdd was identified before new kernel was installed. I've got an HP 6720s notebook with SATA 160GB Hitachi HDD that is working with diabled SATA native mode. I've not found any info 'bout this error in recent 8.Stable so I don't know how to handle this one. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD 8.1 Stable Unreasanoble Rebooting
Today I've got a pretty strange event. It looks like a reboot but unreasonable as far as I see. Before server's uptime was over month, it's sometimes have to reboot for kernel updates or somethings like that. I've digen all logs and didn't find a reason, so here they all. auth.log Sep 16 13:59:58 diablo sshd[2284]: Received signal 15; terminating. Sep 16 14:04:26 diablo sshd[2290]: Server listening on 0.0.0.0 port 22442. cron - nothing debug.log - nothing dmesg - nothing messages Sep 16 13:44:55 diablo transmission-daemon[7965]: Couldn't create socket: Protocol not supported (fdlimit.c:651) Sep 16 13:45:31 diablo last message repeated 5 times Sep 16 13:47:23 diablo last message repeated 13 times Sep 16 13:57:40 diablo last message repeated 51 times Sep 16 13:59:48 diablo last message repeated 12 times Sep 16 14:00:18 diablo named[1575]: stopping command channel on 127.0.0.1#953 Sep 16 14:00:18 diablo named[1575]: exiting Sep 16 14:00:18 diablo syslogd: exiting on signal 15 Sep 16 14:02:31 diablo syslogd: kernel boot file is /boot/kernel/kernel Sep 16 14:02:31 diablo kernel: Copyright (c) 1992-2010 The FreeBSD Project. Sep 16 14:02:31 diablo kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Sep 16 14:02:31 diablo kernel: The Regents of the University of California. All rights reserved. Sep 16 14:02:31 diablo kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Sep 16 14:02:31 diablo kernel: FreeBSD 8.1-STABLE #1 r210501M: Sat Sep 4 11:08:44 MSD 2010 Sep 16 14:02:31 diablo kernel: amd_m...@diablo.miekoff.local:/usr/obj/usr/src/sys/DIABLO64 amd64 Sep 16 14:02:31 diablo kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Sep 16 14:02:31 diablo kernel: CPU: Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2799.98-MHz K8-class CPU) Sep 16 14:02:31 diablo kernel: Origin = GenuineIntel Id = 0x1067a Family = 6 Model = 17 Stepping = 10 Sep 16 14:02:31 diablo kernel: Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Sep 16 14:02:31 diablo kernel: Features2=0x408e39dSSE3,DTES64,MON,DS_CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE Sep 16 14:02:31 diablo kernel: AMD Features=0x20100800SYSCALL,NX,LM Sep 16 14:02:31 diablo kernel: AMD Features2=0x1LAHF Sep 16 14:02:31 diablo kernel: TSC: P-state invariant Sep 16 14:02:31 diablo kernel: real memory = 2147483648 (2048 MB) Sep 16 14:02:31 diablo kernel: avail memory = 2051534848 (1956 MB) Sep 16 14:02:31 diablo kernel: ACPI APIC Table: A_M_I_ OEMAPIC Sep 16 14:02:31 diablo kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Sep 16 14:02:31 diablo kernel: FreeBSD/SMP: 1 package(s) x 2 core(s) Sep 16 14:02:31 diablo kernel: cpu0 (BSP): APIC ID: 0 Sep 16 14:02:31 diablo kernel: cpu1 (AP): APIC ID: 1 Sep 16 14:02:31 diablo kernel: ioapic0 Version 2.0 irqs 0-23 on motherboard Sep 16 14:02:31 diablo kernel: wlan: mac acl policy registered Sep 16 14:02:31 diablo kernel: kbd1 at kbdmux0 Sep 16 14:02:31 diablo kernel: ichwd module loaded Sep 16 14:02:31 diablo kernel: cryptosoft0: software crypto on motherboard Sep 16 14:02:31 diablo kernel: acpi0: A_M_I_ OEMXSDT on motherboard Sep 16 14:02:31 diablo kernel: acpi0: [ITHREAD] Sep 16 14:02:31 diablo kernel: acpi0: Power Button (fixed) Sep 16 14:02:31 diablo kernel: acpi0: reservation of 0, a (3) failed Sep 16 14:02:31 diablo kernel: acpi0: reservation of 10, 7f70 (3) failed Sep 16 14:02:31 diablo kernel: Timecounter ACPI-fast frequency 3579545 Hz quality 1000 Sep 16 14:02:31 diablo kernel: acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 Sep 16 14:02:31 diablo kernel: cpu0: ACPI CPU on acpi0 Sep 16 14:02:31 diablo kernel: ACPI Warning: Incorrect checksum in table [OEMB] - 0x3A, should be 0x2D (20100331/tbutils-354) Sep 16 14:02:31 diablo kernel: cpu1: ACPI CPU on acpi0 Sep 16 14:02:31 diablo kernel: acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Sep 16 14:02:31 diablo kernel: Timecounter HPET frequency 14318180 Hz quality 900 Sep 16 14:02:31 diablo kernel: pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 Sep 16 14:02:31 diablo kernel: pci0: ACPI PCI bus on pcib0 Sep 16 14:02:31 diablo kernel: vgapci0: VGA-compatible display port 0x8800-0x8807 mem 0xdfd0-0xdfd7,0xe000-0xefff,0xdfd8-0xdfdb irq 16 at device 2.0 on pci0 Sep 16 14:02:31 diablo kernel: agp0: Intel 82945G (945G GMCH) SVGA controller on vgapci0 Sep 16 14:02:31 diablo kernel: agp0: detected 7932k stolen memory Sep 16 14:02:31 diablo kernel: agp0: aperture size is 256M Sep 16 14:02:31 diablo kernel: pcib1: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 Sep 16 14:02:31 diablo kernel: pci3: ACPI PCI bus on pcib1 Sep 16 14:02:31 diablo kernel: pcib2: ACPI PCI-PCI bridge irq 17 at device 28.1 on pci0 Sep 16 14:02:31 diablo kernel: pci2: ACPI PCI bus on pcib2 Sep 16 14:02:31 diablo kernel: ae0: Attansic Technology Corp, L2 FastEthernet mem
Re: FreeBSD 8.1 Stable Unreasanoble Rebooting
2010/9/16 Jeremy Chadwick free...@jdc.parodius.com:
On Thu, Sep 16, 2010 at 08:37:29PM +0400, Michael BlackHeart wrote:
Today I've got a pretty strange event. It looks like a reboot but
unreasonable as far as I see. Before server's uptime was over month,
it's sometimes have to reboot for kernel updates or somethings like
that. I've digen all logs and didn't find a reason, so here they all.
auth.log
Sep 16 13:59:58 diablo sshd[2284]: Received signal 15; terminating.
Sep 16 14:04:26 diablo sshd[2290]: Server listening on 0.0.0.0 port 22442.
cron - nothing
debug.log - nothing
dmesg - nothing
messages
Sep 16 13:44:55 diablo transmission-daemon[7965]: Couldn't create
socket: Protocol not supported (fdlimit.c:651)
Sep 16 13:45:31 diablo last message repeated 5 times
Sep 16 13:47:23 diablo last message repeated 13 times
Sep 16 13:57:40 diablo last message repeated 51 times
Sep 16 13:59:48 diablo last message repeated 12 times
Sep 16 14:00:18 diablo named[1575]: stopping command channel on 127.0.0.1#953
Sep 16 14:00:18 diablo named[1575]: exiting
Sep 16 14:00:18 diablo syslogd: exiting on signal 15
Sep 16 14:02:31 diablo syslogd: kernel boot file is /boot/kernel/kernel
Sep 16 14:02:31 diablo kernel: Copyright (c) 1992-2010 The FreeBSD Project.
{...}
This sure looks like a legitimate reboot to me (e.g. shutdown -r now);
note how your system daemons (named, syslogd) are being shut down with
SIGTERM. You can check with last (shutdown/reboot vs. crash).
paranoid
I would highly recommend taking this machine offline and reinstalling
the OS, in addition to newfs'ing all existing filesystems (restore from
last known good backup). buildworld/installworld and
buildkernel/installkernel may not be enough depending on what the
individual did. It's likely the machine could be compromised in some
way, especially if there's any service on it which is public-facing,
regardless of authentication mechanisms you've deployed in front of it.
/paranoid
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
That looks reasonable
last says:
reboot ~ th 16 sen 14:04
reboot ~ th 16 sen 14:03
shutdown ~ th 16 sen 13:59
and it's pretty good syncs with logs but there's no anybody access to
physical console 'cos it's not even plugged in. That's for the first.
Next, I've got, I believe, pretty strong passwords, and also root
can't log in directly, but wheel user also is in operators so he also
can reboot or shutdown, but there's no any attempts or successful
logins. All potentialy dangerous services run under their own
unprerileged users, and so on. Crontabs also doesn't contain scripts,
I prefer periodic system, and there's no anyway anything that cause
reboot.
Thing that worries me it that there were multiple reboots and shutdown
that goes up by itself without anyone pressing a button. And in
messages log there's fsck segment that indicates to unnormal shutdown
or reboot. It looks like it started to shutting down but was in some
case interrupted and after powering up it few times reboots itself.
But commonly FreeBSD doesn't reboot by it's own will.
The same hardware worked over a half a year under 8.0 stables without
such a problem. I just would like to understand from where this
problem comes up.
This machine doesn't contain any critical info so I'll wait for a bit.
Also I'd like to notice that recently I've tuned hdd's spindown exept
system hdd by atacontrol port, powerd and CPU frequency lowering in
idle, maybe something of this could cause this problem? And where
could I check this out?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Broadcom Wireless BCM4312 Rev.02 (BCM4310 UART) troubles
Hello I've got a problem with Broadcomm Wireless. I have notebook HP Compaq 6720s with BCM4312. I disassemblied book and saw there plugable Wireless Module but I'm lazy to do it again to werify it's ID. Windows XP drivers works fine and says that is's PCI\VEN_14E4DEV_4312SUBSYS_1371103CREV_02\429E2C51B000E1 MEMORY E400 - E4003FFF IRQ 17 I've tried : FreeBSD 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:36:49 UTC 2010 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 And noting as i386 8.1 release. Now I'm running: FreeBSD 8.1-STABLE FreeBSD 8.1-STABLE #0 r211991: Mon Aug 30 14:58:34 MSD 2010 root@:/usr/obj/usr/src/sys/GENERIC amd64 With no driver attached pciconf -l -cvb says: no...@pci0:16:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4310 UART (Wireless Ethernet Adapter)' class = network bar [10] = type Memory, range 64, base 0xe400, size 16384, enabled cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 09[58] = vendor (length 120) cap 05[e8] = MSI supports 1 message, 64 bit cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) Clean install, trying bwi driver first cd /usr/ports/net/bwi-firmware-kmod make install clean rehash kldload bwi_ucode_v3 cd /usr/sys/src/modules/bwi make all obj depend install clean kldload if_bwi Aug 18 12:19:58 kernel: bwi0: Broadcom BCM4312 802.11a/b/g Wireless Lan mem 0xe400-0xe4003fff irq 17 at device 0.0 on pci16 Aug 18 12:19:58 kernel: bwi0: [ITHREAD] Aug 18 12:19:58 kernel: bwi0: BBP: id 0x4311, rev 0x2, pkg 0 Aug 18 12:19:58 kernel: bwi0: MAC rev 13 is not supported Aug 18 12:19:58 kernel: bwi0: no MAC was found Aug 18 12:19:58 kernel: device_attach: bwi0 attach returned 6 pciconf -l -cvb says: b...@pci0:16:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4310 UART (Wireless Ethernet Adapter)' class = network cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 09[58] = vendor (length 120) cap 05[e8] = MSI supports 1 message, 64 bit cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) now rebooting 'cos even after kldunloading if_bwi module it's still lists in pciconfand trying bwn cd /usr/ports/net/bwn-firmware-kmod make install clean rehash kldload bwn_v4_ucode.ko kldload if_bwn pciconf -l -cvb says: siba_bwn0: Broadcom BCM4312 802.11a/b/g Wireless mem 0xe400-0xe4003fff irq 17 at device 0.0 on pci16 siba_bwn0: unsupported coreid (USB 1.1 Host) bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4311 rev 13) PHY (analog 4 type 2 rev 9) RADIO (manuf 0x17f ver 0x2050 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] siba_b...@pci0:16:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4310 UART (Wireless Ethernet Adapter)' class = network bar [10] = type Memory, range 64, base 0xe400, size 16384, enabled cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 09[58] = vendor (length 120) cap 05[e8] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) ifconfig bwn0 up scan bwn0: firmware version (rev 410 patch 2160 date 0x751a time 0x7c0a) ifconfig: unable to get scan results bwn0: status of RF switch is changed to OFF book have a switch to turn on/off all radio and it's always on. also when i'm switching it FreeBSD says nothing Also I tried acpi_hp - no sense And i didn't find any apropriate in sysctl Moving next - ndis I've tried couple of drivers With WinXP that running on drivers v. VERSION: 7.10 REV: B from sp41680 And OS goes to kernel panic just when I kldloaded it. No dump, sorry, but I don't think that it matters a thing Another one - VERSION: 6.10 REV: A from sp34152 works a bit better It converts and loads without panic but in debug: kldload bcmwl564_sys.ko ndis0: Broadcom 802.11a/b/g WLAN mem 0xe400-0xe4003fff irq 17 at device 0. 0 on pci16 ndis0: [ITHREAD] ndis0: NDIS API version: 5.1 fpudna in kernel mode! pciconf -lcvb says: nd...@pci0:16:0:0: class=0x028000 card=0x1371103c chip=0x431214e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM4310 UART (Wireless Ethernet Adapter)' class = network bar [10] = type Memory, range 64, base 0xe400, size 16384, enabled cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 09[58] = vendor (length 120) cap 05[e8] = MSI supports 1 message, 64 bit cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) ifconfig says: ndis0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:21:00:43:56:0e media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier and everything doesn't work again. I think this as all info I can get, huh. I've got only two questions: 1)Is there a way to determine what exactly microcode uses Windows Driver (There's no info in devmgmgt.msc
Re: Broadcom Wireless BCM4312 Rev.02 (BCM4310 UART) troubles
Why don't you try to play with wlan(4) on top of bwi/bwn? An example is here: handbook / 31.3.3.1.1 How to Find Access Points. wlan appeared in 7.2 or 7.3 and 8.0 as I remember and I always thought that it's just a matter of security and easy maintaining and probably multi-wlan routing. In a real daily usage I use it as well, for example it works great on my server, but I guess it doesn't matter for a testing hardware, does it? Yes, even with ndis (which is what I use for this adapter, albeit on i386), you have to use wlan. (ndis on i386 will not have the 'fpudna' issues since 32-bit Windows drivers do not use SSE instructions.) Even with ndis I have to run ndis_events for WPA auth to work FWIW. I've tried i386 as well with ndis and it doesn't make a sense. Could you please tell me the driver version you use, it's SP number if it's official HP driver, or link to download the one you have to work with. And a link how to use ndis_events will be great, I've never try this one. Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.1R: ppp default route uses wrong Netif (with pppoe)
As I understand this isn't a bug but a mistype or misunderstand of config ( see man ppp.conf ) I'm running myself 8.0, 8.1 and currently 8.STABLE with pppoe in this way and never have a problem as many peolpe do. Look in listing my-provider: set line PPPoE:nfe0 Here's some set line and should be set device like this: pppoe_myisp: set device PPPoE:fxp0 I think that's the clue. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
