NetBSD Problem Report #46749

From ryo_on@yk.rim.or.jp  Sat Jul 28 17:24:11 2012
Return-Path: <ryo_on@yk.rim.or.jp>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id 03AFE63B85F
	for <gnats-bugs@gnats.netbsd.org>; Sat, 28 Jul 2012 17:24:10 +0000 (UTC)
Message-Id: <20120728172411.03AFE63B85F@www.NetBSD.org>
Date: Sat, 28 Jul 2012 17:24:10 +0000 (UTC)
From: ryoon@NetBSD.org
Reply-To: ryoon@NetBSD.org
To: gnats-bugs@gnats.NetBSD.org
Subject: Accessing to ld0 at sdmmc0 causes kernel panic on NetBSD/i386 current
X-Send-Pr-Version: 3.95

>Number:         46749
>Category:       kern
>Synopsis:       Accessing to ld0 at sdmmc0 causes kernel panic on NetBSD/i386 current
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jul 28 17:25:00 +0000 2012
>Closed-Date:    Sun May 29 23:08:42 +0000 2016
>Last-Modified:  Sun May 29 23:08:42 +0000 2016
>Originator:     Ryo ONODERA
>Release:        NetBSD 6.99.10
>Organization:

>Environment:


System: NetBSD hydrogen.elements.tetera.org 6.99.10 NetBSD 6.99.10 (GENERIC) #0: Sun Jul 29 01:59:47 JST 2012 root@hydrogen.elements.tetera.org:/usr/obj/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386
>Description:
When I access to /dev/ld0e on ld0 at sdmmc0, kernel panics.
SD card is formatted as ffs.

% crash -M netbsd.4.core -N netbsd.4
Crash version 6.99.10, image version 6.99.10.
System panicked: pool_get(ffsdino2): free list modified: magic=0; page 0xc280f000; item addr 0xc280fe00

Backtrace from time of crash is available.
crash> tr
_KERNEL_OPT_NAPMBIOS(c0c40804,104,c05ea788,8,5,0,0,daf45558,c2106d20,0) at 0
_end(104,0,fff1,c0c58b6f,c07eb7c5,c0c595b9,daf4559c,80c7dc,b,0) at daf455b8
vpanic(c0c40804,daf455b8,daf455ac,c0953a7d,c25582c0,c2070000,daf455fc,c07e7973,c
0c40804,c0bd4dae) at vpanic+0x1cf
printf_nolog(c0c40804,c0bd4dae,0,c280f000,c280fe00,c2599b0c,c0c595b9,c280c87c,c2
80c7dc,c2070078) at printf_nolog
pool_cache_cpu_init1(c2070000,1,0,40bc9b,c28096e4,c0b9e320,c2103d40,c2102b80,0,c
2599b0c) at pool_cache_cpu_init1
pool_cache_get_slow(0,1,cb0000,daf45710,daf45710,0,daf4569c,c08fbf95,c280c7dc,0)
 at pool_cache_get_slow+0x19a
pool_cache_get_paddr(c2070000,1,0,4000,ffffffff,0,daf45710,21ff,c0ce0000,0) at p
ool_cache_get_paddr+0x1e5
ffs_vget(c2575000,7ac4b,0,daf457ec,daf457f0,0,6,c25db168,1,10) at ffs_vget+0x37a

ufs_lookup(daf45844,c25db008,daf4585c,c092f7c5,daf4584c,c25db168,daf4588c,c090f6
16,c25d5580,daf45873) at ufs_lookup+0x7b4
VOP_LOOKUP(c25db008,daf458b0,daf45a74,2,0,c24e5790,daf458cc,c25db168,1,daf45a50)
 at VOP_LOOKUP+0x33
