Stack Overflow in GEOM

2013-04-16 Thread Cy Schubert
Has anyone see this before? Just updated my CURRENT partitions on my 
testbed and laptop. The laptop just boots but I've managed to capture this 
on my testbed (attached to a serial port on another system).

This is HEAD from yesterday (Apr 15) morning (PDT). The partition being 
booted is ada0s1d. On my laptop it's ada0s3a. KSTACK_PAGES is 4. Is there a 
way to quickly display that kern.kstack_pages from DDB?

ada0 at ata0 bus 0 scbus0 target 0 lun 0
ada0: SAMSUNG SP0802N TK100-24 ATA-7 device
ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes)
ada0: 76351MB (156368016 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad0
ada1 at ata0 bus 0 scbus0 target 1 lun 0
ada1: Maxtor 6Y120P0 YAR41BW0 ATA-7 device
ada1: 133.000MB/s transfers (UDMA6, PIO 8192bytes)
ada1: 117246MB (240121728 512 byte sectors: 16H 63S/T 16383C)
ada1: Previously was known as ad1
ada2 at ata2 bus 0 scbus2 target 0 lun 0
ada2: WDC WD5000AAKS-00D2B0 12.01C02 ATA-8 SATA 2.x device
ada2: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada2: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
ada2: Previously was known as ad4
ada3 at ata3 bus 0 scbus3 target 0 lun 0
ada3: WDC WD3200KS-00PFB0 21.00M21 ATA-7 SATA 2.x device
ada3: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
ada3: 305245MB (625142448 512 byte sectors: 16H 63S/T 16383C)
ada3: Previously was known as ad6
SMP: AP CPU #1 Launched!
panic: stack overflow detected; backtrace may be corrupted
cpuid = 1
KDB: enter: panic
[ thread pid 13 tid 19 ]
Stopped at  kdb_enter+0x3d: movl$0,kdb_why
db bt
Tracing pid 13 tid 19 td 0x872d6000
kdb_enter(80ca7886,80ca7886,80ca9523,86edcae0,1,...) at 
kdb_enter+0x3d/frame 0x86edca98
panic(80ca9523,86edcb70,80713dd2,86edcbd8,86edcafc,...) at 
panic+0x141/frame 0x86edcad4
__stack_chk_init(86edcbd8,86edcafc,86edcaf8,86edcafc,64,...) at 
__stack_chk_init/frame 0x86edcae0
g_label_disk_ident_taste(87b7dc80,86edcbd8,80,0,0,...) at 
g_label_disk_ident_taste+0x102/frame 0x86edcb70
g_label_taste(80d26b88,872ff500,0,872ff480,872d6000,...) at 
g_label_taste+0x3ca/frame 0x86edcc6c
g_new_provider_event(872ff500,0,25c,80c9798e,0,...) at 
g_new_provider_event+0xb1/frame 0x86edcc88
g_run_events(0,86edcd08,222db60d,83725616,b10094f2,...) at 
g_run_events+0x19f/frame 0x86edccc4
fork_exit(8070d140,0,86edcd08) at fork_exit+0xa3/frame 0x86edccf4
fork_trampoline() at fork_trampoline+0x8/frame 0x86edccf4
--- trap 0, eip = 0, esp = 0x86edcd40, ebp = 0 ---
db 

I've been poking at this off and on last night. Any ideas?


-- 
Cheers,
Cy Schubert cy.schub...@komquats.com
FreeBSD UNIX:  c...@freebsd.org   Web:  http://www.FreeBSD.org


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


Re: Stack Overflow in GEOM

2013-04-16 Thread David Wolfskill
On Tue, Apr 16, 2013 at 10:56:31AM -0700, Cy Schubert wrote:
 Has anyone see this before? Just updated my CURRENT partitions on my 
 testbed and laptop. The laptop just boots but I've managed to capture this 
 on my testbed (attached to a serial port on another system).
 
 This is HEAD from yesterday (Apr 15) morning (PDT). The partition being 
 booted is ada0s1d. On my laptop it's ada0s3a. KSTACK_PAGES is 4. Is there a 
 way to quickly display that kern.kstack_pages from DDB?
 ... 
 panic: stack overflow detected; backtrace may be corrupted
 cpuid = 1
 KDB: enter: panic
 [ thread pid 13 tid 19 ]
 

I'm seeing this, but my situation is ... reversed: my build machine came
up OK:

FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #1134 
r249538M/249542:130: Tue Apr 16 09:15:49 PDT 2013 
r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC  i386

but my laptop exhibits symptoms that I *believe* resemble those you
cited.  (I was unable to get a crash dump, and the machine rebooted too
quickly after I typed panic at the ddb prompt.  I don't have a serial
console on the laptop.)

I had thought that it might be nvidia-driver-related (again), but I also
note that the laptop has a single SATA drive, while the build machine
has SCSI (possibly SAS -- machine is powered off for the day, since its
work is done) drives.  Laptop also has 2x the memory the build machine
does.  (They are each i386.)

My last successful smoke-test for head on the laptop was yesterday:

FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #869  
r249502M/249503:130: Mon Apr 15 05:23:38 PDT 2013 
r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY  i386

I had built head @r249538 this morning, and that's the build where
my smoke-test failed.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Taliban: Evil men with guns afraid of truth from a 14-year old girl.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgpHKZFzFBm6v.pgp
Description: PGP signature


Re: Stack Overflow in GEOM

2013-04-16 Thread Jim Harris
On Tue, Apr 16, 2013 at 11:13 AM, David Wolfskill da...@catwhisker.orgwrote:

 On Tue, Apr 16, 2013 at 10:56:31AM -0700, Cy Schubert wrote:
  Has anyone see this before? Just updated my CURRENT partitions on my
  testbed and laptop. The laptop just boots but I've managed to capture
 this
  on my testbed (attached to a serial port on another system).
 
  This is HEAD from yesterday (Apr 15) morning (PDT). The partition being
  booted is ada0s1d. On my laptop it's ada0s3a. KSTACK_PAGES is 4. Is
 there a
  way to quickly display that kern.kstack_pages from DDB?
  ...
  panic: stack overflow detected; backtrace may be corrupted
  cpuid = 1
  KDB: enter: panic
  [ thread pid 13 tid 19 ]
  

 I'm seeing this, but my situation is ... reversed: my build machine came
 up OK:

 FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #1134
 r249538M/249542:130: Tue Apr 16 09:15:49 PDT 2013
 r...@freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC  i386

 but my laptop exhibits symptoms that I *believe* resemble those you
 cited.  (I was unable to get a crash dump, and the machine rebooted too
 quickly after I typed panic at the ddb prompt.  I don't have a serial
 console on the laptop.)

 I had thought that it might be nvidia-driver-related (again), but I also
 note that the laptop has a single SATA drive, while the build machine
 has SCSI (possibly SAS -- machine is powered off for the day, since its
 work is done) drives.  Laptop also has 2x the memory the build machine
 does.  (They are each i386.)

 My last successful smoke-test for head on the laptop was yesterday:

 FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #869
  r249502M/249503:130: Mon Apr 15 05:23:38 PDT 2013
 r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY  i386

 I had built head @r249538 this morning, and that's the build where
 my smoke-test failed.


This stack trace corruption was noted on svn-src-head@ as well, and appears
to be fixed with r249564.

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


Re: Stack Overflow in GEOM

2013-04-16 Thread David Wolfskill
On Tue, Apr 16, 2013 at 01:01:49PM -0700, Jim Harris wrote:
 ...
  I had built head @r249538 this morning, and that's the build where
  my smoke-test failed.
 
 
 This stack trace corruption was noted on svn-src-head@ as well, and appears
 to be fixed with r249564.
 

Cool; thanks -- I applied that  rebuilt/installed my kernel; the laptop
now boots:

FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #872  
r249538M/249542:130: Tue Apr 16 13:16:46 PDT 2013 
r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY  i386

and runs X; I can login and stuff.  :-)

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Taliban: Evil men with guns afraid of truth from a 14-year old girl.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


