Re: sys/dev/usb/if_axen.c

On 19/11/2023 21:45, sc.dy...@gmail.com wrote: hi, Attached patch should add support AX88179A. I committed this. Thanks, Nick

Re: Booting from CD on VMware 13 for ARM

On 07/12/2022 19:34, Adam wrote: Greetings, The new VMware 13 allows virtualisation on ARM machines, like Apple machines with M1/M2 chips. Is there a way to boot NetBSD from CD on VMware 13 for ARM? On macOS, I tried NetBSD/evbarm-9 and NetBSD-current (aarch64 and earmv7hf) but the

Re: Wacko kernel memory accounting in current/hppa

Hi Tom, On 22/05/2022 17:59, Tom Lane wrote: [snip] I wonder if anyone sees comparable follies elsewhere, or if this is somehow hppa-specific. Should I file a PR? PRs are always welcome. :) This particular bug is very likely in the hppa pmap implementation (sys/arch/hppa/hppa/pmap.c). I'll

Re: netbsd-9 sys/dev/usb/ehci.c panic: exfer->ex_isdone

On 07/01/2021 07:47, Paul Ripke wrote: I've had a couple of recent crashes on amd64, likely due to a dodgy USB hub. Still, no matter how bad the hub is, I think the crashes indicate a bug somewhere. System is: NetBSD slave 9.1_STABLE NetBSD 9.1_STABLE (SLAVE) #5: Wed Dec 9 17:19:04 AEDT 2020

Re: -current and RPI 2/3

On 17/07/2020 14:00, Frank Kardel wrote: I am having trouble to get Raspberries o boot recent -current (9.99.69). Should be fixed now with src/sys/arch/arm/arm/armv6_start.S:1.21 src/sys/arch/arm/include/asan.h:1.3 Raspberry Pi 3 Model B Plus Rev 1.3 Hoping my commit

USB keyboard and ddb [was Re: NetBSD-7.0 boots OK and NetBSD-8.0 hangs/crashes during boot on a MacBook7,1]

On 06/07/2020 10:34, Andreas Gustafsson wrote: > Martin Husemann wrote: >> USB keyboards as console in ddb worked fine last I tested. > > That has not been my experience. For example, > >PR 52569 Entering ddb using USB keyboard panics with "locking against myself" I just committed something

Re: USB(xhci related) panic

On 02/04/2020 10:10, Chavdar Ivanov wrote: Hi, On yesterday's -curreng 9.99.52, attaching an external usb DVD-RW device, I got: uvm_fault(0x81750240, 0x0, 1) -> e fatal page fault in supervisor mode trap type 6 code 0 rip 0x8049e435 cs 0x8 rflags 0x10246 cr2 0x8 ilevel 0 rsp

Re: USB umass hard drive "failed to create xfers" when attaching

On 19/03/2020 09:19, sc.dy...@gmail.com wrote: On 2020/03/19 07:10, Nick Hudson wrote: On 19/03/2020 07:05, sc.dy...@gmail.com wrote: On 2020/02/17 21:33, Nick Hudson wrote: [snip] xhci could do better and support multiple DMA segments, but uvm could also help. To access each DMA

Re: USB umass hard drive "failed to create xfers" when attaching

On 19/03/2020 07:05, sc.dy...@gmail.com wrote: > On 2020/02/17 21:33, Nick Hudson wrote: [snip] >> xhci could do better and support multiple DMA segments, but uvm could >> also help. > > To access each DMA segment in usb_dma_t *dma, should it be processed > like this?

Re: USB umass hard drive "failed to create xfers" when attaching

On 17/02/2020 16:23, Paul Goyette wrote: [...] More info... First, this is on a amd64 system, witwh 8core/16thread and 128GB of RAM. On IRC it was suggested (thanks, maya!) that the error message might be related to memory fragmentation.  I didn't believe it (given how much RAM I have), but a