lookup_once(daf4597c,daf45978,4,c07e8566,0,c2810000,1,daf459dc,1,10) at lookup_o
nce+0x19f
namei_tryemulroot(0,c2045c00,0,c07e9fca,0,c2050988,daf45a0c,c2573680,c1f72e70,c0
b99c20) at namei_tryemulroot+0x21e
namei(daf45a50,c2048200,0,c07e9fca,0,1,0,c0953a7d,c24babd0,ffffffff) at namei+0x
29
check_exec(c25582c0,daf45b4c,c238dee0,c25925b0,daf45c40,0,daf45b1c,c08de4b1,c24b
9920,bb952000) at check_exec+0x36
execve_loadvm(bb906f94,c05681c0,daf45b4c,0,40,55,bb906f54,c253b800,c253bc00,c280
4800) at execve_loadvm+0x1bc
execve1(c25582c0,bb906f54,bb906f84,bb906f94,c05681c0,c24bac44,daf45d1c,c25582c0,
daf45d48,c0cd6448) at execve1+0x32
sys_execve(c25582c0,daf45cf4,daf45d1c,c24b41b0,0,bb952c64,bb952000,c24b991c,0,3b
) at sys_execve+0x30
syscall() at syscall+0x89
--- syscall (number 59) ---
bba98617:
crash>


>How-To-Repeat:
Insert SDHC card to sdmmc slot and,
# mount /dev/ld0e /mnt
# ls /mnt


>Fix:

I have no idea.


>Release-Note:

>Audit-Trail:
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/46749: Accessing to ld0 at sdmmc0 causes kernel panic on
 NetBSD/i386 current
Date: Sat, 28 Jul 2012 17:33:08 +0000

 On Sat, Jul 28, 2012 at 05:25:00PM +0000, ryoon@NetBSD.org wrote:
  > When I access to /dev/ld0e on ld0 at sdmmc0, kernel panics.
  > SD card is formatted as ffs.

 oh wonderful...

 How repeatable is it?

  > % crash -M netbsd.4.core -N netbsd.4
  > Crash version 6.99.10, image version 6.99.10.
  > System panicked: pool_get(ffsdino2): free list modified: magic=0; page 0xc280f000; item addr 0xc280fe00

  > Backtrace from time of crash is available.
  > [...]
  > sys_execve(c25582c0,daf45cf4,daf45d1c,c24b41b0,0,bb952c64,bb952000,c24b991c,0,3b) at sys_execve+0x30

 So it isn't (probably) the access to the thing that's the problem;
 mounting it corrupted the ffs dinode pool, and then it crashes the
 next time you go there.

 If it's repeatable, my inclination would be to sprinkle the mount code
 with integrity checks on that pool to figure out where it's getting
 trashed. But I don't know the pool interface for that offhand.

 -- 
 David A. Holland
 dholland@netbsd.org

From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
To: gnats-bugs@NetBSD.org, dholland-bugs@NetBSD.org
Cc: 
Subject: Re: kern/46749: Accessing to ld0 at sdmmc0 causes kernel panic on
 NetBSD/i386 current
Date: Sun, 29 Jul 2012 02:46:15 +0900 (JST)

 Hi,

 From: David Holland <dholland-bugs@NetBSD.org>, Date: Sat, 28 Jul 2012 17:35:02 +0000 (UTC)

 > The following reply was made to PR kern/46749; it has been noted by GNATS.
 > 
 > From: David Holland <dholland-bugs@netbsd.org>
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: kern/46749: Accessing to ld0 at sdmmc0 causes kernel panic on
 >  NetBSD/i386 current
 > Date: Sat, 28 Jul 2012 17:33:08 +0000
 > 
 >  On Sat, Jul 28, 2012 at 05:25:00PM +0000, ryoon@NetBSD.org wrote:
 >   > When I access to /dev/ld0e on ld0 at sdmmc0, kernel panics.
 >   > SD card is formatted as ffs.
 >  
 >  oh wonderful...
 >  
 >  How repeatable is it?
 >
 >   > % crash -M netbsd.4.core -N netbsd.4
 >   > Crash version 6.99.10, image version 6.99.10.
 >   > System panicked: pool_get(ffsdino2): free list modified: magic=0; page 0xc280f000; item addr 0xc280fe00
 >  
 >   > Backtrace from time of crash is available.
 >   > [...]
 >   > sys_execve(c25582c0,daf45cf4,daf45d1c,c24b41b0,0,bb952c64,bb952000,c24b991c,0,3b) at sys_execve+0x30
 >  
 >  So it isn't (probably) the access to the thing that's the problem;
 >  mounting it corrupted the ffs dinode pool, and then it crashes the
 >  next time you go there.
 >  
 >  If it's repeatable, my inclination would be to sprinkle the mount code
 >  with integrity checks on that pool to figure out where it's getting
 >  trashed. But I don't know the pool interface for that offhand.

 It is repeatable. Every time, kernel panics.
 At least, I have 5 cores in /var/crash.
 But I cannot provide first error message, it is lost.
 I suspect first error message is different from the message above.

 I cannot confirm whether filesystem is broken or not.
 But I will newsfs my SDHC card again.

 Thank you.

 -- 
 Ryo ONODERA // ryo_on@yk.rim.or.jp


