Re: SATA hotplug and AHCI
David Ehrmann wrote: How can I avoid all this and get the drive to be recognized automatically? Can I do this with devd? Did I do what I needed to correctly set up hotplugging? Can you enable verbose mode in /boot/loader.conf (echo 'boot_verbose="YES"' >> /boot/loader.conf)? And show your /var/run/dmesg.boot and kernel's output when you unplug and plug drive back? -- WBR, Andrey V. Elsukov ___ 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: amd(8) cores dump when load high
> On Sat, Dec 27, 2008 at 01:03:54PM +0200, Danny Braniss wrote: > > well, I'm running 7.1-PRERELEASE, what does the amd logs show? > .. > > Dec 27 10:37:01 sf-02 amd[856]: am-utils version 6.1.5 (build 1). > > Dec 27 10:37:01 sf-02 amd[856]: Report bugs to > > https://bugzilla.am-utils.org/ > > or am-ut...@am-utils.org. > > Dec 27 10:37:01 sf-02 amd[856]: Configured by da...@sunfire on date Sun Jun > > 29 16:59:06 IDT 2008. > > Dec 27 10:37:01 sf-02 amd[856]: Built by da...@sunfire on date Sun Jun 29 > > 17:02:07 IDT 2008. > > Dec 27 10:37:01 sf-02 amd[856]: cpu=x86_64 (little-endian), arch=amd64, > > karch=amd64. > > Dec 27 10:37:01 sf-02 amd[856]: full_os=freebsd7.0, os=freebsd7, osver=7.0, > > vendor=unknown, distro=none. > > How did you get this output from /usr/sbin/amd? > > It should be: > # amq -v > Copyright (c) 1997-2006 Erez Zadok > Copyright (c) 1990 Jan-Simon Pendry > Copyright (c) 1990 Imperial College of Science, Technology & Medicine > Copyright (c) 1990 The Regents of the University of California. > am-utils version 6.1.5 (build 800059). > Report bugs to https://bugzilla.am-utils.org/ or am-ut...@am-utils.org. > Configured by David O'Brien on date 4-December-2007 PST. > Built by r...@quynh.nuxi.org on date Fri Dec 19 15:29:18 PST 2008. > cpu=amd64 (little-endian), arch=amd64, karch=amd64. > full_os=freebsd8.0, os=freebsd8, osver=8.0, vendor=undermydesk, distro=The > FreeBSD Project. > > So many of your fields aren't what I expect: build#, configured by, > configured date, cpu, vendor, nor distro. > > -- > -- David(obr...@freebsd.org) as explained in a later message, I rolled my own :-) with the unofficial patches. danny ___ 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: amd(8) cores dump when load high
On Sat, Dec 27, 2008 at 01:03:54PM +0200, Danny Braniss wrote: > well, I'm running 7.1-PRERELEASE, what does the amd logs show? .. > Dec 27 10:37:01 sf-02 amd[856]: am-utils version 6.1.5 (build 1). > Dec 27 10:37:01 sf-02 amd[856]: Report bugs to https://bugzilla.am-utils.org/ > or am-ut...@am-utils.org. > Dec 27 10:37:01 sf-02 amd[856]: Configured by da...@sunfire on date Sun Jun > 29 16:59:06 IDT 2008. > Dec 27 10:37:01 sf-02 amd[856]: Built by da...@sunfire on date Sun Jun 29 > 17:02:07 IDT 2008. > Dec 27 10:37:01 sf-02 amd[856]: cpu=x86_64 (little-endian), arch=amd64, > karch=amd64. > Dec 27 10:37:01 sf-02 amd[856]: full_os=freebsd7.0, os=freebsd7, osver=7.0, > vendor=unknown, distro=none. How did you get this output from /usr/sbin/amd? It should be: # amq -v Copyright (c) 1997-2006 Erez Zadok Copyright (c) 1990 Jan-Simon Pendry Copyright (c) 1990 Imperial College of Science, Technology & Medicine Copyright (c) 1990 The Regents of the University of California. am-utils version 6.1.5 (build 800059). Report bugs to https://bugzilla.am-utils.org/ or am-ut...@am-utils.org. Configured by David O'Brien on date 4-December-2007 PST. Built by r...@quynh.nuxi.org on date Fri Dec 19 15:29:18 PST 2008. cpu=amd64 (little-endian), arch=amd64, karch=amd64. full_os=freebsd8.0, os=freebsd8, osver=8.0, vendor=undermydesk, distro=The FreeBSD Project. So many of your fields aren't what I expect: build#, configured by, configured date, cpu, vendor, nor distro. -- -- David(obr...@freebsd.org) ___ 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: Process stuck in STOP state
On Fri, 26 Dec 2008, Lin Jui-Nan Eric wrote: Hi, Full back-trace is located here: http://aqua.pixnet.tw/~jnlin/textdump/event3/1226/ Did you get anywhere with this? If not, and you are willing to recompile your kernel to include WITNESS, can you (in addition to the above output) get the output of "show alllocks" next time it happens? Gavin ___ 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: Process stuck in STOP state
Hi Gavin, I will compile my kernel with WITNESS and try again! On Mon, Dec 29, 2008 at 11:23 PM, Gavin Atkinson wrote: > On Fri, 26 Dec 2008, Lin Jui-Nan Eric wrote: > >> Hi, >> >> Full back-trace is located here: >> http://aqua.pixnet.tw/~jnlin/textdump/event3/1226/ > > Did you get anywhere with this? If not, and you are willing to recompile > your kernel to include WITNESS, can you (in addition to the above output) > get the output of "show alllocks" next time it happens? > > Gavin > ___ 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: can't disable hyperthreading on 7.1
On Wed, 24 Dec 2008 15:36:10 +0200 Alexander Melnik wrote: AM> Hi AM> I have several computers with 2 xeon processors with hyperthreading under FreeBSD 7.1-RC2 and in any case can not turn off hyperthreading: AM> [...@vmat ~]$ cat /boot/loader.conf AM> machdep.hyperthreading_allowed="0" AM> machdep.hlt_logical_cpus="1" AM> [...@vmat ~]$ sysctl machdep.hyperthreading_allowed AM> machdep.hyperthreading_allowed: 0 AM> [...@vmat ~]$ sysctl machdep.hlt_logical_cpus AM> machdep.hlt_logical_cpus: 1 AM> [...@vmat ~]$ sysctl hw.ncpu AM> hw.ncpu: 4 AM> If machdep.hyperthreading_allowed = "0", the hw.ncpu must be equal to 2? AM> [...@vmat ~]$ top -nd 1 AM> last pid: 825; load averages: 0.00, 0.00, 0.00 up 0+00:21:19 15:22:24 AM> 17 processes: 1 running, 16 sleeping AM> Mem: 6228K Active, 6984K Inact, 20M Wired, 9520K Buf, 960M Free AM> Swap: 2048M Total, 2048M Free AM> PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND AM> 762 root1 40 8428K 3936K sbwait 2 0:00 0.00% sshd AM> 767 old 1 80 4396K 2212K wait 2 0:00 0.00% bash AM> 765 old 1 440 8428K 3952K select 0 0:00 0.00% sshd AM> 571 root1 440 3184K 1200K select 1 0:00 0.00% syslogd AM> 706 root1 440 5876K 3196K select 0 0:00 0.00% sendmail AM> 716 root1 80 3212K 1276K nanslp 2 0:00 0.00% cron AM> 759 root1 50 3184K 1088K ttyin 2 0:00 0.00% getty AM> 758 root1 50 3184K 1088K ttyin 3 0:00 0.00% getty AM> 760 root1 50 3184K 1088K ttyin 0 0:00 0.00% getty AM> 700 root1 440 5752K 3276K select 0 0:00 0.00% sshd AM> 710 smmsp 1 200 5876K 3200K pause 2 0:00 0.00% sendmail AM> 297 root1 960 3128K 1208K select 0 0:00 0.00% dhclient AM> 737 root1 960 3240K 1152K select 3 0:00 0.00% inetd AM> 163 root1 200 1380K 804K pause 0 0:00 0.00% adjkerntz AM> 512 root1 440 1888K 564K select 0 0:00 0.00% devd AM> 313 _dhcp 1 440 3128K 1320K select 0 0:00 0.00% dhclient AM> 825 old 1 440 3496K 1656K CPU0 0 0:00 0.00% top AM> AM> If machdep.hlt_logical_cpus = "1" in the output top in any case should not be seen processors 2 and 3? You can run vmstat -i | grep cpu to see how many CPUs are actually used. I also observe on some hosts (6.3) with machdep.hlt_logical_cpus=1 that in C column of top output there appear CPU numbers for CPUs that are actually halted according to vmstat -i and I am curious too what this means. -- Mikolaj Golub ___ 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: amd(8) cores dump when load high
On Mon, Dec 29, 2008 at 12:48:34PM +0200, Danny Braniss wrote: > > On Sat, Dec 27, 2008 at 01:03:54PM +0200, Danny Braniss wrote: > > > well, I'm running 7.1-PRERELEASE, what does the amd logs show? > > .. > > > Dec 27 10:37:01 sf-02 amd[856]: am-utils version 6.1.5 (build 1). > > > Dec 27 10:37:01 sf-02 amd[856]: Report bugs to > > > https://bugzilla.am-utils.org/ > > > or am-ut...@am-utils.org. > > > Dec 27 10:37:01 sf-02 amd[856]: Configured by da...@sunfire on date Sun > > > Jun 29 16:59:06 IDT 2008. > > > Dec 27 10:37:01 sf-02 amd[856]: Built by da...@sunfire on date Sun Jun 29 > > > 17:02:07 IDT 2008. > > > Dec 27 10:37:01 sf-02 amd[856]: cpu=x86_64 (little-endian), arch=amd64, > > > karch=amd64. > > > Dec 27 10:37:01 sf-02 amd[856]: full_os=freebsd7.0, os=freebsd7, > > > osver=7.0, vendor=unknown, distro=none. > > > > How did you get this output from /usr/sbin/amd? .. > > as explained in a later message, I rolled my own :-) > with the unofficial patches. OK. I saw you later said that you had rolled your own, but I didn't think that your initial reporting of problems was also with that version. Thanks for the clarification. -- -- David (obr...@freebsd.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play "Jeopardy-style quoting" ___ 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: SATA hotplug and AHCI
Andrey V. Elsukov wrote: David Ehrmann wrote: How can I avoid all this and get the drive to be recognized automatically? Can I do this with devd? Did I do what I needed to correctly set up hotplugging? Can you enable verbose mode in /boot/loader.conf (echo 'boot_verbose="YES"' >> /boot/loader.conf)? And show your /var/run/dmesg.boot and kernel's output when you unplug and plug drive back? Here's the baseline output of dmesg and /var/run/dmesg.boot: http://pastebin.com/f5ab2ed28 dmesg.boot never changes. When I remove the drive, I see this from dmesg: ata4: DISCONNECT requested subdisk8: detached ad8: detached ata4: DISCONNECTED And when I plug it back in, ata4: CONNECT requested ata4: DISCONNECTED ata4: CONNECTED ata4: SATA connect time=0ms ata4: SIGNATURE: 000c ata4: No signature, asuming disk device ata4: ahci_reset devices=0x1 ata4: reiniting channel .. ata4: SATA connect time=0ms ata4: SIGNATURE: 000c ata4: No signature, asuming disk device ata4: ahci_reset devices=0x1 ata4: reinit done .. ata4: reiniting channel .. ata4: SATA connect time=0ms ata4: SIGNATURE: 000c ata4: No signature, asuming disk device ata4: ahci_reset devices=0x1 ata4: reinit done .. atacontrol list still says "no device present" for that channel. ___ 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: FreeBSD 7.1-RC2 Available...
Martin wrote: > Am Sun, 28 Dec 2008 10:33:25 -0500 > schrieb "SDH Admin" : > > > Try burning new cd media and/or try another cd-rom drive if possible, > > if the acpi/dma doesn't work. > > Hi, > > I've tried that already with RC1. I've burned it multiple times and > tried 3 drives. It seems someone removed CD emulation boot from the > livefs CD. It won't work with older PCs anymore. I'm using 8.0-CURRENT > now, but I wanted to give you people a notice. Sometimes a live CD is > useful and perhaps you won't be able to boot it anymore. > > I just realized that the CD is not booting on older PCs only, that's > why noone is really concerned about it here, perhaps thinking that I'm > not able to burn an ISO or something like that. But I can definitely > boot 8-CURRENT livefs without problems, so at least it's not a drive > problem. Nasty ! Even though some of us on lists might know to guess & avoid or ask about this, it seems an un-necessary pain as CDROM is only half full. I recall people got caught last time FreeBSD CDs didnt have both boot methods. Maybe whoever removed the code didnt know that ? Hopefully someone could put it back so FreeBSD doesn't look broken to some machines & people ? Cheers, Julian -- Julian Stacey: BSDUnixLinux C Prog Admin SysEng Consult Munich www.berklix.com Mail plain ASCII text. HTML & Base64 text are spam. www.asciiribbon.org ___ 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: Process stuck in STOP state
Dear All, We have recompiled our kernel with WITNESS and generated another textdump: http://aqua.pixnet.tw/~jnlin/textdump/event3/1230/ On Tue, Dec 30, 2008 at 12:00 AM, Lin Jui-Nan Eric wrote: > Hi Gavin, > > I will compile my kernel with WITNESS and try again! > > On Mon, Dec 29, 2008 at 11:23 PM, Gavin Atkinson wrote: >> On Fri, 26 Dec 2008, Lin Jui-Nan Eric wrote: >> >>> Hi, >>> >>> Full back-trace is located here: >>> http://aqua.pixnet.tw/~jnlin/textdump/event3/1226/ >> >> Did you get anywhere with this? If not, and you are willing to recompile >> your kernel to include WITNESS, can you (in addition to the above output) >> get the output of "show alllocks" next time it happens? >> >> Gavin >> > ___ 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"
rdump stuck in sbwait state (RELENG_7)
I upgraded a box (Dell Poweredge 1550, dual PIII processors) from a kernel + world of December 8th to one from today (December 29th) and I am experiencing a new problem with rdump. The symptom is that rdump stops sending data to the remote system. It is responsive to ^T and can be aborted with ^C. Here's the ^T status on the sending box (the aforementioned Dell RELENG_7 system): DUMP: dumping (Pass IV) [regular files] DUMP: 20.49% done, finished in 0:19 at Mon Dec 29 19:58:57 2008 DUMP: 38.00% done, finished in 0:16 at Mon Dec 29 20:00:52 2008 DUMP: 55.45% done, finished in 0:12 at Mon Dec 29 20:01:37 2008 load: 0.00 cmd: rdump 1493 [sbwait] 2.32u 11.25s 0% 34616k load: 0.00 cmd: rdump 1493 [sbwait] 2.32u 11.25s 0% 34616k load: 0.00 cmd: rdump 1495 [pause] 2.37u 11.25s 0% 34616k load: 0.00 cmd: rdump 1492 [running] 2.46u 4.89s 0% 34800k load: 0.00 cmd: rdump 1494 [pause] 2.30u 11.22s 0% 34616k load: 0.00 cmd: rdump 1492 [running] 2.46u 4.89s 0% 34800k load: 0.00 cmd: rdump 1492 [running] 2.46u 4.89s 0% 34800k load: 0.00 cmd: rdump 1495 [pause] 2.37u 11.25s 0% 34616k load: 0.00 cmd: rdump 1493 [sbwait] 2.32u 11.25s 0% 34616k load: 0.00 cmd: rdump 1495 [pause] 2.37u 11.25s 0% 34616k load: 0.00 cmd: rdump 1492 [sbwait] 2.46u 4.89s 0% 34800k load: 0.02 cmd: rdump 1492 [running] 2.46u 4.89s 0% 34800k load: 0.02 cmd: rdump 1492 [running] 2.46u 4.89s 0% 34800k load: 0.02 cmd: rdump 1495 [pause] 2.37u 11.25s 0% 34616k load: 0.02 cmd: rdump 1492 [running] 2.46u 4.89s 0% 34800k A tcpdump on both the sending and receiving systems shows no packets between them from the rdump processes. However, I can rshell both ways and get the expected output, so the link isn't down. ps shows the same thing as ^T. The sbwait process looks like this: 0 1492 1489 0 4 0 36024 34808 sbwait I+p00:07.35 rdump: /dev/amrd0s1f: pass 4: 69.66% done, finished in 0:08 at Mon Dec 29 20:01:53 2008 (rdump) and the status never changes. The remote (receiving) system is a HP DS10 running OpenVMS 8.3 with MultiNet 5.1A as the TCP stack. Despite this being a rather rare envir- onment, I haven't had any problems until this most recent kernel build. I have a large number (over a dozen) other systems running a variety of releases (6.4, 7.0, 7.1-PRERELEASE) which can do this same dump oper- ation without difficulty. I have the offending dump process still in this stuck state, so I can generate whatever sort of debugging information is needed. The box is a test box, so I can crash it and get a core dump if that's what is needed. Terry Kennedy http://www.tmk.com te...@tmk.com New York, NY USA ___ 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: SATA hotplug and AHCI
David Ehrmann wrote: http://pastebin.com/f5ab2ed28 dmesg.boot never changes. When I remove the drive, I see this from dmesg: ata4: DISCONNECT requested subdisk8: detached ad8: detached ata4: DISCONNECTED And when I plug it back in, ata4: CONNECT requested ata4: DISCONNECTED ata4: CONNECTED ata4: SATA connect time=0ms ata4: SIGNATURE: 000c ata4: No signature, asuming disk device ata4: ahci_reset devices=0x1 ata4: reiniting channel .. ata4: SATA connect time=0ms ata4: SIGNATURE: 000c ata4: No signature, asuming disk device ata4: ahci_reset devices=0x1 ata4: reinit done .. ata4: reiniting channel .. ata4: SATA connect time=0ms ata4: SIGNATURE: 000c ata4: No signature, asuming disk device ata4: ahci_reset devices=0x1 ata4: reinit done .. There were several similar reports. AHCI driver can't read correct device signature after hard reset and can't detect attached device. This issue was fixed with hack which you can see in this output: > ata4: SIGNATURE: 000c > ata4: No signature, asuming disk device > ata4: ahci_reset devices=0x1 Linux's libata driver has a quirk for VIA AHCI: /* vt8251 doesn't clear BSY on signature FIS reception, * request follow-up softreset. */ If i right understand it issues softreset for VIA controllers just after hardreset. And after softreset it is trying to read device signature. FreeBSD CURRENT has similar code, but it is disabled by default. You can try install CURRENT and rebuild ata_ahci driver with AHCI_PM option. May be it will help.. -- WBR, Andrey V. Elsukov ___ 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"
