Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#15402 closed bug (fixed)

regression: KDL in "net_server" during boot for Intel I211-AT Gigabit Network using ipro1000 driver

Reported by: taos Owned by: nobody
Priority: normal Milestone: R1/beta2
Component: Drivers/Network/ipro1000 Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #15415
Platform: All

Description

After the update from hrev53379 to hrev53523 (both 64bit), I'm greeted with a KDL during boot if ipro1000 is not blacklisted:

photo of KDL booting hrev53523 without blacklisting ipro1000

Syslog is attached (booted hrev53523 with and without blacklisting ipro1000 + going back to an earlier working revision).

The components of the computer are described in #14999.

Attachments (9)

KDL_hrev53523.jpg​ (89.6 KB ) - added by taos 5 years ago.
photo of KDL booting hrev53523 without blacklisting ipro1000
syslog_hrev53523.txt​ (1.8 MB ) - added by taos 5 years ago.
syslog
KDL_hrev53536.jpg​ (554.2 KB ) - added by taos 5 years ago.
KDL booting hrev53536
KDL_hrev53538.jpg​ (94.2 KB ) - added by taos 5 years ago.
KDL with hrev_53538
syslog_hrev53555.txt​ (876.6 KB ) - added by taos 5 years ago.
syslog from hrev53555
ifconfig_hrev53555.txt​ (304 bytes ) - added by taos 5 years ago.
output of ifconfig in hrev53555
listdev_hrev53555.txt​ (4.9 KB ) - added by taos 5 years ago.
output of listdev in hrev53555
listimage_hrev53555.txt​ (45.3 KB ) - added by taos 5 years ago.
output of listimage in hrev53555
drivers_hrev53555.txt​ (1.6 KB ) - added by taos 5 years ago.
output of listimage | grep drivers in hrev53555

Change History (23)

by taos, 5 years ago

Attachment: KDL_hrev53523.jpg​ added

photo of KDL booting hrev53523 without blacklisting ipro1000

by taos, 5 years ago

Attachment: syslog_hrev53523.txt​ added

syslog

comment:1 by waddlesplash, 5 years ago

Should be fixed in hrev53536, please test.

comment:2 by taos, 5 years ago

Sorry, I still see a KDL after updating to hrev53536:

KDL booting hrev53536

by taos, 5 years ago

Attachment: KDL_hrev53536.jpg​ added

KDL booting hrev53536

comment:3 by waddlesplash, 5 years ago

OK, then try after hrev53538.

comment:4 by taos, 5 years ago

Still getting the KDL with hrev53538:

KDL with hrev_53538

It seems to happen after the last icon, the rocket(?), lights up in the boot sequence. The background changes to desktop blue and the KDL appears immediately afterwards.

I'm not sure if the unsuccessful booting is written to the syslog. Those timestamps seem to be missing.

by taos, 5 years ago

Attachment: KDL_hrev53538.jpg​ added

KDL with hrev_53538

comment:5 by waddlesplash, 5 years ago

Can you run a "dis -b 8" at the prompt and take a picture of that?

comment:6 by taos, 5 years ago

Nope. On this computer, the keyboard stops working immediately (can't even activate or de-activate the Num LED) after leaving the haiku boot menu. I can only use it again after haiku successfully reaches the desktop.

comment:7 by diver, 5 years ago

Blocking: 15415 added

comment:9 by waddlesplash, 5 years ago

That would indeed make more sense.

comment:10 by waddlesplash, 5 years ago

Change made in hrev53552; please retest after that.

comment:11 by taos, 5 years ago

Tested with hrev53555:

Marginally better, the KDL is gone :-) However, there's no network device now.

Syslog (first boot with older version in order to update to hrev53555, second boot with hrev53555, nothing blacklisted), output of listdev, listimage, listimage | grep drivers und ifconfig attached.

Version 0, edited 5 years ago by taos (next)

by taos, 5 years ago

Attachment: syslog_hrev53555.txt​ added

syslog from hrev53555

by taos, 5 years ago

Attachment: ifconfig_hrev53555.txt​ added

output of ifconfig in hrev53555

by taos, 5 years ago

Attachment: listdev_hrev53555.txt​ added

output of listdev in hrev53555

by taos, 5 years ago

Attachment: listimage_hrev53555.txt​ added

output of listimage in hrev53555

by taos, 5 years ago

Attachment: drivers_hrev53555.txt​ added

output of listimage | grep drivers in hrev53555

comment:12 by waddlesplash, 5 years ago

Resolution: → fixed
Status: new → closed

That is a separate issue; please open a new ticket for it :)

comment:13 by taos, 5 years ago

#15441 is now open :-)

comment:14 by nielx, 5 years ago

Milestone: Unscheduled → R1/beta2

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone

Note: See TracTickets for help on using tickets.