From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/46749: Accessing to ld0 at sdmmc0 causes kernel panic on
 NetBSD/i386 current
Date: Sun, 29 Jul 2012 04:37:08 +0900 (JST)

 Hi,

 From: Ryo ONODERA <ryo_on@yk.rim.or.jp>, Date: Sat, 28 Jul 2012 17:50:05 +0000 (UTC)

 >  I cannot confirm whether filesystem is broken or not.
 >  But I will newsfs my SDHC card again.

 With newly newfs-ed SDHC card, I have gotten the following 3 traces
 after some writes.

 % crash -N netbsd.10 -M netbsd.10.core 
 Crash version 6.99.10, image version 6.99.10.
 System panicked: trap
 Backtrace from time of crash is available.
 crash> tr
 _KERNEL_OPT_NAPMBIOS(c0c48058,104,c05ea788,8,5,0,0,daeb5984,2,0) at 0
 _end(104,0,fff7,c0c58b6f,c07eb7c5,0,1000000,c24c2a80,daeb5aa4,6) at daeb59e4
 vpanic(c0c48058,daeb59e4,daeb59d8,c24c2a80,daeb5aa4,6,daeb5a98,c08471a9,c0c48058
 ,daeb5aa4) at vpanic+0x1cf
 printf_nolog(c0c48058,daeb5aa4,daeb5aa4,32,daeb3000,10246,10,0,daeb5b08,0) at pr
 intf_nolog
 trap() at trap+0xcb4
 --- trap (number 6) ---
 ffs_itimes(c37cb028,0,0,0,c37c53c0,12,daeb5bb0,c07e4ebc,c2065160,c31efe74) at ff
 s_itimes+0x46
 ffs_update(c37cddc0,0,0,4,c2064f80,c3144dd0,daeb5c3c,c0903031,c280a02c,c3144de4)
  at ffs_update+0x56
 ffs_sync(c27e7000,3,c20fff00,12,c24c2a80,c27f49a0,daeb5c9c,daeb5cb4,c27e7000,dae
 b5cb4) at ffs_sync+0x3a4
 VFS_SYNC(c27e7000,3,c20fff00,c092f5f9,daeb5c9c,0,12,c27f49a0,c27f49a0,1) at VFS_
 SYNC+0x27
 sync_fsync(daeb5cb4,1,daeb5cdc,c0910490,c27f49a0,12,1,c090fa5a,c0b9e0c8,c27f49a0
 ) at sync_fsync+0x7c
 VOP_FSYNC(c27f49a0,c20fff00,8,0,0,0,0,c24c2a80,c24c27e0,0) at VOP_FSYNC+0x4a
 sched_sync(c24c2a80,e83000,e8c000,0,c0100307,0,0,0,0,0) at sched_sync+0x109
 crash> 




 % crash -N netbsd.11 -M netbsd.11.core
 Crash version 6.99.10, image version 6.99.8.
 WARNING: versions differ, you may not be able to examine this image.
 System panicked: kernel diagnostic assertion "(*vpp)->v_type == VNON" failed: file "/home/builds/ab/HEAD/src/sys/ufs/ffs/ffs_alloc.c", line 616 
 Backtrace from time of crash is available.
 crash> tr
 _KERNEL_OPT_NAPMBIOS(c0baed68,104,c05ea7b8,8,5,0,0,db0a5658,0,db0a5690) at 0
 _end(104,0,fff5,c0c5bb9b,c07ebfc5,4000,2,c24f8978,c2600800,c2819618) at db0a56b8

 vpanic(c0baed68,db0a56b8,db0a56f0,0,c281b794,c2600800,db0a576c,c0307728,c0baed68
 ,c0baef19) at vpanic+0x1cf
 kern_assert(c0baed68,c0baef19,c0bd56c5,c0bd5064,268,4000,c24a93e0,c24f8978,c2600
 800,c28196c4) at kern_assert+0x23
 ffs_valloc(c281b794,8000,ffffffff,db0a587c,c0c82600,c2478560,db0a57cc,c08de872,2
 da0,0) at ffs_valloc+0xb0a
 wapbl_log_position(db0a590c,db0a5920,db0a591c,db0a5904,c2821044,0,db0a58ec,c098d
 32e,4946ade,0) at wapbl_log_position+0x3e3
 ffs_wapbl_start(c2821000,c2821044,a8,1000,c2101f00,0,db0a59ac,0,0,1) at ffs_wapb
 l_start+0xc2
 ffs_mountfs(c25ab58c,c2821000,c25aa7e0,c2821000,c25ab58c,6,0,c0903b90,c282102c,0
 ) at ffs_mountfs+0xa81
 ffs_mount(c2821000,bfbfe9d8,c2055590,db0a5ca0,c238ff00,0,db0a5bdc,c0904f0e,c2821
 000,bfbfe9d8) at ffs_mount+0x211
 VFS_MOUNT(c2821000,bfbfe9d8,c2055590,db0a5ca0,2000000,c2055590,0,c07ea7ca,0,0) a
 t VFS_MOUNT+0x34
 mount_domount(c25aa7e0,db0a5c3c,c0c84e80,bfbfe9d8,2000000,c2055590,db0a5ca0,c253
 e405,7,86a29d38) at mount_domount+0x11c
 do_sys_mount(c25aa7e0,0,8048ea8,bfbfe9d8,2000000,bfbfeddc,0,4,db0a5d1c,0) at do_
 sys_mount+0x238
 sys___mount50(c25aa7e0,db0a5cf4,db0a5d1c,c280abb8,0,bbb1dba3,bbb1d000,c24bc6a0,0
 ,19a) at sys___mount50+0x4d
 syscall() at syscall+0x89
 --- syscall (number 410) ---
 bbb04b57:
 crash> 


 ;; /var/crash/netbsd.8.gz is broken...

 % crash -N /netbsd -M netbsd.8.core
 Crash version 6.99.10, image version 6.99.10.
 System panicked: trap
 Backtrace from time of crash is available.
 crash> tr
 _KERNEL_OPT_NVGA_RASTERCONSOLE(c0c48058,104,c05ea788,8,5,0,0,d984ce48,2,0) at 0
 end(104,0,fff9,c0c58b6f,c07eb7c5,0,1000000,c2598a80,d984cf7c,d) at d984cea8
 vpanic(c0c48058,d984cea8,0,c2598a80,d984cf7c,d,d984cf5c,c08471a9,c0c48058,d984cf
 7c) at vpanic+0x1cf
 printf_nolog(c0c48058,d984cf7c,d984cf7c,1,daf4c000,10082,daf4dffc,0,daf4e000,0) a
 t printf_nolog
 trap() at trap+0xcb4
 --- trap (number 13) ---
 Xtrap0e(38,daf4ec7c,c0100938,c080de6a,daf4eb64,bfbfe4b8,38,daf4ed1c,0,0) at Xtra
 p0e
 do_pmap_load(c080de6a,daf4eb64,bfbfe4b8,38,daf4ed1c,0,0,0,0,4) at do_pmap_load+0
 x16
 copyout(daf4ed1c,bfbfe4b8,7,daf4eca8,0,0,0,4c8,3,1e) at copyout+0x48
 sys_poll(c2598a80,daf4ecf4,daf4ed1c,c27f8d84,0,bb92c010,bb92c000,c24ba774,0,d1) a
 t sys_poll+0x7c
 syscall() at syscall+0x89
 --- syscall (number 209) ---
 bbaaf417:
 crash> 

 -- 
 Ryo ONODERA // ryo_on@yk.rim.or.jp