pgpDNdGCCfr5I.pgp
Description: PGP signature


Re: Stack Overflow in GEOM

2013-04-16 Thread Cy Schubert
In message 1257671366135...@web6f.yandex.ru, Ilya A. Arkhipov writes:
 16.04.2013, 21:56, Cy Schubert cy.schub...@komquats.com:
  Has anyone see this before? Just updated my CURRENT partitions on my
  testbed and laptop. The laptop just boots but I've managed to capture this
  on my testbed (attached to a serial port on another system).
 
  This is HEAD from yesterday (Apr 15) morning (PDT). The partition being
  booted is ada0s1d. On my laptop it's ada0s3a. KSTACK_PAGES is 4. Is there a
  way to quickly display that kern.kstack_pages from DDB?
 
  ada0 at ata0 bus 0 scbus0 target 0 lun 0
  ada0: SAMSUNG SP0802N TK100-24 ATA-7 device
  ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes)
  ada0: 76351MB (156368016 512 byte sectors: 16H 63S/T 16383C)
  ada0: Previously was known as ad0
  ada1 at ata0 bus 0 scbus0 target 1 lun 0
  ada1: Maxtor 6Y120P0 YAR41BW0 ATA-7 device
  ada1: 133.000MB/s transfers (UDMA6, PIO 8192bytes)
  ada1: 117246MB (240121728 512 byte sectors: 16H 63S/T 16383C)
  ada1: Previously was known as ad1
  ada2 at ata2 bus 0 scbus2 target 0 lun 0
  ada2: WDC WD5000AAKS-00D2B0 12.01C02 ATA-8 SATA 2.x device
  ada2: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
  ada2: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
  ada2: Previously was known as ad4
  ada3 at ata3 bus 0 scbus3 target 0 lun 0
  ada3: WDC WD3200KS-00PFB0 21.00M21 ATA-7 SATA 2.x device
  ada3: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
  ada3: 305245MB (625142448 512 byte sectors: 16H 63S/T 16383C)
  ada3: Previously was known as ad6
  SMP: AP CPU #1 Launched!
  panic: stack overflow detected; backtrace may be corrupted
  cpuid = 1
  KDB: enter: panic
  [ thread pid 13 tid 19 ]
  Stopped at škdb_enter+0x3d: movl ššš$0,kdb_why
  db bt
  Tracing pid 13 tid 19 td 0x872d6000
  kdb_enter(80ca7886,80ca7886,80ca9523,86edcae0,1,...) at
  kdb_enter+0x3d/frame 0x86edca98
  panic(80ca9523,86edcb70,80713dd2,86edcbd8,86edcafc,...) at
  panic+0x141/frame 0x86edcad4
  __stack_chk_init(86edcbd8,86edcafc,86edcaf8,86edcafc,64,...) at
  __stack_chk_init/frame 0x86edcae0
  g_label_disk_ident_taste(87b7dc80,86edcbd8,80,0,0,...) at
  g_label_disk_ident_taste+0x102/frame 0x86edcb70
  g_label_taste(80d26b88,872ff500,0,872ff480,872d6000,...) at
  g_label_taste+0x3ca/frame 0x86edcc6c
  g_new_provider_event(872ff500,0,25c,80c9798e,0,...) at
  g_new_provider_event+0xb1/frame 0x86edcc88
  g_run_events(0,86edcd08,222db60d,83725616,b10094f2,...) at
  g_run_events+0x19f/frame 0x86edccc4
  fork_exit(8070d140,0,86edcd08) at fork_exit+0xa3/frame 0x86edccf4
  fork_trampoline() at fork_trampoline+0x8/frame 0x86edccf4
  --- trap 0, eip = 0, esp = 0x86edcd40, ebp = 0 ---
  db
 
  I've been poking at this off and on last night. Any ideas?
 
  --
  Cheers,
  Cy Schubert cy.schub...@komquats.com
  FreeBSD UNIX: šc...@freebsd.org ššWeb: šhttp://www.FreeBSD.org
 
  ___
  freebsd-current@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-current
  To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
 
 Hi,
 
 It should be related with: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=30160
 3+0+current/svn-src-head
 
 Author: ivoras
 Date: Mon Apr 15 16:09:24 2013
 New Revision: 249508
 URL: http://svnweb.freebsd.org/changeset/base/249508
 
 Log:
   Introduce glabel labels based on GEOM ident attributes. In this initial
   implementation, error on the side of conservatism and only create labels
   for GEOMs of classes DISK and MULTIPATH.
 
   Discussed with: trasz
   Approved by: silence from freebsd-geom@