Re: 9.99.38 RPi 3B+ panic: kernel diagnostic assertion "cold || sent_p || ncpu <= 1" failed: file "/c/usr/src/sys/arch/arm/pic/pic.c", line 206

On 19/01/2020 08:12, Nick Hudson wrote: > On 17/01/2020 05:02, Michael Cheponis wrote: > [snip] > >> [   1.5848846] panic: kernel diagnostic assertion "cold || sent_p || > ncpu >> <= 1" failed: file "/c/usr/src/sys/arch/arm/pic/pic.c", l

Re: 9.99.38 RPi 3B+ panic: kernel diagnostic assertion "cold || sent_p || ncpu <= 1" failed: file "/c/usr/src/sys/arch/arm/pic/pic.c", line 206

On 17/01/2020 05:02, Michael Cheponis wrote: [snip] > [   1.5848846] panic: kernel diagnostic assertion "cold || sent_p || > ncpu > <= 1" failed: file "/c/usr/src/sys/arch/arm/pic/pic.c", line 206 > [   1.5848846] cpu0: Begin traceback... > [   1.5848846] 0x80b79e04: netbsd:db_panic+0x14 > [  

Re: Hints for Bananapi and -current

On 01/05/2019 21:07, Frank Kardel wrote: [snip] [   5.9727975] panic: usbd_transfer: not done [   6.0611224] cpu0: Begin traceback... [   6.1478907] 0x9c695b84: netbsd:db_panic+0x14 [   6.2380975] 0x9c695b9c: netbsd:vpanic+0x194 [   6.3276372] 0x9c695bb4: netbsd:snprintf [   6.4161552]

Re: Panic on evbearm6

On 04/11/2018 12:09, Chavdar Ivanov wrote: I just got: -- Nov 4 11:50:40 rpi /netbsd: [ 91750.0747877] panic: kernel diagnostic assertion "(flags & (PR_WAITOK|PR_NOWAIT)) == PR_NOWAIT" failed: file "/home/sysbuild/src/sys/kern/subr_pool.c", line 864 Nov 4 11:50:40 rpi /netbsd: [

Re: build.sh distribution failure for evbarm

On 02/11/2018 14:33, Chavdar Ivanov wrote: This is the command line: ./build.sh -D/home/sysbuild/evbarm/destdir -M/home/sysbuild/evbarm/obj -N2 -R/home/sysbuild/release -T/home/sysbuild/evbarm/tools -U -X/home/sysbuild/xsrc -j8 -mevbarm -u -x release live-image It is actually done by

Re: Heads-up: RPI FDTisation committed

On 12/15/17 12:40, Nick Hudson wrote: On 14/12/2017 23:35, Ryo ONODERA wrote: Hi, Thanks for your build.sh -m evbearmv6hf-el release fix. I have written rpi.img to SD Card and boot it on Raspberry Pi Model B Revision 2.0 (RAM: 512MB). And I do not see any green boot message in HDMI display

Re: Heads-up: RPI FDTisation committed

On 14/12/2017 23:35, Ryo ONODERA wrote: Hi, Thanks for your build.sh -m evbearmv6hf-el release fix. I have written rpi.img to SD Card and boot it on Raspberry Pi Model B Revision 2.0 (RAM: 512MB). And I do not see any green boot message in HDMI display. Older non-FDTised rpi.img boots

Heads-up: RPI FDTisation committed

Today I've committed a bunch of changes to convert the BCM283[567] support in sys/arch/arm/broadcom to use FDT[*]. It's not perfect, but its a good step in the right direction. To the user there should be very little difference apart from - the kernel is now built as netbsd.img (and not

Re: missing break in usbioctl

On 09/01/17 15:49, sc dying wrote: It looks like case USB_REQUEST in usbioctl() of usb.c misses `break.' --- sys/dev/usb/usb.c Sun Jan 29 02:28:16 2017 +++ sys/dev/usb/usb.c Mon Aug 28 08:53:56 2017 @@ -775,6 +775,7 @@ usbioctl(dev_t devt, u_long cmd, void *d len =

Re: Ralink usb not working in Netbsd 8 (RPI2 and SUNXI)

On 08/28/17 18:29, co...@sdf.org wrote: One of the possible causes is changes in the driver itself, too. We've synced the source with the version of the code in another BSD. yeah, thinking it is probably this.. Which card is it? run0 at uhub1 port 4 run0: Ralink 802.11 n WLAN, rev

Re: USB device detection problem

On 06/25/17 11:06, Mike Pumford wrote: Just trying to fire up NetBSD 8-BETA on my builder machine but I've run into a bit of a showstopper (for me) bug in the new kernel. On NetBSD 7-STABLE (Apr 14th) my KVM is detected as: uhub6 at uhub1 port 6: , class 9/0, rev 1.10/1.00, addr 1 uhub6: 4

Re: DDB not working with USB keyboard at xhci port

On 08/21/17 14:56, sc dying wrote: On 2017/08/21 12:00, Nick Hudson wrote: On 08/16/17 06:42, sc dying wrote: When ukbd(4) is a console and connected to USB3 port, you can enter into DDB by pressing ALT+CTRL+ESC but console freezes. (on HEAD, netbsd-7, netbsd-8) xhci has two buses, sc->sc_

Re: DDB not working with USB keyboard at xhci port

On 08/22/17 17:08, sc dying wrote: On Tue, Aug 22, 2017 at 2:18 PM, Nick Hudson <sk...@netbsd.org> wrote: On 08/21/17 14:56, sc dying wrote: On 2017/08/21 12:00, Nick Hudson wrote: On 08/16/17 06:42, sc dying wrote: When ukbd(4) is a console and connected to USB3 port, you can enter in

Re: DDB not working with USB keyboard at xhci port

On 08/16/17 06:42, sc dying wrote: When ukbd(4) is a console and connected to USB3 port, you can enter into DDB by pressing ALT+CTRL+ESC but console freezes. (on HEAD, netbsd-7, netbsd-8) xhci has two buses, sc->sc_bus is for usb3 and sc->sc_bus2 is for usb2. ukbd is usually connected at

Re: re0 watchdog timeouts

On 04/26/17 11:27, Jared McNeill wrote: On Wed, 26 Apr 2017, Riccardo Mottola wrote: and I experience wired network unreliability, I get continuous watchdog timeouts, I see in dmesg: Does this patch help? Not for me on tegra Nick

Re: USB Issues in 7.1_STABLE

On 04/22/17 20:05, Gary Duzan wrote: In Message <58fb8a80.7000...@netbsd.org>, Nick Hudson <sk...@netbsd.org>wrote: =>On 04/22/17 13:57, Gary Duzan wrote: =>> Booting from the installer image, I noticed a couple of USB related =>> issues. First, the boot men

Re: USB Issues in 7.1_STABLE

On 04/22/17 13:57, Gary Duzan wrote: Booting from the installer image, I noticed a couple of USB related issues. First, the boot menu wouldn't recognize my USB keyboard; I had to hit ENTER on my PS/2 keyboard to get the boot to continue. Then the boot process stopped after probing usb1 (see

Re: xhci panic

On 01/20/17 10:56, Patrick Welche wrote: Just tried a this morning's kernel on amd64 (was looking forward to the new xhci.c :-) ), and (laptop so no serial console): xhci0 at pci4 dev 0 function 0: NEC USB3 Houst Controller (rev. 0x04) xhci0: interrupting at msi2 vec 0 uvm_fault(0x..., 0x0, 1)

Re: xhci panic

On 01/20/17 14:35, Patrick Welche wrote: On Fri, Jan 20, 2017 at 02:10:24PM +, Nick Hudson wrote: On 01/20/17 11:50, Patrick Welche wrote: On Fri, Jan 20, 2017 at 11:08:14AM +, Nick Hudson wrote: On 01/20/17 10:56, Patrick Welche wrote: Just tried a this morning's kernel on amd64

Re: xhci panic

On 01/20/17 11:50, Patrick Welche wrote: On Fri, Jan 20, 2017 at 11:08:14AM +, Nick Hudson wrote: On 01/20/17 10:56, Patrick Welche wrote: Just tried a this morning's kernel on amd64 (was looking forward to the new xhci.c :-) ), and (laptop so no serial console): xhci0 at pci4 dev 0

Re: xhci panic

On 01/20/17 10:56, Patrick Welche wrote: Just tried a this morning's kernel on amd64 (was looking forward to the new xhci.c :-) ), and (laptop so no serial console): xhci0 at pci4 dev 0 function 0: NEC USB3 Houst Controller (rev. 0x04) xhci0: interrupting at msi2 vec 0 uvm_fault(0x..., 0x0, 1)

Re: i915 hangs after 201612251500Z changes

On 01/06/17 08:44, Martin Husemann wrote: On Fri, Jan 06, 2017 at 05:06:03PM +0900, Jun Ebihara wrote: 2016-12-26 23:00 boot fine -> UTC 2016-12-26 14:00 boot fine 2016-12-27 00:00 failed -> UTC 2016-12-26 15:00 boot failed There must be something strange going on here (like cvs

Re: evbarm flist needs update for libdrm_nouveau

On 08/17/16 18:31, Michael Plass wrote: === 2 extra files in DESTDIR = Files in DESTDIR but missing from flist. File is obsolete or flist is out of date ? -- ./usr/X11R7/lib/libdrm_nouveau.so.3 ./usr/X11R7/lib/libdrm_nouveau.so.3.0 =

Re: xhci not working with urtwn

On 17-Jul-16 10:01 AM, Takahiro Hayashi wrote: Hi, The patch is generally good, but I'm confused by this part... @@ -3483,12 +3606,7 @@ xhci_device_ctrl_start(struct usbd_xfer XHCI_TRB_2_BYTES_SET(len); control = (isread ? XHCI_TRB_3_DIR_IN : 0) |

Re: umass1: failed to create xfers

On 07/06/16 21:18, Thomas Klausner wrote: I changed my sys/dev/usb sources to the ones from 20160701 and it started working again, diff attached. Nick, can you please take a look? I can't see the problem and it works for me Maybe update to HEAD and send the debug log? Thanks, Thomas

Re: Crash in xhci driver

On 06/30/16 11:56, Takahiro Hayashi wrote: On 2016/06/30 19:45, Paul Goyette wrote: Will the info be kept in a crash dump? I am modifying my set-up to just dump, instead of stopping in ddb. I think you can read - "vmstat -u usbhist -M core", but I've not tried that. Yeah, that

Re: gcc 5.4 and dhcpcd

On 06/07/16 16:44, Patrick Welche wrote: On Tue, Jun 07, 2016 at 03:28:26PM +0100, Patrick Welche wrote: (I'm doing a MKUPDATE build, and hoping that /usr/include/g++/bits/stl_alog.h:66:35: fatal error: bits/uniform_int_dist.h: No such file or directory will go away with a successful build...)

Re: umass problem with xhci (USB 3)

On 04-Jun-16 1:34 AM, Paul Goyette wrote: With a kernel built from sources dated 2016-05-29 at 23:57:35 UTC, when attaching my external hard drive (near-line backup device), I get the following messages: uhub0 at usb0: vendor 8086 xHCI Root Hub, class 9/0, rev 1.00/1.00, addr 0 ... Jun 4

Re: USB borkage lately

On 05/09/16 17:11, Michael wrote: Hello, lately I'm seeing: - communication via ulpcom is completely garbled - unreliable event delivery from a USB trackball - things like button events getting randomly dropped - unreliable communication with a USB keyboard ( things like LEDs staying on

Re: nick-nhusb merge coming soon

On 04/13/16 11:58, Dave Tyson wrote: On Wednesday 13 Apr 2016 07:59:20 Nick Hudson wrote: Hi, I think the first phase of nick-nhusb is in a state ready to be merged. I'd like to merge it in the next few days, but in the meantime I've put some kernels for testing here: http

Re: nick-nhusb merge coming soon

On 04/13/16 08:15, Paul Goyette wrote: On Wed, 13 Apr 2016, Nick Hudson wrote: Hi, I think the first phase of nick-nhusb is in a state ready to be merged. I'd like to merge it in the next few days, but in the meantime I've put some kernels for testing here: http://www.netbsd.org/~skrll

nick-nhusb merge coming soon

Hi, I think the first phase of nick-nhusb is in a state ready to be merged. I'd like to merge it in the next few days, but in the meantime I've put some kernels for testing here: http://www.netbsd.org/~skrll/nick-nhusb Please test and report success or failure. I can provide kernels to

Re: In-tree toolchain for playstation2--almost

On 04/03/16 05:50, John D. Baker wrote: With the switch of playstation2 to gcc 5.3, binutils 2.26 and gdb 7.10, I was eager to give it a whirl. A few bits remain to be fixed. First, "sys/arch/playstation2/machdep_locore.S" has comments of the form: # line +0 in the cache-management

Re: USB scanners and PR 50340

On 03/19/16 19:12, Greg Troxel wrote: Martin Husemann writes: On Sat, Mar 19, 2016 at 07:17:50PM +0200, Andreas Gustafsson wrote: I think we should disable uscanner in GENERIC now. I have been doing that on my own systems for years, as uscanner has never worked for me.

Re: USB crash with recent kernel on Raspberry Pi

On 03/01/16 12:10, Dave Tyson wrote: Been playing with the latest R-Pi snapshot posted by Jun Ebihara on port-arm. Hooked up a USB webcam and tried mplayer. I thought it might fail as I have an outstanding PR-48308 with UVC cameras and it did, but with a different crash. Camera attached OK, but

Re: root on sd0a on odroid-c1

On 02/25/16 14:34, Andrew Cagney wrote: On 22 February 2016 at 12:46, Andrew Cagney wrote: On 20 February 2016 at 17:14, Michael van Elst wrote: andrew.cag...@gmail.com (Andrew Cagney) writes: so I simply added root=sd0a to /boot/boot.ini's boot

Re: Crash on -current in pool_drain()

On 10/18/15 00:30, Paul Goyette wrote: Under heavy load, and after several hours of building packages, I am seeing the following crash. I'm doing a bisect to narrow down more, but it has been happening at least a week ago, with kernel and all modules build from sources updated on 2015-10-13 at

Re: Debugging Epiphany/Midori (webkit-gtk based) on earmv6hf (RPI 2)

On 05/31/15 18:07, Stephan wrote: Hi folks, I am currently testing some applications on the RPI 2. Some work pretty well, others not yet. As for webkit-gtk based browsers, I am experiencing crashes from time to time. One problem that occurs often seems to be related to g_dpgettext2 () from

Re: Debugging Epiphany/Midori (webkit-gtk based) on earmv6hf (RPI 2)

On 10/13/15 17:58, Stephan wrote: Breakpoint 1, 0x46213ff4 in g_dpgettext2 () from /usr/pkg/lib/libglib-2.0.so.0 (gdb) i r $r12 r120x7fffb8c8 2147465416 Breakpoint 1, 0x46213ff4 in g_dpgettext2 () from /usr/pkg/lib/libglib-2.0.so.0 (gdb) i r $r12 r120x7fffb870

Re: Build failure - amd64

On 08/21/15 10:19, Paul Goyette wrote: Christos just committed ... My build is still running (with j=1) so was not yet able to confirm. Sorry for the breakage... I'll pick this up with Taylor to see if there's a better way, e.g. a header. Nick

Re: 7.0_RC1 Raspberry Pi usb wifi

On 07/10/15 12:37, Mayuresh wrote: I have a USB wifi adapter that came bundled with a Raspberry Pi 2 and accessories package. The adapter works fine on Raspbian. It is detected as ugen0 on NetBSD 7.0_RC1 # dmesg | grep ugen ugen0 at uhub1 port 5 ugen0: Ralink 802.11 n WLAN, rev

Re: NetBSD 7.0_RC1 on Raspberry Pi 2 not SMP?

On 07/10/15 13:48, Mayuresh wrote: #uname -a NetBSD pinet 7.0_RC1 NetBSD 7.0_RC1 (RPI2.201506190427Z) evbarm sysctl shows me the following: hw.ncpu = 1 cat /proc/cpuinfo shows no output. Is the default kernel in this release not SMP or is it that SMP is not yet supported for pi? There are

Re: USB keyboard recognized during boot menu, not later

On 06/23/15 15:29, Mayuresh wrote: On Mon, Jun 22, 2015 at 07:30:42PM +, Christos Zoulas wrote: Yes, shows that we are not parsing some string properly. What does $ vmstat -u usbhist say? It prints a blank line. Should I have check that in debug mode? Also do you have options UVMHIST

Re: USB keyboard recognized during boot menu, not later

On 06/21/15 03:32, Mayuresh wrote: On Sat, Jun 20, 2015 at 09:55:14PM -0400, Christos Zoulas wrote: Do the cvs upd -r nick-nhusb in sys to get everything Here are the observations:; - Usb kbd insertion-removal-reinsertion works only on one of the three usb ports. I think the spec says 1

Re: cdce0 network - usb_block_allocmem: in interrupt context, failed

On 04/09/15 20:16, Christof Meerwald wrote: Hi, now with the cdce0 driver being loaded, I now run into a different problem after some time (maybe after an hour) of (very light) cdce0 network usage (mainly just an rlogin session to the ODROID-C1 via cdce0): usb_block_allocmem: in interrupt

Re: USB networking (cdce) with Linux host (g_ether)

On 04/07/15 20:52, Christof Meerwald wrote: On Sun, Apr 05, 2015 at 10:12:50AM +0100, Nick Hudson wrote: Can you boot with -xv flags and an updated -current kernel with USB_DEBUG and usbdebug set? I've add some more debug output to the kernel. this is the output I get when plugging in the USB

Re: USB networking (cdce) with Linux host (g_ether)

On 04/05/15 01:52, Ryo ONODERA wrote: Hi, I believe that following patch is good for us because my USB modem device is bad information and it should be treated as special case. Index: sys/dev/usb/umodem.c === RCS file:

Re: RPI build failure

On 02/17/15 08:31, Chavdar Ivanov wrote: Hi, I've been getting the following: Calculated size of `ramdisk.fs.tmp': 3145728 bytes, 621 inodes Extent size set to 4096 ramdisk.fs.tmp: 3.0MB (6144 sectors) block size 4096, fragment size 512 using 1 cylinder groups of 3.00MB, 768

Re: Bananapi - looping on boot

On 12/30/14 11:44, Frank Kardel wrote: Hi, motg0 at awinio0: OTG motg0: interrupting at irq 70 It appears to be rebooting here - my guess is that you have your power supply plugged into the OTG port and not the power socket. The power socket is on the long side in between the sata

Re: Bananapi - looping on boot

On 12/31/14 10:10, Frank Kardel wrote: Hi, Spot on - work with the other port. I was just too used to the RPI. Yeah, not quite RPI compatible... Glad it's now working. Someone(tm) should fix motg to be more forgiving. Nick

Re: raspberry pi panic 7.0_BETA after install fs resize

On 10/31/14 21:01, Petri Laakso wrote: Hi I'd got panic when doing 7.0_BETA file system resize for raspberry pi after install. I compiled system using build.sh: build.sh command:./build.sh -j4 -m evbarm -u -U release build.sh started:Fri Oct 31 20:33:32 EET 2014

Re: gcc updated to latest 4.8 branch snapshot.

On 10/15/14 17:59, Yasushi Oshima wrote: Hi, matthew green m...@eterna.com.au wrote: there appears to be no fall out, but just in case there is, i've imported the latest 4.8 branch snapshot and plan to get it updated in netbsd-7 as well. this update fixes several sh3 issues, as well as over

Re: gcc updated to latest 4.8 branch snapshot.

On 10/15/14 17:59, Yasushi Oshima wrote: Hi, matthew green m...@eterna.com.au wrote: there appears to be no fall out, but just in case there is, i've imported the latest 4.8 branch snapshot and plan to get it updated in netbsd-7 as well. this update fixes several sh3 issues, as well as over

Re: uvmfault (7.99.1/amd64)

On 09/13/14 07:55, Thomas Klausner wrote: My main machine suddenly hung last night and then rebooted. There was no big load on it at that time. dmesg contains: uvm_fault(0x810157c0, 0x8003393c8000, 1) - e fatal page fault in supervisor mode trap type 6 code 0 rip 80264fc5 cs

Re: Disassembling libraries on earmhf/Raspberry Pi

On 08/14/14 18:50, Stephan wrote: Hi, I think something is wrong with objdump when disassembling libraries on Raspberry Pi (for example objdump -d /lib/libc.so). I am using a current earmhf image. Which image do you mean here? URL? It decodes every instruction as .word 32-bit hex-value

Re: Preparation for creating netbsd-7 branch

On 07/21/14 10:25, Izumi Tsutsui wrote: skrll@ wrote: On 07/21/14 06:49, Izumi Tsutsui wrote: matt@ wrote: For the next release, core/releng should decide per current implementation: - how the default userland MACHINE_ARCH should be deteremined What do you mean by default? What (and how)

Re: RPI kernels in -current expected to work?

On 04/06/14 13:01, Frank Kardel wrote: Hi, I see a long stream of fixup: pd fixup: pde ... nothing to do lines scrolling (forever?) after the initial boot kernel messages. The boot process does not seem to make any reasonably observable progress at that point. This happens with self

Re: 6.99.32: panic when starting X

On 02/23/14 23:19, Thomas Klausner wrote: David took a closer look and told me: It has blown up in this loop reading block-tag 1.53 mrg 313:mutex_enter(usb_blk_lock); 1.1 augustss 314:/* Check for free fragments. */ 1.44 matt 315:

Re: Another 6.99.31 amd64 panic

On 02/24/14 09:38, Chavdar Ivanov wrote: Nope, same with http://nyftp.netbsd.org/pub/NetBSD-daily/HEAD/201402240050Z/amd64/binary/kernel/netbsd-GENERIC.gz ( same with slight change in the addresses ). boot device: raid0 root on raid0a dumps on raid0b root file system type: ffs

Re: 6.99.32: panic when starting X

On 02/23/14 09:41, Thomas Klausner wrote: trap type 4 code 0 rip 808dbe2c cs 8 rflags 13286 cr2 80023b989000 ilevel 0 rsp fe813ba2e9b0 trap() at netbsd:trap+0xd86 --- trap (number 4) --- usb_allocmem_flags() at netbsd:usb_allocmem_flags+0x6c can you convert

Re: evbarm ioctl DIOCGDINFO

On 09/05/13 21:29, Petri Laakso wrote: Hi I don't figure out what's wrong with my freshy built -current as some ld disk related ioctl's seems to fail. Manually extracted sets + heavily patched IMX23_OLINUXINO kernel: boot messages: root file system type: ffs WARNING: no TOD clock present