Re: Problem reading vitals from Gigabyte H77-DH3H
On Sat, Oct 20, 2012 at 3:09 PM, Andriy Gapon a...@freebsd.org wrote: on 20/10/2012 22:42 Andriy Gapon said the following: on 20/10/2012 22:20 Derek Kulinski said the following: I have three questions though: 1. The motherboard has 4 fan sockets (as far as I can tell), CPU_FAN, and SYS_FAN[1-3]. SYS_FAN1 currently is not connected. Seems like: fan0 - CPU_FAN (did not try to disconnect it to check :) fan1 - SYS_FAN1 fan2 - SYS_FAN2 There is no entry for SYS_FAN3. I disconnected it temporarily but it did not seem to affect the output. Is it possible to get that information from the motherboard? The driver would have to be updated for that. Unfortunately ITE does not provide public datasheets. We could pick up some new bits from the Linux driver though. http://lxr.linux.no/#linux+v3.6.2/drivers/hwmon/it87.c In fact, here is a completely untested patch: http://people.freebsd.org/~avg/it-fans-0x80.diff @@ -354,12 +372,15 @@ static void it_refresh_sensor_data(struct it_softc *sc) { /* Refresh our stored data for every sensor */ - it_generic_stemp(sc, sc-sensors[12]); - it_generic_svolt(sc, sc-sensors[3]); - if (sc-fan16bit) + if (sc-fan16bit) { it_16bit_fanrpm(sc, sc-sensors[0]); - else + it_generic_svolt(sc, sc-sensors[5]); + it_generic_svolt(sc, sc-sensors[14]); - Looks to be a copy/paste bug ;-) + } else { it_generic_fanrpm(sc, sc-sensors[0]); + it_generic_svolt(sc, sc-sensors[3]); + it_generic_stemp(sc, sc-sensors[12]); + } } ___ 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: Problem reading vitals from Gigabyte H77-DH3H
on 21/10/2012 10:11 Scot Hetzel said the following: On Sat, Oct 20, 2012 at 3:09 PM, Andriy Gapon a...@freebsd.org wrote: on 20/10/2012 22:42 Andriy Gapon said the following: on 20/10/2012 22:20 Derek Kulinski said the following: I have three questions though: 1. The motherboard has 4 fan sockets (as far as I can tell), CPU_FAN, and SYS_FAN[1-3]. SYS_FAN1 currently is not connected. Seems like: fan0 - CPU_FAN (did not try to disconnect it to check :) fan1 - SYS_FAN1 fan2 - SYS_FAN2 There is no entry for SYS_FAN3. I disconnected it temporarily but it did not seem to affect the output. Is it possible to get that information from the motherboard? The driver would have to be updated for that. Unfortunately ITE does not provide public datasheets. We could pick up some new bits from the Linux driver though. http://lxr.linux.no/#linux+v3.6.2/drivers/hwmon/it87.c In fact, here is a completely untested patch: http://people.freebsd.org/~avg/it-fans-0x80.diff @@ -354,12 +372,15 @@ static void it_refresh_sensor_data(struct it_softc *sc) { /* Refresh our stored data for every sensor */ - it_generic_stemp(sc, sc-sensors[12]); - it_generic_svolt(sc, sc-sensors[3]); - if (sc-fan16bit) + if (sc-fan16bit) { it_16bit_fanrpm(sc, sc-sensors[0]); - else + it_generic_svolt(sc, sc-sensors[5]); + it_generic_svolt(sc, sc-sensors[14]); - Looks to be a copy/paste bug ;-) Indeed. Should be stemp of course. Thank you! + } else { it_generic_fanrpm(sc, sc-sensors[0]); + it_generic_svolt(sc, sc-sensors[3]); + it_generic_stemp(sc, sc-sensors[12]); + } } -- Andriy Gapon ___ 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: 9.1 and intel graphics
Normally I start X by startx which may be followed by an initialization file, so I don't get the default spartan default twm all the time. In Linux and FreeBSD, I generally use X as nonroot. So I don't really know how to start a program such as xterm as another user or how to have both root and nonroot windows in X. On trying to exit X with the KMS driver in FreeBSD, I never got that far, however I'm having snags in updating my ports, am at an impasse now, got Error 70 in the latest case and don't know what that means. But I have experience typing in the dark in NetBSD, not all X-related, and have successfully typed shutdown -r now with nothing showing on the screen. Tom ___ 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: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Sat, Oct 20, 2012 at 07:10:19AM -0700, David Wolfskill wrote: This seems ... fairly weird to me. Yesterday, I built booted: FreeBSD g1-227.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #274 241726M: Fri Oct 19 05:40:05 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 and used the machine all day; nothing unusual (including various reboots (e.g. when I disembarked the train for the final leg of my commute home, so I powered the laptop off). This morning, I built: FreeBSD g1-227.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #275 241776M: Sat Oct 20 04:34:45 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 and on first reboot, I got a panic. After a bit of experimentation, it appears that I get a panic @r241776 if I attempt a normal boot into multi-user mode, but if I first boot to single-user mode, then exit single-user mode, it comes up without a problem. I don't have a serial console, so I started to write down some of the panic information, but my patience ran a bit short. Here's whet I recorded (warning: hand-transcripted -- twice!): ... Starting devd. REDZONE: Buffer underflow detected. 1 byte corrupted before 0xced40080 (4294966796 bytes allocated). Allocation backtrace: #0 0xc0ceac8f at redzone_setup+0xcf #1 0xc0a5d5c9 at malloc+0x1d9 ...[about 20 more such lines I didn't record]... bt Tracing pid 901 tid 100106 td 0xd2b99000 kdb_enter(...) panic(...) free(...) devread(ce8c2d00,f7274c0c,0,c0b1e4f0,d279e380,...) at devread+0x1a6 giant_read(...) at giant_read+0x87 devfs_read(...) at devfs_read+0xc6 dofileread(...) at dofileread+0x99 sys_read(...) at sys_read+0x98 syscall(f7274d08) at syscall+0x387 Within the bounds described above, this appears to be quite reproducible -- on my laptop. My build machine (updated in parallel, at the same GRNs) does not exhibit the panic. I was unable to get a crash dump; I have dumpdev=AUTO in /etc/rc.conf, and the panic was occurring well after swap was enabled. (Yes, I know I have swap over-allocated. I plan to do something about it at some point.) I've attached a copy of dmesg.boot. Anyone else seeing this? Any ideas how to diagnose it? devread is the method of devctl(4) which passes devd notifications from the kernel to userland (to devd, specifically). There were no changes to devctl(4) for quite a time. The corruption is, most likely, in some unrelated piece of code. Could you try to bisect the stable to catch the offender ? The bisect is not guaranteed to work, obviously, since the random corruption effects are unpredictable. pgp9c2yHeIYD1.pgp Description: PGP signature
Re: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Sun, Oct 21, 2012 at 03:13:56PM +0300, Konstantin Belousov wrote: ... Anyone else seeing this? Any ideas how to diagnose it? devread is the method of devctl(4) which passes devd notifications from the kernel to userland (to devd, specifically). There were no changes to devctl(4) for quite a time. I noticed that none of the changes in the last update seemed at all relevant, yes. And thank you for the background (devread()). The corruption is, most likely, in some unrelated piece of code. Could you try to bisect the stable to catch the offender ? The bisect is not guaranteed to work, obviously, since the random corruption effects are unpredictable. I'll try -- but before I do, I've just removed a couple of custom stanzas from /etc/devd.conf (after noting that updating to r241776 does not appear to have affected the reported symptoms). So if the removal avoids the problem, that may reduce the searching a fair bit. :-) (I'm also informed by my spouse that I'm to help her prepare for some expected rain today; this may reduce the amount of time I am able to spend on it.) Adding the above-cited stanzas to devd.conf is one of the few things that I did on the laptop that I haven't done elsewhere -- and while I only track stable/9 daily on a couple of machines, I have 3 more that I update Sunday mornings which would be now. We shall see. :-} Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpd2A5pxDpKr.pgp Description: PGP signature
Re: 9.1 and intel graphics
Hello, On Sun, 21 Oct 2012 05:10:53 -0400 Thomas Mueller muelle...@insightbb.com wrote: Normally I start X by startx which may be followed by an initialization file, so I don't get the default spartan default twm all the time. In Linux and FreeBSD, I generally use X as nonroot. Which is the normal and correct way, IMHO. So I don't really know how to start a program such as xterm as another user or how to have both root and nonroot windows in X. Is there any reason why you don't make use of su(1) or sudo (/usr/ports/security/sudo)? That way you can just launch a xterm as your normal user, and become root when you want / need. HTH -- Torfinn Ingolfsen torfinn.ingolf...@getmail.no ___ 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: 9.1 and intel graphics
Hi Thomas, 21.10.2012 13:10, Thomas Mueller пишет: So I don't really know how to start a program such as xterm as another user or how to have both root and nonroot windows in X. AFAIC Matthew Seaman already gave you a wonderful suggestion to add yourself to the group operator and just use the command shutdown with your own rights only. Did you try this suggestion? -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: 9.1 and intel graphics
On Sun, 21 Oct 2012, Thomas Mueller wrote: Normally I start X by startx which may be followed by an initialization file, so I don't get the default spartan default twm all the time. In Linux and FreeBSD, I generally use X as nonroot. So I don't really know how to start a program such as xterm as another user or how to have both root and nonroot windows in X. Open a terminal, su - to root in it. In the exceptionally rare case of needing to run a graphic program as root, also set the DISPLAY variable to match the normal user's value, then run that program in the terminal. ___ 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: 9.1 and intel graphics
AFAIC Matthew Seaman already gave you a wonderful suggestion to add yourself to the group operator and just use the command shutdown with your own rights only. Did you try this suggestion? Actually, it is wheel group. To me it is normal to read mail and do something mundane in console, to startx for browsing things that cannot be seen pro- perly in lynx, to go back to console when done. I found no harm su-ing in graphics and doing root work, like write to usb stick or else. Eye catching is to use console in public, but... Best regards Zoran ___ 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: 9.1 and intel graphics
On 2012-Oct-20, at 08:29 , Kevin Oberman wrote: On Fri, Oct 19, 2012 at 9:14 PM, Zoran Kolic zko...@sbb.rs wrote: Yesterday I have gotten lenovo e320 laptop, with core i3 2350 and HD3000 integrated. Gonna wait few days till 9.1 release. I never used anything aside intel on my old laptop. Kostik Belousov made a port of kms and I found patches from june and jule on the net. What should I do after 9.1 install in this case? I assume kms is in xorg. Do I have to find and install some driver from intel? Do I need to change xorg.conf after configure flag, that will make conf file? Full support for the HD3000 is in 9-stable and 9.1-Beta and all RCs. To use it you need to build X drivers and drm and the kernel with: WITH_NEW_XORG=YES WITH_KMS=YES in /etc/make.conf. Specifically, the kernel and a few ports. graphics/drm and your org-drivers: xf86-video-intel, xf86-input-synaptics, xf86-input-mouse, and xf86-input-keyboard. Then just start X. Don't try loading the kernel module. It will be loaded by the startx. Finally, what happens when I leave x and want to go back to console mode? You don't If you try, your system will lock up. You need to shutdown from a window in X. Hopefully someone will implement switching back to console mode some day, but it has not happened, yet. I tried out live RC2 from usb stick. Few acpi errors, intel 1000 wifi found. After some time sysctl hw.acpi gave me the cpu temperature of 50C. Fan was on. Probably temp gonna go down when I add powerd and cx_lowest to rc.conf on hdd. Is it normal temp for this cpu? Pretty reasonable. Be sure to set both cx_lowest to Cmax. It is new to 9.1 and fixes some serious issues with C-states on many newer platforms. Specifically that some platforms skip some C-states and FreeBSD never used the ones saving more power than hte one skipped. I always remind folks to blow out the heat sink on laptops about one a year. Dust is a great insulator and laptops often collect a lot more dust than office systems, though my office system started dying during buildworld last week and blowing out the CPU heat sink fixed it up, but it had been sitting around for almost three years collecting dust. I'm trying to do something similar, except with an HD4000 (i5-3570K) on 9.1-RC2. The problem I'm having, after setting the make variables as above, is that xorg-drivers port doesn't show the intel driver. In fact, there's the specific part of the Makefile: .if (${ARCH} == amd64 || ${ARCH} == i386) !defined(WITH_NEW_XORG) VIDEO_ON+= intel .endif So what driver should I be using? Thanks, Neal. ___ 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: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Sun, Oct 21, 2012 at 03:13:56PM +0300, Konstantin Belousov wrote: On Sat, Oct 20, 2012 at 07:10:19AM -0700, David Wolfskill wrote: This seems ... fairly weird to me. Yesterday, I built booted: FreeBSD g1-227.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #274 241726M: Fri Oct 19 05:40:05 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 and used the machine all day; nothing unusual (including various reboots (e.g. when I disembarked the train for the final leg of my commute home, so I powered the laptop off). This morning, I built: FreeBSD g1-227.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #275 241776M: Sat Oct 20 04:34:45 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 and on first reboot, I got a panic. After a bit of experimentation, it appears that I get a panic @r241776 if I attempt a normal boot into multi-user mode, but if I first boot to single-user mode, then exit single-user mode, it comes up without a problem. I don't have a serial console, so I started to write down some of the panic information, but my patience ran a bit short. Here's whet I recorded (warning: hand-transcripted -- twice!): ... Starting devd. REDZONE: Buffer underflow detected. 1 byte corrupted before 0xced40080 (4294966796 bytes allocated). Allocation backtrace: #0 0xc0ceac8f at redzone_setup+0xcf #1 0xc0a5d5c9 at malloc+0x1d9 ...[about 20 more such lines I didn't record]... bt Tracing pid 901 tid 100106 td 0xd2b99000 kdb_enter(...) panic(...) free(...) devread(ce8c2d00,f7274c0c,0,c0b1e4f0,d279e380,...) at devread+0x1a6 giant_read(...) at giant_read+0x87 devfs_read(...) at devfs_read+0xc6 dofileread(...) at dofileread+0x99 sys_read(...) at sys_read+0x98 syscall(f7274d08) at syscall+0x387 Within the bounds described above, this appears to be quite reproducible -- on my laptop. My build machine (updated in parallel, at the same GRNs) does not exhibit the panic. I was unable to get a crash dump; I have dumpdev=AUTO in /etc/rc.conf, and the panic was occurring well after swap was enabled. (Yes, I know I have swap over-allocated. I plan to do something about it at some point.) I've attached a copy of dmesg.boot. Anyone else seeing this? Any ideas how to diagnose it? devread is the method of devctl(4) which passes devd notifications from the kernel to userland (to devd, specifically). There were no changes to devctl(4) for quite a time. The corruption is, most likely, in some unrelated piece of code. Could you try to bisect the stable to catch the offender ? The bisect is not guaranteed to work, obviously, since the random corruption effects are unpredictable. [Lack of trimming is deliberate, in this case, as I found a reversion that appears to address the issue, and I wanted folks looking at this to have the bulk of the symptoms readily at hand. -- dhw] The range of GRNs in question is 241726 - 241776, only 5 of which appliy to stable/9. Here's a list, with the affected files listed: 241742 sys/dev/sound/pci/hda/hdaa_patches.c 241749 sys/cam/cam_queue.c 241762 sys/dev/tws/tws.c sys/dev/tws/tws.h sys/dev/tws/tws_cam.c sys/dev/tws/tws_hdm.h sys/dev/tws/tws_user.c 241767 usr.bin/make/var.c 241769 sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zvol.c I had actually tried reverting 241742 yesterday, to no effect. I don't use ZFS, and I have a pretty hard time understanding how 241767 would break one machine and leave 4 others unscathed. (Yes, I completed my weekly updates, as well, by now.) I don't have tws(4) devices -- certainly not on the laptop. So I tried reverting 241749 ... and I failed to reproduce the problem. Well, one boot out of one, at least. I'll try a few more reality checks, and report back if a correction is in order. But (for now, at least), it looks to me as if 241749 is presenting a problem on this laptop. For folks investigating, I attached a dmesg.boot to the initial post in the thread; I'll be happy to provide more information, should it be requested ( specified). Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpPQgu5Io9Pg.pgp Description: PGP signature
Re: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Sun, Oct 21, 2012 at 09:33:22AM -0700, David Wolfskill wrote: ... So I tried reverting 241749 ... and I failed to reproduce the problem. Well, one boot out of one, at least. I'll try a few more reality checks, and report back if a correction is in order. But (for now, at least), it looks to me as if 241749 is presenting a problem on this laptop. ... 5 for 5. I'm convinced that 241749 causes problems on this laptop for attempts to boot without a stop is single-user mode first. (So that sounds like a timing issue, somehow.) And thanks again, Konstantin! Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgp42Glr1sW5J.pgp Description: PGP signature
Re: Problem reading vitals from Gigabyte H77-DH3H
Hello Andriy, Sunday, October 21, 2012, 1:53:51 AM, you wrote: it_16bit_fanrpm(sc, sc-sensors[0]); - else + it_generic_svolt(sc, sc-sensors[5]); + it_generic_svolt(sc, sc-sensors[14]); - Looks to be a copy/paste bug ;-) Indeed. Should be stemp of course. Thank you! I just fixed the code and looks better now: hw.sensors.it0.fan0: 997 RPM hw.sensors.it0.fan1: invalid hw.sensors.it0.fan2: 1303 RPM hw.sensors.it0.fan3: 1149 RPM hw.sensors.it0.fan4: invalid hw.sensors.it0.volt0: 1,42 VDC (VCORE_A) hw.sensors.it0.volt1: 2,72 VDC (VCORE_B) hw.sensors.it0.volt2: 2,70 VDC (+3.3V) hw.sensors.it0.volt3: 4,60 VDC (+5V) hw.sensors.it0.volt4: 0,06 VDC (+12V) hw.sensors.it0.volt5: -5,08 VDC (Unused) hw.sensors.it0.volt6: -6,53 VDC (-12V) hw.sensors.it0.volt7: 3,74 VDC (+5VSB) hw.sensors.it0.volt8: 2,14 VDC (VBAT) hw.sensors.it0.temp0: 30,00 degC hw.sensors.it0.temp1: 25,00 degC hw.sensors.it0.temp2: 25,00 degC -- Best regards, Derekmailto:tak...@takeda.tk -- DEFINITION: Computer - A device designed to speed and automate errors. ___ 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: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Sun, Oct 21, 2012 at 09:46:34AM -0700, David Wolfskill wrote: On Sun, Oct 21, 2012 at 09:33:22AM -0700, David Wolfskill wrote: ... So I tried reverting 241749 ... and I failed to reproduce the problem. Well, one boot out of one, at least. I'll try a few more reality checks, and report back if a correction is in order. But (for now, at least), it looks to me as if 241749 is presenting a problem on this laptop. ... 5 for 5. I'm convinced that 241749 causes problems on this laptop for attempts to boot without a stop is single-user mode first. (So that sounds like a timing issue, somehow.) And thanks again, Konstantin! I do not know/do not understand the CAM code, the question shall be addressed to Alexander. It still might be a false positive. pgpUVl3jUv9AU.pgp Description: PGP signature
Re: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On 21.10.2012 20:40, Konstantin Belousov wrote: On Sun, Oct 21, 2012 at 09:46:34AM -0700, David Wolfskill wrote: On Sun, Oct 21, 2012 at 09:33:22AM -0700, David Wolfskill wrote: ... So I tried reverting 241749 ... and I failed to reproduce the problem. Well, one boot out of one, at least. I'll try a few more reality checks, and report back if a correction is in order. But (for now, at least), it looks to me as if 241749 is presenting a problem on this laptop. ... 5 for 5. I'm convinced that 241749 causes problems on this laptop for attempts to boot without a stop is single-user mode first. (So that sounds like a timing issue, somehow.) And thanks again, Konstantin! I do not know/do not understand the CAM code, the question shall be addressed to Alexander. It still might be a false positive. I don't see how increasing buffer size by few bytes in mentioned change may cause memory corruption in some other place. I guess change can be just innocent witness that affected some memory placement, moving some existing corruption from one area to another where it was noticed. I am curious, how to interpret phrase 42=94966796 bytes allocated in log. May be it is just corrupted output, but the number still seems quite big, especially for i386 system, making me think about some integer overflow. David, could you write down that part once more? Having few more lines of Allocation backtrace: could also be useful. Could you show your kernel config? I can try to run it on my tests system, hoping to reproduce the problem. -- Alexander Motin ___ 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: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Sun, Oct 21, 2012 at 09:28:06PM +0300, Alexander Motin wrote: ... I am curious, how to interpret phrase 42=94966796 bytes allocated in log. May be it is just corrupted output, but the number still seems quite big, especially for i386 system, making me think about some integer overflow. David, could you write down that part once more? Having few more lines of Allocation backtrace: could also be useful. I'll try connecting a USB=serial dongle see if that's good enough to capture the ddb output. Could you show your kernel config? I can try to run it on my tests system, hoping to reproduce the problem. Attached (file CANARY); also attached output of pciconf -lv. Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. # # CANARY -- David's laptop kernel (based on one for the Compal 30W2/ # Dell i5000e) # include GENERIC # nocpu I486_CPU # nocpu I586_CPU ident CANARY maxusers0 nodeviceataraid # ATA RAID drives nodeviceatapist # ATAPI tape drives # deviceatapicam# emulate ATAPI devices as SCSI ditto via CAM options ATA_CAM # FDC_DEBUG enables floppy debugging. Since the debug output is huge, you # gotta turn it actually on by setting the variable fd_debug with DDB, # however. options FDC_DEBUG nodeviceasr # DPT SmartRAID V, VI and Adaptec SCSI RAID nodevicedpt # DPT Smartcache III, IV - See NOTES for options! nodevicemly # Mylex AcceleRAID/eXtremeRAID nodeviceamr # AMI MegaRAID nodevicearcmsr # Areca SATA II RAID nodeviceasr # DPT SmartRAID V, VI and Adaptec SCSI RAID nodeviceciss# Compaq Smart RAID 5* nodevicedpt # DPT Smartcache III, IV - See NOTES for options nodevicehptmv # Highpoint RocketRAID 182x nodeviceiir # Intel Integrated RAID nodeviceips # IBM (Adaptec) ServeRAID nodevicemly # Mylex AcceleRAID/eXtremeRAID nodevicetwa # 3ware 9000 series PATA/SATA RAID nodeviceaac # Adaptec FSA RAID nodeviceaacp# SCSI passthrough for aac (requires CAM) nodeviceida # Compaq Smart RAID nodevicemlx # Mylex DAC960 family nodevicepst # Promise Supertrak SX6000 nodevicetwe # 3ware ATA RAID nodeviceaac # Adaptec FSA RAID, Dell PERC2/PERC3 nodeviceamr # AMI MegaRAID nodeviceida # Compaq Smart RAID nodevicemlx # Mylex DAC960 family nodevicetwe # 3ware Escalade nodevicezyd # Whatever it is, I don't have it nodevicean # I want to use the module, for hacking nodevicewi # I want to use the module, for hacking # # MMC/SD # # mmc MMC/SD bus # mmcsd MMC/SD memory card # sdhci Generic PCI SD Host Controller # device mmc device mmcsd device sdhci # # SMB bus # # System Management Bus support is provided by the 'smbus' device. # Access to the SMBus device is via the 'smb' device (/dev/smb*), # which is a child of the 'smbus' device. # # Supported devices: # smb standard I/O through /dev/smb* # # Supported SMB interfaces: # iicsmbI2C to SMB bridge with any iicbus interface # bktr brooktree848 I2C hardware interface # intpm Intel PIIX4 (82371AB, 82443MX) Power Management Unit # alpm Acer Aladdin-IV/V/Pro2 Power Management Unit # ichsmbIntel ICH SMBus controller chips (82801AA, 82801AB, 82801BA) # viapm VIA VT82C586B/596B/686A and VT8233 Power Management Unit # amdpm AMD 756 Power Management Unit # amdsmbAMD 8111 SMBus 2.0 Controller # nfpm NVIDIA nForce Power Management Unit # nfsmb NVIDIA nForce2/3/4 MCP SMBus 2.0 Controller # device smbus # Bus support, required for smb below. # # SMB bus # # System Management Bus support is provided by the 'smbus' device. # Access to the SMBus device is via the 'smb' device (/dev/smb*), # which is a child of the 'smbus' device. # # Supported devices: # smb standard io through /dev/smb* # # Supported SMB interfaces: # iicsmbI2C to SMB bridge with any iicbus interface # bktr brooktree848 I2C hardware interface # intpm Intel PIIX4 (82371AB, 82443MX) Power Management Unit # alpm Acer Aladdin-IV/V/Pro2 Power Management Unit # ichsmbIntel ICH SMBus controller chips (82801AA, 82801AB, 82801BA) # viapm VIA VT82C586B/596B/686A and VT8233
Re: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Sun, Oct 21, 2012 at 09:28:06PM +0300, Alexander Motin wrote: ... I am curious, how to interpret phrase 42=94966796 bytes allocated in log. May be it is just corrupted output, but the number still seems quite big, especially for i386 system, making me think about some integer overflow. David, could you write down that part once more? Having few more lines of Allocation backtrace: could also be useful. Could you show your kernel config? I can try to run it on my tests system, hoping to reproduce the problem. ... I was unable to get serial console to work, even with the USB=serial dongle. However, I did find that the ddb dump command appears to have operated appropriately, and so I now have a dump. That, as well as the core.txt and additinal copies of the kernel config (CANARY) and dmesg.boot have been copied, and are now accessible from http://www.catwhisker.org/~david/FreeBSD/stable_9/. For a quick reality check, here's the stuff (cut/pasted from core.txt.4) that I had hand-written in my initial message: 118Starting devd. REDZONE: Buffer underflow detected. 1 byte corrupted before 0xced40080 (4294966796 bytes allocated). Allocation backtrace: #0 0xc0ceaa8f at redzone_setup+0xcf #1 0xc0a5d5c9 at malloc+0x1d9 #2 0xc0a9ead0 at devctl_queue_data_f+0x40 #3 0xc0aa3fba at devaddq+0x20a #4 0xc0aa098d at device_probe+0xad #5 0xc0aa1c9f at bus_generic_attach+0x1f #6 0xc07bcb1a at vga_pci_attach+0x4a #7 0xc0aa0de4 at device_attach+0x3b4 #8 0xc0aa1cab at bus_generic_attach+0x2b #9 0xc0531865 at acpi_pci_attach+0x185 #10 0xc0aa0de4 at device_attach+0x3b4 #11 0xc0aa1cab at bus_generic_attach+0x2b #12 0xc05339c2 at acpi_pcib_attach+0x262 #13 0xc0534cbf at acpi_pcib_pci_attach+0x9f #14 0xc0aa0de4 at device_attach+0x3b4 #15 0xc0aa1cab at bus_generic_attach+0x2b #16 0xc0531865 at acpi_pci_attach+0x185 #17 0xc0aa0de4 at device_attach+0x3b4 Free backtrace: #0 0xc0cead4a at redzone_check+0x1ca #1 0xc0a5d618 at free+0x38 #2 0xc0a9e956 at devread+0x1a6 #3 0xc0a28807 at giant_read+0x87 #4 0xc09710c6 at devfs_read_f+0xc6 #5 0xc0aba8d9 at dofileread+0x99 #6 0xc0aba4f8 at sys_read+0x98 #7 0xc0ddf977 at syscall+0x387 #8 0xc0dc87d1 at Xint0x80_syscall+0x21 REDZONE: Buffer overflow detected. 16 bytes corrupted after 0xced3fe8c (4294966796 bytes allocated). Allocation backtrace: #0 0xc0ceaa8f at redzone_setup+0xcf #1 0xc0a5d5c9 at malloc+0x1d9 #2 0xc0a9ead0 at devctl_queue_data_f+0x40 #3 0xc0aa3fba at devaddq+0x20a #4 0xc0aa098d at device_probe+0xad #5 0xc0aa1c9f at bus_generic_attach+0x1f #6 0xc07bcb1a at vga_pci_attach+0x4a #7 0xc0aa0de4 at device_attach+0x3b4 #8 0xc0aa1cab at bus_generic_attach+0x2b #9 0xc0531865 at acpi_pci_attach+0x185 #10 0xc0aa0de4 at device_attach+0x3b4 #11 0xc0aa1cab at bus_generic_attach+0x2b #12 0xc05339c2 at acpi_pcib_attach+0x262 #13 0xc0534cbf at acpi_pcib_pci_attach+0x9f #14 0xc0aa0de4 at device_attach+0x3b4 #15 0xc0aa1cab at bus_generic_attach+0x2b #16 0xc0531865 at acpi_pci_attach+0x185 #17 0xc0aa0de4 at device_attach+0x3b4 Free backtrace: #0 0xc0ceae92 at redzone_check+0x312 #1 0xc0a5d618 at free+0x38 #2 0xc0a9e956 at devread+0x1a6 #3 0xc0a28807 at giant_read+0x87 #4 0xc09710c6 at devfs_read_f+0xc6 #5 0xc0aba8d9 at dofileread+0x99 #6 0xc0aba4f8 at sys_read+0x98 #7 0xc0ddf977 at syscall+0x387 #8 0xc0dc87d1 at Xint0x80_syscall+0x21 panic: free: address 0xced3f080(0xced3f000) has not been allocated. cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper(c0f99230,c09710c6,c0aba8d9,c0734d37,c1131d40,...) at 0xc051d25e = db_trace_self_wrapper+0x2e kdb_backtrace(c0fd3355,1,c0f94756,f7231ae8,c0aa1cab,...) at 0xc0aa7eda = kdb_backtrace+0x2a panic(c0f94756,ced3f080,ced3f000,cebe4400,ced40080,...) at 0xc0a73bd4 = panic+0x1a4 free(ced40080,c10c3660,f7231c0c,c0b1e30d,ce7ef000,...) at 0xc0a5d6f9 = free+0x119 devread(ce8c2d00,f7231c0c,0,c0b1e4f0,d279ca48,...) at 0xc0a9e956 = devread+0x1a6 giant_read(ce8c2d00,f7231c0c,0,400,0,...) at 0xc0a28807 = giant_read+0x87 devfs_read_f(d279ca48,f7231c0c,ce84b680,0,d2797000,...) at 0xc09710c6 = devfs_read_f+0xc6 dofileread(d279ca48,f7231c0c,,,0,...) at 0xc0aba8d9 = dofileread+0x99 sys_read(d2797000,f7231ccc,c0a7c784,d2797000,0,...) at 0xc0aba4f8 = sys_read+0x98 syscall(f7231d08) at 0xc0ddf977 = syscall+0x387 Xint0x80_syscall() at 0xc0dc87d1 = Xint0x80_syscall+0x21 --- syscall (3, FreeBSD ELF32, sys_read), eip = 0x808f14b, esp = 0xbfbfd92c, ebp = 0xbfbfde58 --- KDB: enter: panic ... (kgdb) #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:249 #1 0xc051b353 in db_dump (dummy=-148694992, dummy2=-148694992, dummy3=-148694992, dummy4=0xf7231830 ) at /usr/src/sys/ddb/db_command.c:538 #2 0xc051ae45 in db_command (cmd_table=Variable cmd_table is not available. ) at /usr/src/sys/ddb/db_command.c:449 #3 0xc051abd0 in db_command_loop () at /usr/src/sys/ddb/db_command.c:502 #4 0xc051d3be in db_trap (type=Unhandled dwarf expression opcode 0xc0 ) at /usr/src/sys/ddb/db_main.c:231 #5 0xc0aa8464 in kdb_trap
Re: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On 21.10.2012 23:23, David Wolfskill wrote: On Sun, Oct 21, 2012 at 09:28:06PM +0300, Alexander Motin wrote: ... I am curious, how to interpret phrase 42=94966796 bytes allocated in log. May be it is just corrupted output, but the number still seems quite big, especially for i386 system, making me think about some integer overflow. David, could you write down that part once more? Having few more lines of Allocation backtrace: could also be useful. Could you show your kernel config? I can try to run it on my tests system, hoping to reproduce the problem. ... I've used your kernel config and my test system was unable to boot from NFS, while GENERIC kernel boots fine. I haven't got panic, but boot just stopped on root mounting. You have so many options specified there so I can't predict which of them could cause this. Now I am trying to binary search for the problematic one(s). -- Alexander Motin ___ 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: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Sat, Oct 20, 2012 at 07:10:19AM -0700, David Wolfskill wrote: This seems ... fairly weird to me. Yesterday, I built booted: FreeBSD g1-227.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #274 241726M: Fri Oct 19 05:40:05 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 and used the machine all day; nothing unusual (including various reboots (e.g. when I disembarked the train for the final leg of my commute home, so I powered the laptop off). This morning, I built: FreeBSD g1-227.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #275 241776M: Sat Oct 20 04:34:45 PDT 2012 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386 and on first reboot, I got a panic. [..] ... Starting devd. REDZONE: Buffer underflow detected. 1 byte corrupted before 0xced40080 (4294966796 bytes allocated). Allocation backtrace: #0 0xc0ceac8f at redzone_setup+0xcf #1 0xc0a5d5c9 at malloc+0x1d9 ...[about 20 more such lines I didn't record]... bt Tracing pid 901 tid 100106 td 0xd2b99000 kdb_enter(...) panic(...) free(...) devread(ce8c2d00,f7274c0c,0,c0b1e4f0,d279e380,...) at devread+0x1a6 giant_read(...) at giant_read+0x87 devfs_read(...) at devfs_read+0xc6 dofileread(...) at dofileread+0x99 sys_read(...) at sys_read+0x98 syscall(f7274d08) at syscall+0x387 This looks a lot like issue you reported a couple of months earlier, even affected buffer address matches. At least part of REDZONE metadata placed directly before the buffer is corrupted. So the idea is to set a watchpoint at a place that is known to contain wrong data (in this case allocation size) and wait for some code to try to modify it. I hacked up the following (really ugly, but should do the job): http://people.freebsd.org/~mjg/patches/watchpoint-hack.diff Note: this assumes that address of affected buffer is always the same. Assuming I didn't mess anything up, instructions are simple: Just try to reproduce the issue, at some point you should be dropped to the debugger. If that happens when dumpdevice is configured, please get a core. Otherwise just a backtrace (bt command). Note 2: this code does no clear the watchpoint, so if it fails to catch the offending case, it may catch completely legitimate code later. ___ 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: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On 22.10.2012 01:03, Alexander Motin wrote: On 21.10.2012 23:23, David Wolfskill wrote: On Sun, Oct 21, 2012 at 09:28:06PM +0300, Alexander Motin wrote: ... I am curious, how to interpret phrase 42=94966796 bytes allocated in log. May be it is just corrupted output, but the number still seems quite big, especially for i386 system, making me think about some integer overflow. David, could you write down that part once more? Having few more lines of Allocation backtrace: could also be useful. Could you show your kernel config? I can try to run it on my tests system, hoping to reproduce the problem. ... I've used your kernel config and my test system was unable to boot from NFS, while GENERIC kernel boots fine. I haven't got panic, but boot just stopped on root mounting. You have so many options specified there so I can't predict which of them could cause this. Now I am trying to binary search for the problematic one(s). Sorry. false alarm. I was just closed firewall in your kernel config. Without it my test system boots your kernel without any problem. -- Alexander Motin ___ 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: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Mon, Oct 22, 2012 at 12:09:08AM +0200, Mateusz Guzik wrote: ... This looks a lot like issue you reported a couple of months earlier, even affected buffer address matches. It's a tad scary that someone else notices that sort of thing before I do. :-} At least part of REDZONE metadata placed directly before the buffer is corrupted. So the idea is to set a watchpoint at a place that is known to contain wrong data (in this case allocation size) and wait for some code to try to modify it. I hacked up the following (really ugly, but should do the job): http://people.freebsd.org/~mjg/patches/watchpoint-hack.diff Note: this assumes that address of affected buffer is always the same. Assuming I didn't mess anything up, instructions are simple: Just try to reproduce the issue, at some point you should be dropped to the debugger. If that happens when dumpdevice is configured, please get a core. Otherwise just a backtrace (bt command). Well, the problem was occurring (only, and reproducibly) during the transition from single-user mode to multi-user mode. Perhaps more frustrating: after building installing the kernel with that patch, apparently locations of things were adjusted in such a way that the panic did not recur. Note 2: this code does no clear the watchpoint, so if it fails to catch the offending case, it may catch completely legitimate code later. Fun! :-) Thanks! Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpLWdcQNyFpa.pgp Description: PGP signature
Re: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Mon, Oct 22, 2012 at 01:31:04AM +0300, Alexander Motin wrote: ... I've used your kernel config and my test system was unable to boot from NFS, while GENERIC kernel boots fine. I haven't got panic, but boot just stopped on root mounting. You have so many options specified there so I can't predict which of them could cause this. Now I am trying to binary search for the problematic one(s). Sorry. false alarm. I was just closed firewall in your kernel config. Without it my test system boots your kernel without any problem. ... OK. I tried the watchpoint patch mjg@ sent; as noted in my response to him, I did not see the problem recur when I booted the resulting kernel. And given your observation, as well as that I've updated 4 other stable/9 systems (sources at r241801 for 3 of them; at r241786 for the other), none of which exhibited the problem, I suspect that something is remarkably sensitive to the storage layout. Hmmm... Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpX8IVdpCZPP.pgp Description: PGP signature
Re: ${CTFCONVERT_CMD} expands to empty string
Those lines cause this error: .if ${MK_CTF} != no CTFCONVERT_CMD= ${CTFCONVERT} ${CTFFLAGS} ${.TARGET} .elif ${MAKE_VERSION} = 520300 CTFCONVERT_CMD= .else CTFCONVERT_CMD= @: .endif My make version is 9201206140 So, either the check for = 520300 is incorrect or change for empty make variables expansion is not merged into stable-9 On 21.10.2012 1:29, Andrey Chernov wrote: On 20.10.2012 16:38, John Baldwin wrote: On Friday, October 19, 2012 09:06:55 PM Andrey Chernov wrote: On recent -stable I got a lots of (see subj) now due to CTF changes in *.mk files. I have WITHOUT_CDDL=yes in my /etc/src.conf and WITHOUT_CDDL have wider scope than WITHOUT_CTF suggested, but WITHOUT_CDDL is not checked in recent CTF changes. Please fix this thing. Which stable? stable-9 ___ 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: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Sun, Oct 21, 2012 at 3:46 PM, David Wolfskill da...@catwhisker.org wrote: On Mon, Oct 22, 2012 at 01:31:04AM +0300, Alexander Motin wrote: ... I've used your kernel config and my test system was unable to boot from NFS, while GENERIC kernel boots fine. I haven't got panic, but boot just stopped on root mounting. You have so many options specified there so I can't predict which of them could cause this. Now I am trying to binary search for the problematic one(s). Sorry. false alarm. I was just closed firewall in your kernel config. Without it my test system boots your kernel without any problem. ... OK. I tried the watchpoint patch mjg@ sent; as noted in my response to him, I did not see the problem recur when I booted the resulting kernel. And given your observation, as well as that I've updated 4 other stable/9 systems (sources at r241801 for 3 of them; at r241786 for the other), none of which exhibited the problem, I suspect that something is remarkably sensitive to the storage layout. Hmmm... This is starting to smell a bit like it may be tied to hardware. If you have two memory cards, you might want to try swapping them. If not, maybe let memtest86 run overnight. Yes, this is a total shot in the dark, but this one is really weird and when I see really weird, I start too look at hardware, especially memory and power supply. (And this really does not sound like power supply to me.) -- R. Kevin Oberman, Network Engineer E-mail: kob6...@gmail.com ___ 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: stable/9 @r241776 panic: REDZONE: Buffer underflow detected...
On Sun, Oct 21, 2012 at 05:28:49PM -0700, Kevin Oberman wrote: ... This is starting to smell a bit like it may be tied to hardware. If you have two memory cards, you might want to try swapping them. If not, maybe let memtest86 run overnight. There are 2 SODIMMS, yes. So I reverted mjg@'s sys/kern/subr_bus.c patch, rebuilt the kernel, and rebooted ... without issue: I was unable to reproduce the problem. Despite my inability to reproduce it, I went ahead powered down, swapped the SODIMMs, and rebooted. Still no recurrence. Yes, this is a total shot in the dark, but this one is really weird and when I see really weird, I start too look at hardware, especially memory and power supply. (And this really does not sound like power supply to me.) ... The machine is a Dell Precision M4400, and I have extended to hardware warranty. So if I can actually demonstrate a real hardware issue -- in a way that Dell will accept -- I should be able to get it fixed. (I've had a fair bit of practice at that, as the warranty includes accidental damage -- and the time I got flipped off my bicycle while the machine was in a (padded) rucksack qualified.) That said, overnight is when the machine updates its local private mirrors of the FreeBSD SVN repositories, so I can start my daily rebuilds of stable/9 head fairly early in the morning. (I prefer to get those -- as well as the port-updating -- completed before I get in to work, as I use the laptop to access all of the other machines I use. And I exercise the just-built stable/9 for the rest of the day) Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil men with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpKV1u7g2unK.pgp Description: PGP signature