NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-i386/59396 (Kernel doesn't boot - syscall (number 5) +0x1fc returns with error)
[My most humble apologies for the previous text, I didn't know it
wasn't in plain text]
About the machine.
It has an NVIDIA Geforce Go 7300. The processor is an Intel Core 2 Duo
T5500 (I checked and it should be an amd64). Ram should be 2GB (that
is what I see from dmesg).
About the commands, I have to manually rewrite everything I see since
I don't have access to the machine, so I'll try to do my best.
I still don't know exactly how the boot process in a Unix system works
but from running 'dmesg' after the syscall error I can see that he
starts loading some drivers (I guess?), of various things (like ACPI),
and everything seems to go alright until this line:
[4.4812925] WARNING: 1 error while detecting hardware; check system log.
[4.4812925] boot device: sd0
[4.4812925] root on dk1
[4.5012926] root file system type: ffs
[4.5012926] kern.module.path=/stand/amd64/10.1/modules
[4.5012926] nouveau0: NVIDIA G72 (046700a3)
[4.5212927] nouveau0: bios: version 05.72.22.58.30
[4.5212927] nouveau0: autoconfiguration error: error: imem: unable to
map PRAMIN BAR 2: -35
[4.5212927] nouveau0: autoconfiguration error: error: imem ctor failed, -35
[4.5212927] nouveau0: autoconfiguration error: unable to create
nouveau device: 35
[4.5212927] WARNING: preposterous TOD clock time
[4.5212927] WARNING: using filesystem time
[4.5264819] WARNING: CHECK AND RESET THE DATE!
[4.6812924] panic: cnopen: no console device
[4.6812924] cpu1: Begin traceback...
[4.6812924] vpanic() at netbsd:vpanic+0x183
[...]
and then the journal goes on listing the same error I already
mentioned in the first message.
So apparently the problem seems related to the nouveau driver (I guess?).
** Tried with 'boot -c' and then 'disable nouveau', then 'exit'. Boot
starts but get stuck at:
[4.7151799] swwdog0: software watchdog initialized
and then after an eternity
[264.7352127] sd0d: error reading fsbn 64 (sd0 bn 64; cn 0 tn 2 sn 0)
It's not the first time I encountered this error. It was also showing
up on normal boots sometimes, but I just ignored it and rebooted the
machine until it worked. (in this case, even repeating the process
multiple times, it doesn't seem to be booting anyway. The trick just
works in normal boot).
Also, fun fact, when the system hangs here and I reboot the machine
(pressing down the power button and then pressing it again), if I keep
the usb stick in the same slot I get:
Disk error on boot
Operating system not found
What I need to do is use another USB slot and then it magically works again.
[UPDATE]
I just realized I was using the 'exit' command, but then I checked the
available commands in the userconf prompt and it had 'quit'. I typed
quit and it booted, And I am now seeing the installation screen. I
tried rebooting and entering a couple of times and it does indeed boot
only if I disable the nouveau driver.
[UPDATE OF THE UPDATE]
Apparently it wasn't the 'exit' or 'quit' the problem. Even with
'quit' sometimes it just hangs and the boot process halts:
[ 4.6968325] swwdog0: software watchdog initialized
[9.7468324]: BBB reset failed, TIMEOUT
[14.7468331]: BBB bulk-in clear stall failed, TIMEOUT
[19.7468334]: BBB bulk-out clear stall failed, TIMEOUT
And then it just starts repeating itself over and over until I kill it.
So apparently it's just random. I just got it to boot once and then never again.
Il giorno lun 5 mag 2025 alle ore 19:50 Mattia Rizzo via gnats
<gnats-admin%netbsd.org@localhost> ha scritto:
>
> The following reply was made to PR port-i386/59396; it has been noted by GNATS.
>
> From: Mattia Rizzo <mattia.rizzo.un%gmail.com@localhost>
> To: gnats-bugs%netbsd.org@localhost
> Cc: port-i386-maintainer%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
> gnats-admin%netbsd.org@localhost, riastradh%netbsd.org@localhost
> Subject: Re: port-i386/59396 (Kernel doesn't boot - syscall (number 5) +0x1fc
> returns with error)
> Date: Mon, 5 May 2025 19:45:15 +0200
>
> --000000000000a73ab306346711da
> Content-Type: text/plain; charset="UTF-8"
>
> About the machine.
> It has an NVIDIA Geforce Go 7300. The processor is an Intel Core 2 Duo
> T5500 (I checked and it should be an amd64). Ram should be 2GB (that is
> what I see from dmesg).
>
> About the commands, I have to manually rewrite everything I see since I
> don't have access from the machine, so I'll try to do my best.
>
> I still don't know exactly how the boot process in a Unix system works but
> from running 'dmesg' after the syscall error I can see that he starts
> loading some drivers (I guess?), of various things (like ACPI), and
> everything seems to go alright until this line:
>
> [4.4812925] WARNING: 1 error while detecting hardware; check system log.
> [4.4812925] boot device: sd0
> [4.4812925] root on dk1
> [4.5012926] root file system type: ffs
> [4.5012926] kern.module.path=/stand/amd64/10.1/modules
> [4.5012926] nouveau0: NVIDIA G72 (046700a3)
> [4.5212927] nouveau0: bios: version 05.72.22.58.30
> [4.5212927] nouveau0: autoconfiguration error: error: imem: unable to map
> PRAMIN BAR 2: -35
> [4.5212927] nouveau0: autoconfiguration error: error: imem ctor failed, -35
> [4.5212927] nouveau0: autoconfiguration error: unable to create nouveau
> device: 35
> [4.5212927] WARNING: preposterous TOD clock time
> [4.5212927] WARNING: using filesystem time
> [4.5264819] WARNING: CHECK AND RESET THE DATE!
> [4.6812924] panic: cnopen: no console device
> [4.6812924] cpu1: Begin traceback...
> [4.6812924] vpanic() at netbsd:vpanic+0x183
> [...]
>
> and then the journal goes on listing the same error I already mentioned in
> the first message.
> So apparently the problem seems related to the nouveau driver (I guess?).
>
> ** Tried with 'boot -c' and then 'disable nouveau', then 'exit'. Boot
> starts but get stuck at:
>
> [4.7151799] swwdog0: software watchdog initialized
> and then after an eternity
> [264.7352127] sd0d: error reading fsbn 64 (sd0 bn 64; cn 0 tn 2 sn 0)
>
> It's not the first time I encounter this error. It was also showing up on
> normal boots sometimes, but I just ignored it and rebooted the machine
> until it worked. (in this case, even repeating the process multiple times,
> it doesn't seem to be booting anyway. The trick just works in normal boot).
> Also, fun fact, when the system hangs here and I reboot the machine
> (pressing down the power button and then pressing it again), if I keep the
> usb stick in the same slot I get:
>
> Disk error on boot
> Operating system not found
>
> What I need to do is use another USB slot and then it magically works again.
>
> [UPDATE]
> I just realized I was using the 'exit' command, but then I checked the
> available commands in the userconf prompt and it had 'quit'. I typed quit
> and it booted, And I am now seeing the installation screen. I tried
> rebooting and entering a couple of times and it does indeed boot only if I
> disable the nouveau driver.
>
> [UPDATE OF THE UPDATE]
> Apparently it wasn't the 'exit' or 'quit' the problem. Even with 'quit'
> sometimes it just hangs and the boot process halts:
> [ 4.6968325] swwdog0: software watchdog initialized
> [9.7468324]: BBB reset failed, TIMEOUT
> [14.7468331]: BBB bulk-in clear stall failed, TIMEOUT
> [19.7468334]: BBB bulk-out clear stall failed, TIMEOUT
> And then it just starts repeating itself over and over until I kill it.
>
> So apparently it just random. I just got it to boot once and then never
> again.
>
>
>
>
>
>
> Il giorno lun 5 mag 2025 alle ore 12:57 <riastradh%netbsd.org@localhost> ha scritto:
>
> > Synopsis: Kernel doesn't boot - syscall (number 5) +0x1fc returns with
> > error
> >
> > State-Changed-From-To: open->feedback
> > State-Changed-By: riastradh%NetBSD.org@localhost
> > State-Changed-When: Mon, 05 May 2025 10:57:43 +0000
> > State-Changed-Why:
> > Sorry about that. The ddb register content here won't help, because
> > what this indicates is that the driver that was supposed to claim the
> > console didn't, so the problem happened earlier on. It may help to
> > type `dmesg' at the ddb prompt, if you can, and share the output as it
> > pages through.
> >
> > Can you describe a little more about the machine? What kind of
> > graphics hardware does it have?
> >
> > If it has AMD/ATI/Radeon or NVIDIA hardware, can you try booting into
> > userconf (boot -c) and typing `disable radeon' or `disable nouveau'?
> >
> >
> >
> >
>
> --000000000000a73ab306346711da
> Content-Type: text/html; charset="UTF-8"
> Content-Transfer-Encoding: quoted-printable
>
> <div dir=3D"ltr"><div>About the machine.</div><div>It has an NVIDIA Geforce=
> Go 7300. The processor is an Intel Core 2 Duo T5500 (I checked and it shou=
> ld be an amd64). Ram should be 2GB (that is what I see from dmesg).</div><d=
> iv><br></div><div>About the commands, I have to manually rewrite everything=
> I see since I don't have access from the machine, so I'll try to d=
> o my best.</div><div><br></div><div>I still don't know exactly how the =
> boot process in a Unix system works but from running 'dmesg' after =
> the syscall error I can see that he starts loading some drivers (I guess?),=
> of various things (like ACPI), and everything seems to go alright until th=
> is line:<br><br></div><div>[4.4812925] WARNING: 1 error while detecting har=
> dware; check system log.</div><div>[4.4812925] boot device: sd0</div><div>[=
> 4.4812925] root on dk1</div><div>[4.5012926] root file system type: ffs</di=
> v><div>[4.5012926] kern.module.path=3D/stand/amd64/10.1/modules</div><div>[=
> 4.5012926] nouveau0: NVIDIA G72 (046700a3)</div><div>[4.5212927] nouveau0: =
> bios: version 05.72.22.58.30</div><div>[4.5212927] nouveau0: autoconfigurat=
> ion error: error: imem: unable to map PRAMIN BAR 2: -35</div><div>[4.521292=
> 7] nouveau0: autoconfiguration error: error: imem ctor failed, -35</div><di=
> v>[4.5212927] nouveau0: autoconfiguration error: unable to create nouveau d=
> evice: 35</div><div>[4.5212927] WARNING: preposterous TOD clock time</div><=
> div>[4.5212927] WARNING: using filesystem time</div><div>[4.5264819] WARNIN=
> G: CHECK AND RESET THE DATE!</div><div>[4.6812924] panic: cnopen: no consol=
> e device</div><div>[4.6812924] cpu1: Begin traceback...</div><div>[4.681292=
> 4] vpanic() at netbsd:vpanic+0x183</div><div>[...]</div><div><br></div><div=
> >and then the journal goes on listing the same error I already mentioned in=
> the first message.</div><div>So apparently the problem seems related to th=
> e nouveau driver (I guess?).</div><div><br></div><div>** Tried with 'bo=
> ot -c' and then 'disable nouveau', then 'exit'. Boot st=
> arts but get stuck at:<br><br></div><div>[4.7151799] swwdog0: software watc=
> hdog initialized<br></div><div>and then after an eternity</div><div>[264.73=
> 52127] sd0d: error reading fsbn 64 (sd0 bn 64; cn 0 tn 2 sn 0)</div><div><b=
> r></div><div>It's not the first time I encounter this error. It was als=
> o showing up on normal boots sometimes, but I just ignored it and rebooted =
> the machine until it worked. (in this case, even repeating the process mult=
> iple times, it doesn't seem to be booting anyway. The trick just works =
> in normal boot).</div><div>Also, fun fact, when the system hangs here and I=
> reboot the machine (pressing down the power button and then pressing it ag=
> ain), if I keep the usb stick in the same slot I get:</div><div><br></div><=
> div>Disk error on boot</div><div>Operating system not found</div><div><br><=
> /div><div>What I need to do is use another USB slot and then it magically w=
> orks again.</div><div><br></div><div>[UPDATE]</div><div>I just realized I w=
> as using the 'exit' command, but then I checked the available comma=
> nds in the userconf prompt and it had 'quit'. I typed quit and it b=
> ooted, And I am now seeing the installation screen. I tried rebooting and e=
> ntering a couple of times and it does indeed boot only if I disable the nou=
> veau driver.<br><br></div><div>[UPDATE OF THE UPDATE]</div><div>Apparently =
> it wasn't the 'exit' or 'quit' the problem. Even with &=
> #39;quit' sometimes it just hangs and the boot process halts:</div><div=
> >[ 4.6968325] swwdog0: software watchdog initialized</div><div>[9.7468324]:=
> BBB reset failed, TIMEOUT</div><div>[14.7468331]: BBB bulk-in clear stall =
> failed, TIMEOUT</div><div>[19.7468334]: BBB bulk-out clear stall failed, TI=
> MEOUT</div><div>And then it just starts repeating itself over and over unti=
> l I kill it.</div><div><br></div><div>So apparently it just random. I just =
> got it to boot once and then never again.</div><div><br></div><div><br></di=
> v><div><br></div><div><br></div><div><br></div></div><br><div class=3D"gmai=
> l_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">Il gio=
> rno lun 5 mag 2025 alle ore 12:57 <<a href=3D"mailto:riastradh%netbsd.or@localhost=
> g">riastradh%netbsd.org@localhost</a>> ha scritto:<br></div><blockquote class=3D"g=
> mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
> ,204,204);padding-left:1ex">Synopsis: Kernel doesn't boot - syscall (nu=
> mber 5) +0x1fc returns with error<br>
> <br>
> State-Changed-From-To: open->feedback<br>
> State-Changed-By: riastradh%NetBSD.org@localhost<br>
> State-Changed-When: Mon, 05 May 2025 10:57:43 +0000<br>
> State-Changed-Why:<br>
> Sorry about that.=C2=A0 The ddb register content here won't help, becau=
> se<br>
> what this indicates is that the driver that was supposed to claim the<br>
> console didn't, so the problem happened earlier on.=C2=A0 It may help t=
> o<br>
> type `dmesg' at the ddb prompt, if you can, and share the output as it<=
> br>
> pages through.<br>
> <br>
> Can you describe a little more about the machine?=C2=A0 What kind of<br>
> graphics hardware does it have?<br>
> <br>
> If it has AMD/ATI/Radeon or NVIDIA hardware, can you try booting into<br>
> userconf (boot -c) and typing `disable radeon' or `disable nouveau'=
> ?<br>
> <br>
> <br>
> <br>
> </blockquote></div>
>
> --000000000000a73ab306346711da--
>
Home |
Main Index |
Thread Index |
Old Index