netbsd:breakpoint+0x5: leave
Does anyone have any suggestions about what to try next? Does anyone want
to have a look around themselves?
Thanks,
John Klos
Hi,
Here are the pcidumps from both the working mfii0 and mfii0 after warm reboot:
https://www.klos.com/~john/pcidump_raid.txt
https://www.klos.com/~john/pcidump_noraid.txt
This is what's different:
3c3
< 0x00: 0x005b1000 0x0010 0x01040003 0x
---
0x00: 0x005b1000
Hi,
I don't know exactly how I sent an email with absolutely no "From:" (I
have an idea, but I probably couldn't do it again if I tried), but that
was me, if anyone wants to reply.
Thanks,
John
Hi,
Here's a nice issue :)
Plug in ure* USB ethernet to amd64 machine running NetBSD-current
(9.99.99, 22-August-2022):
[ 1791670.446266] ure0 at uhub8 port 4
[ 1791670.446266] ure0: Realtek (0x0bda) USB 10/100/1000 LAN (0x8153), rev
2.10/30.00, addr 6
[ 1791670.446266] ure0: RTL8153 ver
Hi, all,
It has been ages since I've used floppies in NetBSD very much, but
checking the man page, different slice letters are used to indicate disk
densities. From fdc(4):
The driver supports the following floppy diskette formats by using
particular partitions:
1.44MB
I saw almost the same situation. To recover from the error, I had to
power-down the machine, unplug the battery, keep a few minutes, plug the
battery and power-up again.
I committed the change yesterday. I guess that it fixes kern/55192 and
kern/56669.
My machine is only 2500 km away, but
Hi,
It also might be relevant to note which port you're running. It must
be capable of having re and wm interfaces, since you name them, but
that still includes a fair bit.
I still see no statement which port(s) you're running...
Here my brain equated port with ethernet, not with NetBSD
> On NetBSD 8, 9, current, [...] Stop darkstat. Machine locks.
> [...] in case anyone can imagine how and why a complete system lockup
> could happen as the result of an interface being used in promiscuous
> mode for long periods of time (and not when used that way for short
> periods of time.
So here's an interesting problem:
On NetBSD 8, 9, current, with both ipfilter and with npf, with different
kinds of ethernet interfaces (re*, wm*), run pkgsrc/net/darkstat. Pass a
lot of traffic (like a week's worth of Internet traffic). Stop darkstat.
Machine locks.
I've only recently been
the kernel
remotely :(
All three of these machines have much older IDE, so I'm wondering what in
NetBSD changed that may've have caused this.
Soon I'll be back and will have access to the Quadra and Jornada, and I'm
open to suggestions about which commits to examine and to test.
Thanks,
John
I erroneously thought that if pseudo-device crypto wasn't in the kernel,
crypto would be done in userland. That's not the case:
What makes you think crypto isn't being done in userland?
Just a bad guess that the reason for pseudo-device crypto was to do some
things in the kernel.
The
cept perhaps special cases?
John Klos
Any thoughts about what's going on here? Is this because the drives are 512e
drives? Three weeks is a LONG time to reconstruct.
So this turns out to be a failing drive. SMART doesn't show it's failing,
but the one that's failing defaults to having the write cache off, and
turning it on
r second, while reconstructing.
Any thoughts about what's going on here? Is this because the drives are
512e drives? Three weeks is a LONG time to reconstruct.
This is observed on NetBSD 9.99.68 on both i386 and on aarch64.
Thanks,
John Klos
I've had the same NetBSD 9.0/amd64, compiled from 22-Feb sources, system
panic twice while trying to run the same workload, which is just fetching
many static files via command-like ftp continuously. This appears to be
resproducible since both panics happened within an hour of starting the
It looks like two of the Dell machines I use have BIOS updates that
include the new microcode, but I don't know when it'll be available for
the other machines I use. The standalone microcode update at
https://downloadcenter.intel.com/download/27337/Linux-Processor-Microcode-Data-File
is dated
Hi,
I have a 2 TB drive connected via USB to a Raspberry Pi 2 which is running
netbsd-8. I tried five times, unsuccessfully, to copy a 200 gigabyte file
via scp to the drive. Each time the Pi locked up, either while just
copying or while doing things in other ssh sessions. It seemed to
I have an amd64 machine running netbsd-7 from 6-August-2015 which
does common hosting (email, web, DNS), IPv6 tunnels and NAT,
amongst other things. It paniced like this a few weeks ago when it had
been running netbsd-7 from March, but otherwise it's been problem free.
Any thoughts or ideas
gigabit cards?
Thanks,
John Klos
(multicast) returned 2
sysctl_createv: sysctl_locate(multicast_kludge) returned 2
John Klos
Parity Re-write is 79% complete.
OK, so this is really more about how parity checking works than
anything else (i guess.)
for RAID1, it reads both disks and compares them, and if one
fails it will write the master data. (more generally, it
reads all disks and if anything fails parity check it
If the state of the RAID is not being maintained, then that's a bug,
and needs to be fixed right away. To my knowledge, however, it does
maintain things correctly. Feel free to file a PR with the specifics
of any failures in this regard...
I will test this via a clean install and create a PR
Hi,
After setting up a RAID-1 mirror with RAIDframe in netbsd-6 (compiled
from yesterday's tree), I'm seeing strange disk issues. The initial mirror
was set up and was initializing while the system was booted off of the
install kernel and both drives (wd0 and wd1) were writing at around 110
what does raidctl -s and -m (separate commands) say?
raidctl -s raid0
Components:
/dev/wd0a: optimal
/dev/wd1a: optimal
No spares.
Component label for /dev/wd0a:
Row: 0, Column: 0, Num Rows: 1, Num Columns: 2
Version: 2, Serial Number: 2013090100, Mod Counter: 75
Is this a NetBSD issue, or something else?
load averages: 7.99, 7.94, 7.91; up 0+21:43:0721:25:56
34 processes: 2 runnable, 24 sleeping, 8 on CPU
CPU0 states: 0.0% user, 100% nice, 0.0% system, 0.0% interrupt, 0.0% idle
CPU1 states: 0.0% user, 100% nice, 0.0%
Hi, all,
Is there any support for the Areca 1880, be it in -current or someone's
not-yet-checked-in tree?
Thanks,
John Klos
: interrupting at ioapic0 pin 17
ehci0: dropped intr workaround enabled
ehci0: BIOS has given up ownership
ehci0: EHCI version 1.0
ehci0: companion controllers, 3 ports each: ohci0 ohci1
...
Thanks,
John Klos
How old is your kernel ? I've had strange issues with ahci and
interrupts on some machines, and a fix (or rather a workaround) for this
has just been pulled up to netbsd-5. It could be your problem as well ...
I had been trying 5.0.2 because I had to keep reinstalling, but I'll try a
new
Hi,
I'm not sure if this a problem with the motherboard I'm using or with
NetBSD, but here goes anyway. I have an MSI MS-7511 amd64 motherboard
which has a form of hardware RAID on the motherboard. However, after using
it for a few minutes, the machine locks up HARD. I can't get into the
29 matches
Mail list logo
