Re: 9.2-PRE: switch off that stupid Nakatomi Socrates
On 30.09.2013 15:50, Matthieu Volat wrote: Le 30 sept. 2013 à 01:54, Ricardo Ferreira ricardo.ferre...@sotechdatacenter.com.br a écrit : Em 29-09-2013 19:11, Charles Sprickman escreveu: On Sep 29, 2013, at 3:28 PM, C. P. Ghost wrote: On 28.09.2013 11:32, Phil Regnauld wrote: Teske, Devin (Devin.Teske) writes: If you work seriously on serious issues long enough... you'll become burned- out. Let me just come right out and say it... I coded it. And thanks, you got me chuckling - nice to see some humor once in a while. To the offended poster: read the last line of tunefs(8) - there's probably many more places you could use serious time looking for deviations from corporate correctnes. Humor can even be etched in silicon, like e.g. on an IC created by Siemens: http://micro.magnet.fsu.edu/creatures/pages/bunny.html Cisco too, besides weird Star Wars ROM messages, you have stuff like the BFR (Big F*cking Router, after Big F*cking Gun in Doom) screened on the PCB: https://www.kumari.net/gallery/index.php/Technology/Networking/BFR_2_001 https://www.kumari.net/gallery/index.php/Technology/Networking/BFR_2 I have no idea what Sluggo and Nancy are doing on this board: https://www.kumari.net/gallery/index.php/Technology/Networking/CIMG0988 Charles ;-) -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org keep it cool u have others like: man chmod... BUGS There is no perm option for the naughty bits of a horse. and so many others. So... I find strange nobody mentioned the one in make :) % make love Not War. Nice, but how does it handle if a Makefile contains a love target? Regards, David. ___ 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.2-PRE: switch off that stupid Nakatomi Socrates
My apologies for being rude the few days ago. I don't know what happened to me, I'm usually not naughty like that. Bapt who knows me IRL would also say that. My personal life is not at its best state currently and everything that upset me get me nervous and rude.. I've been using FreeBSD for 5 years and developed some patches / improvements which honoured an entry to the additional contributors and I don't really want my name to be removed :-). Seriously, I feel really embarrassed for what I've said.To really explain why I got angry like that (but that does not excuse my words) is the following situation: 1. I've first stambled accross the new boot graphical Nakatomi Socrates art. I've been afraid of being hacked or something gone wrong in the SVN branches. Fortunately, quickly, some of the developers told me that it was a joke / tribute for the 9.2 RELEASE, then I just said I would not recommend to set it as default but with very clean words. And then I disabled it using loader_logo=orb as they said. 2. More than one month later, I upgraded to 9.2-RELEASE and then I saw the Nakatomi Socrates version shown in the right bottom and that's why I first thought that it was reenabled again (even in orb logo, I didn't know the existence of loader_version before!). So that's why I felt so angry.. Nevertheless this does not excuse my behavior. I love FreeBSD and still hack, develop it and don't want to get in troubles with *you* so please agree to my apologies. PS: I'm not a dinosaur as you may have thought, I like the small jokes that you can see for example in the syscons screen savers, the jokes in the man pages and such. But these things are more hidden and you need some research to get them which provides more excitement when you see them, on the other hand the Nakatomi Socrates art / version were *for me* a bit too intense as you see them by default, without enabling something. Again, sorry for that noise. Love, regards. David. ___ 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.2-PRE: switch off that stupid Nakatomi Socrates
On 21.09.2013 12:40, Matthew Seaman wrote: On 21/09/2013 11:31, O. Hartmann wrote: I'd like to switch off this silly Nakatomi Socrates message which reminds me on Linux and their childish naming schemes. It is only cosmetics, but it bothers me whenever I switch on the laptop. I guess there is a switch already prsent to have in the bootloader config? It's turned off by default in more recent 9.2-STABLE Otherwise: loader_logo=orb in /boot/loader.conf -- see loader.conf(5) Cheers, Matthew Hi, I have loader_logo=orb and I still have a message at the right bottom with that stupid joke. It's really pisses me off *now*. I already said it was okay to add a new logo for that stupid joke. But now, I have orb set and I still see that in my bootloader. How can I disable this forever ?! Also in the future you can just forgot that crappy ideas as you can see, nobody liked it. David. ___ 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.2-PRE: switch off that stupid Nakatomi Socrates
On 28.09.2013 00:12, Teske, Devin wrote: On Sep 27, 2013, at 3:06 PM, David Demelier wrote: On 21.09.2013 12:40, Matthew Seaman wrote: On 21/09/2013 11:31, O. Hartmann wrote: I'd like to switch off this silly Nakatomi Socrates message which reminds me on Linux and their childish naming schemes. It is only cosmetics, but it bothers me whenever I switch on the laptop. I guess there is a switch already prsent to have in the bootloader config? It's turned off by default in more recent 9.2-STABLE Otherwise: loader_logo=orb in /boot/loader.conf -- see loader.conf(5) Cheers, Matthew Hi, I have loader_logo=orb and I still have a message at the right bottom with that stupid joke. I already responded to this once. loader_version= See version.4th(8). It's really pisses me off *now*. Why *now*? I already answered this... (link to archives below) http://lists.freebsd.org/pipermail/freebsd-stable/2013-September/075260.html If you say that you tried this and it didn't work, then by all means... come back (pissed off or not) and we'll debug the situation. I already asked a few weeks ago what was this strange artwork on my boot loader and I was told to use loader_logo to completely disable it. I've first said that it's funny but I would not recommend to enable it by default because it's really not serious and the artwork was really immature in the scope of the FreeBSD project. Then I was happy because I get my orb as usual. And today, I've updated to 9.2-RELEASE SVN tag and saw there was again a message about this stupid Nakatomi Socrates version in green. So I needed to check again *why* this has been enabled by default and that's why it was starting to get my nerves. I personally think (but you may totally disagree with) that an operating system *is* an operating system. And I really hate easter eggs or anything else not serious being integrated into the system. I think about a new user installing FreeBSD 9.2, I would not imagine his reaction front of this kind of tribute or whatever you call that. For me it stands for that's not serious, it looks like a toy. Fortunately now it's just a version but I would really not imagine when the screen was looking with the tribute loader_logo. Seriously, I don't understand why people waste time to create jokes like that instead of working on serious issues. You may think I'm putting to much significance on this kind of matter but I like (and I'm not the only one) serious, clean things. And the real reason that made me yell like that was that I needed to ask / complain a second time to remove that tribute thing again. The person that recommended loader_logo was incorrectly thinking you were talking about the ARTWORK that you get by default in RC1-RC3 which is now non-default (requiring loader_logo=tribute to enable beyond RC3). The named releases however are staying enabled by default. And as I answered in the archives... loader_version=whatever you want to name your release or loader_version= is how you customize the text which seems to piss you off so much. Thanks. I already said it was okay to add a new logo for that stupid joke. But now, I have orb set and I still see that in my bootloader. How can I disable this forever ?! http://lists.freebsd.org/pipermail/freebsd-stable/2013-September/075260.html Also in the future you can just forgot that crappy ideas as you can see, nobody liked it. Uh... I'm ignoring that. Check again in the lists, I'm not the only one complaining on 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
Re: 9.2-PRE: switch off that stupid Nakatomi Socrates
On 28.09.2013 00:32, Teske, Devin wrote: On Sep 27, 2013, at 3:06 PM, David Demelier wrote: On 21.09.2013 12:40, Matthew Seaman wrote: On 21/09/2013 11:31, O. Hartmann wrote: I'd like to switch off this silly Nakatomi Socrates message which reminds me on Linux and their childish naming schemes. It is only cosmetics, but it bothers me whenever I switch on the laptop. I guess there is a switch already prsent to have in the bootloader config? It's turned off by default in more recent 9.2-STABLE Otherwise: loader_logo=orb in /boot/loader.conf -- see loader.conf(5) Cheers, Matthew Hi, I have loader_logo=orb and I still have a message at the right bottom with that stupid joke. Named Releases is far from a joke. Maybe you'd like something a bit more boring like 9.2-RELEASE The fact is... there is (and only ever will be) one iteration of FreeBSD 9.2. I assume that you have had no clue up until this point that there was yet another BSD 9.2. A fictitious version of BSD in a 1980's film, named... Nakatomi Socrates Yes I know that, I've already seen the image a lot a few weeks ago. Yeah, we could have decided to let the opportunity pass; to show that we're the first BSD to ever hit 9.2 out of all the flavors, producing the first ever non-fictitious BSD 9.2... But where would the fun be in that? FreeBSD is not Linux, I (and again, I'm not the only one) thought the idea of naming Linux 3.11 Linux for workgroups very stupid. In the Linux world we like to add funny messages / easter eggs directly in the kernel source, but I think this silly and not serious. So I don't really want to bring these Linux manners into our FreeBSD world. Rest assured... I've not seen *any* hollywood films with a number higher than 9.2... so our future looks pretty darn boring. The name for 10.0-RELEASE could very well be NULL or boring ol' 10.0-RELEASE But one thing is clear. There is a real tangible benefit to seeing the version on the boot screen. As we move to integrate BE's into the Forth boot screen, it may become paramount to know what version of loader(8) you're using. So please try not to be so judge-mental about these things. This is a real tangible improvement and simply because you've heard that those crazy people in Linux-land are naming their releases... That had zero bearing on why we did it. We may never name another release ever again. I personally would like to see loader(8) set the value to include an SVN revision so that everytime you rebuild loader(8), the version info updates; displayed prominently in the bottom right corner (which of course... you'll again be free to override it if you don't like it... just as you are free to completely disable the entire menu by adding beastie_disable=YES to loader.conf(8)). ___ 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.2-PRE: switch off that stupid Nakatomi Socrates
On 21.09.2013 12:31, O. Hartmann wrote: Hello, I'd like to switch off this silly Nakatomi Socrates message which reminds me on Linux and their childish naming schemes. It is only cosmetics, but it bothers me whenever I switch on the laptop. I guess there is a switch already prsent to have in the bootloader config? Thanks, oh Yes, I've already said a few weeks ago that it should not be default as it's really not serious for a system like FreeBSD, I'm happy that it has been removed just before 9.2-RELEASE. Cheers, David ___ 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: State of Unicode collation support in FreeBSD?
2013/9/10 Wolfgang Zenker wolfg...@lyxys.ka.sub.org: * David Demelier demelier.da...@gmail.com [130910 10:26]: 2013/8/28 Wolfgang Zenker wolfg...@lyxys.ka.sub.org: [crossposted to -stable and -i18n] could someone point me to infos regarding Unicode collation support in FreeBSD? All I could find was https://wiki.freebsd.org/KonradJankowski/Collation but that page has not been changed in more than two years. Looking at sources of -current it doesn't look like those changes made it into the source tree yet. I think no one is really interested to add real UTF-8 support to Syscons. Currently you can get UTF-8 output by using Syscons xterm ttys (which is default) and set your appropriate locales. For input it's currently (unfortunately) not supported. If you use X.Org, then your fine using UTF-8. There might be a misunderstanding: Collation is about ordering characters and sorting strings. What we have in FreeBSD right now is support for input and output of utf-8 characters, and with X11 and the right set of fonts they display ok, and at least using vim editing utf-8 text works ok. But sorting utf-8 strings yields interesting results as soon as you have non-ascii characters in your strings. Aaah, okay sorry I really did misunderstanding the question yes ;-). Regards, -- Demelier David ___ 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
9.2-RC1 panic at shutdown
Hello folks,
I have a panic at shutdown related to FUSE.
#0 doadump (textdump=value optimized out) at pcpu.h:234
234 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt full
#0 doadump (textdump=value optimized out) at pcpu.h:234
No locals.
#1 0x8090d9a6 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:449
_ep = (struct eventhandler_entry *) 0x0
_el = (struct eventhandler_list *) 0xfe0004813880
first_buf_printf = 1
#2 0x8090dea7 in panic (fmt=0x1 Address 0x1 out of bounds) at
/usr/src/sys/kern/kern_shutdown.c:637
td = (struct thread *) 0x1
bootopt = value optimized out
newpanic = value optimized out
ap = {{gp_offset = 16, fp_offset = 48, overflow_arg_area =
0xff80e7d402b0, reg_save_area = 0xff80e7d401d0}}
panic_cpu = 0
buf = privileged instruction fault, '\0' repeats 227 times
#3 0x80cf2c20 in trap_fatal (frame=0x1, eva=value optimized
out) at /usr/src/sys/amd64/amd64/trap.c:879
code = value optimized out
ss = 40
type = 1
esp = value optimized out
softseg = {ssd_base = 0, ssd_limit = 1048575, ssd_type = 27,
ssd_dpl = 0, ssd_p = 1, ssd_long = 1, ssd_def32 = 0, ssd_gran = 1}
msg = value optimized out
#4 0x80cf3431 in trap (frame=0xff80e7d40510) at
/usr/src/sys/amd64/amd64/trap.c:605
td = (struct thread *) 0xfe008be0b000
p = (struct proc *) 0xfe0034073000
i = value optimized out
ucode = value optimized out
code = 0
type = 1
addr = value optimized out
ksi = {ksi_link = {tqe_next = 0xff80e7d408dc, tqe_prev =
0x60}, ksi_info = {si_signo = 96, si_errno = 0, si_code = 0, si_pid = 0,
si_uid = 41125008, si_status = -512,
si_addr = 0xfe00027388f0, si_value = {sival_int = 3, sival_ptr =
0x3, sigval_int = 3, sigval_ptr = 0x3}, _reason = {_fault = {_trapno =
40}, _timer = {_timerid = 40, _overrun = 0},
_mesgq = {_mqd = 40}, _poll = {_band = 40}, __spare__ =
{__spare1__ = 40, __spare2__ = {-405535488, -128, -2137810668, -1, 3, 0,
0, ksi_flags = 2147483647,
ksi_sigq = 0xfe0002d1}
#5 0x80cdc863 in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:232
No locals.
#6 0x81afd551 in M_FUSEFH () from /usr/local/modules/fuse.ko
No symbol table info available.
#7 0xff80e7d405d8 in ?? ()
No symbol table info available.
#8 0x80d97858 in VOP_UNSET_TEXT_APV (vop=0x81afd3eb,
a=0xff80e7d40610) at vnode_if.c:4110
_enable_stops = 0
rc = value optimized out
#9 0x80b9476e in vnode_pager_dealloc
(object=0xfe004c3060e8) at vnode_if.h:1745
vp = value optimized out
refs = 0
#10 0x80b86739 in vm_object_terminate
(object=0xfe004c3060e8) at /usr/src/sys/vm/vm_object.c:766
p = 0xfe0035273000
p_next = 0xfe0035273000
#11 0x80b937f9 in vnode_destroy_vobject (vp=0xfe0035273000)
at /usr/src/sys/vm/vnode_pager.c:168
obj = (struct vm_object *) 0xfe004c3060e8
#12 0x81af78a1 in fuse_reclaim () from /usr/local/modules/fuse.ko
No symbol table info available.
#13 0x80d8 in VOP_RECLAIM_APV (vop=0xfe008be0b000,
a=0xfe0035273000) at vnode_if.c:1988
_enable_stops = 0
rc = value optimized out
#14 0x809aacd4 in vgonel (vp=0xfe0035273000) at vnode_if.h:830
td = (struct thread *) 0xfe008be0b000
active = 1
mp = (struct mount *) 0x0
#15 0x809ae1de in vflush (mp=0xfe00048ae338, rootrefs=1,
flags=2, td=0xfe008be0b000) at /usr/src/sys/kern/vfs_subr.c:2687
_rc = value optimized out
vp = (struct vnode *) 0xfe0035273000
mvp = (struct vnode *) 0xfe008bc36800
rootvp = (struct vnode *) 0xfe0035273000
vattr = {va_type = 2175779674, va_mode = 65535, va_nlink = -1,
va_uid = 689, va_gid = 0, va_fsid = 3889432544, va_fileid = -2133215974,
va_size = 4, va_blocksize = 525312,
va_atime = {tv_sec = -2198131494912, tv_nsec = 689}, va_mtime =
{tv_sec = -545866381232, tv_nsec = -2137280809}, va_ctime = {tv_sec =
-2127027808, tv_nsec = -2198131494912},
va_birthtime = {tv_sec = -2199022730240, tv_nsec = -2119187622},
va_gen = 18446743523953738417, va_flags = 0, va_rdev = 3889432736,
va_bytes = 18446741875578056904, va_filerev = 0,
va_vaflags = 2175779700, va_spare = 219043332096}
busy = 0
error = 0
#16 0x81af623b in fuse_unmount () from /usr/local/modules/fuse.ko
No symbol table info available.
#17 0xfe00048ae338 in ?? ()
No symbol table info available.
#18 0xfe008bdb7d50 in ?? ()
No symbol table info available.
#19 0xfe008be0b000 in ?? ()
No symbol table info available.
#20 0x in ?? ()
No symbol table info available.
I've read somewhere FreeBSD is stable, more than linux, I agree but
during this year I've got something like 10-15
Re: 9.2-RC1 panic at shutdown
On 12.09.2013 19:21, Florent Peterschmitt wrote: Le 12/09/2013 19:19, David Demelier a écrit : Hello folks, I have a panic at shutdown related to FUSE. #16 0x81af623b in fuse_unmount () from /usr/local/modules/fuse.ko Yes, then, did you rebuilt the kernel module after an upgrade? Yes it should, I have PORTS_MODULES set in my make.conf which should, but I will try to be sure! ___ 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: State of Unicode collation support in FreeBSD?
2013/8/28 Wolfgang Zenker wolfg...@lyxys.ka.sub.org: [crossposted to -stable and -i18n, replies directed to -stable] Hi everyone, could someone point me to infos regarding Unicode collation support in FreeBSD? All I could find was https://wiki.freebsd.org/KonradJankowski/Collation but that page has not been changed in more than two years. Looking at sources of -current it doesn't look like those changes made it into the source tree yet. Wolfgang I think no one is really interested to add real UTF-8 support to Syscons. Currently you can get UTF-8 output by using Syscons xterm ttys (which is default) and set your appropriate locales. For input it's currently (unfortunately) not supported. If you use X.Org, then your fine using UTF-8. Cheers, -- Demelier David ___ 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: Some PR never seen to delete
On 30.08.2013 22:30, Jakub Lach wrote: Why would you want to have valid ones closed? They are not all valids anymore. For instance burncd(1) is deprecated and does not work with ahci IIRC. I don't have xfce4 crash anymore. And the random ACPI panics have been fixed. For the other, they are almost 3 years old. Cheers ___ 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
Some PR never seen to delete
Hi, In the past I've sent some PR that has never been seen, I think we should close them now. 2010/09/16 kern/150628 [acd] [ata] burncd(1) can't write to optical drive 2010/07/14 ports/148591 x11 information note for x11-drivers/xf86-input-synaptic 2010/12/01 kern/152750 wireless[ath] ath0 lot of bad series hwrate 2010/12/12 bin/153052 [patch] watch(8) breaks tty on error 2011/01/25 ports/154288 glewis[patch] games/nethack*: remove old ports and cleanup latest 2011/02/07 kern/154567 wireless[ath] ath(4) lot of bad series(0) 2011/07/01 conf/158557rc [patch] /etc/rc.d/pf broken messages 2012/11/05 kern/173408 acpi[acpi] [regression] ACPI Regression: battery does not update often 2012/11/22 kern/173840 snd_hda(4) volume mixer not working anymore 2012/11/24 kern/173896 Kernel does not boot if splash loaded and hint.sc.0.vesa_mode set 2012/12/23 ports/174650 xfcex11-wm/xfce4 crash with exaGetPixmapFirstPixel called for invalid bpp 1 2012/12/28 kern/174766 acpi[acpi] Random acpi panic 2013/01/31 kern/175722 wireless[ath]lot of bad seriesx hwrate in kernel messages Some are still valid but will never been taken so I propose to close them. Cheers, -- Demelier David ___ 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: virtualbox crashes r254557
2013/8/27 Marko Cupać marko.cu...@mimar.rs: This happens a lot when using bridged ethernet. I have core dump. Should I post it here or send it to some email? Thank you in advance. -- Marko Cupać ___ 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 Yes you can paste the dump here -- Demelier David ___ 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
Update to 9.2-PRERELEASE, what is this?
Hi, After updating to r25, I have a strange boot loader, see: http://files.malikania.fr/DSC_0223.jpg What's that? Is this a joke? Cheers, ___ 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
Bind in FreeBSD, security advisories
Hi, For years, a lot of security advisories have been present for bind. I'm just guessing if it's not a good idea to remove bind from base? This will probably free by half the number of FreeBSD SA's in the future. Regards, -- Demelier David ___ 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: SU+J hard recovery failure
Le jeudi 28 mars 2013 11:05:58 Daniel O'Connor a écrit : On 27/03/2013, at 18:43, David Demelier demelier.da...@gmail.com wrote: Yesterday I had a panic on my laptop. Unfortunately the SU+J was not able to recovery the file system, the error was something like : Unknown error: Help! Could not find directory 9854215 And it went to the single user mode, I needed to fsck_ufs manually to recover the disk. What afraid me is what if happens on a headless machine? It will be hard to recover. For headless remote systems I use fsck_y_enable=YES. In my experience 'fsck -y' almost invariably recovers the disk to a point where it can boot and then I can login remotely. When the problem appeared, I could not use fsck -y because it will asks Use journal? and if journal is used the error above reappears and you can not clean the file system.. I needed to do a full fsck without any journal at all. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C Regards, -- David Demelier ___ 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
SU+J hard recovery failure
Hello folks, Yesterday I had a panic on my laptop. Unfortunately the SU+J was not able to recovery the file system, the error was something like : Unknown error: Help! Could not find directory 9854215 And it went to the single user mode, I needed to fsck_ufs manually to recover the disk. What afraid me is what if happens on a headless machine? It will be hard to recover. Regards, -- Demelier David ___ 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: Panic : bad pte
Le mercredi 20 mars 2013 20:09:42 David Demelier a écrit : 2013/3/19 Jeremy Chadwick j...@koitsu.org: On Tue, Mar 19, 2013 at 06:34:24PM +0100, David Demelier wrote: Hello, There it is, all my computers on FreeBSD 9.1-RELEASE had panic. I can just say there is a problem in the 9.1-RELEASE because I had no panic before. What afraid me is that my production server also panic'ed a few days ago, fortunately it does not appears so often. This is a panic that happened on my desktop computer, with a graphic card. The crash usually appears when X starts. GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Unread portion of the kernel message buffer: panic: bad pte cpuid = 3 KDB: stack backtrace: Uptime: 2m31s Dumping 183 out of 1950 MB:..9%..18%..27%..35%..44%..53%..62%..79%..88%..96% Reading symbols from /boot/modules/nvidia.ko...done. Loaded symbols for /boot/modules/nvidia.ko #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 224 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x0004 in ?? () #2 0x8048c156 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #3 0x8048c619 in panic (fmt=0x1 Address 0x1 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:636 #4 0x8065f88a in pmap_remove_pages (pmap=0xfe0005a2fa60) at /usr/src/sys/amd64/amd64/pmap.c:4156 #5 0x8063d26b in vmspace_exit (td=0xfe0005a05470) at /usr/src/sys/vm/vm_map.c:422 #6 0x8045d725 in exit1 (td=0xfe0005a05470, rv=Variable rv is not available. ) at /usr/src/sys/kern/kern_exit.c:315 #7 0x8045e5ce in sys_sys_exit (td=Variable td is not available. ) at /usr/src/sys/kern/kern_exit.c:122 #8 0x8066737f in amd64_syscall (td=0xfe0005a05470, traced=0) at subr_syscall.c:135 #9 0x80652d97 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #10 0x000800d51c1c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Of course I may do something wrong, and I hope so but unfortunately I can't find any solution. May the nvidia driver be the problem? Interesting timing. Semi-recently (February) src/sys/amd64/amd64/pmap.c in 9.1-STABLE (not -RELEASE) was modified to increase the information shown for this specific type of panic. See revision 247079: http://svnweb.freebsd.org/base/stable/9/sys/amd64/amd64/pmap.c?view=log I've CC'd Konstantin Belousov (kib@), who should be able to help step you through getting information out of the crash dump, to help track down the root cause. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | You will not believe that, when I leave the desktop. I completely detach the AC adaptor (usually at evening). And everyday when I plug it and start the machine it panics. But when it reboots and start again no panic anymore. I just can't believe it. The panic is completely different from yesterday's one : Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x8010 fault code = supervisor read data, page not present instruction pointer = 0x20:0x8049db4e stack pointer = 0x28:0xff8000225a90 frame pointer = 0x28:0xfe000247c8e0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= resume, IOPL = 0 current process = 10 (idle: cpu0) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: Uptime: 1m3s Dumping 324 out of 1950 MB:..5%..15%..25%..35%..45%..55%..65%..74%..84%..94% Reading symbols from /boot/modules/nvidia.ko...done. Loaded symbols for /boot/modules/nvidia.ko #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 224 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x0004 in ?? () #2 0x80489506 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #3 0x804899c9 in panic (fmt=0x1 Address 0x1 out of bounds) at /usr/src/sys/kern
Re: Panic : bad pte
2013/3/19 Jeremy Chadwick j...@koitsu.org: On Tue, Mar 19, 2013 at 06:34:24PM +0100, David Demelier wrote: Hello, There it is, all my computers on FreeBSD 9.1-RELEASE had panic. I can just say there is a problem in the 9.1-RELEASE because I had no panic before. What afraid me is that my production server also panic'ed a few days ago, fortunately it does not appears so often. This is a panic that happened on my desktop computer, with a graphic card. The crash usually appears when X starts. GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Unread portion of the kernel message buffer: panic: bad pte cpuid = 3 KDB: stack backtrace: Uptime: 2m31s Dumping 183 out of 1950 MB:..9%..18%..27%..35%..44%..53%..62%..79%..88%..96% Reading symbols from /boot/modules/nvidia.ko...done. Loaded symbols for /boot/modules/nvidia.ko #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 224 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x0004 in ?? () #2 0x8048c156 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #3 0x8048c619 in panic (fmt=0x1 Address 0x1 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:636 #4 0x8065f88a in pmap_remove_pages (pmap=0xfe0005a2fa60) at /usr/src/sys/amd64/amd64/pmap.c:4156 #5 0x8063d26b in vmspace_exit (td=0xfe0005a05470) at /usr/src/sys/vm/vm_map.c:422 #6 0x8045d725 in exit1 (td=0xfe0005a05470, rv=Variable rv is not available. ) at /usr/src/sys/kern/kern_exit.c:315 #7 0x8045e5ce in sys_sys_exit (td=Variable td is not available. ) at /usr/src/sys/kern/kern_exit.c:122 #8 0x8066737f in amd64_syscall (td=0xfe0005a05470, traced=0) at subr_syscall.c:135 #9 0x80652d97 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #10 0x000800d51c1c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Of course I may do something wrong, and I hope so but unfortunately I can't find any solution. May the nvidia driver be the problem? Interesting timing. Semi-recently (February) src/sys/amd64/amd64/pmap.c in 9.1-STABLE (not -RELEASE) was modified to increase the information shown for this specific type of panic. See revision 247079: http://svnweb.freebsd.org/base/stable/9/sys/amd64/amd64/pmap.c?view=log I've CC'd Konstantin Belousov (kib@), who should be able to help step you through getting information out of the crash dump, to help track down the root cause. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | Making life hard for others since 1977. PGP 4BD6C0CB | You will not believe that, when I leave the desktop. I completely detach the AC adaptor (usually at evening). And everyday when I plug it and start the machine it panics. But when it reboots and start again no panic anymore. I just can't believe it. The panic is completely different from yesterday's one : Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x8010 fault code = supervisor read data, page not present instruction pointer = 0x20:0x8049db4e stack pointer = 0x28:0xff8000225a90 frame pointer = 0x28:0xfe000247c8e0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= resume, IOPL = 0 current process = 10 (idle: cpu0) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: Uptime: 1m3s Dumping 324 out of 1950 MB:..5%..15%..25%..35%..45%..55%..65%..74%..84%..94% Reading symbols from /boot/modules/nvidia.ko...done. Loaded symbols for /boot/modules/nvidia.ko #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 224 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x0004 in ?? () #2 0x80489506 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #3 0x804899c9 in panic (fmt=0x1 Address 0x1 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:636 #4 0x80664e39 in trap_fatal (frame=0xc, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:857 #5 0x806651c4 in trap_pfault (frame
Re: System doesn't resume with active vbox VM
If the system reboots then you have a panic. Can you add dumpdev=AUTO in your /etc/rc.conf? And then please give us a kernel panic backtrace : http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html 2013/3/18 Dominic Fandrey kamik...@bsdforen.de My system doesn't resume with an active VirtualBox VM, in this case Windows XP/32. I didn't test any other systems. The system comes back to the console screen, but doesn't get back into X. After a couple of seconds (no dump occurs) I get the BIOS screen and the system reboots with unclean file systems. # uname -a FreeBSD mobileKamikaze.norad 9.1-STABLE FreeBSD 9.1-STABLE #3 r247136: Fri Feb 22 00:52:22 CET 2013 root@mobileKamikaze.norad:/usr/obj/HP6510b-9/amd64/usr/src/sys/HP6510b-9 amd64 Hardware virtualization is turned on, the additions are installed in the VM. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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 -- Demelier David ___ 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
Panic : bad pte
Hello, There it is, all my computers on FreeBSD 9.1-RELEASE had panic. I can just say there is a problem in the 9.1-RELEASE because I had no panic before. What afraid me is that my production server also panic'ed a few days ago, fortunately it does not appears so often. This is a panic that happened on my desktop computer, with a graphic card. The crash usually appears when X starts. GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Unread portion of the kernel message buffer: panic: bad pte cpuid = 3 KDB: stack backtrace: Uptime: 2m31s Dumping 183 out of 1950 MB:..9%..18%..27%..35%..44%..53%..62%..79%..88%..96% Reading symbols from /boot/modules/nvidia.ko...done. Loaded symbols for /boot/modules/nvidia.ko #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 224 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x0004 in ?? () #2 0x8048c156 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #3 0x8048c619 in panic (fmt=0x1 Address 0x1 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:636 #4 0x8065f88a in pmap_remove_pages (pmap=0xfe0005a2fa60) at /usr/src/sys/amd64/amd64/pmap.c:4156 #5 0x8063d26b in vmspace_exit (td=0xfe0005a05470) at /usr/src/sys/vm/vm_map.c:422 #6 0x8045d725 in exit1 (td=0xfe0005a05470, rv=Variable rv is not available. ) at /usr/src/sys/kern/kern_exit.c:315 #7 0x8045e5ce in sys_sys_exit (td=Variable td is not available. ) at /usr/src/sys/kern/kern_exit.c:122 #8 0x8066737f in amd64_syscall (td=0xfe0005a05470, traced=0) at subr_syscall.c:135 #9 0x80652d97 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #10 0x000800d51c1c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) Of course I may do something wrong, and I hope so but unfortunately I can't find any solution. May the nvidia driver be the problem? Kind regards -- Demelier David ___ 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: svn - but smaller?
Yes that would be great to have svnup into base as we had with cvsup then I will be able to fetch ports/base without doing any other steps before :) 2013/3/11 Isaac (.ike) Levy i...@blackskyresearch.net On Feb 23, 2013, at 7:36 PM, John Mehr wrote: Hello all, I've believe I've made just about all of the progress optimizing svnup as I can and I've just submitted it as a new port. With my ~ 350kb/s DSL connection, it now takes just under 30 minutes to download a fresh base/releng/8.3 tree using svnup (Subversion's svn takes approximately 12 minutes). Incremental updates, such as tracking one of the stable branches takes only 2-3 minutes. For anyone that wants to preview the port before it gets added to the ports tree (assuming I got the send-pr correct), the tarball is located at: http://jcm.dsl.visi.com/freebsd/svnup/svnup-0.5.tar.xz Please let me know if you find any issues. If anyone has any info about sunup(1) making it's way into base, please tell me so I can kill this page: https://wiki.freebsd.org/UsersFetchingSource (After trying to catch up on the relevant lists, I just updated that 'status page' on the FreeBSD wiki.) -- John, this is spectacular- thank you! Rocket- .ike ___ 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 -- Demelier David ___ 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: Panic at shutdown
Le mardi 12 février 2013 21:42:01 Ronald Klop a écrit : On Tue, 12 Feb 2013 19:44:49 +0100, David Demelier demelier.da...@gmail.com wrote: Le mardi 12 février 2013 10:01:10 Andriy Gapon a écrit : on 12/02/2013 09:57 David Demelier said the following: Yes I have added debugging option in my kernel. I have makeoptions DEBUG=-g in my config. Do I need more ? .symbols? I don't understand what you are saying, I have /boot/kernel/kernel.symbols. Please tell me what I'm doing wrong. I've just read and done the steps written there : http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug- gdb.html So I've run # cd /usr/obj/usr/src/sys/Melon # kgdb kernel.debug /var/crash/vmcore.0 Why not something like kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.0? That looks like what the manual page of kgdb seems to suggest. Regards, Ronald. and that's the only trace I get using bt full : 229 #define IS_BSP()(PCPU_GET(cpuid) == 0) (kgdb) bt full #0 doadump (textdump=value optimized out) at pcpu.h:229 No locals. #1 0x in ?? () No symbol table info available. I have that, in fact I was using bt full instead of short bt : #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x0004 in ?? () #2 0x805146b6 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #3 0x80514b79 in panic (fmt=0x1 Address 0x1 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:636 #4 0x8071e919 in trap_fatal (frame=0xc, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:857 #5 0x8071eca4 in trap_pfault (frame=0xff80d63db5d0, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:773 #6 0x8071f09b in trap (frame=0xff80d63db5d0) at /usr/src/sys/amd64/amd64/trap.c:456 #7 0x8070993f in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #8 0x802ddbf5 in AcpiOsAcquireObject (Cache=0xfe00015de400) at /usr/src/sys/contrib/dev/acpica/utilities/utcache.c:316 #9 0x802e27c1 in AcpiUtAllocateObjectDescDbg (ModuleName=0x80795110 dsutils, LineNumber=703, ComponentId=Variable ComponentId is not available. ) at /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:437 #10 0x802e2972 in AcpiUtCreateInternalObjectDbg (ModuleName=0x80795110 dsutils, LineNumber=703, ComponentId=64, Type=1) at /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:112 #11 0x802b32ea in AcpiDsCreateOperand (WalkState=0xfe000380fc00, Arg=0xfe00017d39c0, ArgIndex=0) at /usr/src/sys/contrib/dev/acpica/dispatcher/dsutils.c:703 #12 0x802b3686 in AcpiDsCreateOperands (WalkState=0xfe000380fc00, FirstArg=0xfe00017d39c0) at /usr/src/sys/contrib/dev/acpica/dispatcher/dsutils.c:798 #13 0x802b4323 in AcpiDsExecEndOp (WalkState=0xfe000380fc00) at /usr/src/sys/contrib/dev/acpica/dispatcher/dswexec.c:449 #14 0x802d55e9 in AcpiPsParseLoop (WalkState=0xfe000380fc00) at /usr/src/sys/contrib/dev/acpica/parser/psloop.c:1249 #15 0x802d6a5b in AcpiPsParseAml (WalkState=0xfe000380fc00) at /usr/src/sys/contrib/dev/acpica/parser/psparse.c:525 #16 0x802d7ad7 in AcpiPsExecuteMethod (Info=0xfe00411b9500) at /usr/src/sys/contrib/dev/acpica/parser/psxface.c:368 #17 0x802ce3af in AcpiNsEvaluate (Info=0xfe00411b9500) at /usr/src/sys/contrib/dev/acpica/namespace/nseval.c:193 #18 0x802d3567 in AcpiEvaluateObject (Handle=0xfe00017d6d40, Pathname=0x807b2e9b _TMP, ExternalParams=0x0, ReturnBuffer=0xff80d63dba50) at /usr/src/sys/contrib/dev/acpica/namespace/nsxfeval.c:289 #19 0x8031ca84 in acpi_GetInteger (handle=0xfe00017d6d40, path=0x807b2e9b _TMP, number=0xff80d63dbab4) at /usr/src/sys/dev/acpica/acpi.c:2204 #20 0x80331756 in acpi_tz_get_temperature (sc=0xfe0001a2fa00) at /usr/src/sys/dev/acpica/acpi_thermal.c:462 #21 0x803329d6 in acpi_tz_monitor (Context=0xfe0001a2fa00) at /usr/src/sys/dev/acpica/acpi_thermal.c:497 #22 0x80332f92 in acpi_tz_thread (arg=Variable arg is not available. ) at /usr/src/sys/dev/acpica/acpi_thermal.c:864 #23 0x804e7a3d in fork_exit (callout=0x80332e50 acpi_tz_thread, arg=0x0, frame=0xff80d63dbc00) at /usr/src/sys/kern/kern_fork.c:992 #24 0x80709dfe in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:602 #25 0x in ?? () #26 0x in ?? () #27 0x0001 in ?? () #28 0x in ?? () #29 0x in ?? () #30 0x in ?? () #31 0x in ?? () #32 0x in ?? () #33 0x in ?? () #34 0x in ?? () #35 0x in ?? () #36 0x in ?? () #37 0x
Re: Panic at shutdown
2013/2/14 David Demelier demelier.da...@gmail.com
Le mardi 12 février 2013 21:42:01 Ronald Klop a écrit :
On Tue, 12 Feb 2013 19:44:49 +0100, David Demelier
demelier.da...@gmail.com wrote:
Le mardi 12 février 2013 10:01:10 Andriy Gapon a écrit :
on 12/02/2013 09:57 David Demelier said the following:
Yes I have added debugging option in my kernel. I have makeoptions
DEBUG=-g in my config. Do I need more ?
.symbols?
I don't understand what you are saying, I have
/boot/kernel/kernel.symbols.
Please tell me what I'm doing wrong. I've just read and done the steps
written
there :
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-
gdb.html
So I've run
# cd /usr/obj/usr/src/sys/Melon
# kgdb kernel.debug /var/crash/vmcore.0
Why not something like kgdb /boot/kernel/kernel.symbols
/var/crash/vmcore.0?
That looks like what the manual page of kgdb seems to suggest.
Regards,
Ronald.
and that's the only trace I get using bt full :
229 #define IS_BSP()(PCPU_GET(cpuid) == 0)
(kgdb) bt full
#0 doadump (textdump=value optimized out) at pcpu.h:229
No locals.
#1 0x in ?? ()
No symbol table info available.
--
David Demelier
___
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-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Today I have a little bit more :
#0 0x804f358b in isbufbusy (bp=0xfe0003810480) at
/usr/src/sys/kern/kern_shutdown.c:280
280 if (((bp-b_flags (B_INVAL | B_PERSISTENT)) == 0
(kgdb) bt full
#0 0x804f358b in isbufbusy (bp=0xfe0003810480) at
/usr/src/sys/kern/kern_shutdown.c:280
No locals.
#1 0x0004 in ?? ()
No symbol table info available.
#2 0x804f3aa6 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:451
_ep = (struct eventhandler_entry *) 0x100
_el = (struct eventhandler_list *) 0x804f35b3
first_buf_printf = 1
#3 0x804f3f69 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:624
td = (struct thread *) 0x1
bootopt = 260
newpanic = 1
ap = {{gp_offset = 16, fp_offset = 48, overflow_arg_area =
0xff80daaf0420, reg_save_area = 0xff80daaf0350}}
panic_cpu = 0
buf = general protection fault, '\0' repeats 231 times
#4 0x806fcf69 in trap_fatal (frame=0x9, eva=Variable eva is not
available.
) at /usr/src/sys/amd64/amd64/trap.c:851
code = Variable code is not available.
I feel very very ashamed because these random panics were occurring because
of my kernel config that contained drm and radeondrm devices while I use
x11/nvidia-driver.. However, I think we should add a notice in the
nvidia-driver pkg-message to prevent any problems?
--
Demelier David
___
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: Panic at shutdown
Le mardi 12 février 2013 21:42:01 Ronald Klop a écrit :
On Tue, 12 Feb 2013 19:44:49 +0100, David Demelier
demelier.da...@gmail.com wrote:
Le mardi 12 février 2013 10:01:10 Andriy Gapon a écrit :
on 12/02/2013 09:57 David Demelier said the following:
Yes I have added debugging option in my kernel. I have makeoptions
DEBUG=-g in my config. Do I need more ?
.symbols?
I don't understand what you are saying, I have
/boot/kernel/kernel.symbols.
Please tell me what I'm doing wrong. I've just read and done the steps
written
there :
http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-
gdb.html
So I've run
# cd /usr/obj/usr/src/sys/Melon
# kgdb kernel.debug /var/crash/vmcore.0
Why not something like kgdb /boot/kernel/kernel.symbols
/var/crash/vmcore.0?
That looks like what the manual page of kgdb seems to suggest.
Regards,
Ronald.
and that's the only trace I get using bt full :
229 #define IS_BSP()(PCPU_GET(cpuid) == 0)
(kgdb) bt full
#0 doadump (textdump=value optimized out) at pcpu.h:229
No locals.
#1 0x in ?? ()
No symbol table info available.
--
David Demelier
___
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-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Today I have a little bit more :
#0 0x804f358b in isbufbusy (bp=0xfe0003810480) at
/usr/src/sys/kern/kern_shutdown.c:280
280 if (((bp-b_flags (B_INVAL | B_PERSISTENT)) == 0
(kgdb) bt full
#0 0x804f358b in isbufbusy (bp=0xfe0003810480) at
/usr/src/sys/kern/kern_shutdown.c:280
No locals.
#1 0x0004 in ?? ()
No symbol table info available.
#2 0x804f3aa6 in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:451
_ep = (struct eventhandler_entry *) 0x100
_el = (struct eventhandler_list *) 0x804f35b3
first_buf_printf = 1
#3 0x804f3f69 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:624
td = (struct thread *) 0x1
bootopt = 260
newpanic = 1
ap = {{gp_offset = 16, fp_offset = 48, overflow_arg_area =
0xff80daaf0420, reg_save_area = 0xff80daaf0350}}
panic_cpu = 0
buf = general protection fault, '\0' repeats 231 times
#4 0x806fcf69 in trap_fatal (frame=0x9, eva=Variable eva is not
available.
) at /usr/src/sys/amd64/amd64/trap.c:851
code = Variable code is not available.
--
David Demelier
___
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: Panic at shutdown
Le mardi 12 février 2013 10:01:10 Andriy Gapon a écrit : on 12/02/2013 09:57 David Demelier said the following: Yes I have added debugging option in my kernel. I have makeoptions DEBUG=-g in my config. Do I need more ? .symbols? I don't understand what you are saying, I have /boot/kernel/kernel.symbols. Please tell me what I'm doing wrong. I've just read and done the steps written there : http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug- gdb.html So I've run # cd /usr/obj/usr/src/sys/Melon # kgdb kernel.debug /var/crash/vmcore.0 and that's the only trace I get using bt full : 229 #define IS_BSP()(PCPU_GET(cpuid) == 0) (kgdb) bt full #0 doadump (textdump=value optimized out) at pcpu.h:229 No locals. #1 0x in ?? () No symbol table info available. -- David Demelier ___ 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: Panic at shutdown
Okay I will update everything and use GENERIC config, if I get more info I'll tell you :-), Cheers and thanks for your answers 2013/2/12 Andriy Gapon a...@freebsd.org on 12/02/2013 20:44 David Demelier said the following: Le mardi 12 février 2013 10:01:10 Andriy Gapon a écrit : on 12/02/2013 09:57 David Demelier said the following: Yes I have added debugging option in my kernel. I have makeoptions DEBUG=-g in my config. Do I need more ? .symbols? I don't understand what you are saying, I have /boot/kernel/kernel.symbols. Please tell me what I'm doing wrong. I've just read and done the steps written there : http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug- gdb.html So I've run # cd /usr/obj/usr/src/sys/Melon # kgdb kernel.debug /var/crash/vmcore.0 and that's the only trace I get using bt full : 229 #define IS_BSP()(PCPU_GET(cpuid) == 0) (kgdb) bt full #0 doadump (textdump=value optimized out) at pcpu.h:229 No locals. #1 0x in ?? () No symbol table info available. I don't know what you are doing wrong, but the above message (No symbol table info available) is wrong. Perhaps your world (kgdb) and kernel are out of sync, maybe something else... -- Andriy Gapon -- Demelier David ___ 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: Panic at shutdown
Le jeudi 7 février 2013 10:55:09 Andriy Gapon a écrit : Without so much as a stack trace there is nothing to chew on. A useable vmcore would be better. Did you perhaps use kgdb with a mismatching kernel? -- I still have panic, and recompiled kernel, the stack info is not better but I have a lot of message before : (Always related to ACPI) GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Unread portion of the kernel message buffer: ACPI Error: Object not a Integer, type Reference (20110527/exresnte-210) ACPI Error: Method execution failed [\_SB_.BAT0._UID] (Node 0xfe00017eaaf0), AE_AML_OPERAND_TYPE (20110527/uteval-113) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BTDR] (Node 0xfe00017e6ac8), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BSTA] (Node 0xfe00017e6aa0), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_SB_.BAT0._STA] (Node 0xfe00017eaac8), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method execution failed [\_SB_.BAT0._STA] (Node 0xfe00017eaac8), AE_AML_OPERAND_TYPE (20110527/uteval-113) ACPI Error: Object not a Integer, type Reference (20110527/exresnte-210) ACPI Error: Method execution failed [\_SB_.BAT0._UID] (Node 0xfe00017eaaf0), AE_AML_OPERAND_TYPE (20110527/uteval-113) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BTDR] (Node 0xfe00017e6ac8), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.BSTA] (Node 0xfe00017e6aa0), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_SB_.BAT0._STA] (Node 0xfe00017eaac8), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method execution failed [\_SB_.BAT0._STA] (Node 0xfe00017eaac8), AE_AML_OPERAND_TYPE (20110527/uteval-113) ACPI Error: Object not a Integer, type Reference (20110527/exresnte-210) ACPI Error: Method execution failed [\_SB_.BAT0._UID] (Node 0xfe00017eaaf0), AE_AML_OPERAND_TYPE (20110527/uteval-113) ACPI Error: Needed [Integer/String/Buffer], found [Mutex] 0xfe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_GPE.HWWP] (Node 0xfe00017d2208), AE_AML_OPERAND_TYPE (20110527/psparse-560) Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x368 fault code = supervisor read data, page not present instruction pointer = 0x20:0x804e433b stack pointer = 0x28:0xff80dd819730 frame pointer = 0x28:0xfe0003aa3920 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1543 (upowerd) trap number = 12 panic: page fault cpuid = 0 Uptime: 2h11m52s Dumping 632 out of 3054 MB:..3%..11%..21%..31%..41%..51%..61%..71%..81%..92% Reading symbols from /boot/kernel/vboxdrv.ko...done. Loaded symbols for /boot/kernel/vboxdrv.ko #0 doadump (textdump=value optimized out) at pcpu.h:229 warning: Source file is more recent than executable. 229 #define IS_BSP()(PCPU_GET(cpuid) == 0) (kgdb) bt full #0 doadump (textdump=value optimized out) at pcpu.h:229 No locals. #1 0x in ?? () No symbol table info available. (kgdb) bt full #0 doadump (textdump=value optimized out) at pcpu.h:229 No locals. #1 0x in ?? () No symbol table info available. -- David Demelier ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable
Re: Panic at shutdown
Yes I have added debugging option in my kernel. I have makeoptions DEBUG=-g in my config. Do I need more ? I'm not sure to understand what you meant about stray signatures.. -- Demelier David ___ 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: Panic at shutdown
On 07/02/2013 09:55, Andriy Gapon wrote: Without so much as a stack trace there is nothing to chew on. A useable vmcore would be better. Did you perhaps use kgdb with a mismatching kernel? I don't remember, I just rebuild a new kernel and will provide more info if panic occurs again! ___ 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
Panic at shutdown
Hello there, I recently had a panic at shutdown in 9.1-STABLE, there's the backtrace: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Unread portion of the kernel message buffer: 118. 118Feb 5 23:30:31 Melon syslogd: exiting on signal 15 5wlan0: link state changed to DOWN 5lagg0: link state changed to DOWN Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...7 1 1 0 done All buffers synced. ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfe0001807678 (20110527/exresop-443) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.SMAB] (Node 0xfe00017edc08), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.GFXZ._TMP] (Node 0xfe00017d3280), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed type [Reference], found [Integer] 0xfe0001807678 (20110527/exresop-116) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.INTM] (Node 0xfe00017d4168), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.DTSZ._TMP] (Node 0xfe00017d4500), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node 0xfe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.CPUZ._TMP] (Node 0xfe00017d41e0), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node 0xfe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.SKNZ._TMP] (Node 0xfe00017d8258), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node 0xfe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.BATZ._TMP] (Node 0xfe00017d8118), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed type [Reference], found [Integer] 0xfe0001807678 (20110527/exresop-116) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.KRFS] (Node 0xfe00017e71e0), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_SB_.GRFS] (Node 0xfe00017f37f8), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.FDTZ._TMP] (Node 0xfe00017d8078), AE_AML_OPERAND_TYPE (20110527/psparse-560) Uptime: 2h1m59s ACPI Error: Needed type [Reference], found [Integer] 0xfe0001807678 (20110527/exresop-116) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEGP.DGFX._DOS] (Node 0xfe00017d9528), AE_AML_OPERAND_TYPE (20110527/psparse-560) can't evaluate \_SB_.PCI0.PEGP.DGFX._DOS - AE_AML_OPERAND_TYPE usbus0: Controller shutdown uhub0: at usbus0, port 1, addr 1 (disconnected) ugen0.2: Broadcom Corp at usbus0 (disconnected) ubt0: at uhub0, port 1, addr 2 (disconnected) usbus0: Controller shutdown complete usbus1: Controller shutdown uhub1: at usbus1, port 1, addr 1 (disconnected) usbus1: Controller shutdown complete usbus2: Controller shutdown uhub2: at usbus2, port 1, addr 1 (disconnected) usbus2: Controller shutdown complete usbus3: Controller shutdown uhub3: at usbus3, port 1, addr 1 (disconnected) ugen3.2: Chicony Electronics Co., Ltd. at usbus3 (disconnected) usbus3: Controller shutdown complete usbus4: Controller shutdown uhub4: at usbus4, port 1, addr 1
Re: Panic at shutdown
On 06/02/2013 16:31, David Demelier wrote: Hello there, I recently had a panic at shutdown in 9.1-STABLE, there's the backtrace: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as amd64-marcel-freebsd... Unread portion of the kernel message buffer: 118. 118Feb 5 23:30:31 Melon syslogd: exiting on signal 15 5wlan0: link state changed to DOWN 5lagg0: link state changed to DOWN Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...7 1 1 0 done All buffers synced. ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfe0001807678 (20110527/exresop-443) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.SMAB] (Node 0xfe00017edc08), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.GFXZ._TMP] (Node 0xfe00017d3280), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed type [Reference], found [Integer] 0xfe0001807678 (20110527/exresop-116) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.INTM] (Node 0xfe00017d4168), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.DTSZ._TMP] (Node 0xfe00017d4500), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node 0xfe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.CPUZ._TMP] (Node 0xfe00017d41e0), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node 0xfe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.SKNZ._TMP] (Node 0xfe00017d8258), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed [Integer/String/Buffer], found [Reference] 0xfe0001807678 (20110527/exresop-533) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node 0xfe00017d6050), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.BATZ._TMP] (Node 0xfe00017d8118), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Needed type [Reference], found [Integer] 0xfe0001807678 (20110527/exresop-116) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.EC0_.KRFS] (Node 0xfe00017e71e0), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_SB_.GRFS] (Node 0xfe00017f37f8), AE_AML_OPERAND_TYPE (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_TZ_.FDTZ._TMP] (Node 0xfe00017d8078), AE_AML_OPERAND_TYPE (20110527/psparse-560) Uptime: 2h1m59s ACPI Error: Needed type [Reference], found [Integer] 0xfe0001807678 (20110527/exresop-116) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20110527/dswexec-498) ACPI Error: Method parse/execution failed [\_SB_.PCI0.PEGP.DGFX._DOS] (Node 0xfe00017d9528), AE_AML_OPERAND_TYPE (20110527/psparse-560) can't evaluate \_SB_.PCI0.PEGP.DGFX._DOS - AE_AML_OPERAND_TYPE usbus0: Controller shutdown uhub0: at usbus0, port 1, addr 1 (disconnected) ugen0.2: Broadcom Corp at usbus0 (disconnected) ubt0: at uhub0, port 1, addr 2 (disconnected) usbus0: Controller shutdown complete usbus1: Controller shutdown uhub1: at usbus1, port 1, addr 1 (disconnected) usbus1: Controller shutdown complete usbus2: Controller shutdown uhub2: at usbus2, port 1, addr 1 (disconnected) usbus2: Controller shutdown complete usbus3: Controller shutdown uhub3: at usbus3, port 1, addr 1 (disconnected) ugen3.2: Chicony Electronics
Re: mergemaster -p / installkernel problem
What did you have in your mergemaster.rc ? To help next people who may have the same problem :) 2013/1/28 Michiel Boland bolan...@xs4all.nl On 01/28/2013 02:10, Kevin Oberman wrote: You don't by any chance have a mergemaster.rc in /etc or .mergemasterrc in $HOME? Duh... I'll go stand in the corner for the next 37 years. Cheers Michiel __**_ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**stablehttp://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscribe@**freebsd.orgfreebsd-stable-unsubscr...@freebsd.org -- Demelier David ___ 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: Question: /usr/sbin/pkg vs /usr/local/sbin/pkg in 9.1
On 27/12/2012 11:02, Matthew Seaman wrote: On 27/12/2012 09:44, Rainer Duffner wrote: as I see it, pkgng is actually included in 9.1 as /usr/sbin/pkg, right? /usr/sbin/pkg and /usr/local/sbin/pkg are very different. /usr/local/sbin/pkg is a binary package management system. /usr/sbin/pkg is a shim that can bootstrap the installation of /usr/local/sbin/pkg if it is not already installed, or that invokes /usr/local/sbin/pkg preserving the rest of the command line otherwise. Is there a way to say I have the pkg tool in base already? pkgng is not in base and there are no plans to import it. If you are going to use pkgng then you need to install it, either from ports or by using the /usr/sbin/pkg shim to install from a pkgng package. Why there is no plan to import it? Or is the pkg in base supposed to just install the pkgng from ports? Indirectly. /usr/sbin/pkg installs from a pre-compiled tarball, which is generated from the ports-mgmt/pkg port. Cheers, Matthew Cheers, David ___ 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
Kernel panic when playing games/iourbanterror
Hello, When playing a lot Urban Terror, the system panic with ACPI related issues : Fatal trap 9: general protection fault while in kernel mode cpuid = 1; apic id = 01 instruction pointer = 0x20:0x802c6f15 stack pointer = 0x28:0xff80d89ac6c0 frame pointer = 0x28:0x0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 1288 (hald) trap number = 9 panic: general protection fault cpuid = 1 Uptime: 1h52m22s Dumping 596 out of 3054 MB:..3%..11%..22%..33%..41%..51%..62%..73%..81%..92% Reading symbols from /boot/modules/vboxdrv.ko...done. Loaded symbols for /boot/modules/vboxdrv.ko #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 224 __asm(movq %%gs:0,%0 : =r (td)); (kgdb) list *0xff80d89ac6c0 No source file for address 0xff80d89ac6c0. (kgdb) backtrace #0 doadump (textdump=Variable textdump is not available. ) at pcpu.h:224 #1 0x0004 in ?? () #2 0x804f3ae6 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:448 #3 0x804f3fa9 in panic (fmt=0x1 Address 0x1 out of bounds) at /usr/src/sys/kern/kern_shutdown.c:636 #4 0x806fcfa9 in trap_fatal (frame=0x9, eva=Variable eva is not available. ) at /usr/src/sys/amd64/amd64/trap.c:857 #5 0x806fd554 in trap (frame=0xff80d89ac610) at /usr/src/sys/amd64/amd64/trap.c:599 #6 0x806e81bf in calltrap () at /usr/src/sys/amd64/amd64/exception.S:228 #7 0x802c6f15 in AcpiUtUpdateObjectReference ( Object=0xfe0001824a80, Action=0) at /usr/src/sys/contrib/dev/acpica/utilities/utdelete.c:563 #8 0x802b77a4 in AcpiExResolveNodeToValue ( ObjectPtr=0xfe0001a2c2e0, WalkState=0xfe0001a2c000) at /usr/src/sys/contrib/dev/acpica/executer/exresnte.c:184 #9 0x802b7ad3 in AcpiExResolveToValue (StackPtr=0xfe0001a2c2e0, WalkState=0xfe0001a2c000) at /usr/src/sys/contrib/dev/acpica/executer/exresolv.c:124 #10 0x802ac433 in AcpiDsEvaluateNamePath (WalkState=0xfe0001a2c000) at /usr/src/sys/contrib/dev/acpica/dispatcher/dsutils.c:886 ---Type return to continue, or q return to quit--- #11 0x802aceef in AcpiDsExecEndOp (WalkState=0xfe0001a2c000) at /usr/src/sys/contrib/dev/acpica/dispatcher/dswexec.c:436 #12 0x802c05ba in AcpiPsParseLoop (WalkState=0xfe0001a2c000) at /usr/src/sys/contrib/dev/acpica/parser/psloop.c:1249 #13 0x802c10a8 in AcpiPsParseAml (WalkState=0xfe0001a2c000) at /usr/src/sys/contrib/dev/acpica/parser/psparse.c:525 #14 0x802c1d45 in AcpiPsExecuteMethod (Info=0xfe0033df8540) at /usr/src/sys/contrib/dev/acpica/parser/psxface.c:368 #15 0x802bb784 in AcpiNsEvaluate (Info=0xfe0033df8540) at /usr/src/sys/contrib/dev/acpica/namespace/nseval.c:193 #16 0x802bec91 in AcpiEvaluateObject (Handle=0xfe00017f7b80, Pathname=0x8078229f _BST, ExternalParams=0x0, ReturnBuffer=0xff80d89ac960) at /usr/src/sys/contrib/dev/acpica/namespace/nsxfeval.c:289 #17 0x80309802 in acpi_cmbat_get_bst (arg=Variable arg is not available. ) at /usr/src/sys/dev/acpica/acpi_cmbat.c:257 #18 0x80309af8 in acpi_cmbat_bst (dev=0xfe0001936400, bstp=0xfe008b319400) at /usr/src/sys/dev/acpica/acpi_cmbat.c:418 #19 0x8045bd22 in devfs_ioctl_f (fp=0xfe001ba256e0, com=3231990289, data=Variable data is not available. ) at /usr/src/sys/fs/devfs/devfs_vnops.c:757 #20 0x8053a23d in kern_ioctl (td=0xfe00039ae8e0, fd=Variable fd is not available. ) at file.h:293 #21 0x8053a4ad in sys_ioctl (td=0xfe00039ae8e0, uap=0xff80d89acb70) at /usr/src/sys/kern/sys_generic.c:691 ---Type return to continue, or q return to quit--- #22 0x806fc902 in amd64_syscall (td=0xfe00039ae8e0, traced=0) at subr_syscall.c:135 #23 0x806e84a7 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:387 #24 0x000801d89c5c in ?? () Previous frame inner to this frame (corrupt stack?) Before the panic, a lot of ACPI Error appears in dmesg like that : ACPI Error: Method execution failed [\\_SB_.BAT0._UID] (Node 0xfe00017f7b00), AE_AML_NO_OPERAND (20110527/uteval-113) ACPI Error: No object attached to node 0xfe00017f7b00 (20110527/exresnte-139) ACPI Error: Method execution failed [\\_SB_.BAT0._UID] (Node 0xfe00017f7b00), AE_AML_NO_OPERAND (20110527/uteval-113) ACPI Error: No object attached to node 0xfe00017f7b00 (20110527/exresnte-139) This happens on 9.1-RELEASE amd64 Cheers, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to
Re: thinkpad and synaptics
If you plan to use the Xorg synaptics driver you *must* remove moused_enable from rc.conf, Xorg can't use the synaptics mouse if the moused already sits on the /dev/psm0 device. This is not really well documented, tough. I've sent a PR to document pkg-message for xf85-input-synaptics but it has never been checked, http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/148591 See the documentation in the patch.txt, it should works. Regards 2012/12/17 Zoran Kolic zko...@sbb.rs As first, thanks for answer. Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard Option AutoAddDevices Off EndSection [...] Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection In rc.conf: moused_enable=YES in loader.conf: hw.psm.synaptics_support=1 OK. I know it is writen zillion times and it still does not work for me. It is thinkpad e320, amd64, 9.1, kms. I had a lot of problems regarding fonts and non working vertical scroll on the pad. What I did: put synaptics_support run moused changed xorg.conf in a million ways This xorg.conf is similar to mine. I also have psm0 in /dev/ spite I have no loader.conf option right now. I assume that installing xf86 synaptics did the job. Simply, it does not scroll, with this configuration. I might need to rest a day or two, to sleep and to read more. Best regards and, once more, thanks all for help. 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 -- Demelier David ___ 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: Will we get a RELEASE-9.1 for Christmas?
Is the SVN revision gonna disappear from the uname -a output ? I hope. cheers, 2012/12/12 Mark Linimon lini...@lonesome.com On Tue, Dec 11, 2012 at 11:18:44AM -0500, Mark Saad wrote: the ISO are on the master server The release is official when, and only when, a signed email from the release engineering team says that it is. In a past release cycle there was indeed a last-minute fix that had to be made after the ISO had already started propogating. mcl ___ 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 -- Demelier David ___ 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: Will we get a RELEASE-9.1 for Christmas?
You're right, but one who install a 9.1-RELEASE from iso will obviously still have the same SVN revision, of course it is still great when following -STABLE. 2012/12/12 Pete French petefre...@ingresso.co.uk Is the SVN revision gonna disappear from the uname -a output ? I hope. This comment surprises me - having the svn revision there is one of the best thigns about moving to svn from csup for me. I can look at a running machine, and know how to chekcout precisely the code is was built from. Very useful. -pete. -- Demelier David ___ 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: Cannot cross compile 9.1-RELEASE to i386
On 06/12/2012 22:26, David Demelier wrote: Hello, I'm trying to make as small as possible a FreeBSD installation for my Alix 2D2, I did it with 8.1-RELEASE so, a lot of changes appeared I think. I'm trying to make TARGET_ARCH=i386 buildworld and it fails at: === sys/boot/i386/gptboot (all) Warning: Object directory not changed from original /usr/src/sys/boot/i386/gptboot cc -DBOOTPROG=\gptboot\ -O1 -DGPT -DUFS1_AND_UFS2 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/gptboot/../../common -I/usr/src/sys/boot/i386/gptboot/../common -I/usr/src/sys/boot/i386/gptboot/../btx/lib -I. -I/usr/src/sys/boot/i386/gptboot/../boot2 -I/usr/src/sys/boot/i386/gptboot/../../.. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -c gptldr.S ld -static -N --gc-sections -nostdlib -e start -Ttext 0x7c00 -o gptldr.out gptldr.o objcopy -S -O binary gptldr.out gptldr.bin make: don't know how to make /usr/src/sys/boot/i386/gptboot/../btx/lib/crt0.o. Stop *** [all] Error code 2 Stop in /usr/src/sys/boot/i386. *** [all] Error code 1 Stop in /usr/src/sys/boot. *** [all] Error code 1 Stop in /usr/src/sys. *** [sys.all__D] Error code 1 Stop in /usr/src. *** [everything] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. My src.conf is like that: WITHOUT_JAIL=yes WITHOUT_ACPI=yes WITHOUT_AMD=yes WITHOUT_APM=yes WITHOUT_ATM=yes WITHOUT_AUDIT=yes WITHOUT_AUTHPF=yes WITHOUT_BIND=yes WITHOUT_BLUETOOTH=yes WITHOUT_BSNMP=yes WITHOUT_CALENDAR=yes WITHOUT_CDDL=yes WITHOUT_CLANG=yes WITHOUT_CTM=yes WITHOUT_CVS=yes WITHOUT_CXX=yes WITHOUT_DICT=yes WITHOUT_EXAMPLES=yes WITHOUT_FDT=yes WITHOUT_FLOPPY=yes WITHOUT_FREEBSD_UPDATE=yes WITHOUT_GAMES=yes WITHOUT_GCOV=yes WITHOUT_GDB=yes WITHOUT_HTML=yes WITHOUT_INFO=yes WITHOUT_IPFILTER=yes WITHOUT_IPFW=yes WITHOUT_IPX=yes WITHOUT_JAIL=yes WITHOUT_KERBEROS=yes WITHOUT_KERNEL_SYMBOLS=yes WITHOUT_LOCATE=yes WITHOUT_MAKE=yes WITHOUT_NDIS=yes WITHOUT_NIS=yes WITHOUT_NLS=yes WITHOUT_OBJC=yes WITHOUT_PAM=yes WITHOUT_PORTSNAP=yes WITHOUT_PPP=yes WITHOUT_RCMDS=yes WITHOUT_SHAREDOCS=yes WITHOUT_SYSINSTALL=yes Did I added a WITHOUT_ that could break or is it a cross-compile issue? (Host version is amd64). Cheers, The problem was an old CPUTYPE defined in the make.conf, working now :) ___ 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
Cannot cross compile 9.1-RELEASE to i386
Hello, I'm trying to make as small as possible a FreeBSD installation for my Alix 2D2, I did it with 8.1-RELEASE so, a lot of changes appeared I think. I'm trying to make TARGET_ARCH=i386 buildworld and it fails at: === sys/boot/i386/gptboot (all) Warning: Object directory not changed from original /usr/src/sys/boot/i386/gptboot cc -DBOOTPROG=\gptboot\ -O1 -DGPT -DUFS1_AND_UFS2 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/gptboot/../../common -I/usr/src/sys/boot/i386/gptboot/../common -I/usr/src/sys/boot/i386/gptboot/../btx/lib -I. -I/usr/src/sys/boot/i386/gptboot/../boot2 -I/usr/src/sys/boot/i386/gptboot/../../.. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -std=gnu99 -c gptldr.S ld -static -N --gc-sections -nostdlib -e start -Ttext 0x7c00 -o gptldr.out gptldr.o objcopy -S -O binary gptldr.out gptldr.bin make: don't know how to make /usr/src/sys/boot/i386/gptboot/../btx/lib/crt0.o. Stop *** [all] Error code 2 Stop in /usr/src/sys/boot/i386. *** [all] Error code 1 Stop in /usr/src/sys/boot. *** [all] Error code 1 Stop in /usr/src/sys. *** [sys.all__D] Error code 1 Stop in /usr/src. *** [everything] Error code 1 Stop in /usr/src. *** [buildworld] Error code 1 Stop in /usr/src. My src.conf is like that: WITHOUT_JAIL=yes WITHOUT_ACPI=yes WITHOUT_AMD=yes WITHOUT_APM=yes WITHOUT_ATM=yes WITHOUT_AUDIT=yes WITHOUT_AUTHPF=yes WITHOUT_BIND=yes WITHOUT_BLUETOOTH=yes WITHOUT_BSNMP=yes WITHOUT_CALENDAR=yes WITHOUT_CDDL=yes WITHOUT_CLANG=yes WITHOUT_CTM=yes WITHOUT_CVS=yes WITHOUT_CXX=yes WITHOUT_DICT=yes WITHOUT_EXAMPLES=yes WITHOUT_FDT=yes WITHOUT_FLOPPY=yes WITHOUT_FREEBSD_UPDATE=yes WITHOUT_GAMES=yes WITHOUT_GCOV=yes WITHOUT_GDB=yes WITHOUT_HTML=yes WITHOUT_INFO=yes WITHOUT_IPFILTER=yes WITHOUT_IPFW=yes WITHOUT_IPX=yes WITHOUT_JAIL=yes WITHOUT_KERBEROS=yes WITHOUT_KERNEL_SYMBOLS=yes WITHOUT_LOCATE=yes WITHOUT_MAKE=yes WITHOUT_NDIS=yes WITHOUT_NIS=yes WITHOUT_NLS=yes WITHOUT_OBJC=yes WITHOUT_PAM=yes WITHOUT_PORTSNAP=yes WITHOUT_PPP=yes WITHOUT_RCMDS=yes WITHOUT_SHAREDOCS=yes WITHOUT_SYSINSTALL=yes Did I added a WITHOUT_ that could break or is it a cross-compile issue? (Host version is amd64). Cheers, ___ 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
Prevent starting network on usbus
Hello, Since I've updated to 9.0-RELEASE, the network rc script starts network from usbus0 to usbus7. I don't think I need them. How can I disable them ? Cheers, -- Demelier David ___ 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: Prevent starting network on usbus
2012/1/13 N.J. Mann n...@njm.me.uk: In message CAO+PfDfD0nMSshpybMzKrVSBQKFyp=c6sjmmplpit1ihw_b...@mail.gmail.com, David Demelier (demelier.da...@gmail.com) wrote: Since I've updated to 9.0-RELEASE, the network rc script starts network from usbus0 to usbus7. I don't think I need them. How can I disable them ? echo hw.usb.no_pf=1 /boot/loader.conf Thanks, it works. This is the second USB tunable I know now. I know hw.usb.no_boot_wait too but I can't find any man pages that talk about them. Is it documented somewhere? Cheers, Cheers, Nick. -- -- Demelier David ___ 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
make installworld fails (touch not found)
Hi, Today I pulled up the last changes for RELENG_8 branch and I got an error when doing the make installworld target : === gnu/usr.bin/texinfo/doc (install) install-info --quiet --defsection=Miscellaneous --defentry= info.info /usr/share/info/dir install-info --quiet --defsection=Miscellaneous --defentry= info-stnd.info /usr/share/info/dir install-info --quiet --defsection=Miscellaneous --defentry= texinfo.info /usr/share/info/dir install -o root -g wheel -m 444 info.info.gz info-stnd.info.gz texinfo.info.gz /usr/share/info === include (install) creating osreldate.h from newvers.sh touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 Anyone having the same issue? Cheers, -- David Demelier ___ 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: make installworld fails (touch not found)
On 14/09/2011 19:10, Boris Kochergin wrote: On 09/14/11 12:37, Kevin Oberman wrote: On Wed, Sep 14, 2011 at 9:09 AM, David Demelier demelier.da...@gmail.com wrote: Hi, Today I pulled up the last changes for RELENG_8 branch and I got an error when doing the make installworld target : === gnu/usr.bin/texinfo/doc (install) install-info --quiet --defsection=Miscellaneous --defentry= info.info /usr/share/info/dir install-info --quiet --defsection=Miscellaneous --defentry= info-stnd.info /usr/share/info/dir install-info --quiet --defsection=Miscellaneous --defentry= texinfo.info /usr/share/info/dir install -o root -g wheel -m 444 info.info.gz info-stnd.info.gz texinfo.info.gz /usr/share/info === include (install) creating osreldate.h from newvers.sh touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 Anyone having the same issue? Check the setting of the date/time on the system. I've also seen this happen when my /usr/src was out of sync with /usr/obj. -Boris Thanks that was the problem! -- David Demelier ___ 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: snd_hda : sometimes sound sometimes not
On 28/05/2011 15:46, Jeremy Chadwick wrote: On Sat, May 28, 2011 at 03:30:26PM +0200, David Demelier wrote: On 12/05/2011 08:47, David Demelier wrote: Hello, I don't know if there is a lot of changes in the snd_hda driver in the -STABLE branch but since I upgraded to it sometimes I have sound and sometimes not. The mixer are exactly the same when these event occurs. This happened this morning. After booting I do not have any sound. I rebooted and suddenly I've got sound again... I only tweak snd_hda(4) for a pin sense on the front panel (it has no sound neither) So I added in /boot/devices.hints : hint.hdac.1.cad0.nid27.config=as=1 seq=15 And there's the both dmesg ok.txt when sound is here and not.txt when there isn't as you can see there is no difference related to the hda driver. http://markand.malikania.fr/ok.txt http://markand.malikania.fr/nok.txt I'm guessing something. My laptop has a mute shortcut, if I press it at the BIOS stage I will not have sound neither thus is it possible that my chipset is muted from anything? Cheers, Sorry to cross-post again, but I just wanted to tell you that the problem disappeared in -CURRENT so now I just how the unknown bogus code will be MFC before 8.3-RELEASE Unless someone can chime in with details of the commits which changed, assuming the magic change will be MFC'd is a bad one. It's safe to say that when 8.3-RELEASE comes out if this problem haunts you again, you will be mailing the list about it, and this cycle will continue until 9.0-RELEASE comes out. Does any developer/committer have familiarity with this issue and have some ideas as to what may have changed in CURRENT that addresses David's issue? And if so, can that code be MFC'd safely or patches provided to David for RELENG_8 that he can try out? I'm CC'ing mav@ here (snd_hda(4) says he's one of the authors), although he may not have any knowledge of the code which may need to be MFC'd. He may be able to point us to who has a better idea though. No worries Jeremy but thanks for your interest you seems to be the only one who believed my problem. The problem has been fixed in -STABLE, I don't know where but it works now -- David Demelier ___ 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: snd_hda : sometimes sound sometimes not
On 12/05/2011 08:47, David Demelier wrote: Hello, I don't know if there is a lot of changes in the snd_hda driver in the -STABLE branch but since I upgraded to it sometimes I have sound and sometimes not. The mixer are exactly the same when these event occurs. This happened this morning. After booting I do not have any sound. I rebooted and suddenly I've got sound again... I only tweak snd_hda(4) for a pin sense on the front panel (it has no sound neither) So I added in /boot/devices.hints : hint.hdac.1.cad0.nid27.config=as=1 seq=15 And there's the both dmesg ok.txt when sound is here and not.txt when there isn't as you can see there is no difference related to the hda driver. http://markand.malikania.fr/ok.txt http://markand.malikania.fr/nok.txt I'm guessing something. My laptop has a mute shortcut, if I press it at the BIOS stage I will not have sound neither thus is it possible that my chipset is muted from anything? Cheers, Sorry to cross-post again, but I just wanted to tell you that the problem disappeared in -CURRENT so now I just how the unknown bogus code will be MFC before 8.3-RELEASE Cheers, -- David Demelier ___ 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: snd_hda : sometimes sound sometimes not
On 12/05/2011 08:47, David Demelier wrote: Hello, I don't know if there is a lot of changes in the snd_hda driver in the -STABLE branch but since I upgraded to it sometimes I have sound and sometimes not. The mixer are exactly the same when these event occurs. This happened this morning. After booting I do not have any sound. I rebooted and suddenly I've got sound again... I only tweak snd_hda(4) for a pin sense on the front panel (it has no sound neither) So I added in /boot/devices.hints : hint.hdac.1.cad0.nid27.config=as=1 seq=15 And there's the both dmesg ok.txt when sound is here and not.txt when there isn't as you can see there is no difference related to the hda driver. http://markand.malikania.fr/ok.txt http://markand.malikania.fr/nok.txt I'm guessing something. My laptop has a mute shortcut, if I press it at the BIOS stage I will not have sound neither thus is it possible that my chipset is muted from anything? Cheers, I will try to downgrade 8.2-RELEASE and then update the kernel code to more specific version to see where the regression happens. How can I try this step by step ? Should I try to svn / cvs day per day? Cheers, -- David Demelier ___ 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: snd_hda : sometimes sound sometimes not
On 16/05/2011 18:32, Clifton Royston wrote: On Mon, May 16, 2011 at 06:22:16PM +0200, David Demelier wrote: On 12/05/2011 08:47, David Demelier wrote: Hello, I don't know if there is a lot of changes in the snd_hda driver in the -STABLE branch but since I upgraded to it sometimes I have sound and sometimes not. The mixer are exactly the same when these event occurs. This happened this morning. After booting I do not have any sound. I rebooted and suddenly I've got sound again... I only tweak snd_hda(4) for a pin sense on the front panel (it has no sound neither) So I added in /boot/devices.hints : hint.hdac.1.cad0.nid27.config=as=1 seq=15 And there's the both dmesg ok.txt when sound is here and not.txt when there isn't as you can see there is no difference related to the hda driver. http://markand.malikania.fr/ok.txt http://markand.malikania.fr/nok.txt I'm guessing something. My laptop has a mute shortcut, if I press it at the BIOS stage I will not have sound neither thus is it possible that my chipset is muted from anything? Cheers, I will try to downgrade 8.2-RELEASE and then update the kernel code to more specific version to see where the regression happens. How can I try this step by step ? Should I try to svn / cvs day per day? At least do a binary search via svn revision on the regression: That is, look up the current revision of stable you are on, look up the revision of the 8.2-RELEASE branch point, and update to halfway in between. If it has the problem, go halfway between that and the 8.2-RELEASE, if it doesn't, go halfway between that and your current revision, and so on. This approach will cut the number of updates and builds you need to try to the logarithm of the number of distinct revisions. My impression is that it's so obvious to some people they never mention it and to others it's a complete revelation. -- Clifton Hi, I downloaded RELENG_8 src/ via cvs because I usually used csup instead. I absolutely have no idea how to find the middle between 8.2-RELEASE and my 8-STABLE revision though :-( Cheers, -- David Demelier ___ 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: snd_hda : sometimes sound sometimes not
On 15/05/2011 12:15, Marcin Wisnicki wrote: On Thu, 12 May 2011 08:47:13 +0200, David Demelier wrote: Hello, I don't know if there is a lot of changes in the snd_hda driver in the -STABLE branch but since I upgraded to it sometimes I have sound and sometimes not. Try disabling MSI in loader.conf: hw.pci.enable_msix=0 hw.pci.enable_msi=0 and see if it works. Is this safe? I saw this in the man snd_hda hint.hdac.%d.msi Controls MSI (Message Signaled Interrupts) support. Could I use this instead? ___ 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 -- David Demelier ___ 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
snd_hda : sometimes sound sometimes not
Hello, I don't know if there is a lot of changes in the snd_hda driver in the -STABLE branch but since I upgraded to it sometimes I have sound and sometimes not. The mixer are exactly the same when these event occurs. This happened this morning. After booting I do not have any sound. I rebooted and suddenly I've got sound again... I only tweak snd_hda(4) for a pin sense on the front panel (it has no sound neither) So I added in /boot/devices.hints : hint.hdac.1.cad0.nid27.config=as=1 seq=15 And there's the both dmesg ok.txt when sound is here and not.txt when there isn't as you can see there is no difference related to the hda driver. http://markand.malikania.fr/ok.txt http://markand.malikania.fr/nok.txt I'm guessing something. My laptop has a mute shortcut, if I press it at the BIOS stage I will not have sound neither thus is it possible that my chipset is muted from anything? Cheers, -- David Demelier ___ 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: .zfs directory: snapshot: Bad file descriptor
On 21/03/2011 12:23, Olaf Seibert wrote: On my production system (still 8.1, I haven't had time yet to upgrade to 8.2) I have a ZFS. Nightly I make snapshots of each filesystem in it. Suddenly, one of the file systems has no snapshots any more: $ ls -l /tank/vol-fourquid-1/.zfs ls: snapshot: Bad file descriptor total 0 $ ls -l /tank/vol-fourquid-1/.zfs/snapshot ls: /tank/vol-fourquid-1/.zfs/snapshot: Bad file descriptor Snapshots in other file systems seem ok, for example: $ ls -l /home/local/.zfs total 0 dr-xr-xr-x 9 root wheel 9 Oct 21 2009 snapshot/ $ ls -l /home/local/.zfs/snapshot/ total 32 drwxr-xr-x 48 root vb 48 Apr 19 2010 friday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 monday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 saturday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 sunday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 thursday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 tuesday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 wednesday/ zpool status thinks all is ok: $ zpool status pool: tank state: ONLINE status: The pool is formatted using an older on-disk format. The pool can still be used, but some features are unavailable. action: Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. scrub: none requested config: NAMESTATE READ WRITE CKSUM tankONLINE 0 0 0 raidz2ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 errors: No known data errors How worried should I be about corruption anyway, say if I unmount and remount the affected file system? -Olaf. I don't know how to manage ZFS filesystem but usually on UFS file system when you have a bad file descriptor you must run fsck(8) manually to check up the disk. Cheers, -- David Demelier ___ 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: FBSD 8.2R does not probe sound card
On 18/03/2011 17:45, Gua Chung Lim wrote: Thank you for your kind responses. Though I don't understand much what you said, I shall give you further info. pcm1 device is the HDMI audio output on your graphics card. My only suggestion here is to play with the sysctl hw.snd.default_unit: # tail -n 1 /etc/sysctl.conf hw.snd.default_unit=1 (I left /boot/loader.conf untouched.) # shutdown -r now after reboot # kldload snd_driver # sysctl -d hw.snd.default_unit hw.snd.default_unit: default sound device # sysctl hw.snd.default_unit hw.snd.default_unit: 0 The speakers are still quiet. I wonder why it is still 0, even if /etc/sysctl.conf set it to 1. What programs are you using to test the sound output? Just repeat backspaces at the blank command prompt. guacl@bsdhost:~%BSBSBS... If sound driver is functioning, the speakers should echo. Note that the internal speaker (inside the case) does echo, for sure. Thank you. Please add snd_hda_load=YES in /boot/loader.conf, you won't need to kldload manually. -- David Demelier ___ 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: Sense fetching [Was: cdrtools /devel ...]
On 08/03/2011 16:15, Brandon Gooch wrote: On Tue, Mar 8, 2011 at 8:29 AM, Jakub Lachjakub_l...@mailplus.pl wrote: Hello. Just ensuring that this issue would not be forgotten, If I recall correctly, without added patches one cannot burn CD with cdrtools, quite a problem for media burning suite ;) best regards, - Jakub Lach mav@ is working on graid(4), a replacement for ataraid(4) using the GEOM framework. This effort has taken precedence over a few outstanding patches he was working on, but he will eventually come back to it :) Perhaps another developer will step up and continue the work on the patches: http://people.freebsd.org/~mav/sense/ -Brandon ___ 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 I hope because I want to use ahci on my machines! :-) -- David Demelier ___ 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
ALPS GlidePoint not detected on dell inspiron
Hello,
A friend has a DELL Inspiron 1525 with an ALPS GlidePoint touchpad. We
have added hw.psm.synaptics_support=1 in his /boot/loader.conf but it
still detected as a standard ps2 mouse.
Looking at sys/dev/atkbdc/psm.c :
461 { MOUSE_MODEL_GLIDEPOINT, /* ALPS GlidePoint */
462 0xc0, MOUSE_PS2_PACKETSIZE, enable_aglide },
I'm guessing if his touchpad has 0xc0 as model, how can I check this?
For the moment there is this in his dmesg:
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: [ITHREAD]
psm0: model GlidePoint, device ID 0
Cheers,
--
Demelier David
___
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
Problem with battery ACPI
Hello, My sucky laptop does not make any noise usually, but tonight it started to do so : Jan 17 21:04:32 Melon kernel: ACPI Error: No object attached to node 0xff00014f4780 (20100331/exresnte-211) Jan 17 21:04:32 Melon kernel: ACPI Error (uteval-0318): Method execution failed [\_SB_.BAT0._UID] (Node 0xff00014f4780), AE_AML_NO_OPERAND Jan 17 21:04:36 Melon wpa_supplicant[362]: CTRL-EVENT-SCAN-RESULTS Jan 17 21:04:39 Melon kernel: ACPI Error: No object attached to node 0xff00014f4780 (20100331/exresnte-211) Jan 17 21:04:39 Melon kernel: ACPI Error (uteval-0318): Method execution failed [\_SB_.BAT0._UID] (Node 0xff00014f4780), AE_AML_NO_OPERAND Jan 17 21:04:39 Melon kernel: ACPI Error: No object attached to node 0xff00014f4780 (20100331/exresnte-211) Jan 17 21:04:39 Melon kernel: ACPI Error: ACPI Error (uteval-0318): No object attached to node 0xff00014f4780Method execution failed (20100331/exresnte-211)[\_SB_.BAT0._UID] (Node 0xff00014f4780) Jan 17 21:04:39 Melon kernel: ACPI Error (uteval-0318): , AE_AML_NO_OPERANDMethod execution failed Jan 17 21:04:39 Melon kernel: [\_SB_.BAT0._UID] (Node 0xff00014f4780), AE_AML_NO_OPERAND Jan 17 21:04:39 Melon kernel: ACPI Error: No object attached to node 0xff00014f4780 (20100331/exresnte-211) Jan 17 21:04:39 Melon kernel: ACPI Error (uteval-0318): ACPI Error: Method Nexeocu tioon bfajileecdt attached to node 0xff00014f4780[\_SB_.BAT0._UID] (Node 0xff00014f4780) (20100331/exresnte-211), AE_AML_NO_OPERAND Jan 17 21:04:39 Melon kernel: ACPI Error (uteval-0318): Jan 17 21:04:39 Melon kernel: Method execution failed [\_SB_.BAT0._UID] (Node 0xff00014f4780), AE_AML_NO_OPERAND Jan 17 21:04:39 Melon kernel: ACPI Error: No object attached to node 0xff00014f4780 (20100331/exresnte-211) Jan 17 21:04:39 Melon kernel: ACPI Error (uteval-0318): Method execution failed [\_SB_.BAT0._UID] (Node 0xff00014f4780), AE_AML_NO_OPERAND I don't know what does it mean, I only know that HP SUCKS and DO NOT BUY HP ANYMORE. If anyone knows ;-) Cheers, -- David Demelier ___ 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: ath0: lot of bad series hwrate and AH_SUPPORT_AR5416
On 30/11/2010 00:25, Adrian Chadd wrote: (I should get me an AR9285 to test with at some point.) On 29 November 2010 18:52, David DEMELIERdemelier.da...@gmail.com wrote: ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 That's ath_rate_sample saying I don't know about that hardware rate, but it transmitted successfully! So something queued up a patcket at that hwrate. 0x1B is CCK_1MB_L - that should be fine in 11bg? Or is this somehow running in 11A mode? Would you please paste 'ifconfig wlan0' here? mark...@melon ~ $ ifconfig wlan0 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether c4:17:fe:c4:14:b9 inet 130.79.183.186 netmask 0xfc00 broadcast 130.79.183.255 media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11g status: associated ssid osiris-sec channel 11 (2462 MHz 11g) bssid 00:26:99:23:69:23 regdomain 106 indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit TKIP 3:128-bit txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL bintval 102 I also don't understand why the option AH_SUPPORT_AR5416 is needed in kernel, I found this http://lists.freebsd.org/pipermail/freebsd-current/2009-May/006417.html and it should include it if the driver needs it, isn't it? Here my kernel won't build if I remove it so I have : options AH_SUPPORT_AR5416 device ath device ath_hal device ath_rate_sample Would you please file a PR for that and email me the PR number? PR as :kern/152736 Thanks, adrian ___ 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: ath0: lot of bad series hwrate and AH_SUPPORT_AR5416
2010/12/1 Adrian Chadd adr...@freebsd.org: On 1 December 2010 18:11, David Demelier demelier.da...@gmail.com wrote: Or is this somehow running in 11A mode? Would you please paste 'ifconfig wlan0' here? mark...@melon ~ $ ifconfig wlan0 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether c4:17:fe:c4:14:b9 inet 130.79.183.186 netmask 0xfc00 broadcast 130.79.183.255 media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11g status: associated ssid osiris-sec channel 11 (2462 MHz 11g) bssid 00:26:99:23:69:23 regdomain 106 indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit TKIP 3:128-bit txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL bintval 102 Ok, so it's in 11bg mode. I'd have to do some digging to try and understand what's busted. CAn you please do this: sysctl dev.ath.0.sample_stats=1 Oww, mark...@melon ~ $ sudo sysctl dev.ath.0.sample_stats=1 dev.ath.0.sample_stats: 0 - 0 then look at dmesg; it'll dump the sample rate statistics out there. Also, please create a PR for this. I'd like to squish any obvious bugs here before I commit any new stuff. :) Adrian -- Demelier David ___ 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: ath0: lot of bad series hwrate and AH_SUPPORT_AR5416
2010/12/1 David DEMELIER demelier.da...@gmail.com: 2010/12/1 Adrian Chadd adr...@freebsd.org: On 1 December 2010 18:11, David Demelier demelier.da...@gmail.com wrote: Or is this somehow running in 11A mode? Would you please paste 'ifconfig wlan0' here? mark...@melon ~ $ ifconfig wlan0 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether c4:17:fe:c4:14:b9 inet 130.79.183.186 netmask 0xfc00 broadcast 130.79.183.255 media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11g status: associated ssid osiris-sec channel 11 (2462 MHz 11g) bssid 00:26:99:23:69:23 regdomain 106 indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit TKIP 3:128-bit txpower 20 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL bintval 102 Ok, so it's in 11bg mode. I'd have to do some digging to try and understand what's busted. CAn you please do this: sysctl dev.ath.0.sample_stats=1 Oww, mark...@melon ~ $ sudo sysctl dev.ath.0.sample_stats=1 dev.ath.0.sample_stats: 0 - 0 [00:26:99:23:69:23] refcnt 4 static_rix -1 ratemask 0xfc8 [ 250] cur rix 10 since switch: packets 79 ticks 6548703 [ 250] last sample 7 cur sample -1 packets sent 390165 [ 250] packets since sample 3 sample tt 524 [1600] cur rix 10 since switch: packets 4 ticks 6532752 [1600] last sample 11 cur sample -1 packets sent 802 [1600] packets since sample 10 sample tt 644 [11: 250]1:1(100%) T1 F0 avg 1103 last 458798 [12: 250] 720:719 ( 99%) T 791 F0 avg 728 last 2022 [12:1600]1:0( 0%) T5 F1 avg 1480 last 458798 [18: 250] 4381:4381 (100%) T 4785 F0 avg 634 last 379 [24: 250]16630:16627( 99%) T18102 F0 avg 622 last 891 [24:1600] 14:11 ( 78%) T 30 F1 avg 1125 last 238025 [36: 250]90373:90368( 99%) T98250 F0 avg 514 last 877 [36:1600] 125:120 ( 96%) T 168 F0 avg 973 last 32568 [48: 250] 117104:117092 ( 99%) T 128546 F0 avg 590 last 362 [48:1600] 198:186 ( 93%) T 280 F0 avg 690 last 16211 [54: 250] 160999:160989 ( 99%) T 176303 F0 avg 529 last 820 [54:1600] 495:485 ( 97%) T 609 F0 avg 986 last 20730 ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x1 Ah I didn't see there was output. then look at dmesg; it'll dump the sample rate statistics out there. Also, please create a PR for this. I'd like to squish any obvious bugs here before I commit any new stuff. :) Adrian -- Demelier David -- Demelier David ___ 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.1-RELEASE: snd_hda works as module only, suspend/resume leaves display off
2010/11/15 Stefan Walter ste...@freebsd.org: Hi, I've been using 8.1-RELEASE on this desktop machine for a few months already, but only now found the time to look at a couple of problems with snd_hda and suspend/resume it still has. Maybe someone here has hints to fix them - I'd be grateful to hear them. Audio with snd_hda(4) works, but only if loaded as a module AND only if I load the module AFTER booting. If I compile it into the kernel or add snd_hda_load=YES to /boot/loader.conf, dmesg shows the following: hdac0: HDA Codec #0: ATI RS690/780 HDMI pcm0: HDA ATI RS690/780 HDMI PCM #0 HDMI at cad 0 nid 1 on hdac0 hdac1: HDA Codec #0: Realtek ALC885 pcm1: HDA Realtek ALC885 PCM #0 Analog at cad 0 nid 1 on hdac1 pcm2: HDA Realtek ALC885 PCM #1 Analog at cad 0 nid 1 on hdac1 pcm3: HDA Realtek ALC885 PCM #2 Digital at cad 0 nid 1 on hdac1 mixer(8) shows: Mixer vol is currently set to 75:75 Mixer pcm is currently set to 75:75 There is no audio in that case. Unloading and reloading the module (or just loading the module manually after the boot process) logs: hdac0: ATI SB600 High Definition Audio Controller mem 0xfe024000-0xfe027fff irq 16 at device 20.2 on pci0 hdac0: HDA Driver Revision: 20100226_0142 hdac0: [ITHREAD] hdac0: HDA Codec #0: Realtek ALC885 hdac1: ATI (Unknown) High Definition Audio Controller mem 0xfdffc000-0xfdff irq 19 at device 5.1 on pci1 hdac1: HDA Driver Revision: 20100226_0142 hdac1: [ITHREAD] hdac1: HDA Codec #0: ATI RS690/780 HDMI pcm0: HDA Realtek ALC885 PCM #0 Analog at cad 0 nid 1 on hdac0 pcm1: HDA Realtek ALC885 PCM #1 Analog at cad 0 nid 1 on hdac0 pcm2: HDA Realtek ALC885 PCM #2 Digital at cad 0 nid 1 on hdac0 pcm3: HDA ATI RS690/780 HDMI PCM #0 HDMI at cad 0 nid 1 on hdac1 mixer then shows: Mixer vol is currently set to 75:75 Mixer pcm is currently set to 75:75 Mixer speaker is currently set to 75:75 Mixer line is currently set to 75:75 Mixer mic is currently set to 0:0 Mixer mix is currently set to 0:0 Mixer rec is currently set to 75:75 Mixer igain is currently set to 0:0 Audio then seems to work fine. (Plugging earphones into the computer's case's front plugs doesn't do anything, though - audio still comes from the speakers attached to the plug at the back of the case. Any ideas about that?) Loading snd_hda from a startup script would probably work, but I guess that's not the way it was meant to work. The other problem is with suspend/resume: Suspend To RAM (S3) works by using acpiconf -s 3, and pushing the power button wakes the system up again. Everything seems to work, only the LCD monitor remains off. (There also seem to be occasional cases in which the keyboard doesn't work any more, but I haven't really looked at that, yet. Usually, the system comes back up properly.) Loading dpms(4) doesn't seem to make a difference. The only way to turn the display on again seems to be typing shutdown -r now blindly. Regards, Stefan Same here, if I have snd_hda directly in kernel, screen doesn't wake up with or without hw.acpi.reset_video=1. I don't like much modules since it takes some time to load at boot so if a fix could be made it will be great.. Cheers, -- Demelier David ___ 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.1-RELEASE: snd_hda works as module only, suspend/resume leaves display off
2010/12/1 Adam Vande More amvandem...@gmail.com: On Wed, Dec 1, 2010 at 3:49 PM, David DEMELIER demelier.da...@gmail.com wrote: Same here, if I have snd_hda directly in kernel, screen doesn't wake up with or without hw.acpi.reset_video=1. I don't like much modules since it takes some time to load at boot Are you booting from a tape drive or something? -- Adam Vande More No, but loading if you convert your kernel into modules, it takes a lot of time to load every modules. PC-BSD does it and it's slow. -- Demelier David ___ 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
ath0: lot of bad series hwrate and AH_SUPPORT_AR5416
Hi, I just bought an Atheros 9285 for my laptop, I love it but there is a lot of this in my dmesg : ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 ath0: bad series3 hwrate 0x1b, tries 2 ts_status 0x0 I also don't understand why the option AH_SUPPORT_AR5416 is needed in kernel, I found this http://lists.freebsd.org/pipermail/freebsd-current/2009-May/006417.html and it should include it if the driver needs it, isn't it? Here my kernel won't build if I remove it so I have : options AH_SUPPORT_AR5416 device ath device ath_hal device ath_rate_sample Kind regards, -- Demelier David ___ 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
Failure to burn with ahci mode.
Hi, I posted this PR : http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/146464 I can't burn with the optical drive, I can read it but not burn. When I try to use burncd it says acd0: FAILURE - MODE_SELECT_BIG timed out It's a Master: acd0 hp DVDRAM GT20L/DC05 SATA revision 1.x Slave: no device present I would love to use ahci instead of ide since it's really faster. I don't know how I can help you more, FreeBSD Melon.malikania.fr 8.1-STABLE FreeBSD 8.1-STABLE #3: Sun Sep 26 10:15:10 CEST 2010 r...@melon.malikania.fr:/usr/obj/usr/src/sys/Melon amd64 Kind regards, -- Demelier David ___ 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: Failure to burn with ahci mode.
2010/9/26 Andriy Gapon a...@icyb.net.ua: on 26/09/2010 12:31 David DEMELIER said the following: Hi, I posted this PR : http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/146464 I can't burn with the optical drive, I can read it but not burn. When I try to use burncd it says acd0: FAILURE - MODE_SELECT_BIG timed out It's a Master: acd0 hp DVDRAM GT20L/DC05 SATA revision 1.x Slave: no device present I would love to use ahci instead of ide since it's really faster. I don't know how I can help you more, FreeBSD Melon.malikania.fr 8.1-STABLE FreeBSD 8.1-STABLE #3: Sun Sep 26 10:15:10 CEST 2010 r...@melon.malikania.fr:/usr/obj/usr/src/sys/Melon amd64 Try using ahci(4) driver. -- Andriy Gapon That's what I'm doing. -- Demelier David ___ 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: Failure to burn with ahci mode.
2010/9/26 Erik Trulsson ertr1...@student.uu.se: On Sun, Sep 26, 2010 at 11:53:01AM +0200, David DEMELIER wrote: 2010/9/26 Andriy Gapon a...@icyb.net.ua: on 26/09/2010 12:31 David DEMELIER said the following: Hi, I posted this PR : http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/146464 I can't burn with the optical drive, I can read it but not burn. When I try to use burncd it says acd0: FAILURE - MODE_SELECT_BIG timed out It's a Master: acd0 hp DVDRAM GT20L/DC05 SATA revision 1.x Slave: no device present I would love to use ahci instead of ide since it's really faster. I don't know how I can help you more, FreeBSD Melon.malikania.fr 8.1-STABLE FreeBSD 8.1-STABLE #3: Sun Sep 26 10:15:10 CEST 2010 r...@melon.malikania.fr:/usr/obj/usr/src/sys/Melon amd64 Try using ahci(4) driver. -- Andriy Gapon That's what I'm doing. If you were using the ahci(4) driver the optical drive ought to show up as cd0 rather than acd0. Anyway, I think burncd will only work with the old ata(4) driver. The new ahci(4) and ada(4) drivers use the cam(4) system and looks pretty much like SCSI drives to the rest of the system. Try the sysutils/cdrecord port for burning. (Should work with all SCSI and ATAPI optical drives, regardless of which driver is used.) -- Insert your favourite quote here. Erik Trulsson ertr1...@student.uu.se No it's still acd0, do I need atapicam as device in my kernel configuration? Thanks for your answers. -- Demelier David ___ 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: Failure to burn with ahci mode.
2010/9/26 Jeremy Chadwick free...@jdc.parodius.com: On Sun, Sep 26, 2010 at 07:12:17PM +0200, David DEMELIER wrote: 2010/9/26 Erik Trulsson ertr1...@student.uu.se: On Sun, Sep 26, 2010 at 11:53:01AM +0200, David DEMELIER wrote: 2010/9/26 Andriy Gapon a...@icyb.net.ua: on 26/09/2010 12:31 David DEMELIER said the following: Hi, I posted this PR : http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/146464 I can't burn with the optical drive, I can read it but not burn. When I try to use burncd it says acd0: FAILURE - MODE_SELECT_BIG timed out It's a Master: acd0 hp DVDRAM GT20L/DC05 SATA revision 1.x Slave: no device present I would love to use ahci instead of ide since it's really faster. I don't know how I can help you more, FreeBSD Melon.malikania.fr 8.1-STABLE FreeBSD 8.1-STABLE #3: Sun Sep 26 10:15:10 CEST 2010 r...@melon.malikania.fr:/usr/obj/usr/src/sys/Melon amd64 Try using ahci(4) driver. -- Andriy Gapon That's what I'm doing. If you were using the ahci(4) driver the optical drive ought to show up as cd0 rather than acd0. Anyway, I think burncd will only work with the old ata(4) driver. The new ahci(4) and ada(4) drivers use the cam(4) system and looks pretty much like SCSI drives to the rest of the system. Try the sysutils/cdrecord port for burning. (Should work with all SCSI and ATAPI optical drives, regardless of which driver is used.) -- Insert your favourite quote here. Erik Trulsson ertr1...@student.uu.se No it's still acd0, do I need atapicam as device in my kernel configuration? Thanks for your answers. There's a difference between ataahci.ko (device ataahci) and ahci.ko, in case you're confusing to two. Can you please provide your loader.conf and kernel configuration file? Thanks. -- | 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 | http://files.malikania.fr/Melon and http://files.malikania.fr/loader.conf mark...@melon ~ $ sudo camcontrol devlist WDC WD3200BEKT-60F3T1 12.01A12 at scbus0 target 0 lun 0 (ada0) hp DVDRAM GT20L DC05 at scbus1 target 0 lun 0 (cd0) mark...@melon ~ $ sudo cdrecord downloads/FreeBSD-8.1-RELEASE-amd64-livefs.iso cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd8.1) Copyright (C) 1995-2010 Jörg Schilling cdrecord: Error 0. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. mark...@melon ~ $ sudo cdrecord -scanbus Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd8.1) Copyright (C) 1995-2010 Jörg Schilling cdrecord: Error 0. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Cheers -- Demelier David ___ 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: Failure to burn with ahci mode.
2010/9/26 Andriy Gapon a...@icyb.net.ua: on 26/09/2010 20:37 David DEMELIER said the following: mark...@melon ~ $ sudo camcontrol devlist WDC WD3200BEKT-60F3T1 12.01A12 at scbus0 target 0 lun 0 (ada0) hp DVDRAM GT20L DC05 at scbus1 target 0 lun 0 (cd0) mark...@melon ~ $ sudo cdrecord downloads/FreeBSD-8.1-RELEASE-amd64-livefs.iso cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd8.1) Copyright (C) 1995-2010 Jörg Schilling cdrecord: Error 0. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. mark...@melon ~ $ sudo cdrecord -scanbus Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd8.1) Copyright (C) 1995-2010 Jörg Schilling cdrecord: Error 0. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Doesn't look like you have xpt and pass devices in your kernel, which are (almost) mandatory when use CAM-based drivers. Not sure if ahci(4) mentions this. -- Andriy Gapon Everything works now… Sorry for the noise ! We can close the PR too. -- Demelier David ___ 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: Failure to burn with ahci mode.
2010/9/26 David DEMELIER demelier.da...@gmail.com: 2010/9/26 Andriy Gapon a...@icyb.net.ua: on 26/09/2010 20:37 David DEMELIER said the following: mark...@melon ~ $ sudo camcontrol devlist WDC WD3200BEKT-60F3T1 12.01A12 at scbus0 target 0 lun 0 (ada0) hp DVDRAM GT20L DC05 at scbus1 target 0 lun 0 (cd0) mark...@melon ~ $ sudo cdrecord downloads/FreeBSD-8.1-RELEASE-amd64-livefs.iso cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd8.1) Copyright (C) 1995-2010 Jörg Schilling cdrecord: Error 0. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. mark...@melon ~ $ sudo cdrecord -scanbus Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd8.1) Copyright (C) 1995-2010 Jörg Schilling cdrecord: Error 0. Cannot open or use SCSI driver. cdrecord: For possible targets try 'cdrecord -scanbus'. cdrecord: For possible transport specifiers try 'cdrecord dev=help'. Doesn't look like you have xpt and pass devices in your kernel, which are (almost) mandatory when use CAM-based drivers. Not sure if ahci(4) mentions this. -- Andriy Gapon Everything works now… Sorry for the noise ! We can close the PR too. -- Demelier David or not, mark...@melon ~ $ sudo cdrecord downloads/FreeBSD-8.1-RELEASE-i386-livefs.iso cdrecord: No write mode specified. cdrecord: Assuming -sao mode. cdrecord: If your drive does not accept -sao, try -tao. cdrecord: Future versions of cdrecord may have different drive dependent defaults. Cdrecord-ProDVD-ProBD-Clone 3.00 (amd64-unknown-freebsd8.1) Copyright (C) 1995-2010 Jörg Schilling Using libscg version 'schily-0.9'. No target specified, trying to find one... Using dev=1,0,0. Device type: Removable CD-ROM Version: 0 Response Format: 2 Capabilities : Vendor_info: 'hp ' Identifikation : 'DVDRAM GT20L' Revision : 'DC05' Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM. Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R LAYER_JUMP Starting to write CD/DVD/BD at speed 24 in real SAO mode for single session. Last chance to quit, starting real write0 seconds. Operation starts. cdrecord: WARNING: Drive returns wrong startsec (0) using -150 cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 FF FF FF 6A 00 00 20 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 11.961s timeout 200s write track pad data: error after 0 bytes BFree: 597 K BSize: 597 K cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 20 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.001s timeout 200s write track data: error after 0 bytes cdrecord: A write error occured. cdrecord: Please properly read the error message above. I will rollback to the old working ata driver. -- Demelier David ___ 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: Web feeds for UPDATING files
2010/9/25 jhell jh...@dataix.net: On 09/25/2010 09:24, Alexander Kojevnikov wrote: On 25 September 2010 17:04, Alexander Kojevnikov alexan...@kojevnikov.com wrote: On 25 September 2010 15:44, jhell jh...@dataix.net wrote: Really awesome! This will come in handy to serve up stable/*/UPDATING and head/UPDATING to. And thinking along those lines it could probably be incorporated directly into the DAV tree on svn. to serve directly from there. Great idea, I'll try to implement both feeds during the weekend and will post here and on freebsd-current@ and freebsd-stable@ when it's done. ...and done: http://updating.versia.com/ The site now features Atom feeds for the following files: * ports/UPDATING * head/UPDATING * stable/7/UPDATING * stable/8/UPDATING Hope you find the feeds useful. Cheers, Alex PS: I apologise to ports/UPDATING subscribers who got quite a few duplicate entries. I barely missed the Ballmer Peak, just delete those. Your amazing! Thanks Alexander! -- jhell,v ___ 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 It's so great that it should be merge to the official FreeBSD web page! Thanks a lot! Kind regards, -- Demelier David ___ 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: Strange video mode output with VESA
2010/9/16 David DEMELIER demelier.da...@gmail.com: 2010/7/19 Jung-uk Kim j...@freebsd.org: On Friday 16 July 2010 07:18 pm, Jung-uk Kim wrote: On Friday 16 July 2010 03:22 pm, Jung-uk Kim wrote: On Friday 16 July 2010 03:00 pm, David DEMELIER wrote: 2010/6/19 paradox ddkp...@yahoo.com: On Wednesday 02 June 2010 04:25 pm, David DEMELIER wrote: Hi there, I was so happy to see that VESA is available for amd64, but unfortunately it does not work really well for me. Take a look at this picture : http://img717.imageshack.us/img717/7311/dsc00399h.jpg My laptop is a 15,6 so the best resolution is 1366x768, I tried this : vidcontrol MODE_496. As you can see on the picture all : the lines are completely everywhere, if I mouse the cursor they move away (I'm not drunk!). I have SC_PIXEL_MODE in my kernel config. The console terminal is okay until I don't excess 1280x960x32 video mode. Do you have any idea to fix this ? It is kinda known problem. �If the mode has larger bytes per scan line than the minimum, few characters per line are lost when the screen is scrolled up or down, i.e., framebuffer copies of whole screen. �When you move the mouse onto the line, entire line is redrawn and restored. �That's what you are seeing. �Ed might have a better idea how to fix it (CC'ed). Jung-uk Kim this is incorrent calculate the scan lines in the vesa driver Jung-uk Kim should to fix it But Jung-uk Kim said Ed' should fix it so we are in an infinite loop :- No, I didn't say that. What I meant was Ed may be a better qualified person to fix syscons vs. terminal emulator interaction issues. :-( Can you please try the attached patch? FYI, I just went ahead and committed a (slightly better) patch on head as r210248. It will be MFC'ed soon. Jung-uk Kim Sorry, I completely forgot this thread, I tried your patch, it didn't solved the problem but the offset is shorter now, only 2 or 3 characters per line are bad positionned. I will try the r210248 revision, this revision only applies to the file scvgarndr.c ? Thanks. -- Demelier David I tried the r210248 revision but it doesn't works, I still have a little offset but less than without the patch. Kind regards, -- Demelier David ___ 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: Strange video mode output with VESA
2010/7/19 Jung-uk Kim j...@freebsd.org: On Friday 16 July 2010 07:18 pm, Jung-uk Kim wrote: On Friday 16 July 2010 03:22 pm, Jung-uk Kim wrote: On Friday 16 July 2010 03:00 pm, David DEMELIER wrote: 2010/6/19 paradox ddkp...@yahoo.com: On Wednesday 02 June 2010 04:25 pm, David DEMELIER wrote: Hi there, I was so happy to see that VESA is available for amd64, but unfortunately it does not work really well for me. Take a look at this picture : http://img717.imageshack.us/img717/7311/dsc00399h.jpg My laptop is a 15,6 so the best resolution is 1366x768, I tried this : vidcontrol MODE_496. As you can see on the picture all : the lines are completely everywhere, if I mouse the cursor they move away (I'm not drunk!). I have SC_PIXEL_MODE in my kernel config. The console terminal is okay until I don't excess 1280x960x32 video mode. Do you have any idea to fix this ? It is kinda known problem. �If the mode has larger bytes per scan line than the minimum, few characters per line are lost when the screen is scrolled up or down, i.e., framebuffer copies of whole screen. �When you move the mouse onto the line, entire line is redrawn and restored. �That's what you are seeing. �Ed might have a better idea how to fix it (CC'ed). Jung-uk Kim this is incorrent calculate the scan lines in the vesa driver Jung-uk Kim should to fix it But Jung-uk Kim said Ed' should fix it so we are in an infinite loop :- No, I didn't say that. What I meant was Ed may be a better qualified person to fix syscons vs. terminal emulator interaction issues. :-( Can you please try the attached patch? FYI, I just went ahead and committed a (slightly better) patch on head as r210248. It will be MFC'ed soon. Jung-uk Kim Sorry, I completely forgot this thread, I tried your patch, it didn't solved the problem but the offset is shorter now, only 2 or 3 characters per line are bad positionned. I will try the r210248 revision, this revision only applies to the file scvgarndr.c ? Thanks. -- Demelier David ___ 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: Strange video mode output with VESA
2010/6/19 paradox ddkp...@yahoo.com: On Wednesday 02 June 2010 04:25 pm, David DEMELIER wrote: Hi there, I was so happy to see that VESA is available for amd64, but unfortunately it does not work really well for me. Take a look at this picture : http://img717.imageshack.us/img717/7311/dsc00399h.jpg My laptop is a 15,6 so the best resolution is 1366x768, I tried this : vidcontrol MODE_496. As you can see on the picture all the lines : are completely everywhere, if I mouse the cursor they move away (I'm not drunk!). I have SC_PIXEL_MODE in my kernel config. The console terminal is okay until I don't excess 1280x960x32 video mode. Do you have any idea to fix this ? It is kinda known problem. If the mode has larger bytes per scan line than the minimum, few characters per line are lost when the screen is scrolled up or down, i.e., framebuffer copies of whole screen. When you move the mouse onto the line, entire line is redrawn and restored. That's what you are seeing. Ed might have a better idea how to fix it (CC'ed). Jung-uk Kim this is incorrent calculate the scan lines in the vesa driver Jung-uk Kim should to fix it But Jung-uk Kim said Ed' should fix it so we are in an infinite loop :- -- Demelier David ___ 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
Yet another problem with my laptop
Hello, I always have problems with my laptop, this time is a lot of messages while running on battery : Jun 20 14:29:51 Melon kernel: ACPI Error (uteval-0318): Method execution failed [\_SB_.BAT0._UID] (Node 0xff0001537760), AE_AML_NO_OPERAND There is a lot of these message in /var/log/messages, but I can't see any troubles with my battery. -- Demelier David ___ 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: Kernel panic when unpluggin AC adaptor
2010/6/11 John Baldwin j...@freebsd.org: On Friday 11 June 2010 6:27:48 am Giovanni Trematerra wrote: On Thu, Jun 10, 2010 at 10:58 PM, Giovanni Trematerra giovanni.tremate...@gmail.com wrote: On Tue, May 4, 2010 at 6:35 PM, David DEMELIER demelier.da...@gmail.com wrote: Good news ! It worked, check the picture here : http://img63.imageshack.us/img63/4244/dsc00361g.jpg Into the file sys/dev/acpica/acpi_cpu.c at the end of acpi_cpu_notify (a per cpu notification handler), called when _CST objects changing, global cpu_cx_count is set to the greatest value of all sc-cpu_cx_count per-cpu variables. That could result in a panic as David reported, because that lets to invoke acpi_cpu_global_cx_lowest_sysctl from /etc/rc.d/power_profile, when AC adapter is unplugged, with a value that not all the CPUs could handle in the acpi_cpu_idle. The patch also change global cpu_cx_lowest according to new value of global cpu_cx_count if needed. David Demelier made a great work to test every patch I sent him to identify the source of the problem. Please, let me know your comments and possibly commit the patch if you think is good enough. As jhb@ pointed me out in private with the previous patch a CPU could never enter in the lowest Cx-state even if it gained. So I'd like to propose this new solution. When hw.acpi.cpu.cx_lowest sysctl is set, the global handler in sys/dev/acpi_cpu.c will set the greatest sc-cpu_cx_lowest value supported by the CPU and not the same value for all CPUs. Later, when CPU, possibly gain new Cx-states, the acpi_cpu_notify handler will set sc-cpu_cx_lowest accordingly with global cx_lowest and the Cx-states supported by the CPU. Now I think that /etc/rc.d/power_profile script has a problem but that is a different story. The script select the lowest_value only querying cx-states of the dev.cpu.0. If different CPUs may have different Cx-states, the script should use as lowest_value the lowest value between all the CPUs. Yes. Please, let me know your comments and possibly commit the patch if you think is good enough. I think this is a good compromise for now. -- John Baldwin Thanks for Giovanni's patience and work, he made a lot of research to solve this little problem :-). Is there a chance that this patch appears in 8.1-RELEASE ? Kind regards. -- Demelier David ___ 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
textproc/iso8879 fails to build.
Hi, I got this build error when trying to build editors/abiword : === Extracting for iso8879-1986_2 = MD5 Checksum OK for isoENTS.zip. = SHA256 Checksum OK for isoENTS.zip. === Patching for iso8879-1986_2 === iso8879-1986_2 depends on executable: unzip - found === Configuring for iso8879-1986_2 === Installing for iso8879-1986_2 === iso8879-1986_2 depends on file: /usr/local/bin/xmlcatmgr - found === Generating temporary packing list === Checking if textproc/iso8879 already installed Archive: /usr/distfiles/isoENTS.zip caution: filename not matched: -d caution: filename not matched: /usr/local/share/sgml/iso8879 *** Error code 11 Stop in /usr/ports/textproc/iso8879. *** Error code 1 Stop in /usr/ports/textproc/docbook-410. *** Error code 1 Stop in /usr/ports/sysutils/polkit. Cheers. -- Demelier David ___ 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
Strange video mode output with VESA
Hi there, I was so happy to see that VESA is available for amd64, but unfortunately it does not work really well for me. Take a look at this picture : http://img717.imageshack.us/img717/7311/dsc00399h.jpg My laptop is a 15,6 so the best resolution is 1366x768, I tried this : vidcontrol MODE_496. As you can see on the picture all the lines are completely everywhere, if I mouse the cursor they move away (I'm not drunk!). I have SC_PIXEL_MODE in my kernel config. The console terminal is okay until I don't excess 1280x960x32 video mode. Do you have any idea to fix this ? -- Demelier David mode# flags typesize font window linear buffer -- 0 (0x000) 0x0001 T 40x25 8x8 0xb8000 32k 32k 0x 32k 1 (0x001) 0x0001 T 40x25 8x8 0xb8000 32k 32k 0x 32k 2 (0x002) 0x0001 T 80x25 8x8 0xb8000 32k 32k 0x 32k 3 (0x003) 0x0001 T 80x25 8x8 0xb8000 32k 32k 0x 32k 4 (0x004) 0x0003 G 320x200x2 C 8x8 0xb8000 32k 32k 0x 32k 5 (0x005) 0x0003 G 320x200x2 C 8x8 0xb8000 32k 32k 0x 32k 6 (0x006) 0x0003 G 640x200x1 C 8x8 0xb8000 32k 32k 0x 32k 13 (0x00d) 0x0003 G 320x200x4 4 8x8 0xa 64k 64k 0x 256k 14 (0x00e) 0x0003 G 640x200x4 4 8x8 0xa 64k 64k 0x 256k 16 (0x010) 0x0003 G 640x350x2 2 8x14 0xa 64k 64k 0x 128k 18 (0x012) 0x0003 G 640x350x4 4 8x14 0xa 64k 64k 0x 256k 19 (0x013) 0x0001 T 40x25 8x14 0xb8000 32k 32k 0x 32k 20 (0x014) 0x0001 T 40x25 8x14 0xb8000 32k 32k 0x 32k 21 (0x015) 0x0001 T 80x25 8x14 0xb8000 32k 32k 0x 32k 22 (0x016) 0x0001 T 80x25 8x14 0xb8000 32k 32k 0x 32k 23 (0x017) 0x0001 T 40x25 8x16 0xb8000 32k 32k 0x 32k 24 (0x018) 0x0001 T 80x25 8x16 0xb8000 32k 32k 0x 32k 26 (0x01a) 0x0003 G 640x480x4 4 8x16 0xa 64k 64k 0x 256k 27 (0x01b) 0x0003 G 640x480x4 4 8x16 0xa 64k 64k 0x 256k 28 (0x01c) 0x0003 G 320x200x8 P 8x8 0xa 64k 64k 0x 64k 30 (0x01e) 0x0001 T 80x50 8x8 0xb8000 32k 32k 0x 32k 32 (0x020) 0x0001 T 80x30 8x16 0xb8000 32k 32k 0x 32k 34 (0x022) 0x0001 T 80x60 8x8 0xb8000 32k 32k 0x 32k 37 (0x025) 0x0003 G 320x240x8 V 8x8 0xa 64k 64k 0x 256k 112 (0x070) 0x T 80x43 8x8 0xb8000 32k 32k 0x 32k 113 (0x071) 0x0001 T 80x43 8x8 0xb8000 32k 32k 0x 32k 256 (0x100) 0x001f G 640x400x8 P 8x16 0xa 64k 64k 0xc000 250k 257 (0x101) 0x001f G 640x480x8 P 8x16 0xa 64k 64k 0xc000 300k 259 (0x103) 0x001f G 800x600x8 P 8x14 0xa 64k 64k 0xc000 487k 261 (0x105) 0x001f G 1024x768x8 P8x16 0xa 64k 64k 0xc000 768k 263 (0x107) 0x001f G 1280x1024x8 P 8x16 0xa 64k 64k 0xc000 1280k 269 (0x10d) 0x001f G 320x200x16 D8x8 0xa 64k 64k 0xc000 125k 270 (0x10e) 0x001f G 320x200x16 D8x8 0xa 64k 64k 0xc000 125k 272 (0x110) 0x001f G 640x480x16 D8x16 0xa 64k 64k 0xc000 600k 273 (0x111) 0x001f G 640x480x16 D8x16 0xa 64k 64k 0xc000 600k 275 (0x113) 0x001f G 800x600x16 D8x14 0xa 64k 64k 0xc000 937k 276 (0x114) 0x001f G 800x600x16 D8x14 0xa 64k 64k 0xc000 937k 278 (0x116) 0x001f G 1024x768x16 D 8x16 0xa 64k 64k 0xc000 1536k 279 (0x117) 0x001f G 1024x768x16 D 8x16 0xa 64k 64k 0xc000 1536k 281 (0x119) 0x001f G 1280x1024x16 D 8x16 0xa 64k 64k 0xc000 2560k 282 (0x11a) 0x001f G 1280x1024x16 D 8x16 0xa 64k 64k 0xc000 2560k 288 (0x120) 0x001f G 320x200x32 D8x8 0xa 64k 64k 0xc000 250k 289 (0x121) 0x001f G 640x480x32 D8x16 0xa 64k 64k 0xc000 1200k 290 (0x122) 0x001f G 800x600x32 D8x14 0xa 64k 64k 0xc000 1875k 291 (0x123) 0x001f G 1024x768x32 D 8x16 0xa 64k 64k 0xc000 3072k 292 (0x124) 0x001f G 1280x1024x32 D 8x16 0xa 64k 64k 0xc000 5120k 307 (0x133) 0x001f G 720x400x8 P 8x16 0xa 64k 64k 0xc000 300k 309 (0x135) 0x001f G 720x400x16 D8x16 0xa 64k 64k 0xc000 575k 310 (0x136) 0x001f G 720x400x32 D8x16 0xa 64k 64k 0xc000 1150k 323 (0x143) 0x001f G 1400x1050x8 P 8x16 0xa 64k 64k 0xc000 1443k 325 (0x145) 0x001f G 1400x1050x16 D 8x16 0xa 64k 64k 0xc000 2887k 326 (0x146) 0x001f G 1400x1050x32 D 8x16 0xa 64k 64k 0xc000 5775k 339 (0x153) 0x001f G 1152x864x8 P8x16 0xa 64k 64k 0xc000 972k 341 (0x155) 0x001f G 1152x864x16 D 8x16 0xa 64k 64k
Re: Kernel panic when unpluggin AC adaptor
2010/5/25 Giovanni Trematerra giovanni.tremate...@gmail.com: On Tue, May 25, 2010 at 5:52 PM, David DEMELIER demelier.da...@gmail.com wrote: 2010/5/25 Giovanni Trematerra giovanni.tremate...@gmail.com: On Mon, May 24, 2010 at 9:43 PM, David DEMELIER demelier.da...@gmail.com wrote: 2010/5/12 Giovanni Trematerra giovanni.tremate...@gmail.com: On Fri, May 7, 2010 at 8:33 PM, Demelier David demelier.da...@gmail.com wrote: Le Vendredi 07 mai 2010 à 18:22 +0200, Giovanni Trematerra a écrit : On Fri, May 7, 2010 at 2:08 PM, Demelier David demelier.da...@gmail.com wrote: Hi, I noticed that pluggin the AC adaptor when I boot without it does not panic. It only panic when removing it. Maybe that could help ? Good to know. The problem lies somewhere when performance state change. In your case it happens when you remove AC adaptor. Let's hope someone on acpi@ ml comes up with a good idea. Okay so for the moment no change, I'll wait for someone with an idea that could solve my problem. For me because the panic only happens when changing profile from ac plugged - ac unplugged (and not the reverse) I would think it's a cpu related acpi issue. I looked deeper and it seems to me that when you unplug the AC adapter, acpi_cpu_notify calls acpi_cpu_cx_cst that try to allocate a new cx_ptr-p_lvlx via acpi_PkgGas. If acpi_PkgGas set cx_ptr-p_lvlx to NULL for any reasons you'll have the panic that you reported. A solution would be to set acpi_cpu_hook to NULL so acpi_cpu_idle won't call it. I need some time to have a patch because of the possible race between acpi_cpu_notify and acpi_cpu_idle during set acpi_cpu_hook to NULL. if you have time and want panic your system you could try the attached patch, just to be sure that we catch it. Hi, it paniced today ! I don't know why it randomly panic but it did, the backtrace didn't change. There is a picture about the panic : http://img541.imageshack.us/img541/2773/dsc00388xa.jpg What was you trying? acpi_idle5.diff.txt patch? How did it panic? Unplugging AC adapter? Hi, I tried this one : lvlx.diff.txt. Yes by unplugging the AC adapter. This is an old one. Could you try acpi_idle5.diff.txt? I kept you in Cc when I sent to the list. If you have problems, let me know, I'll resend to you the patch. Thank you. Hi, it panic'ed with the same backtrace. Thanks. -- Demelier David ___ 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: Kernel panic when unpluggin AC adaptor
2010/5/26 Giovanni Trematerra giovanni.tremate...@gmail.com: On Wed, May 26, 2010 at 11:14 AM, David DEMELIER demelier.da...@gmail.com wrote: 2010/5/25 Giovanni Trematerra giovanni.tremate...@gmail.com: On Tue, May 25, 2010 at 5:52 PM, David DEMELIER demelier.da...@gmail.com wrote: 2010/5/25 Giovanni Trematerra giovanni.tremate...@gmail.com: On Mon, May 24, 2010 at 9:43 PM, David DEMELIER demelier.da...@gmail.com wrote: 2010/5/12 Giovanni Trematerra giovanni.tremate...@gmail.com: On Fri, May 7, 2010 at 8:33 PM, Demelier David demelier.da...@gmail.com wrote: Le Vendredi 07 mai 2010 à 18:22 +0200, Giovanni Trematerra a écrit : On Fri, May 7, 2010 at 2:08 PM, Demelier David demelier.da...@gmail.com wrote: Hi, I noticed that pluggin the AC adaptor when I boot without it does not panic. It only panic when removing it. Maybe that could help ? Good to know. The problem lies somewhere when performance state change. In your case it happens when you remove AC adaptor. Let's hope someone on acpi@ ml comes up with a good idea. Okay so for the moment no change, I'll wait for someone with an idea that could solve my problem. For me because the panic only happens when changing profile from ac plugged - ac unplugged (and not the reverse) I would think it's a cpu related acpi issue. I looked deeper and it seems to me that when you unplug the AC adapter, acpi_cpu_notify calls acpi_cpu_cx_cst that try to allocate a new cx_ptr-p_lvlx via acpi_PkgGas. If acpi_PkgGas set cx_ptr-p_lvlx to NULL for any reasons you'll have the panic that you reported. A solution would be to set acpi_cpu_hook to NULL so acpi_cpu_idle won't call it. I need some time to have a patch because of the possible race between acpi_cpu_notify and acpi_cpu_idle during set acpi_cpu_hook to NULL. if you have time and want panic your system you could try the attached patch, just to be sure that we catch it. Hi, it paniced today ! I don't know why it randomly panic but it did, the backtrace didn't change. There is a picture about the panic : http://img541.imageshack.us/img541/2773/dsc00388xa.jpg What was you trying? acpi_idle5.diff.txt patch? How did it panic? Unplugging AC adapter? Hi, I tried this one : lvlx.diff.txt. Yes by unplugging the AC adapter. This is an old one. Could you try acpi_idle5.diff.txt? I kept you in Cc when I sent to the list. If you have problems, let me know, I'll resend to you the patch. Thank you. Hi, it panic'ed with the same backtrace. Can you please post your dmesg? Sent ! -- Demelier David 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-PRERELEASE #3: Wed May 26 11:48:16 CEST 2010 r...@melon.malikania.fr:/usr/obj/usr/src/sys/Melon amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU T6570 @ 2.10GHz (2094.77-MHz K8-class CPU) Origin = GenuineIntel Id = 0x1067a Family = 6 Model = 17 Stepping = 10 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=0x408e3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 3221225472 (3072 MB) avail memory = 3092127744 (2948 MB) ACPI APIC Table: HPQOEM 3074 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 cryptosoft0: software crypto on motherboard acpi0: HPQOEM SLIC-MPC on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_ec0: Embedded Controller: GPE 0x16 port 0x62,0x66 on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0x7000-0x70ff mem 0xc000-0xcfff,0xd840-0xd840 irq 16 at device 0.0 on pci1 acpi_video0: ACPI video extension on vgapci0 hdac0: ATI RV730 High Definition Audio Controller mem 0xd841-0xd8413fff irq 17 at device 0.1 on pci1 hdac0: HDA Driver Revision: 20100226_0142 hdac0: [ITHREAD] uhci0: Intel 82801I (ICH9) USB controller port 0x80a0-0x80bf irq 16 at device 26.0 on pci0 uhci0: [ITHREAD] usbus0: Intel 82801I (ICH9) USB
Re: Kernel panic when unpluggin AC adaptor
2010/5/26 Giovanni Trematerra giovanni.tremate...@gmail.com: On Wed, May 26, 2010 at 3:55 PM, Giovanni Trematerra giovanni.tremate...@gmail.com wrote: On Wed, May 26, 2010 at 12:01 PM, David DEMELIER demelier.da...@gmail.com wrote: 2010/5/26 Giovanni Trematerra giovanni.tremate...@gmail.com: On Wed, May 26, 2010 at 11:14 AM, David DEMELIER demelier.da...@gmail.com wrote: 2010/5/25 Giovanni Trematerra giovanni.tremate...@gmail.com: On Tue, May 25, 2010 at 5:52 PM, David DEMELIER demelier.da...@gmail.com wrote: 2010/5/25 Giovanni Trematerra giovanni.tremate...@gmail.com: On Mon, May 24, 2010 at 9:43 PM, David DEMELIER demelier.da...@gmail.com wrote: 2010/5/12 Giovanni Trematerra giovanni.tremate...@gmail.com: On Fri, May 7, 2010 at 8:33 PM, Demelier David demelier.da...@gmail.com wrote: Le Vendredi 07 mai 2010 à 18:22 +0200, Giovanni Trematerra a écrit : On Fri, May 7, 2010 at 2:08 PM, Demelier David demelier.da...@gmail.com wrote: Hi, I noticed that pluggin the AC adaptor when I boot without it does not panic. It only panic when removing it. Maybe that could help ? Good to know. The problem lies somewhere when performance state change. In your case it happens when you remove AC adaptor. Let's hope someone on acpi@ ml comes up with a good idea. Okay so for the moment no change, I'll wait for someone with an idea that could solve my problem. For me because the panic only happens when changing profile from ac plugged - ac unplugged (and not the reverse) I would think it's a cpu related acpi issue. I looked deeper and it seems to me that when you unplug the AC adapter, acpi_cpu_notify calls acpi_cpu_cx_cst that try to allocate a new cx_ptr-p_lvlx via acpi_PkgGas. If acpi_PkgGas set cx_ptr-p_lvlx to NULL for any reasons you'll have the panic that you reported. A solution would be to set acpi_cpu_hook to NULL so acpi_cpu_idle won't call it. I need some time to have a patch because of the possible race between acpi_cpu_notify and acpi_cpu_idle during set acpi_cpu_hook to NULL. if you have time and want panic your system you could try the attached patch, just to be sure that we catch it. Hi, it paniced today ! I don't know why it randomly panic but it did, the backtrace didn't change. There is a picture about the panic : http://img541.imageshack.us/img541/2773/dsc00388xa.jpg What was you trying? acpi_idle5.diff.txt patch? How did it panic? Unplugging AC adapter? Hi, I tried this one : lvlx.diff.txt. Yes by unplugging the AC adapter. This is an old one. Could you try acpi_idle5.diff.txt? I kept you in Cc when I sent to the list. If you have problems, let me know, I'll resend to you the patch. Thank you. Hi, it panic'ed with the same backtrace. Can you please post your dmesg? Sent ! As your PC is in a good mood to make test, :) could you try this patch? Thank you -- Gianni Here the patch :( Sorry, still the same :-( -- Demelier David ___ 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: Kernel panic when unpluggin AC adaptor
2010/5/25 Giovanni Trematerra giovanni.tremate...@gmail.com: On Mon, May 24, 2010 at 9:43 PM, David DEMELIER demelier.da...@gmail.com wrote: 2010/5/12 Giovanni Trematerra giovanni.tremate...@gmail.com: On Fri, May 7, 2010 at 8:33 PM, Demelier David demelier.da...@gmail.com wrote: Le Vendredi 07 mai 2010 à 18:22 +0200, Giovanni Trematerra a écrit : On Fri, May 7, 2010 at 2:08 PM, Demelier David demelier.da...@gmail.com wrote: Hi, I noticed that pluggin the AC adaptor when I boot without it does not panic. It only panic when removing it. Maybe that could help ? Good to know. The problem lies somewhere when performance state change. In your case it happens when you remove AC adaptor. Let's hope someone on acpi@ ml comes up with a good idea. Okay so for the moment no change, I'll wait for someone with an idea that could solve my problem. For me because the panic only happens when changing profile from ac plugged - ac unplugged (and not the reverse) I would think it's a cpu related acpi issue. I looked deeper and it seems to me that when you unplug the AC adapter, acpi_cpu_notify calls acpi_cpu_cx_cst that try to allocate a new cx_ptr-p_lvlx via acpi_PkgGas. If acpi_PkgGas set cx_ptr-p_lvlx to NULL for any reasons you'll have the panic that you reported. A solution would be to set acpi_cpu_hook to NULL so acpi_cpu_idle won't call it. I need some time to have a patch because of the possible race between acpi_cpu_notify and acpi_cpu_idle during set acpi_cpu_hook to NULL. if you have time and want panic your system you could try the attached patch, just to be sure that we catch it. Hi, it paniced today ! I don't know why it randomly panic but it did, the backtrace didn't change. There is a picture about the panic : http://img541.imageshack.us/img541/2773/dsc00388xa.jpg What was you trying? acpi_idle5.diff.txt patch? How did it panic? Unplugging AC adapter? Hi, I tried this one : lvlx.diff.txt. Yes by unplugging the AC adapter. -- Demelier David ___ 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: Kernel panic when unpluggin AC adaptor
2010/5/12 Giovanni Trematerra giovanni.tremate...@gmail.com: On Fri, May 7, 2010 at 8:33 PM, Demelier David demelier.da...@gmail.com wrote: Le Vendredi 07 mai 2010 à 18:22 +0200, Giovanni Trematerra a écrit : On Fri, May 7, 2010 at 2:08 PM, Demelier David demelier.da...@gmail.com wrote: Hi, I noticed that pluggin the AC adaptor when I boot without it does not panic. It only panic when removing it. Maybe that could help ? Good to know. The problem lies somewhere when performance state change. In your case it happens when you remove AC adaptor. Let's hope someone on acpi@ ml comes up with a good idea. Okay so for the moment no change, I'll wait for someone with an idea that could solve my problem. For me because the panic only happens when changing profile from ac plugged - ac unplugged (and not the reverse) I would think it's a cpu related acpi issue. I looked deeper and it seems to me that when you unplug the AC adapter, acpi_cpu_notify calls acpi_cpu_cx_cst that try to allocate a new cx_ptr-p_lvlx via acpi_PkgGas. If acpi_PkgGas set cx_ptr-p_lvlx to NULL for any reasons you'll have the panic that you reported. A solution would be to set acpi_cpu_hook to NULL so acpi_cpu_idle won't call it. I need some time to have a patch because of the possible race between acpi_cpu_notify and acpi_cpu_idle during set acpi_cpu_hook to NULL. if you have time and want panic your system you could try the attached patch, just to be sure that we catch it. Hi, it paniced today ! I don't know why it randomly panic but it did, the backtrace didn't change. There is a picture about the panic : http://img541.imageshack.us/img541/2773/dsc00388xa.jpg Cheers. -- Demelier David ___ 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: Kernel panic when unpluggin AC adaptor
Hi, I tested your patch and it didn't panic. I checked the dev.cpu
sysctl nodes to see if the CPU freq is changing or not.
I unplugged the cable :
mark...@melon ~ $ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 450
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/1 C3/162
dev.cpu.0.cx_lowest: C3
dev.cpu.0.cx_usage: 0.00% 99.99% 0.00% last 131us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/1 C3/162
dev.cpu.1.cx_lowest: C3
dev.cpu.1.cx_usage: 0.00% 99.99% 0.00% last 260us
I plugged the cable :
mark...@melon ~ $ sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 2101
dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902
1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750
150/1875
dev.cpu.0.cx_supported: C1/1 C2/57
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% 0.00% last 497us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/1 C2/57
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% 0.00% last 497us
Of course I enabled
# Little power management.
performance_cx_lowest=HIGH
performance_cpu_freq=${performance_cx_lowest}
economy_cx_lowest=LOW
economy_cpu_freq=${economy_cx_lowest}
in my /etc/rc.conf, it the behavior expected ?
Thanks for your answers :-).
--
Demelier David
___
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: Kernel panic when unpluggin AC adaptor
I remove the patch, and built the kernel (I updated the src this morning) and it does not panic now. It's really odd. If it reappears soon I will tell you. Thanks. -- Demelier David ___ 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: Kernel panic when unpluggin AC adaptor
2010/5/4 Jeremy Chadwick free...@jdc.parodius.com: On Tue, May 04, 2010 at 10:32:14AM +0200, David DEMELIER wrote: Since I added dumpdev=/dev/ad4s1b in my /boot/loader.conf it does not panic anymore ... I'm not lucky (or ?). 1) dumpdev=xxx should go into /etc/rc.conf, not /boot/loader.conf. Putting in in /boot/loader.conf will change/do nothing. You should probably be using 'dumpdev=auto' anyway (it then uses whatever you define as swap in /etc/fstab). 2) If you meant to say /etc/rc.conf instead of /boot/loader.conf, setting dumpdev shouldn't fix your problem. I think it's a red herring. 3) You sent the above to me directly; please keep the mailing list CC'd, as others need to know what you've tried/done. Thanks. Yes I also added dumpdev=AUTO in /etc/rc.conf at the beginning. That was Garett who told me to add it to loader.conf. $ sysctl dev.cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.freq: 2101 dev.cpu.0.freq_levels: 2101/35000 1837/30625 1600/23888 1400/20902 1200/15000 1050/13125 900/11250 750/9375 600/7500 450/5625 300/3750 150/1875 dev.cpu.0.cx_supported: C1/1 C2/57 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% 0.00% last 497us dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/1 C2/57 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% 0.00% last 497us (I used Cc: entry I hope it sends to all) -- Demelier David ___ 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: Kernel panic when unpluggin AC adaptor
I made a panic and it said Dumping 1176Mb but even after 5 minutes there was no output. Usually you'll have something like Dumping 1176Mb: 1176 1040 960 ... etc ? Here it's stays at Dumping 1176Mb: and no changes. Cheers, David. ___ 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: Kernel panic when unpluggin AC adaptor
Good news ! It worked, check the picture here : http://img63.imageshack.us/img63/4244/dsc00361g.jpg ___ 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: Kernel panic when unpluggin AC adaptor
2010/5/4 Kostik Belousov kostik...@gmail.com: On Tue, May 04, 2010 at 06:35:52PM +0200, David DEMELIER wrote: Good news ! It worked, check the picture here : http://img63.imageshack.us/img63/4244/dsc00361g.jpg Please try adding code fragment like this: if (cx_next-p_lvlx == NULL) printf(Going to panic.\n); to dev/acpi/acpi_cpu.c:acpi_cpu_idle() function, right before CPU_GET_REG(cx_next-p_lvlx, 1); line and see if it prints the message immediately before the panic. Yes it does at the beginning of the kernel panic. Cheers. -- Demelier David ___ 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
Kernel panic when unpluggin AC adaptor
Hi, I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just panics when I unplug my AC. The current process = 11 (idle: cpu1) is this related to the cpufreq and related stuff ? It also says cannot dump. Device not defined or unavailable so I can't give you more infos now. King regards. -- Demelier David ___ 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: Kernel panic when unpluggin AC adaptor
2010/5/3 David DEMELIER demelier.da...@gmail.com:
Hi,
I just updated my 8.0-STABLE/amd64 today around 17h CEST, and it just
panics when I unplug my AC. The current process = 11 (idle: cpu1) is
this related to the cpufreq and related stuff ?
It also says cannot dump. Device not defined or unavailable so I can't
give you more infos now.
I can confirm that :
#performance_cx_lowest=HIGH
#performance_cpu_freq=${performance_cx_lowest}
#economy_cx_lowest=LOW
#economy_cpu_freq=${economy_cx_lowest}
in rc.conf was the problem.
--
Demelier David
___
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