From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/46749: Accessing to ld0 at sdmmc0 causes kernel panic on
 NetBSD/i386 current
Date: Mon, 30 Jul 2012 00:47:24 +0900 (JST)

 And newfs /dev/rld0e on today's NetBSD/i386 current generates error.

 % sudo newfs -O 2 /dev/rld0e
 /dev/rld0e: 30959.0MB (63403968 sectors) block size 16384, fragment size 2048
         using 168 cylinder groups of 184.28MB, 11794 blks, 22912 inodes.
 super-block backups (for fsck_ffs -b #) at:
 160, 377568, 754976, 1132384, 1509792, 1887200, 2264608, 2642016, 3019424,
 ...............................................................................
 cg 0: bad magic number

 --
 Ryo ONODERA // ryo_on@yk.rim.or.jp
 PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3


From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/46749: Accessing to ld0 at sdmmc0 causes kernel panic on
 NetBSD/i386 current
Date: Mon, 30 Jul 2012 03:05:52 +0900 (JST)

 Hi,

 I have forgotten to attach dmesg.

 pci3: i/o space, memory space enabled
 cbb0 at pci3 dev 3 function 0: vendor 0x1180 product 0x0476 (rev. 0x8d)
 sdhc0 at pci3 dev 3 function 1: vendor 0x1180 product 0x0822 (rev. 0x13)
 sdhc0: interrupting at ioapic0 pin 17
 sdhc0: SD Host Specification 1.0, rev.2
 sdhc0: using DMA transfer
 sdmmc0 at sdhc0 slot 0
 (snip)
 ld0 at sdmmc0: <SDC  >
 ld0: 30959 MB, 7862 cyl, 128 head, 63 sec, 512 bytes/sect x 63404032 sectors
 ld0: 4-bit width, bus clock 25.000 MHz


From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/46749: Accessing to ld0 at sdmmc0 causes kernel panic on
 NetBSD/i386 current
Date: Thu, 02 Aug 2012 08:10:16 +0900 (JST)

 From: Ryo ONODERA <ryo_on@yk.rim.or.jp>, Date: Sun, 29 Jul 2012 15:50:04 +0000 (UTC)

 > The following reply was made to PR kern/46749; it has been noted by GNATS.
 > 
 > From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: kern/46749: Accessing to ld0 at sdmmc0 causes kernel panic on
 >  NetBSD/i386 current
 > Date: Mon, 30 Jul 2012 00:47:24 +0900 (JST)
 > 
 >  And newfs /dev/rld0e on today's NetBSD/i386 current generates error.
 >  
 >  % sudo newfs -O 2 /dev/rld0e
 >  /dev/rld0e: 30959.0MB (63403968 sectors) block size 16384, fragment size 2048
 >          using 168 cylinder groups of 184.28MB, 11794 blks, 22912 inodes.
 >  super-block backups (for fsck_ffs -b #) at:
 >  160, 377568, 754976, 1132384, 1509792, 1887200, 2264608, 2642016, 3019424,
 >  ...............................................................................
 >  cg 0: bad magic number

 With today's current, "cg 0: bad magic number" error does not occur.
 But accessing to ld0 causes kernel panic.

 % crash -M netbsd.18.core -N netbsd.18
 Crash version 6.99.10, image version 6.99.10.
 System panicked: lock error
 Backtrace from time of crash is available.
 crash> tr
 _KERNEL_OPT_NAPMBIOS(c0c485a1,104,c05ed378,8,5,0,0,daf6b378,61353263,0) at 0
 _end(104,0,ffec,c0c60d67,c07f24a5,1,0,c0ce1b04,c2812838,c25a07e4) at daf6b3d8
 vpanic(c0c485a1,daf6b3d8,4,c057b1ce,c210e000,60,daf6b3fc,c07eb3de,c0c485a1,c0c0e
 14f) at vpanic+0x1cf
 printf_nolog(c0c485a1,c0c0e14f,c0b566f5,c0c0c81f,c2812838,0,c25a07e0,c08e56e2,c2
 5a07e0,0) at printf_nolog
 lockdebug_abort(c2812838,c0ce1b04,c0b566f5,c0c0c81f,c210cd00,c2812838,daf6b4ac,c
 058a9b9,c0c87640,c247e020) at lockdebug_abort+0x2b
 rw_abort(c0c87640,c247e020,daf6b44c,c07ebb9c,c206d160,c25a09b4,0,c057528d,c0d247
 80,3) at rw_abort+0x29
 rw_vector_enter(c2812838,1,1,0,0,1,daf6b4fc,c0806c40,c259acc0,ffffffff) at rw_ve
 ctor_enter+0x570
 genfs_lock(daf6b518,a,daf6b52c,c0807041,c0d5d53c,c2817aac,daf6b52c,c07ebb9c,c206
 d160,c0ba5ad4) at genfs_lock+0xa9
 VOP_LOCK(c2812794,2,daf6b59c,c0993f5a,c2817aac,0,daf6b56c,c09024eb,c2817aac,0) a
 t VOP_LOCK+0x2c
 vn_lock(c2812794,2,c0c617b1,0,2,0,daf6b62c,c03025b3,c2817aac,0) at vn_lock+0xe0
 vget(c2812794,2,1,5980,db0a00a8,c2812794,1306,0,0,c24ff928) at vget+0xe2
 ufs_ihashget(1304,0,2,0,2,daf6b6cc,daf6b65c,0,c2812794,c28106c4) at ufs_ihashget
 +0x9a
 ffs_vget(c2819000,2,0,daf6b86c,c0301e5d,4000,daf6b6ec,c24ff8d8,c2549000,c28106c4
 ) at ffs_vget+0x103
 ffs_valloc(c2812794,8000,ffffffff,daf6b86c,c247e020,c210cd00,daf6b77c,c059218b,c
 0c87640,c247e020) at ffs_valloc+0x232
 wapbl_log_position(daf6b8fc,daf6b910,daf6b90c,daf6b8f4,c2819044,0,daf6b8dc,c0993
 f0e,4946ade,0) at wapbl_log_position+0x3e3
 ffs_wapbl_start(c2819000,c2819044,a8,1000,c2107f00,0,daf6b9ac,c0575472,0,c25a09b
 4) at ffs_wapbl_start+0xc2
 ffs_mountfs(c25a258c,c2819000,c25a07e0,c2819000,c25a258c,6,0,c090a700,c281902c,0
 ) at ffs_mountfs+0xbf2
 ffs_mount(c2819000,bfbfe9d8,c205b590,daf6bca0,c2396f10,0,daf6bbdc,c090ba7e,c2819
 000,bfbfe9d8) at ffs_mount+0x211
 VFS_MOUNT(c2819000,bfbfe9d8,c205b590,daf6bca0,2000000,c205b590,0,fffffffe,0,0) a
 t VFS_MOUNT+0x34
 mount_domount(c25a07e0,daf6bc3c,c0c89ec0,bfbfe9d8,2000000,c205b590,daf6bca0,c254
 4405,7,86a29d38) at mount_domount+0x11c
 do_sys_mount(c25a07e0,0,8048ea8,bfbfe9d8,2000000,bfbfeddc,0,4,daf6bd1c,0) at do_
 sys_mount+0x238
 sys___mount50(c25a07e0,daf6bcf4,daf6bd1c,c2800bd4,0,bbb1dba3,bbb1d000,c24c26a0,0
 ,19a) at sys___mount50+0x4d
 syscall() at syscall+0x89
 --- syscall (number 410) ---
 bbb04b57:
 crash>

 --
 Ryo ONODERA // ryo_on@yk.rim.or.jp
 PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3


From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/46749: Accessing to ld0 at sdmmc0 causes kernel panic on
 NetBSD/i386 current
Date: Fri, 31 Aug 2012 01:16:25 +0900 (JST)

 Hi,

 nonaka@ gives me a patch to disable DMA.
 https://gist.github.com/3285238

 With the patch, it seems ld at sdmmc works properly.

 It seems that broken device support is abandoned more than a month.
 Please commit the patch as bandaid.

 --
 Ryo ONODERA // ryo_on@yk.rim.or.jp
 PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB  FD1B F404 27FA C7D1 15F3


From: Ryo ONODERA <ryo_on@yk.rim.or.jp>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/46749: Accessing to ld0 at sdmmc0 causes kernel panic on
 NetBSD/i386 current
Date: Mon, 24 Dec 2012 06:56:59 +0900 (JST)

 Even after recent sdmmc updates, my ld at sdmmc does not work...

 When I inser 32GB SDHC card to car slot, I have gotten following
 errors, and it does not work.

 sdmmc0: couldn't enable card: 60
 sdmmc0: couldn't supply bus power
 sdmmc0: couldn't enable card: 6

State-Changed-From-To: open->feedback
State-Changed-By: jmcneill@NetBSD.org
State-Changed-When: Tue, 04 Aug 2015 22:42:13 +0000
State-Changed-Why:
Many recent sdmmc and sdhc changes, can you re-test?


State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 29 May 2016 23:08:42 +0000
State-Changed-Why:
Feedback timeout; assume fixed.


>Unformatted:

Home	PR Database Search