You were correct. Backing out r249508 in my tree resolves the panic on both 
hosts.


-- 
Cheers,
Cy Schubert cy.schub...@komquats.com
FreeBSD UNIX:  c...@freebsd.org   Web:  http://www.FreeBSD.org


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


Re: Stack Overflow in GEOM

2013-04-16 Thread Ivan Voras
On 17 April 2013 00:44, Cy Schubert cy.schub...@komquats.com wrote:

 You were correct. Backing out r249508 in my tree resolves the panic on both
 hosts.

Hi,

Sorry about that - should be fixed by
http://svnweb.freebsd.org/base?view=revisionrevision=249564 .
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: Stack Overflow in GEOM

2013-04-16 Thread Cy Schubert
In message CAF-QHFVPZUOSZr-xhOjNgLSgw0aJm8BazEwig-meaP1xZPvwXA@mail.gmail.c
om
, Ivan Voras writes:
 On 17 April 2013 00:44, Cy Schubert cy.schub...@komquats.com wrote:
 
  You were correct. Backing out r249508 in my tree resolves the panic on both
  hosts.
 
 Hi,
 
 Sorry about that - should be fixed by
 http://svnweb.freebsd.org/base?view=revisionrevision=249564 .
 

hey, no prob. Fetching it now. Thanks.


-- 
Cheers,
Cy Schubert cy.schub...@komquats.com
FreeBSD UNIX:  c...@freebsd.org   Web:  http://www.FreeBSD.org


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