#11210 closed bug (fixed)
Kernel panic with Intel Gigabit CT Desktop Adapter
Reported by: | gunnarbeutner | Owned by: | korli |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Network/ipro1000 | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
While booting the nightly snapshot hrev47826 I get a kernel panic. See the attached photo for details.
When I physically remove the NIC I can boot the system without any problems.
The PCI ID for the adapter is 8086, a01f.
Attachments (1)
Change History (11)
by , 10 years ago
Attachment: | haiku-ipro1000-lq.jpg added |
---|
comment:1 by , 10 years ago
Component: | Network & Internet → Drivers/Network/ipro1000 |
---|---|
Description: | modified (diff) |
Keywords: | ipro1000 removed |
Platform: | x86-64 → All |
comment:2 by , 10 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 10 years ago
In context of MSI-X interrupts, the interrupt handling code in ipro1000 doesn't use filters. Defining an empty HAIKU_CHECK_DISABLE_INTERRUPTS() in glue.c might be enough to fix the problem, because each received interrupt is surely ours.
Please try in src/add-ons/kernel/drivers/network/ipro1000/dev/e1000/glue.c:
int HAIKU_CHECK_DISABLE_INTERRUPTS(device_t dev) { return 1; }
and remove "NO_HAIKU_CHECK_DISABLE_INTERRUPTS();" at line 9
comment:4 by , 10 years ago
I'll see if I can get a Haiku build environment set up somewhere. This will probably have to wait until the weekend though.
comment:5 by , 10 years ago
Blocking: | 7665 added |
---|
comment:9 by , 7 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Probably fixed in hrev51563.
comment:10 by , 6 years ago
Blocking: | 7665 removed |
---|
Kernel panic / stacktrace