Fatal trap 12: hda

2012-09-23 Thread Barbara 
After updating src on RELENG_9 from r240236 to r240821 I have rebuilt
my world+kernel.
On reboot I had a kernel panic, supervisor read, page not present
for process swapper.
Trying to reboot in Single User Mode I accidentally disabled ACPI.
Luckily the machine booted succesfully but there was nothing new in
/var/crash.
Then I tried again with ACPI enabled: same kernel panic.
So I run nm on the instruction pointer of the panic and I noticed that
it was in hdaa_sense_init, in sys/dev/sound/pci/hda/hdaa.c.
BTW, I have device sound and device snd_hda in my KERNCONF, and
the sound hw detection happens before HDs, is that the reason why I
wasn't able to get a dump or dumping using DDB and the panicking
process is swapper? Is there any trick I'm missing for that?

Booting in verbose mode and comparing the output with ACPI enabled
(where the panic happens) and disabled, I guessed that the problem was
where No presence detection support at nid... is printed, as it was
missing in the former case for nid 27 - Headphone (Green Jack). With
ACPI disabled the value was looking quite weird: 36765696.
So I made the following change:


--- sys/dev/sound/pci/hda/hdaa.c.orig   2012-09-22 20:06:20.0 +0200
+++ sys/dev/sound/pci/hda/hdaa.c2012-09-23 20:39:32.0 +0200
@@ -627,7 +627,7 @@
(HDA_CONFIG_DEFAULTCONF_MISC(w-wclass.pin.config) 
 1) != 0) {
device_printf(devinfo-dev,
No presence detection support at nid %d\n,
-   as[i].pins[15]);
+   as-pins[15]);
} else {
if (w-unsol  0)
poll = 1;


Maybe the fix is not correct, but at least the new kernel boots successfully.
Can someone review that?
I tried looking in svn commits between the two builds, but I don't
know what exposed the problem.
If anyone is interested in my verbose log, or doing some tests, please ask.

Barbara
___
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

R: make installworld fails (touch not found)

2011-09-14 Thread Barbara 


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,

Forgot to adjkerntz -i?

Barbara

___
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

ums0 diconnections

2011-01-04 Thread Barbara 


Sometimes my mouse seems frozen, then it become responsive again after few 
seconds.
The following lines are added in /var/log/messages:

Jan  4 16:52:59 satanasso kernel: ugen1.2: Logitech at usbus1 (disconnected)
Jan  4 16:52:59 satanasso kernel: ums0: at uhub1, port 2, addr 2 
(disconnected)
Jan  4 16:52:59 satanasso hald[1508]: 16:52:59.420 [W] hf-devd.c:379: 
malformed devd event: 
Jan  4 16:52:59 satanasso hald[1508]: 16:52:59.435 [W] hf-devd.c:379: 
malformed devd event: 
Jan  4 16:53:01 satanasso kernel: ugen1.2: Logitech at usbus1
Jan  4 16:53:01 satanasso kernel: ums0: Logitech Optical USB Mouse, class 
0/0, rev 2.00/3.40, addr 2 on usbus1
Jan  4 16:53:01 satanasso kernel: ums0: 3 buttons and [XYZ] coordinates ID=0
Jan  4 16:53:02 satanasso hald[1508]: 16:53:02.439 [W] hf-devd.c:379: 
malformed devd event: 
Jan  4 16:53:02 satanasso hald[1508]: 16:53:02.440 [W] hf-devd.c:379: 
malformed devd event: 

As far as I can remember, this is happening since about a month.
I don't think that it's a hw problem, could it be a sw one?
BTW, I see similar error from hald when, for example, I plug in USB drives.

Thanks
Barbara

___
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 portsnap aren't portsnapping

2009-08-23 Thread barbara 
Sorry, it's not the first time I notice that, but I don't know where is the 
better place to report it. Any advise about that will be appreciated.

It seems that there aren't new port snapshot on the servers.
Can someone else confirm that?

For example a new version of Makefile for multimedia/vlc has been committed 
more than 7 hours ago, but I'm still not getting the new one.

Thanks


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: today portsnap aren't portsnapping

2009-08-23 Thread barbara 
 Hi,

 On Sun, Aug 23, 2009 at 8:28 AM, barbarabarbara.xxx1...@libero.it wrote:
  Sorry, it's not the first time I notice that, but I don't know where is the 
  better place to report it. Any advise about that will be appreciated.
 
  It seems that there aren't new port snapshot on the servers.
  Can someone else confirm that?
 
  For example a new version of Makefile for multimedia/vlc has been committed 
  more than 7 hours ago, but I'm still not getting the new one.
 
  Thanks
 

 What mirror are you using by default?

 orion# portsnap fetch update
 Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found.
 Fetching snapshot tag from portsnap1.FreeBSD.org... done.
 Fetching snapshot metadata... done.
 Updating from Thu Aug 20 09:52:10 EDT 2009 to Sat Aug 22 19:06:01 EDT 2009.
 Fetching 4 metadata patches... done.
 Applying metadata patches... done.
 Fetching 0 metadata files... done.
 Fetching 2996 
 patches.10203040506070809010011012013014015016017018019020021022023024025026027028029030031032033034035036037038039040041042043044045046047048049050051052053054055056057058059060061062063064065066067068069070071072073074075076077078079080081082083084085086087088089090091092093094095096097098099010001010102010301040105010601070108010901100111011201130114011501160117011801190120012101220123012401250126012701280129013001310132013301340135013601370138013901400141014201430144014501460147014801490150015101520153015401550156015701580159016001610162016301640165016601670168016901700171017201730174017501760177017801790180018101820183018401850186018701880189019001910192019301940195019601970198019902000201020202030204020502060207020802090210021102120213021402150216021702180219022002210222022302240225022602270228022902300231023202330234023502360237023802390240024102420243024402450246024702480249025002510252025302540255025602570258025902600261026202630264026502660267026802690270027102720273027402750276027702780279028002810282028302840285028602870288028902900291029202930294029502960297029802990...
 done.
 Applying patches...


 --
 Glen Barber


I've tried with portsnap[1-3].freebsd.org mirrors.
Can you check with:
grep ^DISTVERSION /usr/ports/multimedia/vlc/Makefile

I'm getting:
DISTVERSION=1.0.0
but the last version committed 7h26m ago has 1.0.1


___
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: today portsnap aren't portsnapping

2009-08-23 Thread barbara 
 On Sun, Aug 23, 2009 at 8:39 AM, barbarabarbara.xxx1...@libero.it wrote:
 
  I've tried with portsnap[1-3].freebsd.org mirrors.
  Can you check with:
 grep ^DISTVERSION /usr/ports/multimedia/vlc/Makefile
 
  I'm getting:
 DISTVERSION=1.0.0
  but the last version committed 7h26m ago has 1.0.1
 

 Yes, I have the updated version for that port.

 orion# grep ^DISTVERSION /usr/ports/multimedia/vlc/Makefile
 DISTVERSION=1.0.1



I've tried again and it worked. That's strange.
I've also got the latest audio/gnome-media, committed more than 12h ago.


___
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: today portsnap aren't portsnapping

2009-08-23 Thread barbara 
 On Sun, Aug 23, 2009 at 8:52 AM, barbarabarbara.xxx1...@libero.it wrote:
  On Sun, Aug 23, 2009 at 8:39 AM, barbarabarbara.xxx1...@libero.it wrote:
  
   I've tried with portsnap[1-3].freebsd.org mirrors.
   Can you check with:
  grep ^DISTVERSION /usr/ports/multimedia/vlc/Makefile
  
   I'm getting:
  DISTVERSION=1.0.0
   but the last version committed 7h26m ago has 1.0.1
  
 
  Yes, I have the updated version for that port.
 
  orion# grep ^DISTVERSION /usr/ports/multimedia/vlc/Makefile
  DISTVERSION=1.0.1
 
 
 
  I've tried again and it worked. That's strange.
  I've also got the latest audio/gnome-media, committed more than 12h ago.
 

 Very odd.  How many patches did it apply altogether?



# portsnap fetch update
Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found.
Fetching snapshot tag from portsnap2.FreeBSD.org... done.
Fetching snapshot metadata... done.
Updating from Sun Aug 23 01:06:01 CEST 2009 to Sun Aug 23 12:55:27 CEST 2009.
Fetching 4 metadata patches... done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 12 patches.10. done.
Applying patches... done.
Fetching 1 new ports or files... done.
Removing old files and directories... done.
Extracting new files:
/usr/ports/Tools/portbuild/
/usr/ports/Tools/scripts/
/usr/ports/archivers/lzma/
/usr/ports/audio/gnome-media/
/usr/ports/converters/Makefile
/usr/ports/converters/rcctools/
/usr/ports/databases/firebird20-client/
/usr/ports/devel/p5-Getopt-Long-Descriptive/
/usr/ports/multimedia/avidemux2/
/usr/ports/multimedia/vlc/
/usr/ports/net-im/libmsn/
/usr/ports/net/p5-File-Rsync/
/usr/ports/textproc/mdocml/
Building new INDEX files... done.


___
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: kern/134584: [panic] spin lock held too long

2009-07-30 Thread barbara 
 The following reply was made to PR kern/134584; it has been noted by GNATS.

 From: Attilio Rao atti...@freebsd.org
 To: barbara barbara.xxx1...@libero.it
 Cc: bug-followup bug-follo...@freebsd.org, FreeBSD-stable 
 FreeBSD-stable@freebsd.org
 Subject: Re: kern/134584: [panic] spin lock held too long
 Date: Sun, 26 Jul 2009 16:36:44 +0200

  2009/7/26 barbara barbara.xxx1...@libero.it:
   It happened again, on shutdown.
   As the previous time, it happened after a high (for a desktop) uptime and, 
 if it could matter, after running net-p2p/transmission-gtk2 for several hours.
   I don't know if it's related, but often quitting transmission, doesn't 
 terminate the process. Sometimes it end after several minutes the gui exited, 
 sometimes it's still running after hours.
   I've noticed it as the destination folder is on a manually mounted device 
 and I can't umount it as fstat reports the device used by a transmission 
 process.
   So I often have to kill it.
   This happened both the time I had this kind of panic.

  Can you try to reproduce it with WITNESS and *without*
  WITNESS_SKIPSPIN? I would need to look at show alllocks and
  possibily ps because it seems that the lock owner is preempted but
  it should not happen while holding a spinlock (unless the acquired
  spinlock is the one in the preempting path, in this case thought it
  should drop inside sched_switch() and we can try to understand why
  that doesn't happen).


Yesterday it happened again but the machines locked on panic command and 
nothing was dumped.
It also happened today, and as yesterday after some hours (~10) of uptime, but 
this time I've got no ddb.txt, just vmcore.

It stopped after the following message:
cpu reset: Stopping other CPUs

The output of show alllocks command is (http://pastebin.com/f2323ad60):
Process 1 (init) thread 0xc589bd80 (12)
exclusive sleep mutex Giant r = 0 (0xc0873b10) locked @ 
/usr/src/sys/kern/kern_module.c:102

That is the mtx_lock(Giant); line in static void module_shutdown(void 
*arg1, int arg2).


ps -axl from crashinfo (http://pastebin.com/f15e7ff90):
  UID   PID  PPID CPU PRI NI   VSZ   RSS MWCHAN STAT  TT   TIME COMMAND
0 0 0   0 -16  0 0 0 sched  DLs   ??  10505772:02.00 
[swapper]
0 1 0   0  -8  0  1888 0 -  RLs   ??  8198756:46.00 [init]
0 2 0   0  -8  0 0 0 -  DL??  -31491914:-33.55 
[g_event]
0 3 0   0  -8  0 0 0 -  DL??  -18031048:-1.55 [g_up]
0 4 0   0  -8  0 0 0 -  DL??  29902314:39.00 
[g_down]
0 5 0   0   8  0 0 0 -  DL??0:00.00 [kqueue tas
0 6 0   0  -8  0 0 0 ccb_sc DL??0:00.00 [xpt_thrd]
0 7 0   0   8  0 0 0 -  DL??0:00.00 [acpi_task_
0 8 0   0   8  0 0 0 -  DL??0:00.00 [acpi_task_
0 9 0   0   8  0 0 0 -  DL??0:00.00 [acpi_task_
010 0   0 -16  0 0 0 audit_ DL??0:00.00 [audit]
011 0   0 171  0 0 0 -  RL??  30495164:05.00 [idle: 
cpu1
012 0   0 171  0 0 0 -  RL??  -8752676:-56.55 
[idle: cpu0
013 0   0 -44  0 0 0 -  WL??  1297477:00.00 [swi1: 
net]
014 0   0 -32  0 0 0 -  RL??  25300285:42.00 [swi4: 
cloc
015 0   0 -36  0 0 0 -  WL??0:00.00 [swi3: vm]
016 0   0 -16  0 0 0 -  DL??  33237141:47.00 
[yarrow]
017 0   0 -40  0 0 0 -  WL??  33608583:19.00 [swi2: 
camb
018 0   0 -28  0 0 0 -  WL??0:00.00 [swi5: +]
019 0   0   8  0 0 0 -  DL??  577:12.00 [thread tas
020 0   0 -24  0 0 0 -  WL??  15874802:41.00 [swi6: 
Gian
021 0   0 -24  0 0 0 -  WL??  34388543:22.00 [swi6: 
task
022 0   0 -52  0 0 0 -  WL??0:00.00 [irq9: acpi
023 0   0 -80  0 0 0 -  WL??  33965005:45.00 
[irq24: vga
024 0   0 -64  0 0 0 -  WL??0:00.00 [irq28: ata
025 0   0 -64  0 0 0 -  WL??  15406643:53.00 
[irq21: ata
026 0   0 -64  0 0 0 -  WL??  225221:21.00 [irq14: 
ata
027 0   0 -64  0 0 0 -  WL??  -19343052:-29.55 
[irq15: ata
028 0   0 -64  0 0 0 -  WL??  -5763326:-52.55 
[irq20: uhc
029 0   0   8  0 0 0 usbevt DL??  143817:50.00 [usb0]
030 0   0   8  0 0 0 usbtsk DL??0:00.00 [usbtask-hc
031 0   0   8  0 0 0 usbtsk DL??0:00.00 [usbtask-dr
032 0   0 -64  0 0 0 -  WL??0:00.00 [irq22: uhc
033 0   0   8  0 0 0 usbevt DL??  139260:44.00 [usb1]
034 0   0

Re: status of flash9/flash10 support in RELENG_7 ?

2009-07-27 Thread barbara 
 On Sun, Jul 26, 2009 at 06:15:22PM +0200, barbara wrote:
   On Sun, 2009-07-26 at 10:32 +0200, Marc Fonvieille wrote:
On Sun, Jul 26, 2009 at 08:20:09AM +0200, barbara wrote:
 
  An example of the URLs that is giving me problems is the following
 
  http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
 
  (basically all videos from that site cause the same problem). I 
  would be
  grateful if you cold check it.
 


 The video looks fine here, even if I'm getting a warning about the 
 flash version.
 http://img24.imageshack.us/img24/2741/screenshotmassacolpitod.png

 I've found that on 7, the better combination for me is
 linux-flashplugin9, linux_base-fc4 and compat.linux.osrelease=2.4.2.
   
Same here: the video plays fine on 7.2-S with linux_base-fc4 and
linux-flashplugin9
   
 On CURRENT, using linux_base-f10, I get much more stuck process, while
 on 7 it barely happens.
   
On 8-BETA2 with linux_base-f10 and linux-f10-flashplugin10 that video
makes npviewer coredumping.
   
   This video played on my 8-BETA2 (r195818, SMP, i386) with linux_base-f10
   and linux-f10-flashplugin10 without dumping core. Was your BETA2 before
   or after library version bump and, if latter, did you rebuild all your
   ports?
  
 
  I've cvsupped and rebuilt my system on Jul. 23 and rebuilt all my ports.
  linux-f10-flashplugin10 is dumping core or not working for me too.
  BTW, why nspluginwrapper doesn't find the plugin?
 

 I assume it's cause nothing is installed under
 /usr/local/lib/browser_plugins/ so you need to do a

 ln -s /usr/local/lib/npapi/linux-f10-flashplugin/libflashplayer.so \
 /usr/local/lib/browser_plugins/

 just before the nspluginwrapper -v -a -i as I mentioned it in the
 Handbook.


That did the trick, thank you!
It's still lagging when I close the window, anyway it's working now.


Barbara



___
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: kern/134584: [panic] spin lock held too long

2009-07-27 Thread barbara 
 2009/7/26 barbara barbara.xxx1...@libero.it:
  It happened again, on shutdown.
  As the previous time, it happened after a high (for a desktop) uptime and, 
  if it could matter, after running net-p2p/transmission-gtk2 for several 
  hours.
  I don't know if it's related, but often quitting transmission, doesn't 
  terminate the process. Sometimes it end after several minutes the gui 
  exited, sometimes it's still running after hours.
  I've noticed it as the destination folder is on a manually mounted device 
  and I can't umount it as fstat reports the device used by a transmission 
  process.
  So I often have to kill it.
  This happened both the time I had this kind of panic.

 What hw is that? How many CPUs does it have?



It's desktop pc, dual Athlon CPU, VIA chipset and...
You can find my dmesg.boot here:
http://pastebin.com/f507125f1
Aks if you need more info!

In the meanwhile I've rebuilt my kernel adding WITNESS, KDB, DDB options. Is 
this what you need?
I'm not able to work with the debugger. I suppose I have to type the commands 
you asked (ps, show alllocks) when it's panicking and the debbugger starts and 
write down the output with pen and paper, am I corrent? Or is there a way to 
redirect or dump the output somewhere?
Sorry, I'll try reading the chapter in the dev. handbook and I will try to do 
my best, but please, tell me if you have some suggestions.

I'll try to reproduce the problem, even it's not happening regularly.
If you need more info or to test code, etc. I'll be glad to help you.
BTW, can the output of crashinfo be of any help? Here you can find ps -axl from 
crashinfo:
http://pastebin.com/f3d54f01b

Thanks
Barbara


___
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: kern/134584: [panic] spin lock held too long

2009-07-26 Thread barbara 
It happened again, on shutdown.
As the previous time, it happened after a high (for a desktop) uptime and, if 
it could matter, after running net-p2p/transmission-gtk2 for several hours.
I don't know if it's related, but often quitting transmission, doesn't 
terminate the process. Sometimes it end after several minutes the gui exited, 
sometimes it's still running after hours.
I've noticed it as the destination folder is on a manually mounted device and I 
can't umount it as fstat reports the device used by a transmission process.
So I often have to kill it.
This happened both the time I had this kind of panic.

Barbara


Script started on Sun Jul 26 08:22:33 2009
You have mail.
satanasso# kgdb kernel.debug /var/crash/vmcore.17
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 i386-marcel-freebsd...

Unread portion of the kernel message buffer:
118Stopping devd.
118Writing entropy file:
118.
118Terminated
118.
118Jul 25 17:45:18 satanasso syslogd: exiting on signal 15
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 6 5 3 1 2 2 0 0 done
All buffers synced.
Uptime: 22h41m12s
Rebooting...
cpu_reset: Stopping other CPUs
spin lock 0xc08ae540 (sched lock 1) held by 0xc588f480 (tid 16) too long
panic: spin lock held too long
cpuid = 0
Uptime: 22h41m14s
Physical memory: 2031 MB
Dumping 171 MB: (CTRL-C to abort)  156 140 124 108 92 76 60 44 28 12

Reading symbols from /boot/kernel/linux.ko...Reading symbols from 
/boot/kernel/linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/modules/nvidia.ko...done.
Loaded symbols for /boot/modules/nvidia.ko
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from 
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/linprocfs.ko...Reading symbols from 
/boot/kernel/linprocfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linprocfs.ko
Reading symbols from /boot/kernel/logo_saver.ko...Reading symbols from 
/boot/kernel/logo_saver.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/logo_saver.ko
Reading symbols from /boot/kernel/ntfs.ko...Reading symbols from 
/boot/kernel/ntfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/ntfs.ko
#0  doadump () at pcpu.h:196
196 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) bt
#0  doadump () at pcpu.h:196
#1  0xc059b097 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2  0xc059b36c in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3  0xc058bd1f in _mtx_lock_spin_failed (m=0x0) at 
/usr/src/sys/kern/kern_mutex.c:449
#4  0xc058c425 in _thread_lock_flags (td=0xc588f480, opts=0, file=0xc08200c8 
/usr/src/sys/kern/kern_intr.c, line=801) at /usr/src/sys/kern/kern_mutex.c:537
#5  0xc0576787 in intr_event_schedule_thread (ie=Variable ie is not available.
) at /usr/src/sys/kern/kern_intr.c:801
#6  0xc0577aa5 in swi_sched (cookie=0xc5880e00, flags=Variable flags is not 
available.
) at /usr/src/sys/kern/kern_intr.c:1028
#7  0xc055a6df in hardclock (usermode=0, pc=3229503748) at 
/usr/src/sys/kern/kern_clock.c:339
#8  0xc07ce23a in lapic_handle_timer (frame=0xc54aaba0) at 
/usr/src/sys/i386/i386/local_apic.c:705
#9  0xc07c6c9f in Xtimerint () at apic_vector.s:108
#10 0xc07e5104 in DELAY (n=100) at cpufunc.h:352
#11 0xc07e2c03 in cpu_reset () at /usr/src/sys/i386/i386/vm_machdep.c:594
#12 0xc059a753 in shutdown_reset (junk=0x0, howto=0) at 
/usr/src/sys/kern/kern_shutdown.c:493
#13 0xc059b117 in boot (howto=0) at /usr/src/sys/kern/kern_shutdown.c:421
#14 0xc059b247 in reboot (td=0xc588fd80, uap=0xc54aacfc) at 
/usr/src/sys/kern/kern_shutdown.c:172
#15 0xc07e07d5 in syscall (frame=0xc54aad38) at 
/usr/src/sys/i386/i386/trap.c:1089
#16 0xc07c6720 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:262
#17 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) thread apply all bt

Thread 52 (Thread 100051):
#0  sched_switch (td=0xc5c91d80, newtd=Variable newtd is not available.
) at /usr/src/sys/kern/sched_ule.c:1944
#1  0xc05a3033 in mi_switch (flags=Variable flags is not available.
) at /usr/src/sys/kern/kern_synch.c:444
#2  0xc05cf859 in sleepq_switch (wchan=Variable wchan is not available.
) at /usr/src/sys/kern/subr_sleepqueue.c:497
#3  0xc05d03d7 in sleepq_timedwait (wchan=0xc08bd300) at 
/usr/src/sys/kern/subr_sleepqueue.c:615
#4  0xc05a3483 in _sleep (ident=0xc08bd300, lock=0xc08bd2c0, priority=68, 
wmesg

Re: status of flash9/flash10 support in RELENG_7 ?

2009-07-26 Thread barbara 
 On Sat, Jul 25, 2009 at 06:42:44PM -0700, Kevin Oberman wrote:
 ...
   i see that for 8.x you suggest using fc10, which is also something i
   tried on RELENG_7 but had similar symptoms. Is there any known reason
   why HEAD and RELENG_7 should be different in terms of linux_base support ?
 
  Here is what is working for me for both Flash9 and Skype:
  linux_base-f8-8_11
  nspluginwrapper-1.2.2_2
  skype-2.0.0.72,1
  linux-flashplugin-9.0r159:
 
  Be sure that your various linux packages are updated to the -f8-
  versions, too. The upgrade for linux_base is the tricky one.

 Unfortunately I think there are many more details that one has
 to consider, such as CPU type and number of cores/threads,
 OS version, and presumably firefox version as well.
 Can you tell me more on the above ?

 I had flash9 working once, but it don't remember all the packages
 (and something was stale for sure); it got broken while installing
 skype (a mail thread mentioned an issue with some shared lib version,
 which was exactly the problem i had with skype. The fix was to
 either create a symlink on a library or install linux_base-f10 to fix it).

 An example of the URLs that is giving me problems is the following

 http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video

 (basically all videos from that site cause the same problem). I would be
 grateful if you cold check it.



The video looks fine here, even if I'm getting a warning about the flash 
version.
http://img24.imageshack.us/img24/2741/screenshotmassacolpitod.png

I've found that on 7, the better combination for me is linux-flashplugin9, 
linux_base-fc4 and compat.linux.osrelease=2.4.2.
On CURRENT, using linux_base-f10, I get much more stuck process, while on 7 it 
barely happens.

Barbara



___
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: status of flash9/flash10 support in RELENG_7 ?

2009-07-26 Thread barbara 
 On Sun, 2009-07-26 at 10:32 +0200, Marc Fonvieille wrote:
  On Sun, Jul 26, 2009 at 08:20:09AM +0200, barbara wrote:
   
An example of the URLs that is giving me problems is the following
   
http://tv.repubblica.it/copertina/massa-colpito-da-un-detrito/35446?video
   
(basically all videos from that site cause the same problem). I would be
grateful if you cold check it.
   
  
  
   The video looks fine here, even if I'm getting a warning about the flash 
   version.
   http://img24.imageshack.us/img24/2741/screenshotmassacolpitod.png
  
   I've found that on 7, the better combination for me is
   linux-flashplugin9, linux_base-fc4 and compat.linux.osrelease=2.4.2.
 
  Same here: the video plays fine on 7.2-S with linux_base-fc4 and
  linux-flashplugin9
 
   On CURRENT, using linux_base-f10, I get much more stuck process, while
   on 7 it barely happens.
 
  On 8-BETA2 with linux_base-f10 and linux-f10-flashplugin10 that video
  makes npviewer coredumping.
 
 This video played on my 8-BETA2 (r195818, SMP, i386) with linux_base-f10
 and linux-f10-flashplugin10 without dumping core. Was your BETA2 before
 or after library version bump and, if latter, did you rebuild all your
 ports?


I've cvsupped and rebuilt my system on Jul. 23 and rebuilt all my ports.
linux-f10-flashplugin10 is dumping core or not working for me too.
BTW, why nspluginwrapper doesn't find the plugin?

Barbara


___
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: 7.2-release/amd64: panic, spin lock held too long

2009-07-21 Thread barbara 
  I hope you can get some crash dumps for the developers to look at,
  Attilio was trying to help me but sadly the machine had to be put into
  active use so I could no longer play with FreeBSD due to unsolved
  instability.

 I want to help investigate this problem also but I remembered that the
 /var/crash was empty after the panic.. Just the same as your
 situation.
 So is there other ways to get the crash dumps?
 My machine is also put into service now but I think it should be OK
 for a short down time.

Could that one (on i386) be related?
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/134584


___
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: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE

2009-03-27 Thread barbara 
 On Sun, Mar 22, 2009 at 08:29:57PM +0100, barbara wrote:
 
  Any news about that?
 
  http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047527.html
 

 I'm sorry, I forgot this issue which was caused by my disk crash
 happened in the end of Jan, 2009.
 I've updated age(4) patch in the following URL.
 http://people.freebsd.org/~yongari/age/age.diff

 Please test the with
 1. shutdown your box
 2. remove power cable and wait 5 min.
 3. unplug UTP cabble
 4. boot and see whether age(4) does not lockup your box
 5. plug UTP cable and see whether age(4) can send/receive traffics

 And please do
 1. reboot your box with UTP cable plugged in
 2. check whether age(4) works

 Please also see whether ethernet MAC address is correctly detected
 in both cases.

 Thanks for reminder.


I tried with the last commited version after updating src with no luck: still 
hang on boot (actually it hangs when I kldload it, as I removed it from my 
KERNCONF, so I can boot with the NIC enabled).
Then I applied your patch and, as with the previous one you asked me to try, 
it's working.

I did the two tests exactly how you asked and everything seems fine.
The MAC address is correct in both cases.
The connection is working and I did some huge file transfer with ssh with 
another pc with performance comparable with my rl0 (I think at the limits of a 
100Mbps net, imposed by my router).

Here you can find my dmesg -a
http://pastebin.com/f4afd50db
If you have any other test I can do for you, please ask.

Do you have any idea if it will included it 7.2-RELEASE?

Thanks
Barbara


___
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

Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE

2009-03-22 Thread barbara 

Any news about that?

http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047527.html


___
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

g_vfs_done()...errors

2009-01-16 Thread barbara 

Hello,
while reading/writing dvd on 6-STABLE (can't remember on 7-STABLE right now), 
I'm getting the message buffer filled by errors.
This is my dvd-rw
$ sysctl dev.acd.0.%desc
dev.acd.0.%desc: PIONEER DVD-RW DVR-109/1.58
attached to
$ sysctl dev.atapci.1.%desc
dev.atapci.1.%desc: VIA 8237A UDMA133 controller

And the followings are some examples of the error:

g_vfs_done():cd0[READ(offset=3533693165190270976, length=2048)]error = 5
g_vfs_done():cd0[READ(offset=8751655366962446336, length=2048)]error = 5
g_vfs_done():cd0[READ(offset=8751655370713257984, length=2048)]error = 5

g_vfs_done():acd0[READ(offset=3533693165190270976, length=2048)]error = 5
g_vfs_done():acd0[READ(offset=8751655366962446336, length=2048)]error = 5
g_vfs_done():acd0[READ(offset=8751655370713257984, length=2048)]error = 5

Is it possible such a value for offset (DVD-SL)?
Does anyone know the reason of the error?
Should I be somehow worried?

Thanks


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE

2009-01-09 Thread Barbara 
On Mon, Jan 05, 2009 at 11:36:54AM +0100, Barbara wrote:

[...]

  I've 
tried all the thing you've suggested with 
  the same result.
  I've 
disabled LAN Option ROM, but it seems that I don't have 
  the other 
options you mentioned.
  I've downloaded and burned the 7.1-RELEASE dvd 
  
and tried to boot from it, but it hangs at the same point.
  Finally I've 
tried 
  booting a CURRENT snapshot cd (8.0-CURRENT-200812) and I was able to 
properly 
  configure the device in sysinstall.
  Any idea about the 
problem?

No, there is no source code differences between CURRENT and 7.1-
RELEASE.

  I've installed 
  from 7.0 and I have another NIC, but being 
now age in GENERIC, I hope it will 
  not cause troubles to other people 
installing for the first time.
  Anyway thank 
  you for now, and ask me if 
there is something that I can do to fix the problem 
  like more tests, 
patches, etc.
  

Would try the following WIP version?
http://people.
freebsd.org/~yongari/age/if_age.c
http://people.freebsd.
org/~yongari/age/if_agereg.h
I have no longer access to L1 hardware so I don't 
know whether it
helps or not.

-- 
Regards,
Pyun YongHyeon

Well, it 
works!
As I've said, it's not a real problem for me, but I'm so sorry about not 
having tested before so it could be merged before 7.1-RELEASE, but I had it 
disabled and nearly forgot about that.
Please, feel free to ask whenever you 
want if you want me doing tests on that NIC.

Thanks
Barbara

___
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: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE

2009-01-05 Thread Barbara 


On Wed, Dec 31, 2008 at 06:34:08AM +0100, Barbara wrote:
  Hello,
  one 
of my motherboards has an onboard Attansic network interface, I 
  think an 
AR8121.
  
  # pciconf -lcv
  no...@pci0:4:0:0:   class=0x02 
  
card=0x82261043 chip=0x10481969 rev=0xb0 hdr=0x00
  vendor = 
'Attansic 
  (Now owned by Atheros)'
  device = 'L1 Gigabit 
Ethernet 10/100/1000Base-T 
  Ethernet Controller'
  class  = 
network
  subclass   = ethernet
  cap 
  01[40] = powerspec 2  
supports D0 D3  current D0
  cap 05[48] = MSI supports 
  1 message, 64 
bit
  cap 10[58] = PCI-Express 1 endpoint
  cap 03[6c] = VPD
  
 
 
  Today I decided to give it a try.
  But if I try loading the if_age 
module, the 
  system prints the following lines and then it freezes.
  
 
 age0: Attansic 
  Technology Corp, L1 Gigabit Ethernet mem 0xfbdc-
0xfbdf irq 36 at 
  device 0.0 on pci4
  age0: PCI device revision : 
0x00b0
  age0: Chip id/revision : 
  0x9006
  age0: 1280 Tx FIFO, 2364 Rx 
FIFO
  age0: MSIX count : 0
  age0: MSI count : 
  1
  age0: Using 1 
MSI messages.
  age0: Read request size : 512 bytes.
  age0: TLP 
  
payload size : 128 bytes.
  

I guess it could be related with VPD access 
code in age(4) or
automatic power-down feature of hardware. Unfortunately I 
have no
longer access to L1 hardware so it looks hard to write a patch for

the issue. Would you try following instructions?
 - Shutdown your box.
 - 
Completely remove power cord from your system and wait 5 to 10
   min.(Just 
turning system off is not enough.)
 - Make sure to plug UTP cable to your 
controller before system
   boot.
 - Plug power cord and let system boot.
 - 
Enter BIOS menu and search onboard PCIe LAN configuration in the
   menu. If 
LAN Option ROM was enabled, disable the option.
 - Some motherboard might 
have set another option for Check
   Atheros LAN cable. If it was set, 
disable it. If you also have
   an option for Asus Express Gate try 
disabling it.
 - Save changes and reboot.

Does that make any difference?


-- 
Regards,
Pyun YongHyeon

I've tried all the thing you've suggested with 
the same result.
I've disabled LAN Option ROM, but it seems that I don't have 
the other options you mentioned.
I've downloaded and burned the 7.1-RELEASE dvd 
and tried to boot from it, but it hangs at the same point.
Finally I've tried 
booting a CURRENT snapshot cd (8.0-CURRENT-200812) and I was able to properly 
configure the device in sysinstall.
Any idea about the problem?
I've installed 
from 7.0 and I have another NIC, but being now age in GENERIC, I hope it will 
not cause troubles to other people installing for the first time.
Anyway thank 
you for now, and ask me if there is something that I can do to fix the problem 
like more tests, patches, etc.

Best regards
Barbara

___
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

R: cvsup freebsd 6_2 to freebsd 7_1 not upgrading?

2009-01-05 Thread Barbara 

Hello List,
I'm trying to upgrade my system from 6_2 to 7_1 and cannot seem 
to do it.
Perhaps I'm missing something. Here is the basic procedure I'm 
following.

#cp /usr/share/examples/cvsup/standard-supfile /root/stand_sup

#vi /root/stand_sup
host=CHANGE_ME.freebsd.org
host=cvsup15.us.FreeBSD.
org
tag=RELENG_6_2
tag=RELENG_7_1

#cd /usr/src
#cvsup -g -L2 
/root/stand_sup
...
#make -j4 buildworld; make -j4 buildkernel; make 
installkernel

... (come back a hour or so later)
#make installworld; reboot



It seems that you have missed to run mergemaster -p before, and 
mergemaster after running make installworld.
IMHO, not running mergemaster, 
you have not updated /etc/motd so it shows 6.2...
And, as pointed by Brooks 
Davis you should have rebooted before running make installworld.


___
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

cvsup freebsd 6_2 to freebsd 7_1 not upgrading?

2009-01-05 Thread Barbara 


Messaggio originale
Da: barbara.xxx1...@libero.it
Data: 05/01/2009 
22.01
A: br...@box201.com, FreeBSD-stable@FreeBSD.org
Ogg: R: cvsup 
freebsd 6_2 to freebsd 7_1 not upgrading?


Hello List,
I'm trying to 
upgrade my system from 6_2 to 7_1 and cannot seem 
to do it.
Perhaps I'm 
missing something. Here is the basic procedure I'm 
following.

#cp 
/usr/share/examples/cvsup/standard-supfile /root/stand_sup

#vi 
/root/stand_sup
host=CHANGE_ME.freebsd.org
host=cvsup15.us.FreeBSD.

org
tag=RELENG_6_2
tag=RELENG_7_1

#cd /usr/src
#cvsup -g -L2 

/root/stand_sup
...
#make -j4 buildworld; make -j4 buildkernel; make 

installkernel

... (come back a hour or so later)
#make installworld; 
reboot



It seems that you have missed to run mergemaster -p before, 
and 
mergemaster after running make installworld.
IMHO, not running 
mergemaster, 
you have not updated /etc/motd so it shows 6.2...
Obviously 
among the other files.
And, as pointed by Brooks 
Davis you should have 
rebooted before running make installworld.
Try also reading the comments in 
/usr/src/Makefile

___
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: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE

2008-12-31 Thread Barbara 
 Today I decided to give it a try.
 But if I try loading the if_age module, 
the
 system prints the following lines and then it freezes.



Could you 
please print the full dmesg / uname (build date) output?


Thanks.


---

Kevin K.
Systems Administrator
www.linux-vps-servers.com


Sure!
/usr/src 
has been synced right before starting the buildworld.
# uname -a
FreeBSD 
satanasso.local.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Wed Dec 31 03:55:
33 CET 2008 r...@satanasso.local.net:/usr/obj/usr/src/sys/SATANASSO  i386


If I load age adding it in my kernconf or with the loader, the system freezes 
so the relevant part on dmesg should be the following two lines:
pci4: ACPI 
PCI bus on pcib5
pci4: network, ethernet at device 0.0 (no driver attached)



Here comes the full dmesg output.
Unfortunately the web client of my mail 
provider, does something stupid with the text, so I know it could be confused.

If asked I can send it via email as attachment.

# dmesg
Copyright (c) 1992-
2009 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 7.1-PRERELEASE #0: Wed Dec 31 03:55:33 CET 2008
r...@satanasso.
local.net:/usr/obj/usr/src/sys/SATANASSO
Timecounter i8254 frequency 1193182 
Hz quality 0
CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ (2499.74-MHz 
686-class CPU)
  Origin = AuthenticAMD  Id = 0x60fb1  Stepping = 1
  
Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT
  Features2=0x2001SSE3,CX16
  
AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+,3DNow!
  AMD 
Features2=0x11fLAHF,CMP,SVM,ExtAPIC,CR8,Prefetch
  Cores per package: 2
real 
memory  = 2147155968 (2047 MB)
avail memory = 2087157760 (1990 MB)
ACPI APIC 
Table: A_M_I_ OEMAPIC 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 
cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
ioapic0 Version 0.3 irqs 0-23 
on motherboard
ioapic1 Version 0.3 irqs 24-47 on motherboard
kbd1 at kbdmux0

acpi0: A_M_I_ OEMRSDT on motherboard
acpi0: [ITHREAD]
acpi0: Power Button 
(fixed)
acpi0: reservation of 0, a (3) failed
acpi0: reservation of 10, 
7ff0 (3) failed
Timecounter ACPI-fast frequency 3579545 Hz quality 1000

acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0

acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0

Timecounter HPET frequency 14318180 Hz quality 900
pcib0: ACPI Host-PCI 
bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI 
PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
pcib2: 
ACPI PCI-PCI bridge irq 27 at device 2.0 on pci0
pci2: ACPI PCI bus on 
pcib2
vgapci0: VGA-compatible display port 0xdc00-0xdc7f mem 0xfa00-
0xfaff,0xd000-0xdfff,0xf800-0xf9ff irq 24 at device 0.0 on 
pci2
nvidia0: GeForce 8500 GT on vgapci0
vgapci0: child nvidia0 requested 
pci_enable_busmaster
vgapci0: child nvidia0 requested pci_enable_io
nvidia0: 
[GIANT-LOCKED]
nvidia0: [ITHREAD]
pcib3: ACPI PCI-PCI bridge irq 31 at device 
3.0 on pci0
pci6: ACPI PCI bus on pcib3
pcib4: ACPI PCI-PCI bridge irq 35 
at device 3.1 on pci0
pci5: ACPI PCI bus on pcib4
pcib5: ACPI PCI-PCI 
bridge irq 39 at device 3.2 on pci0
pci4: ACPI PCI bus on pcib5
pci4: 
network, ethernet at device 0.0 (no driver attached)
pcib6: ACPI PCI-PCI 
bridge irq 43 at device 3.3 on pci0
pci3: ACPI PCI bus on pcib6
atapci0: 
VIA 8237A SATA150 controller port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,
0xc480-0xc483,0xc400-0xc40f,0xc000-0xc0ff irq 21 at device 15.0 on pci0

atapci0: [ITHREAD]
ata2: ATA channel 0 on atapci0
ata2: [ITHREAD]
ata3: ATA 
channel 1 on atapci0
ata3: [ITHREAD]
atapci1: VIA 8237A UDMA133 controller 
port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0

ata0: ATA channel 0 on atapci1
ata0: [ITHREAD]
ata1: ATA channel 1 on 
atapci1
ata1: [ITHREAD]
uhci0: VIA 83C572 USB controller port 0xb480-0xb49f 
irq 20 at device 16.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: VIA 
83C572 USB controller on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root 
hub, class 9/0, rev 1.00/1.00, addr 1 on usb0
uhub0: 2 ports with 2 removable, 
self powered
uhci1: VIA 83C572 USB controller port 0xb800-0xb81f irq 22 at 
device 16.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: VIA 83C572 
USB controller on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, 
class 9/0, rev 1.00/1.00, addr 1 on usb1
uhub1: 2 ports with 2 removable, self 
powered
uhci2: VIA 83C572 USB controller port 0xb880-0xb89f irq 21 at device 
16.2 on pci0
uhci2: [GIANT-LOCKED]
uhci2: [ITHREAD]
usb2: VIA 83C572 USB 
controller on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 
9/0, rev 1.00/1.00, addr 1 on usb2
uhub2: 2 ports with 2 removable, self 
powered
uhci3: VIA 83C572 USB controller

RE: Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE

2008-12-31 Thread Barbara 
 Today I decided to give it a try.
 But if I try loading the if_age 
module, 
the
 system prints the following lines and then it freezes.




Could you 
please print the full dmesg / uname (build date) output?



Thanks.


---

Kevin K.
Systems Administrator
www.linux-vps-
servers.com



Maybe this is better:
http://pastebin.ca/1297510

___
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

Lock enabling onboard lan (Attansic L1 GbE) on 7.1-PRERELEASE

2008-12-30 Thread Barbara 
Hello,
one of my motherboards has an onboard Attansic network interface, I 
think an AR8121.

# pciconf -lcv
no...@pci0:4:0:0:   class=0x02 
card=0x82261043 chip=0x10481969 rev=0xb0 hdr=0x00
vendor = 'Attansic 
(Now owned by Atheros)'
device = 'L1 Gigabit Ethernet 10/100/1000Base-T 
Ethernet Controller'
class  = network
subclass   = ethernet
cap 
01[40] = powerspec 2  supports D0 D3  current D0
cap 05[48] = MSI supports 
1 message, 64 bit
cap 10[58] = PCI-Express 1 endpoint
cap 03[6c] = VPD


Today I decided to give it a try.
But if I try loading the if_age module, the 
system prints the following lines and then it freezes.

age0: Attansic 
Technology Corp, L1 Gigabit Ethernet mem 0xfbdc-0xfbdf irq 36 at 
device 0.0 on pci4
age0: PCI device revision : 0x00b0
age0: Chip id/revision : 
0x9006
age0: 1280 Tx FIFO, 2364 Rx FIFO
age0: MSIX count : 0
age0: MSI count : 
1
age0: Using 1 MSI messages.
age0: Read request size : 512 bytes.
age0: TLP 
payload size : 128 bytes.


___
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

Fatal trap 12: page fault while in kernel mode (swi6: task queue)

2008-12-26 Thread Barbara 
Can anyone help understanding the reason?

# uname -rsm
FreeBSD 6.4-STABLE i386


# kgdb kernel.debug /var/crash/vmcore.7 
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 i386-marcel-freebsd...

Unread portion of 
the kernel message buffer:
acd0: WARNING - PREVENT_ALLOW read data overrun 180

kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in 
kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x104
fault code  = 
supervisor read, page not present
instruction pointer = 0x20:0xc0541da5
stack 
pointer = 0x28:0xe5928c00
frame pointer   = 0x28:0xe5928c18
code 
segment = base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 
1
processor eflags= resume, IOPL = 0
current process = 17 (swi6: task queue)

trap number = 12
panic: page fault
cpuid = 0
Uptime: 4h16m22s
Physical memory: 
2031 MB
Dumping 204 MB: 189 173 157 141 125 109 93 77 61 45 29 13

Reading 
symbols from /boot/kernel/linux.ko...done.
Loaded symbols for 
/boot/kernel/linux.ko
Reading symbols from /boot/modules/nvidia.ko...done.

Loaded symbols for /boot/modules/nvidia.ko
Reading symbols from 
/boot/kernel/acpi.ko...done.
Loaded symbols for /boot/kernel/acpi.ko
Reading 
symbols from /boot/kernel/linprocfs.ko...done.
Loaded symbols for 
/boot/kernel/linprocfs.ko
Reading symbols from /boot/kernel/logo_saver.ko...
done.
Loaded symbols for /boot/kernel/logo_saver.ko
#0  doadump () at pcpu.h:
165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) bt
#0  
doadump () at pcpu.h:165
#1  0xc054d7d9 in boot (howto=260) at 
/usr/src/sys/kern/kern_shutdown.c:410
#2  0xc054dba6 in panic (fmt=0xc0736cc9 %
s) at /usr/src/sys/kern/kern_shutdown.c:566
#3  0xc071812c in trap_fatal 
(frame=0xe5928bc0, eva=0) at /usr/src/sys/i386/i386/trap.c:838
#4  0xc07177e4 
in trap (frame=
  {tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -960560384, 
tf_esi = 4, tf_ebp = -443380712, tf_isp = -443380756, tf_ebx = -942867596, 
tf_edx = 6, tf_ecx = 4, tf_eax = 1, tf_trapno = 12, tf_err = 0, tf_eip = 
-1068229211, tf_cs = 32, tf_eflags = 65538, tf_esp = -942867596, tf_ss = 0}) at 
/usr/src/sys/i386/i386/trap.c:270
#5  0xc06ff98a in calltrap () at 
/usr/src/sys/i386/i386/exception.s:139
#6  0xc0541da5 in _mtx_lock_sleep 
(m=0xc7ccfb74, tid=3334406912, opts=0, file=0x0, line=0) at 
/usr/src/sys/kern/kern_mutex.c:546
#7  0xc054ca79 in _sema_post 
(sema=0xc7ccfb74, file=0x0, line=0) at /usr/src/sys/kern/kern_sema.c:79
#8  
0xc04705e3 in ata_completed (context=0xc7ccfb28, dummy=1) at 
/usr/src/sys/dev/ata/ata-queue.c:481
#9  0xc057547d in taskqueue_run 
(queue=0xc6c8a000) at /usr/src/sys/kern/subr_taskqueue.c:257
#10 0xc0575793 in 
taskqueue_swi_run (dummy=0x0) at /usr/src/sys/kern/subr_taskqueue.c:299
#11 
0xc052ff1b in ithread_execute_handlers (p=0xc6bef860, ie=0xc6c44e80) at 
/usr/src/sys/kern/kern_intr.c:682
#12 0xc0530077 in ithread_loop 
(arg=0xc6c62510) at /usr/src/sys/kern/kern_intr.c:766
#13 0xc052e800 in 
fork_exit (callout=0xc0530010 ithread_loop, arg=0x1, frame=0x1) at 
/usr/src/sys/kern/kern_fork.c:788
#14 0xc06ff9ec in fork_trampoline () at 
/usr/src/sys/i386/i386/exception.s:208
(kgdb) frame 6
#6  0xc0541da5 in 
_mtx_lock_sleep (m=0xc7ccfb74, tid=3334406912, opts=0, file=0x0, line=0) at 
/usr/src/sys/kern/kern_mutex.c:546
546 owner = (struct thread *)(v  
MTX_FLAGMASK);
(kgdb) list
541 #if defined(SMP)  !defined
(NO_ADAPTIVE_MUTEXES)
542 /*
543  * If the current owner of the lock is 
executing on another
544  * CPU, spin instead of blocking.
545  */
546 
owner = (struct thread *)(v  MTX_FLAGMASK);
547 #ifdef ADAPTIVE_GIANT
548 if 
(TD_IS_RUNNING(owner)) {
549 #else
550 if (m != Giant  TD_IS_RUNNING
(owner)) {

___
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

R: Re: 6.4-RC2 crashes after a few minutes of uptime

2008-11-23 Thread Barbara 
 About kgdb...
 I never used freebsd-update, so sorry if I'm saying 
something  
 stupid, but could it be the case that the kernel has been 
built  
 without debugging symbols or something like that? Does freebsd- 
 
update provide a kernel.debug?

I haven't had to use a the kernel.debug file 
in the obj dir in a long  
time. As far as I know, these days, the GENERIC 
kernel includes debug  
symbols. And in cases when there aren't any debug 
symbols, that  
shouldn't prevent kgdb from loading, I wouldn't think.

Hello,

I had a k panic some hours ago but I think that's related to a problem with one 
of my HDs.

I've got a dump in /var/crash, and as you were interested, I run:


# kgdb /boot/kernel/kernel /var/crash/vmcore.6


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 i386-
marcel-freebsd...(no debugging symbols found)...

Attempt to extract a 
component of a value that is not a structure pointer.

Attempt to extract a 
component of a value that is not a structure pointer.

Attempt to extract a 
component of a value that is not a structure pointer.

Attempt to extract a 
component of a value that is not a structure pointer.

Terminated


I had 
to pkill kgdb as it was in a loop.

Running it against kernel.debug in 
/usr/obj/usr/src/sys/$KERNCONF/ worked as expected.
I've always followed this 
way, so I don't know if it was working with earlier releases.

B

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

R: Re: R: Re: 6.4-RC2 crashes after a few minutes of uptime

2008-11-23 Thread Barbara 
 About kgdb...
 I never used freebsd-update, so sorry if I'm saying
 
something
 stupid, but could it be the case that the kernel has been
 
built
 without debugging symbols or something like that? Does freebsd-


 update provide a kernel.debug?

 I haven't had to use a the kernel.
debug file
 in the obj dir in a long
 time. As far as I know, these days, 
the GENERIC
 kernel includes debug
 symbols. And in cases when there 
aren't any debug
 symbols, that
 shouldn't prevent kgdb from loading, I 
wouldn't think.

 Hello,

 I had a k panic some hours ago but I think 
that's related to a  
 problem with one
 of my HDs.

 I've got a dump 
in /var/crash, and as you were interested, I run:


# kgdb 
/boot/kernel/kernel /var/crash/vmcore.6


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 i386-
 marcel-freebsd...(no debugging 
symbols found)...

Attempt to extract a
 component of a value that is 
not a structure pointer.

Attempt to extract a
 component of a value 
that is not a structure pointer.

Attempt to extract a
 component of 
a value that is not a structure pointer.

Attempt to extract a
 
component of a value that is not a structure pointer.

Terminated



 I had
 to pkill kgdb as it was in a loop.

 Running it against kernel.
debug in
 /usr/obj/usr/src/sys/$KERNCONF/ worked as expected.
 I've always 
followed this
 way, so I don't know if it was working with earlier releases.


Ah, well you must not be using GENERIC then, because it does have the  

debugging symbols.

I think this is the setting in the GENERIC config that 
controls it:

makeoptionsDEBUG=-g

But I guess what you're doing works if 
you're using a custom kernel  
that does not have that config setting.

- 
rory


I'm not using GENERIC but I have 
makeoptions DEBUG=-g
in my KERNCONF.

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

6.4-RC2 crashes after a few minutes of uptime

2008-11-16 Thread Barbara 



Ok, guess something is amiss with the CD-ROM drive on this notebook,  
as 
in GNOME, it flashes an icon of a CD on the desktop from time to  
time, as if 
it has detected a disc in the drive. But of course there  
is no disc in the 
drive. I believe it did the same with 6.3 though,  
but as said before didn't 
ever panic due to this issue.

So, some anecdotal info, after running RC2 for 
a few days now. It  
seems the pattern is that it seems to always panic a few 
minutes after  
a first cold boot, but then seems to remain stable after the 
second  
boot. Odd, as with 6.3 this didn't happen. So, I happened to catch 
a  
panic while working in the syscons console after one of these cold  

boots. As far as I can tell,  the panic does have something to do with  
the 
the CD-ROM drive, as right after I saw this message on the  
console, it 
immediately paniced:

acd0: WARNING - PREVENT_ALLOW read data overrun 180


and then the panic is as follows:

kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
fault virtual address  = 0x78

fault code = supervisor read, page not present
instruction pointer= 
0x20:0xc06d39b9
stack pointer  = 0x28:0xca865c10
frame pointer  = 0x28:
0xca865c14
code segment   = base 0x0, limit 0xf, type 0x1b
   = DPL 0, 
pres 1, def32 1, gran 1
processor eflags   = resume, IOPL = 0
current process
= 19 (swi6: task queue)
trap number= 12
panic: page fault
Uptime: 
1h9m7s
Physical memory: 179MB
Dumping 43MB: 28 12
Dump complete

Hi Rory,

did you see my replies or are you missing them for any reason?

Your panics and 
some aspects about how they happens look like mine to me, look here:
http:
//lists.freebsd.org/pipermail/freebsd-stable/2008-October/045865.html


Unfortunately I got no answer about that and I've had no comment in the pr I've 
filed http://www.freebsd.org/cgi/query-pr.cgi?pr=128076
I wonder if someone had 
the time to look at it.


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

Re: 6.4-RC2 crashes after a few minutes of uptime

2008-11-16 Thread barbara 
  Hi Rory,
 
  did you see my replies or are you missing them for any reason?

 Yes, I have seen your replies. I must have missed the PR you mentioned 
 last time, sorry.

No problem!

  Your panics and
  some aspects about how they happens look like mine to me, look here:
  http:
  //lists.freebsd.org/pipermail/freebsd-stable/2008-October/045865.html

 Yes, indeed. That looks very similar to the issue I'm running into
 with 6.4-RC2 as well. Sounds like it might be a regression in ata(4).  
 At least you were able to open the core dump. Are you still able to
 open core dumps with RC2?


I'm not sure. I'm running STABLE and I had no panics after the branch has 
changed to RC2. It seems that my panics are not frequent as yours.
Anyway my box freezed a couple of times after last newvers.sh and the symptoms 
looked like the same, with messages about acd0. I was able to ping it but it 
won't let me ssh in, like it was using all the cpus.

About kgdb...
I never used freebsd-update, so sorry if I'm saying something stupid, but could 
it be the case that the kernel has been built without debugging symbols or 
something like that? Does freebsd-update provide a kernel.debug?
I've seen that you are not using shiny quad-core, but could you try building a 
kernel by yourself? I think that you could do it using a different, more 
powerful, freebsd box if you have it, or even on qemu. I could help if you wish.



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

R: Re: 6.4-RC2 crashes after a few minutes of uptime

2008-11-07 Thread Barbara 

The person who followed up with a list of things that *may* have made
the 
problem go away mentioned one of the things was disabling powerd.
Do you have 
that enable, and if yes would you mind disabling it to see
if that's the 
culprit?

Thanks for the report.


Hi, it's the person speaking ;)
It seems 
that I spoke too early.
About an hour ago my box hung, but this time it didn't 
panicked (it isn't since ~Oct. 12). And as confirmed by Rory, it's seems that 
powerd isn't responsible.
The only thing I was able to do has been switching to 
ttyv0 but after entering my login, it didn't prompted for the password.
In the 
meanwhile, messages similar to the following were popping out:

acd0: 
WARNING - PREVENT_ALLOW taskqueue timeout - completing request directly

acd0: WARNING - PREVENT_ALLOW freeing taskqueue zombie request
acd0: 
WARNING - TEST_UNIT_READY taskqueue timeout - completing request directly

acd0: WARNING - TEST_UNIT_READY freeing taskqueue zombie request

Again, as 
I've reported in http://www.freebsd.org/cgi/query-pr.cgi?pr=128076 , I was not 
using acd0 and I never did since the box had been turned on.
The box was 
replying if pinged, but I was unable to access it via ssh, so I had to press 
the reset button.

What happened is similar to what is described here:
http:
//lists.freebsd.org/pipermail/freebsd-ports/2006-December/037796.html

And here 
http://www.freebsd.org/cgi/query-pr.cgi?pr=110015 I can see another swi6 panic 
with the same message in the kernel buffer (acd0: WARNING - PREVENT_ALLOW read 
data overrun 180) I had in pr.

Isn't my backtrace of any help in tracking 
down the problem?

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

Re: What could be causing unexpected reads to acd0?

2008-10-26 Thread barbara 
Sorry, I've just joined the stable ml.

Is the problem that is happening to you, something similar to what is described 
here (and linked threads)?
http://www.freebsd.org/cgi/query-pr.cgi?pr=128076


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

6.4-PRELEASE sporadically panicking with fatal trap 12

2008-10-11 Thread barbara 
Hello,
I'm running 6.4-PRELEASE, last built on 2008-10-05 with /usr/src updated on the 
same day.
I had a panic that looks to me very similiar to the one described here (hence 
the subject):
http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045405.html

What caught my curiosity is the message:

Unread portion of the kernel message buffer:

acd0: WARNING - TEST_UNIT_READY read data overrun 180

kernel trap 12 with interrupts disabled

I don't have atapicam built in the kernel and it wasn't loaded, and I'm pretty 
sure no media was inserted in my dvdrw unit since the last boot.
The other report has a similar message too (acd1: WARNING - READ_TOC read data 
overrun 1812)


Here's the backtrace:

# kgdb kernel.debug /var/crash/vmcore.2
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 i386-marcel-freebsd...



Unread portion of the kernel message buffer:

acd0: WARNING - TEST_UNIT_READY read data overrun 180

kernel trap 12 with interrupts disabled





Fatal trap 12: page fault while in kernel mode

cpuid = 0; apic id = 00

fault virtual address   = 0x104

fault code  = supervisor read, page not present

instruction pointer = 0x20:0xc05419e5

stack pointer   = 0x28:0xe5928c00

frame pointer   = 0x28:0xe5928c18

code segment= base 0x0, limit 0xf, type 0x1b

= DPL 0, pres 1, def32 1, gran 1

processor eflags= resume, IOPL = 0

current process = 17 (swi6: task queue)

trap number = 12

panic: page fault

cpuid = 0

Uptime: 22h2m3s

Physical memory: 2031 MB

Dumping 287 MB: 272 256 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16



Reading symbols from /boot/kernel/linux.ko...done.

Loaded symbols for /boot/kernel/linux.ko

Reading symbols from /boot/modules/nvidia.ko...done.

Loaded symbols for /boot/modules/nvidia.ko

Reading symbols from /boot/kernel/acpi.ko...done.

Loaded symbols for /boot/kernel/acpi.ko

Reading symbols from /boot/kernel/linprocfs.ko...done.

Loaded symbols for /boot/kernel/linprocfs.ko

Reading symbols from /boot/kernel/logo_saver.ko...done.

Loaded symbols for /boot/kernel/logo_saver.ko

Reading symbols from /boot/kernel/smbfs.ko...done.

Loaded symbols for /boot/kernel/smbfs.ko

Reading symbols from /boot/kernel/libiconv.ko...done.

Loaded symbols for /boot/kernel/libiconv.ko

Reading symbols from /boot/kernel/libmchain.ko...done.

Loaded symbols for /boot/kernel/libmchain.ko

#0  doadump () at pcpu.h:165

165 __asm __volatile(movl %%fs:0,%0 : =r (td));

(kgdb) list *0xc05419e5

0xc05419e5 is in _mtx_lock_sleep (/usr/src/sys/kern/kern_mutex.c:548).

543  * If the current owner of the lock is executing on 
another

544  * CPU, spin instead of blocking.

545  */

546 owner = (struct thread *)(v  MTX_FLAGMASK);

547 #ifdef ADAPTIVE_GIANT

548 if (TD_IS_RUNNING(owner)) {

549 #else

550 if (m != Giant  TD_IS_RUNNING(owner)) {

551 #endif

552 turnstile_release(m-mtx_object);
(kgdb)

(kgdb) bt full

#0  doadump () at pcpu.h:165

No locals.

#1  0xc054d419 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410

first_buf_printf = 1

#2  0xc054d7e6 in panic (fmt=0xc0736da9 %s) at 
/usr/src/sys/kern/kern_shutdown.c:566

td = (struct thread *) 0xc6bf0300

bootopt = 260

newpanic = 0

ap = 0xc6bf0300 `øŸÆàڟÆ

buf = page fault, '\0' repeats 245 times

#3  0xc071822c in trap_fatal (frame=0xe5928bc0, eva=0) at 
/usr/src/sys/i386/i386/trap.c:838

code = 40

ss = 40

esp = 0

type = 12

softseg = {ssd_base = 0, ssd_limit = 1048575, ssd_type = 27, ssd_dpl = 
0, ssd_p = 1, ssd_xx = 0, ssd_xx1 = 0, ssd_def32 = 1, ssd_gran = 1}

msg = 0x0

#4  0xc07178e4 in trap (frame=

  {tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -960560384, tf_esi = 4, 
tf_ebp = -443380712, tf_isp = -443380756, tf_ebx = -937328156, tf_edx = 6, 
tf_ecx = 4, tf_eax = 1, tf_trapno = 12, tf_err = 0, tf_eip = -1068230171, tf_cs 
= 32, tf_eflags = 65538, tf_esp = -937328156, tf_ss = 0})

at /usr/src/sys/i386/i386/trap.c:270

td = (struct thread *) 0xc6bf0300

p = (struct proc *) 0xc6bef860

sticks = 4999

type = 12

i = 0

ucode = 0

code = 0

eva = 260

#5  0xc06ffaaa in calltrap () at /usr/src/sys/i386/i386/exception.s:139

No locals.

#6  0xc05419e5 in _mtx_lock_sleep (m=0xc82181e4, tid=3334406912, opts=0, 
file=0x0, line=0) at

Re: 6.4-PRELEASE sporadically panicking with fatal trap 12

2008-10-11 Thread barbara 

 barbara wrote:
  Hello,
  I'm running 6.4-PRELEASE, last built on 2008-10-05 with /usr/src updated on 
  the same day.
  I had a panic that looks to me very similiar to the one described here 
  (hence the subject):
  http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045405.html
 
  What caught my curiosity is the message:
 
  Unread portion of the kernel message buffer:
 
  acd0: WARNING - TEST_UNIT_READY read data overrun 180
 
  kernel trap 12 with interrupts disabled
 
  I don't have atapicam built in the kernel and it wasn't loaded, and I'm 
  pretty sure no media was inserted in my dvdrw unit since the last boot.
  The other report has a similar message too (acd1: WARNING - READ_TOC read 
  data overrun 1812)
 
 
  Here's the backtrace:
 
 Interesting.  I ran 6.3 for a bit before I changed over to 7.0.  Neither
 6.3 or 7.0 exhibited this problem.

 I'm at 7.1 prerelease #4 now, and I'm using Fluxbox instead of Gnome.
 The system has been up six days with no problems.  I'll probably try
 using Gnome again after 7.1 release is out.  There's also a patch to ATA
 that I might try.  Or possibly I'll just wait for 7.1. :-)


Obviously I was confused when I wrote about atapicam, in fact the message is 
about acd0.
Anyway I'm sure that no media was inserted during the whole uptime.
I'm running both 6 and 7 stable and I've never seen this before too.

Few minutes ago, while cron was running, the system froze for a couple of 
minutes and the these lines was added to /var/log/messages:

acd0: WARNING - PREVENT_ALLOW taskqueue timeout - completing request 
directly
acd0: WARNING - PREVENT_ALLOW freeing taskqueue zombie request

and again, no media was inserted.
The only change I did in the last days was enabling powerd, I have no idea if 
this could be related.


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

Re: 6.4-PRELEASE sporadically panicking with fatal trap 12

2008-10-11 Thread barbara 
  barbara wrote:
   Hello,
   I'm running 6.4-PRELEASE, last built on 2008-10-05 with /usr/src updated 
   on the same day.
   I had a panic that looks to me very similiar to the one described here 
   (hence the subject):
   http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045405.html
  
   What caught my curiosity is the message:
  
 Unread portion of the kernel message buffer:
  
 acd0: WARNING - TEST_UNIT_READY read data overrun 180
  
 kernel trap 12 with interrupts disabled
  
   I don't have atapicam built in the kernel and it wasn't loaded, and I'm 
   pretty sure no media was inserted in my dvdrw unit since the last boot.
   The other report has a similar message too (acd1: WARNING - READ_TOC read 
   data overrun 1812)
  
  
   Here's the backtrace:
  
  Interesting.  I ran 6.3 for a bit before I changed over to 7.0.  Neither
  6.3 or 7.0 exhibited this problem.
 
  I'm at 7.1 prerelease #4 now, and I'm using Fluxbox instead of Gnome.
  The system has been up six days with no problems.  I'll probably try
  using Gnome again after 7.1 release is out.  There's also a patch to ATA
  that I might try.  Or possibly I'll just wait for 7.1. :-)
 

 Obviously I was confused when I wrote about atapicam, in fact the message is 
 about acd0.
 Anyway I'm sure that no media was inserted during the whole uptime.
 I'm running both 6 and 7 stable and I've never seen this before too.

 Few minutes ago, while cron was running, the system froze for a couple of 
 minutes and the these lines was added to /var/log/messages:

   acd0: WARNING - PREVENT_ALLOW taskqueue timeout - completing request 
 directly
   acd0: WARNING - PREVENT_ALLOW freeing taskqueue zombie request

 and again, no media was inserted.
 The only change I did in the last days was enabling powerd, I have no idea if 
 this could be related.


Here's another one, but it looks different.
Having no clue, I've restored the not enabled state of powerd for the moment.


# kgdb kernel.debug /var/crash/vmcore.3
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 i386-marcel-freebsd...

Unread portion of the kernel message buffer:
kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0xca0a9228
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc055d136
stack pointer   = 0x28:0xe58f8c68
frame pointer   = 0x28:0xe58f8ca8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 12 (swi4: clock sio)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 5h19m51s
Physical memory: 2031 MB
Dumping 282 MB: 267 (CTRL-C to abort)  251 235 219 203 187 (CTRL-C to abort)  
171 155 139 123 107 91 75 59 43 27 11 (CTRL-C to abort)

Reading symbols from /boot/kernel/linux.ko...done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/modules/nvidia.ko...done.
Loaded symbols for /boot/modules/nvidia.ko
Reading symbols from /boot/kernel/acpi.ko...done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/linprocfs.ko...done.
Loaded symbols for /boot/kernel/linprocfs.ko
Reading symbols from /boot/kernel/logo_saver.ko...done.
Loaded symbols for /boot/kernel/logo_saver.ko
#0  doadump () at pcpu.h:165
165 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) bt full
#0  doadump () at pcpu.h:165
No locals.
#1  0xc054d419 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:410
first_buf_printf = 1
#2  0xc054d7e6 in panic (fmt=0xc0736da9 %s) at 
/usr/src/sys/kern/kern_shutdown.c:566
td = (struct thread *) 0xc6bea900
bootopt = 260
newpanic = 0
ap = 0xc6bea900 `\230ŸÆ\200ݟÆ
buf = page fault, '\0' repeats 245 times
#3  0xc071822c in trap_fatal (frame=0xe58f8c28, eva=0) at 
/usr/src/sys/i386/i386/trap.c:838
code = 40
ss = 40
esp = 0
type = 12
softseg = {ssd_base = 0, ssd_limit = 1048575, ssd_type = 27, ssd_dpl = 
0, ssd_p = 1, ssd_xx = 0, ssd_xx1 = 0,
  ssd_def32 = 1, ssd_gran = 1}
msg = 0x0
#4  0xc07178e4 in trap (frame=
  {tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -960218240, tf_esi = 4, 
tf_ebp = -443577176, tf_isp = -443577260, tf_ebx = 0, tf_edx = -624430808, 
tf_ecx = -905276896, tf_eax = 19190235, tf_trapno = 12, tf_err = 0, tf_eip = 
-1068117706, tf_cs = 32, tf_eflags = 65538, tf_esp = 2, tf_ss = -1068092317}) 
at /usr/src/sys/i386/i386/trap.c:270
td = (struct thread *) 0xc6bea900
p